DocBook

DocBook is a general purpose XML schema particularly well suited to books and papers about computer hardware and software (though it is by no means limited to these applications). DocBook has been under active maintenance for more than 20 years,; it began life as an SGML document type definition. Because it is a large and robust schema, and because its main structures correspond to the general notion of what constitutes a “book,” DocBook has been adopted by a large and growing community of authors writing books of all kinds. DocBook is supported “out of the box” by a number of commercial tools, and there is rapidly expanding support for it in a number of free software environments. These features have combined to make DocBook a generally easy to understand, widely useful, and very popular schema. Dozens of organizations are using DocBook for millions of pages of documentation, in various print and online formats, worldwide.

“Be in the Room Where It Happens”

Institutions such as Portico that are engaged in ensuring that the digital record of our time is accessible, usable, discoverable, and verifiable for the very long term continually face the challenge of processing and managing content at very large scales, often with minimal, and sometimes diminishing, resources to accomplish the task. A key resource in meeting the challenge of preserving born-digital and digitized scholarly literature has been the NLM and JATS standards, and the community of practice centered on those standards. We will be talking about our shared experience in developing those standards: what motivated our participation, what benefits we have seen, and what challenges we still face.

JATS/BITS/NISO STS

The Journal Article Tag Suite is an application of NISO Z39.96-2015, which defines a set of XML elements and attributes for tagging journal articles. BITS, the Book Interchange Tag Suite, and NISO STS, the NISO Standards Tag Suite, are applications of NISO Z39.96-2015 for books and standards. All of the models share a common foundation, customized to meet the needs of specific document types.

DITA

DITA, the OASIS Darwin Information Typing Architecture, is an XML-based specification for modular and extensible topic-based information. DITA is specializable, which allows for the introduction of specific semantics for specific purposes without increasing the size of other DTDs, and which allows the inheritance of shared design and behavior and interchangeability with unspecialized content.

Organizational and Funding Options for Markup Vocabulary Creation and Maintenance

There are many ways to create a markup vocabulary and many forums in which it can be done. Creating and maintaining markup vocabularies requires significant ongoing volunteer time and effort, significant funding, or both. In light of this, it often makes sense for a multi-institution group to undertake the creation and management process, particularly when interchange is a goal. The community has examples of this consensus model, such as the TEI (which was created by a grant-supported project and is maintained by a consortium created for the purpose) and the STS (which was originally a derivative of JATS, further developed by ISO, and then donated to NISO for the establishment of consensus and for maintenance). Selection of an organizational home and source of funding can have marked effects on vocabularies. The organizational structure affects representation, who has a voice in the process, intellectual property concerns (e.g., patents, copyrights, other standards), and decision making policies. Costs involved in creating and maintaining markup vocabularies begin at conception and continue through development into maintenance and promotion. These costs include editing, hosting, publishing and distribution, and management of the standards process. Real-world examples of the organization and funding of successful markup vocabularies will provide patterns others may find useful.

The Universal Business Language ecosystem and the OASIS TC process

A rich worldwide ecosystem has grown around the freely-available Universal Business Language (UBL) standard for 81 business documents such as purchase orders, invoices, waybills, etc., and 4600 semantic business objects expressed in those business documents The UBL development committee was formed in 2001 as a technical committee in OASIS (the Organization for the Advancement of Structured Information Standards) under a strict set of transparency rules supported by a rich set of collaborative tools with which the committee members have created both normative and non-normative work products. For UBL, normative XML schemas and non-normative JSON schemas are examples of both of these kinds of work products, specified for user communities to leverage in their communication environments for electronic business solutions. Solutions built on a foundation of open standards are attractive to large ecosystems of developers and end users working towards shared objectives. To be truly open, the development and deployment of such a specification must address three critically important issues: governance, transparency and availability. UBL was developed under the governance of the OASIS Technical Committee Process, working with a tool set that is available to any community wanting to create a markup vocabulary. OASIS, a membership organization, fosters the successful development of work products by its members participating in its technical committees. And so it is important to look into the detail of these two perspectives of UBL: how UBL is best deployed within the ecosystem due to its magnitude, and how UBL is governed and maintained during the development process. Illustrated by UBL, when considering where to bring together participants developing new open vocabulary ecosystems, OASIS with its TC process should be a front-runner in your consideration of a positive and productive environment for building team results.

Transcending structure: Applying shared markup vocabularies with your friends and enemies

Markup makes it easier to share. We share documents with our peers, our partners, and even our competitors. Communities of interest form, they define document structures, test them in practice, and affirm them by adoption. Joining a community has obvious advantages: reduced development costs, ease of interchange, tried and tested tools, and an available pool of authors, editors, and developers already familiar with the vocabulary. Over time, the pace of vocabulary evolution slows naturally. The major structures are developed, applied, tested, and accepted. New structures are added more slowly, and more reluctantly. The community has transitioned into maintenance mode where large scale refactorings and backwards-incompatible changes are known to have burdonsome costs and “best practices” are known to make sharing easier. What can the “Markup Community in General” do to support these stricter best practices communities?

Structural Metadata & Standardization Failures: Just a Little Bit of History Repeating

The design of the Extensible Markup Language has placed a premium on modularity and promoting the re-use and inter-mixture of pre-existing tag sets in the service of new goals. While this design tends to promote standardization, it clearly does not guarantee it, as the multiplicity of competing XML languages for rights expression or word processing demonstrates. This paper examines the history and evolution of structural metadata standards within the digital library community to help identify factors leading to production of multiple markup languages competing for similar or identical ecological niches.

TEI

TEI, the Text Encoding Initiative, was founded in 1987 to develop guidelines for encoding machine-readable texts of interest to the humanities and social sciences. The Text Encoding Initiative (TEI) is a text-centric community of practice in the academic field of digital humanities, operating continuously since the 1980s. The community currently runs a mailing list, meetings and conference series, and maintains an eponymous technical standard, a journal, a wiki, a GitHub repository and a toolchain. The TEI Guidelines, which collectively define an XML format, are the defining output of the community of practice. The format differs from other well-known open formats for text (such as HTML and OpenDocument) in that it’s primarily semantic rather than presentational.