JATS-Con 2023 Schedule with Abstracts

Welcome and Introductions

JATS and Public Access: It's more than just a footnote

Jeffrey Beck, NCBI/NLM/NIH

Materials | Video

Digital Transformation Driven By JATS, BITS, and NISO STS

Mandy May, Association for Materials Protection and Performance
Brian Trombley, Ariza Content Solutions
Nate Lavigne, Association for Materials Protection and Performance

For many years professional societies and associations have been investing in digital transformation on both the publishing side and the membership side. Many large societies and associations have made substantial investments in these efforts over the years, but many small and mid-sized organizations have lagged behind.

This paper demonstrates how The Association for Materials Performance and Protection (AMPP), formed by a merger between Houston-based NACE International and Pittsburgh-based SSPC: The Society for Protective Coatings, is speeding up their digital transformation with a complete overhaul of their technology stacks for publishing (heavy focus on JATS, BITS, and NISO STS), membership management, eCommerce, and web presence. We discuss key drivers for this massive change, the planning approach that has occurred to date, and the path forward as AMPP moves to implement. Specific focus will be shared on proper planning, tools selection, and the precision execution plan for this seismic and transformative effort.

A Generic STS Viewer on the Web

Wendell Piez, National Institute of Standards and Technology (NIST/ITL/CSD)

In an alternate universe, XML (1998) and XSLT 1.0 (1999) were not developed so early and did not have to wait for the rest of the web to catch up. In ours, it took two decades before other critically important pieces of the puzzle - CSS, DOM, ECMAScript/Javascript - to mature to the point where the platform became viable for truly distributed architectures as it has always promised. Take a look at XSLT 1.0 in the browser, operating over standards-based STS (Standards Tag Suite) XML, and see what it can do today. Its virtue is not that it does things that have not been done before; It just makes these ordinary capabilities radically more accessible.

Fidelity and flexibility for clients and their products leveraging XSLT and XSL-FO

G. Ken Holman, Réalta Online Publishing Solutions Ltd.

Single-source publishing has long been touted as the required approach to reliably producing multiple output products for a given work. But how the solutions are engineered impacts on the maintenance, the fidelity, and the flexibility over the long term. Choices made in the early days impact on the ability to meet evolving client needs as they rise. This presentation is a case study of a single-source publishing solution architecture using XSLT and XSL-FO. It is designed for ease of maintenance, fidelity across output products, and responsiveness to new and changing client requirements.

Connecting the Dots Between BITS and PDF: A Comparison of Technologies for Automated Typesetting

Martin Kraetke, le-tex publishing services

XML first and XML last workflows with InDesign come with several limitations. XML last workflows are typically focused on the PDF. The XML is created later in the process and receives a lower level of attention. Since InDesign is primarily focused on graphical representation, you need to add semantics for example by associating style names with XML elements. XML first seemed to be a more efficient alternative. However, InDesign’s XML import and export interfaces are outdated, slow, and not agnostic to the XML structure. But more concerning is that the visual appearance and the XML structure can fall apart. With simple text corrections, an InDesign user can corrupt the underlying XML structure without even noticing it. Given the problems of XML workflows with InDesign, technologies for automated typesetting promise to be faster and better suited for maintaining both print and data quality. For this purpose, the advantages and disadvantages of XSL-FO, PrintCSS, and LaTeX are discussed in this talk. BITS is used as an example, although the conclusions apply to other XML grammars as well.

PIDs and JATS: How do I tag those crucial but pesky identifiers?

Jeffrey Beck, NCBI/NLM/NIH
Deborah Lapeyre, Mulberry Technologies, Inc.

By a PID (Persistent Identifier or Persistent Unique Identifier) we mean 'a string of letters and numbers used to distinguish between and locate different objects, people, or concepts'. The idea is that PIDS will be long-lasting references to resources or objects, mostly digital resources.

Well-known PIDs include DOIs (Digital Object Identifiers), which are used to identify digital objects such journal articles, books, and datasets and ORCiDs (Open Researcher and Contributor IDentifiers) which identify people such as authors and researchers.

As use case examples, PIDs can be used to find: Who exactly is this author? What else have they written? With which institutions are they affiliated? Who is providing the funding? Have they collaborated with any of these authors? Can I access the source data behind this article? PIDs can be used to distinguish between people/institutions/departments with the same name and unite the records of these same people/institutions/departments when that name changes.

We are not going to talk about the economic or strategic advantages of PIDs or why you should use PIDs in your JATS. We will try to be agnostic on which PIDs to use and which repositories and PID infrastructures to favor. We will concentrate on how to record the PIDS you need in your JATS articles.

There are many types of PIDs including:

• document-level PIDs
• object-level PIDs for things inside a work (such as tables, figures)
• external object PIDs
• PIDs which identify people
• Role identifiers to say what participation a person had in a work
• PIDs which identify organizations, institutions, and funders
• PIDS for research projects, subprojects, and tasks or activities
• PIDs for datasets and data collections
• PIDs to be used when citing software
• PIDs for research resources (plasmids, cell lines, organisms, etc)

New PIDs for new situations (or to replace older systems of PIDs) are being devised every day. How do we handle the PIDs we use now? How do we handle the PIDs we hope to add soon? How do we handle new PIDs that are just coming into being? How can we all help fulfill the promise of PIDs to connect and link many worlds, building an 'interconnected declarative informational fabric'?

For the types of PIDs we can both imagine and adequately describe, we will provide specific how-this-could-be-tagged in JATS examples. Conversely, we will identify what JATS elements/attributes might be used for which specific identifiers. Where there is more than one valid interpretation, we may discuss alternatives.

The Challenges of Backward-incompatible Schemas

Patricia Feeney, Crossref

Online Standards Development: Success of XML first and Challenges of XML only

Patrice Canonne, ISO

JATS Open Session

Video

JATS4R Accessibility Subgroup Progress Report

Audrey Hamelers, JATS4R Accessibility Subgroup
Joni Dames, Inera | Wiley Partner Solutions
Stephen Laverick, Green Fifteen Publishing Consultancy

Print-disabled readers in university have spoken out about the serious problems inaccessible journal articles create for them. The JATS4R (JATS for Reuse) Accessibility group has been working to define best XML tagging practices for including sufficient information to derive accessible rendered products (e.g., HTML, PDF, EPUB). This article will provide an overview of the group's work on developing accessibility tagging recommendations for various content types within JATS, including Figures, Tables, Audio and Video, Math, links, and accessibility metadata.

The session will provide a review of the work done so far, including the challenges faced and solutions proposed for each area. The session will also cover the estimated impact of these accessibility models on the overall usability of JATS content for users with disabilities. We will address what can be done without changes to the JATS model and list any potential recommendations that have been or will be made to the JATS Standing Committee for the next revision to JATS.

We will also encourage people to get involved during the public comment period.

Being Research Data

Bruce Rosenblum, Wiley Partner Solutions