Re: [xml-dev] Please stop writing specifications that cannot be parsed/p

["G. Ken Holman" <gkholman@CraneSoftwrights.com>]

Indeed, Michael, the fact the XML standards were 
written in XML allowed me to populate most of my 
two books just by massaging the standardized 
content. I then used my own books as reference 
material when writing the rest of the book 
content because the indexes and annexes all were 
hyperlinked to the specification sources.

But the guys/gals clicking on the word processor 
icon to write an industrial washing machine 
safety standard likely are not prepared to invent something new.

And my company has an OEM, 
https://standardsdigital.com/ who services 
national standards bodies (NSBs) who are 
implementing https://fontoxml.com/ with the look 
and feel of a word processor in a browser yet 
create NISO STS XML. Our company provides a 
publishing API so that the tool can send the 
content to our server and get back in short order 
the formatted results for review by the author in real time.

So, again, I think the issue is awareness. The 
technology is there to help a wide spectrum of 
users. It is just a matter of getting NSBs and 
SDOs to embrace the technology by showing their 
users the downstream benefits of authoring in XML.

I would also point out that Sean McGrath's 
company, https://propylon.com/ is looking 
specifically at requirements tracking, 
specifically in the area of detecting changing 
requirements in the life cycle of published standards.

Lots going on ... just need to spread the word.

. . . . . . Ken

At 2023-05-26 01:03 +0100, Michael Kay wrote:

> >no-one has to invent something new to get what you are asking for
>
> But if you're prepared to invent something new 
> then you can probably do better...
>
> For example, the XPath function library is 
> defined in an XML document that contains all the 
> function signatures in a custom vocabulary 
> reflecting the object model for XPath functions, 
> and that data is extremely useful; it can be 
> used for example to create the data used by a 
> type-checker. I'm sure there are cases where an 
> XML format can be standardised across a wide 
> range of specifications (for example, a format 
> for defining BNF grammars) but I'm sure that 
> highly specialised custom formats also have a role to play.
>
> Of course in our own community we're very 
> prepared to eat our own dogfood in this way. 
> Getting people to use a similar approach when 
> they're writing safety standards for industrial 
> washing machines is a different kettle of fish. 
> Those guys just click on the word processor icon and start typing.
>
> Michael Kay
> Saxonica
>
>
>
> > On 26 May 2023, at 00:20, G. Ken Holman 
> <gkholman@CraneSoftwrights.com> wrote:
> >
> > Roger, already standards from ISO and CEN are 
> being published in NISO STS XML:
> >
> > https://www.niso-sts.org/
> >
> > And there some SDOs (Standards Development 
> Organizations) that are building requirements 
> into their STS XML so they can be harvested 
> downstream after publishing by requirements 
> management software tracking, for example, "may", "shall", "should", etc.:
> >
> > https://www.ncbi.nlm.nih.gov/books/NBK556169/#holman-semantics2
> >
> > I commend that paper I wrote regarding the 
> identification of semantics (say, of requirements) in standards content.
> >
> > I've co-founded a company in Ireland that is 
> servicing the standards development community 
> of SDOs with software that is publishing these 
> richly-encoded XML documents into PDF, HTML, and DOCX:
> >
> > https://RealtaOnline.com
> >
> > Moreover, SDOs are looking to us to enrich 
> their XML and we are experimenting with AI in this regard. Exciting stuff.
> >
> > I'm delivering a presentation at JATS-Con 
> 2023 you may wish to attend to learn more about 
> how Réalta Online is using standards such as 
> XSLT and XSL-FO to enrich and publish standards 
> with fidelity across output products:
> >
> > https://jats.nlm.nih.gov/jats-con/2023/schedule2023a.html#1-1145
> >
> > So I think all that is needed is an awareness 
> campaign to make standards writers and SDOs 
> aware that the technology exists already. We 
> don't have to wait to be able to do what it is 
> you are asking. It just has to be done with the tools at hand.
> >
> > And not just for ISO and CEN standards. 
> Hundreds of SDOs exist out there publishing 
> thousands of standards documents. Please spread 
> the word about NISO STS XML and the leverage 
> they can get by adopting something that exists 
> ... no-one has to invent something new to get what you are asking for.
> >
> > I hope this is helpful.
> >
> > . . . . . . . Ken
> >
> > At 2023-05-25 19:57 +0000, Roger L Costello wrote:
> >> Dear Specification Writer,
> >>
> >> Please stop writing specifications that 
> cannot be parsed/processed by software. Please 
> stop formatting your specifications as Word and 
> PDF. Instead, use a format that is amenable to 
> machine processing. The XML format is ideal. We 
> want to analyze your specifications. We don't 
> want to spend dozens of hours screen-scraping your Word/PDF documents.
> >>
> >> If you simply must persist in writing 
> Word/PDF documents, then please write in a 
> consistent way so that we can screen-scrape 
> without having to write special case code. To 
> illustrate, in one of your specifications you 
> provide a bunch of tables with data; each table 
> has many rows. In some tables you reference a 
> note. Here's a row with a note reference:
> >>
> >> 119 Approach Route (1) Note 1 5.7
> >>
> >> Here's another row with a note reference:
> >>
> >> 52 SID Ident (1) (Note 1) 5.78
> >>
> >> Why did you embed Note 1 within parentheses 
> in the second case but not the first? That's an 
> example of not being consistent. Such 
> inconsistencies make it difficult to do 
> screen-scraping. Please be consistent. If at 
> all possible, write a parser to parse the data 
> that you embed in your specification. This will 
> immediately inform you of any inconsistencies.
> >>
> >> Thank you,
> >> From the people who must read, understand, and analyze your specifications
> >>

--
Contact info, blog, articles, etc. http://www.CraneSoftwrights.com/x/ |
Check our site for free XML, XSLT, XSL-FO and UBL developer resources |
Streaming hands-on XSLT/XPath 2 training class @US$125 (5 hours free) |
Essays (UBL, XML, etc.) http://www.linkedin.com/today/author/gkholman |