Home | Public Area
Public Groups Area » Public Documents » Public View Comment

#00179 Comment Details - z39-96-dsftu-final.pdf

Document Information
Title NISO Z39.96-201x, JATS: Journal Article Tag Suite
File Name z39-96-dsftu-final.pdf State Final
Date Added 2011-03-30 07:39:41 Revision Number 0
Submitter Name Cynthia Hodgson Size 2MB
Comment Information
Summary
Decide and Document use of id attribute on Affiliation
 State (Disposition) New (Unresolved)
Date Added 2011-10-17 14:13:04 Last Updated 2011-10-17 14:13:05
Submitter Name Debbie Lapeyre Assigned To Unassigned
Company Name Mulberry Technologies, Inc. Response None
Interest Category Supplier Category Substantive
Origin Member Section, Page, Line
Item N/A Item Description
Submitter Comment
The SPJ Working Group met on December 6, 2010, to review the Journal Archiving and Interchange/Publishing Tag Set Tag Libraries version 3.1 Draft. The members liked the Draft very much in general, and appreciated the efforts of JATS Working Group. If approved, the version 3.1 will encourage the use of JATS significantly in Japan.

There was, however, one issue which the members wanted JATS Working Group to look at with regard to the @id attribute for Affiliation Alternatives as follows.
As we look at the page 2 of the document, " Journal Article Tag Sets Element and Attribute Changes Version 3.0 to Version 3.1", the example of the Affiliation Alternatives element contains the ID attribute three times as shown below, one on the alternatives elements and once for each affiliation:

aff-alternatives id="aff2"

aff id="aff-ja"
institution xml:lang="ja-Jpan"
Japanese name.../institution
/aff

aff id="aff-en"
institution xml:lang="en"
English name.../institution
/aff
/aff-alternatives

This could cause some difficulty for users in programming to retrieve correct information from the XML. We would like to recommend JATS to issue a guideline how to reference information. The members of the SPJ Working Group believe there should be only one unambiguous ID attribute for a set of elements which semantically contain the same information, such as multi-language (English and Japanese) expressions of a single organization.
Submitter Proposed Solution
Based on this belief, we would like to propose a couple of possible solutions.

1) Allow the ID attribute only in the Affiliation Alternatives wrapper

This will allow users to retrieve necessary data directed by the xml:lang data. Its drawback is that users have to rewrite the current programs substantially. Some commented substantial rewriting is inevitable anyway, though, as Affiliation Alternatives is a new element.

2) Allow describing ID attribute only in the default language Affiliation as defined in the xml:lang on the Article element.

That means, there should not be any ID attributes either in the Affiliation Alternatives wrapper, or non-default language Affiliation. This will result in minimum rewriting of the current programs. Its drawback is, depending on the program, the data that were not identified by @id may not be able to be retrieved.

Please look at this issue. As this is a general issue possible for other element wrappers, too, please make the guideline as general.