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

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

<- Previous	Index	Next ->
[jats-list] [ANN]JATS-Con 2012: Pre, Kelly, Laura (NIH/NL	Thread	[jats-list] Fwd: [oXygen-user] Tool, Wendell Piez
[jats-list] [ANN]JATS-Con 2012: Pre, Kelly, Laura (NIH/NL	Date	RE: [jats-list] a new JATS wiki, Maloney, Christopher
	Month

<-prev [Thread] next->	<-prev [Date] next->
Month Index \| List Home

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