Update on the NISO Standard Tag Set Suite (STS)...

Update on the NISO Standard Tag Set Suite (STS) Project

Publishing for Standards Professionals Workshop:Typefi User Conference, 17 March 2016

Bruce RosenblumCEO, Inera, Inc.

Co-chair, NISO STS Working Group

Remember When…

Copyright 2006 Inera Incorporated. All Rights Reserved

Standardization & Interchange

• Euro – Lowered economic barriers– Eased travel between countries

• Standards increase– Interoperability– Economic opportunity

• Standards for standards– Aid production– Facilitate interchange– Promote interoperability– Create new publication opportunities

A Quick History on ISO STS

• ISO Goals: – Improve ISO publication process– Output in many formats: PDF, HTML or EPUB– Create change documents (redlines)– See: Rosenblum, B. Standards Engineering, Vol. 65,

No. 6, November/December 2013• Worked with consultant

– Reviewed existing XML standards for documents• DITA, DocBook, JATS, TEI

– JATS selected for foundation– Modified JATS to STS for Standards

JATS ISOSTS

• Based on JATS version 0.4• Added:

– New top-level element <standard>– Standards-specific metadata elements

• iso-meta, reg-meta, nat-meta

– TBX (ISO 30042:2008) terms and definitions model– Elements to cite other standards

ISOSTS in Public

• ISO posted to public Website – http://www.iso.org/schema/isosts/ – DTD, Documentation, other resources– Available for other standards developers

• But what is this “JATS” on which it’s based?

JATS Origins, circa 2001

• e-Publication Problems– Long-term (100+ year) archive of e-only journals– Interchange & distribution– Publisher distributor/host/metadata index

• Goals– Common model of semantic expression– Scholarly e-journal article archive and interchange– Cover all disciplines (science, engineering, social

sciences, humanities)

JATS Background

• Basis– Mellon Foundation funded DTD Feasibility Study– https://old.diglib.org/preserve/hadtdfs.pdf

• Funding– National Library of Medicine– Mellon Foundation

Why JATS Foundation for STS?

• Standards & journal articles share structures– Sections– Tables– Figures– Equations– Bibliography

• Well-developed and well-tested model• Easily modifiable for Standards use• Strong third party support

JATS Release History

• NLM 1.0: released April 2003• NLM 2.0: released December 2004• NLM 2.3: released March 2007• NLM 3.0: released November 2008• Moved to NISO, renamed JATS: July 2009• First JATS-Con: November 2010• ANSI NISO Z39.96 JATS 1.0: released August 2012• BITS 1.0: released December 2013• ANSI NISO Z39.96 JATS 1.1: released January 2016

Why Create NISO STS?

• ISO STS has been:– Successful for ISO and NSBs– Too limited for other standards bodies

• NISO STS will provide:– A stable standard for most standards publishers– Guidance to tool and conversion vendors– A common format for sharing

• Metadata• Full text

– Common XML model across pubs (standards, journals)• Lower barrier to entry for XML publication

Working Group Formation

• Call for participation, August 2015• Large global interest

– SDO’s, NSB’s– Suppliers, Vendors, Consultants

• Some joined NISO specifically for STS project• Almost 50 members from > 30 organizations• Too large for one group

– Steering group– Technical group

NISO STS Steering Committee

Kim Breitfelder, IEEEJo Collins, NENKeith Doubleday, IHS GlobalBecky Fadik, SAE InternationalLaurent Galichet, ISOLinda Guard, U.S. Pharmacopeial ConventionDebbie Lapeyre, Mulberry Technologies, Inc.*Eamonn Neylon, Signal ArcGareth Oakes, Global Publishing SolutionsEvan Owens, Cenveo Publisher Services*Markus Plessel, IEEETim Preuss, Silverchair Information SystemsKaren Reczek, NISTAntti Saari, SFS

* JATS & BITS Working Group Members

Ivan Salcedo, BSIAl Sanders, Boeing, Greg Saunders, , OASD-R&EBrian Trombley, DCLB. Tommie Usdin, Mulberry Technologies, Inc.*Mike Visser, Thomson ReutersLesley West, ASTM Cord Wischhöfer, DINElizabeth Wolf, Copyright Clearance CenterHong Xu, CENWei Zhao, Ontario Council of University LibrariesObservers:Anja Bielfeld , IECGeorge Gulla, ANSIBob Hager, ANSI

Co-chairsBruce Rosenblum, Inera Inc.*

Robert Wheeler, ASMEWorking Group Members

NISO STS Technical Committee

Matt Brown, BSIHeather Flanagan, IETFLaurent Galichet, ISOHoward Gilson, ASTMFrans Gooskens, NENVinay Gupta, Edaptive Technologies LLCBob Hollowell, ASMEGerrit Imsieke, le-tex Publishing Services

* JATS & BITS Working Group Members

Serge Juillerat, ISODebbie Lapeyre, Mulberry Technologies, Inc.*Nikos Markantonatos, Atypon Systems Inc.*Mary McRae, Dartmouth Journal Services*Ken Rawson, IEEEB. Tommie Usdin, Mulberry Technologies, Inc.*David Winchell, XSB Inc.Observer:Bob Dreyfuss, Consultant

