JATS-Con 2020 Schedule with Abstracts

Registration

Welcome and Introductions

Opening Presentation

Patricia Feeney, Crossref

Upgrading a Production System to JATS 1.2: Throw out your old food containers

Vincent Lizzi, Taylor & Francis Group
Joanna Czerepowicz, Taylor & Francis Group

Following the release of JATS 1.2 in March 2019, the Digital Production team within the Journals Production department of Taylor & Francis began a project to modernize our article XML based on JATS 1.2. This upgrade from a customized version of JATS 1.0 to JATS 1.2 would be the first major upgrade since transitioning from a proprietary DTD in 2012. This project began with a number of inter-dependencies, which increased as the project went on and became aligned with other projects to significantly improve our digital foundation. The Digital Production team has worked closely with the Taylor & Francis Global Supplier Management Team, prepress vendors, contractors, and development teams for internal content management systems to complete this upgrade. This paper and presentation give a progress report in which we share some of the experiences and lessons we have learned from this upgrade.

Change Tracking in the XML-Based LiXuid Production Workflow Using Fonto’s Document History

Bert Willems, Fonto
Charles O’Connor, Aries Systems

When Aries was looking for an XML editing platform to build on for the LiXuid XML workflow, a top priority was change tracking that was robust and usable to satisfy the needs of journal production staff. The solutions available at the time, based on using processing instructions, either did not capture the full range of possible changes or were unreliable in their behavior. Aries also wanted to avoid having to superset JATS to add change tracking elements. Fortunately, Fonto, one of the candidate XML editors, was working on a solution based on DeltaXML called Document History. What sets Document History apart is its ability to display changes made across different revisions of an XML document. This principle is called a changelog and it is different from A/B comparisons typically employed in change tracking solutions. A changelog is a comparison between multiple, subsequent revisions of an XML document merged back into one annotated XML document which is then visualized. This changelog contains the necessary information to attribute changes to specific users and moments in time, something that is typically only offered by active change tracking systems. Another property of this changelog is its ability to show overlapping and conflicting changes. Both textual and XML changes are displayed in Document History as a redlined version of the document. Through the UI, users have the ability to determine what range of revisions they want to look at, and the application provides the ability to navigate quickly to the associated XML editor as well as to mark change as seen.

THE Reason for JATS' Success

B. Tommie Usdin, Mulberry Technologies, Inc., Moderator

JATS is about 20 years old, and is in use not only for its original use; JATS and JATS-based vocabularies are in use in a wide variety of environments and contexts. Many people attribute that success to ONE key feature of JATS. Interestingly, while many name the one and only one feature they see as critical to the success of JATS, there is no consensus on what that feature is. In this session, a variety of people will identify the one critical feature that they believe was key to the success of JATS and tell us why that feature is so important.

What do you do when you receive bad XML? Panel Discussion

A "Living Documents" BITS Case Study

Dorothy Hoskins, Atypon Systems, LLC

The BITS update extension for "Living Documents" case study looks into the details of applying our theoretical DTD in practice. The DTD extension depends upon inserting specific elements that contain text strings marked with the text version, and displays these different strings in useful ways to help readers understand what changed in the online text between versions.

The update tagging is very granular, and we made some assumptions regarding how these tags would be used. Now in a real book, we face the practical application of our DTD extension.

We will look at a number of questions: What are the publisher's "must have" and "nice to have" requirements? What is the difficulty/level of effort of tagging the updates in the content? What differentiates an editorial change from a meaningful update for the end user? How well can we deliver a user experience that meets their needs? Are there some types of updates that are not feasible with the normal online user experience, if so, what other UX can we provide?

We will show screenshots of the content in the website and the underlying XML that is creating the user experience.

Leaping the Field: On Being an Early Adopter and Jumping from PDF to NISO STS

Mark Gross, Data Conversion Laboratory, Inc.
Daneil Berger, American Water Works Association

The American Water Works Association (AWWA) was one of the first Standards Associations to convert content to NISO STS XML. Data Conversion Laboratory (DCL) worked with AWWA to transform its standards content and provide a platform for interchange and interoperability.

This project was particularly interesting and challenging as AWWA had no prior XML and the conversion process was from PDF to NISO STS. After 1 year of working with NISO STS, this paper reviews how it has improved AWWA's publishing process and what the larger standards community should understand about the specification.

Mark Gross, President of Data Conversion Laboratory, and Daniel Berger, Senior Manager of Production at AWWA, will discuss

