Dear fellow standard professionals,
As presented at the NISO STS event today: In April, some of us launched
an initiative to further enhance interoperability of NISO STS. As we
have heard again today, NISO STS is an enabling rather than a
prescriptive technology, and therefore it leaves you a lot of wiggle
room on how to actually mark up your content. We also heard today that
it might be desirable, particularly in adoption scenarios, to define
further constraints that go beyond what the DTD allows in order to
reduce ambiguity or manual inspection/mapping of incoming content,
thereby increasing interoperability. We foresee these extra checking
rules to be bundled in checking profiles, where we will focus on a
baseline interoperability profile that might include both ISO’s existing
rules and newly written, NISO-STS-specific rules.
In addition, we think it might help XML professionals within SDOs or at
vendors to have access to a readily available, customizable NISO STS
renderer, like the one that ISO made available for ISO STS.
We are providing both, XSLT rendering code and Schematron checking code,
in the Github repository https://github.com/sts4i/sts4i-tools
ISO’s existing XSLT and Schematron files are included here, too, and the
whole thing is being made available under an Apache 2.0 license which
permits commercial use.
There is another repository that holds sample NISO STS content:
https://github.com/sts4i/sample-documents
The copyright holders have agreed to make the (superseded) standard DIN
EN ISO 13849-1:2008-12 available as NISO STS XML. This standard covers a
interesting NISO STS features such as nested adoptions where each layer
uses <std-meta>, multiple IDs per object, etc.
Caveat: The NISO STS file contains what currently comes out of the DIN
legacy XML → NISO STS converter. There might still be some rough edges.
The sample document is using TBX for terminology; I’ll add a
term-display variant soon, and we will add other sample content, too.
This is only a first shot at it, and it is far from production-grade,
coverage-complete, mutually-accepted, etc.
Even if you are not an XML developer, you can still file Github issues
for the conversion code, the checking rules, and the sample content markup.
Looking forward to your feedback and participation.
—Gerrit
--
Gerrit Imsieke
Geschäftsführer / Managing Director
le-tex publishing services GmbH
Weissenfelser Str. 84, 04229 Leipzig, Germany
Phone +49 341 355356 110, Fax +49 341 355356 510
gerrit.imsieke@xxxxxxxxx, http://www.le-tex.de
Registergericht / Commercial Register: Amtsgericht Leipzig
Registernummer / Registration Number: HRB 24930
Geschäftsführer: Gerrit Imsieke, Svea Jelonek,
Thomas Schmidt, Dr. Reinhard Vöckler
------------------------------------------------------------------------------
Meet us at Frankfurt Book Fair
Hall 4.2, L 72.
More at https://www.le-tex.de/en/buchmesse.html