Co-chairsBruce Rosenblum, Inera Inc.*

Robert Wheeler, ASMEWorking Group Members

NISO STS Goals

• Expand for SDO and other use beyond NSBs• Align with JATS 1.1 and future versions• Support additional structures

– Indexes– CALS tables

• Maintain backwards compatibility for existing users of ISO STS

NISO STS Development Plan

• Multi-phase project• Phase 1

– Modest extensions for normative SDO standards

• Future phases may address– Non-normative documents

• consider BITS

– Dual-language standards – Historical standards

Sub-Groups STS (1)

• SDO Metadata– SDO-specific metadata– Co-developed or Co-published standards

• Citing Standards– Normative references– Inline citations– DOI links

• Terms and Definitions– TBX– Other models

Sub-Groups STS (2)

• Translations– Metadata– Marking added or removed text

• Section types– Standard attributes to define standard sections– e.g. foreword, intro, scope, terms

Key Decisions To-Date (1)

• All reasonable efforts to make NISO STS 1.0 backwards compatible with ISOSTS

• Phase I will be designed for publishing cases that are structurally similar to ISO standards

• Phase I will consider only normativedocuments, but does not preclude use with non-normative documents

• Phase I will model current content, but does not preclude tagging of back-content

Key Decisions To-Date (2)

• The model will focus on requirements of published documents. It will not focus on the needs of XML authoring or production

• Phase I will not consider formatting, branding, and publisher-specific look-and-feel

• The XML model will be available in DTD, XSD, and RelaxNG formats

• NISO STS will be based on JATS 1.1 Publishing, not JATS 1.1 Archiving to facilitate interchange

Additions

• The BITS models for Indexes and Tables of Contents

• Notes-group wrapper• Xinclude

Likely Extensions

• DOI support– Metadata– In-text citations– Normative reference list and bibliography

• Metadata element to hold SDO-specific metadata

• Second terms and definitions model, beyond TBX, for simple T&D markup

Why Set Suite?

• Separate models will be available with MathML2 and MathML3 for compatibility

• Separate models will be available with XHTML tables, and with XHTML and CALS tables– “Interchange” — XHTML-only– “Production” — XHTML and CALS

• Four models total:XHTML+MathML2 XHTML+CALS+MathML2

XHTML+MathML3 XHTML+CALS+MathML3

JATS/BITS/STS Alignment

• JATS & BITS: informally aligned• JATS & STS: 4 years without alignment

– <version> resolved– <pub-date> open issue– <std> open issue– <title-group> BITS “fixed” for 2.0

• Future challenge: JATS/BITS/STS Alignment– Messages between groups– Working group member overlap

NISO STS Timeline

• Timeline– Monthly steering group calls– Monthly technical group calls– Sub-group calls as necessary– Committee draft summer 2016– At vote no later than April 2017

• Future– Possible future phases– Address out-of-scope phase 1 items

STS Adopters

– API (2)– ASI (Austria) (1)– ASCE (1)*– ASME (2)– ASTM (2)– BSI (2)– CEN (1)– DIN (2)– DS (2)

Adopted (1)/Adopting (2)/Considering (3)ISOSTS or JATS-based*

– IEEE (1)*– ISO (1)– NEN (1)– SA (2)– SAE (1)*– SFS (1)– SIS (3)– Standards Norway (1)– U.S. DoD (3)

STS Benefits: New Workflows

• Streamline production workflows– Greater automation– Pre-publication content validation

• Reduce time to publish• Improved tools

– more innovative tools available because of increased market size

– less customization needed from publishing vendors

• Lower costs from production vendors

STS Benefits: New Products

• Easier production of HTML, ePub, Mobile• Develop new products

– e.g. ISO Online Browsing Platform • Aids when multiple standards are used across an

enterprise or for a single project;• Co-publish standards • Interchange with distributor partners• Inter-standard linking

– Click-through linking– Digital Object Identifiers (DOIs)

STS Benefits: Adoption

• Consistent metadata delivery to distribution partners

• Site-crawling indexers benefit from consistencies

• Encourage adoption with industry users that are publishing internal standards

STS Benefits: Discovery

• Deliver products to preferred customer devices• Improve end-user information discovery

– Consistent metadata aids library discovery– Improved library management

• Tips and Tricks of Incorporating Industry Standards into a Library, Charleston Conference 2015

• http://schd.ws/hosted_files/2015charlestonconference/d7/Tips%20and%20Tricks%20of%20Incorporating%20Industry%20Standards%20into%20a%20Library%20Collection_Abbott_04Nov15.pdf

How STS Can Impact Your Business?

• That’s up to you• STS provides an enabling technology

– Updated workflow– New products– Common platform for vendors– Greater interoperability

• STS does not drive your business decisions– Business requirements drive technology decisions;

not vice versa

Follow NISO STS Developments

• http://www.niso.org/workrooms/sts/

Conclusions

• ISO STS has been successful for ISO and NSBs• NISO STS expands STS for SDO needs• Benefits of using a standard XML model

– Production efficiencies– New product opportunities– Easier interchange with development and

distribution partners

Contact Us

• Bruce Rosenblum– brosenblum@inera.com

• Robert Wheeler– WheelerR@asme.org