• Content structure: tips and best practices that ensure the free flow of standards content. Discussion around XML as well as workflow processes that enforce the NISO STS XML standard.
• Content conversion: critical components of analysis, specification, conversion, QA/QC, timeline, and budget. The content included some challenging situations that required some non-perfect decisions in terms of MathML, images, tables, and footnotes.
• Content interchange: how the new format helps with indexing and searching and supports improved discoverability of AWWA's content.
• Tag suite: nuances of the tags during conversion and desired enhancements after 1 full year in production.

MECA and JATS Compatibility: A case study utilizing the JATS Compatibility Meta Model

Laura Randall, NCBI/NLM/NIH
Sally Ubnoske, Aries Systems Corporation

The NISO Manuscript Exchange Common Approach (MECA) project is a cross-organization industry initiative to develop a common approach to manuscript transfer that can be adopted across the scholarly publishing industry. MECA establishes a vocabulary set that includes transfer, review, and manifest models. These models are designed to work with different article XML schemas, including the latest NISO JATS standard (v1.2). In order to avoid conflicts between these project vocabularies and the JATS, we reviewed the MECA vocabularies against the NISO JATS Compatibility Meta Model (v0.7).

This paper describes the review and analysis of the MECA schemas against the JATS Meta Model, how we documented the analysis, and the recommendations we made to resolve issues revealed by the analysis. It includes the documentation we produced to communicate the results of the analysis and what actions we took to move forward with the project, including both changes to the schemas and requests to changes in the JATS.

We hope sharing our experiences with this process will help others who are trying to do the same.

Predicting the affiliation country from article metadata

Danilo de Jesus da Silva Bellini, SciELO

It's not so hard to find an article that doesn't have all its metadata, or whose metadata content is wrong, from a typographical error to a text that makes no sense for some field. Country names can be easily standardized, but sometimes it's missing, or can be written in distinct forms and in several distinct languages. The goal of this work is to show and classify the several techniques that can be used in order to clean or normalize the country names, giving examples of actual implementations that use each technique, and how this path brings us to a machine learning approach based on word2vec to predict the country from other metadata, and how we can evaluate the results of such an algorithm.

This article describes a result of the project for the normalization of institutional affiliation of the authors of documents in the SciELO Network, and its software implementation is publicly available in the SciELO AMP (Article Metadata Predictor) project.

A Deep Dive into JATS Documentation

B. Tommie Usdin, Mulberry Technologies, Inc.

JATS use is supported by a wide variety of information resources. The JATS Standing Committee maintains the JATS Standard and the JATS Tag Libraries. In addition, there are recommendations from JATS4R, conference proceedings, user guidelines, and discussion lists. Similar resources support users of BITS and NISO STS.

The Stadards aare the de jure definition of the tag sets. Their value to users is mosl in the fact that they exist!!

The Tag Libraries are the de facto definition of the tag sets. They are the information resources users should turn to with qquestions about structure, usage, and definitions. The tag libraries are a rich and complex reference source. I believe that even regular users will be surprised by some of the information content and navigation tools provided in the tag libraries.

At the time this proposal to speak was written we were working on a revision of the tag libraries that would make them more accessible and more responsive to the needs of frequent users. If that revision is complete by JATS-Con, we will introduce the new look. If the revision is not complete by JATS-Con we will show a demonstration.

Other resources include the proceedings of several conferences including JATS-Con, JATS4R Recommendations, the archive of JATS-List, Guidelines provided by major recipients of JATS articles, and tagged articles provided on the web sites of several JATS users.

JATS to JATS with Eddie 2

Liam Quin, Delightful Computing

When faced with the task of writing XSLT transformations to make from one version of JATS to another, often with proprietary (in-house) extensions at one end or both, developers may find the size of the vocabulary intimidating.

Eddie 2 is a tool that implements a systematic methodology for writing XSLT transformations that convert between broadly similar DTDs such as two versions of JATS. Using this tool can make development both faster and more robust. The paper describes the analysis-first methodology and how the tool supports it.

Learn more at Delightful Computing.

JATS Open Session

WYSIMTWYG ―What you see is more than what you get when using XML

Ken Holman, Setare Solutions Limited

Authoring standards documents in XML provides publishing options not available when using traditional word-processing-based desktop publishing. Organizations not having used XML yet may be unaware of the opportunities to tailor back-room renditions of standards documents that are augmented to be useful to authors and editors yet remain unpublished and are never seen by users of the final result. This is a case study about meeting a client's requirements to convert existing standards to NISO STS, update them, and add semantic markup. It reveals the use of a tailored rendition of standards documents to expose and review markup not visible to the end user. Agreement on the semantic markup is critical to the use of the content from the published document in downstream processes. Tailored augmented renditions are important tools to support the review of hidden markup, and are not available as readily when not using XML as the basis for publishing.

Conference Closing

Jeffrey Beck, NCBI/NLM/NIH