[jats-list] Re: JATS revision request: add @id to front, body, and back

Subject: [jats-list] Re: JATS revision request: add @id to front, body, and back
From: Kevin Hawkins <kevin.s.hawkins@xxxxxxxxxxxxxxxxxx>
Date: Wed, 21 Nov 2012 16:51:41 -0500
Hi folks who decide on these things,

Could you say when this request will be considered and, if accepted, when a release of JATS including this might be made? We've got some development coming up in early 2013 that will depend on this being in the standard or us at least knowing that it's been accepted (in which case we'd hack a DTD in the meantime). Thanks,

Kevin

On 10/18/2012 2:38 PM, Kevin Hawkins wrote:
Hello,

At JATS-Con we were asked to submit bugs and feature requests for JATS
to this list now rather than waiting for waiting for the continuous
maintenance process to be set up. So on behalf of my colleagues at the
University of Michigan Library, I am requesting the addition of id= to
<front>, <body>, and <back>.

In constructing http://www.lib.umich.edu/mpach , we will be storing JATS
documents -- plus embedded media, supplemental material, and optionally
a user-provided typeset PDF -- with a METS "wrapper" in the HathiTrust
repository. HathiTrust METS files include a <structMap> pointing to the
salient structural features of the digital object (each identified with
a unique ID), which allows for traversal of the item in the interface.
We want to be able to point not only to each <sec> but also to <front>
and to any text in a <body> or a <back> which might lack <sec>s inside
it. We also need these IDs for fulltext indexing surposes so that all
PCDATA within a JATS document has a parent element with an ID. Adding
id= to <front>, <body>, and <back> will ensure this condition.

Frankly, we think that it would be best to make id= a global attribute.
While Debbie explained to me during JATS-Con that making it not global
was an attempt to avoid what was thought of as a mistake in the design
of TEI and DocBook, we feel that you can't really decide in advance what
use cases users will have for putting an id= on an element, even if the
element can only occur once according to the DTD.

Please let me know if you have any questions,

Kevin

Current Thread