[jats-list] Downstream non-publishing use of JATS XML

["G. Ken Holman g.ken.holman@xxxxxxxxx" <jats-list-service@xxxxxxxxxxxxxxxxxxxxxx>]

In my conference contribution I talk about how a NISO-STS/JATS 
document can be seeded with semantic markup using a taxonomy 
identifying components of an ontology.

https://www.ncbi.nlm.nih.gov/books/NBK556169/

In the presented example the semantic markup is not visible in the 
resulting publication. The XML is processed downstream where 
<named-content> element are extracted, massaged, and imported into a 
requirements management system. This can be very helpful for 
conformance checking and tracking.

I was hoping to ask the audience during the QA session of where I can 
find other examples of JATS semantic markup being used downstream and 
independent of the publishing process. Not to denigrate the important 
publishing process, that still has to happen and is the primary 
output ... I'm asking about additional benefits of being able to 
exploit the XML for non-publishing processes after the publishing has 
been addressed.

I see this as a critical benefit of having chosen to use XML in 
general and JATS in particular.

When XML has to compete with other publishing solutions, XML has the 
edge with the ability to leverage the one input to multiple different 
kinds of results, not just different appearances.

. . . . . Ken

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