Home | Public Area

Comment #00543 - suggested copyedits of definition of name-alternatives - z39.96-2012.pdf

Comment 543
Addressed (Unresolved)
ANSI/NISO Z39.96-2012, JATS: Journal Article Tag Suite (version 1.0) (Revision 0)
Comment Submitted by
Kevin Hawkins
2014-10-19 17:17:42

Blue and Green say this in the definition of :



* An alternate name indexing (For example, an XML database may need to record all the name variants found for an individual from “President Thomas Jefferson” to “Long Tom”, with @specific-use used to mark “primary” and “index”.); or

* Both validated and known-to-be-incorrect names. (For example, in the PubMed DTD, there is an attribute called “ValidYN” [valid yes or no], that can be used to record the fact that one version of a name was received, found to be in error and corrected. Only the corrected version should be displayed, but both name variants might be used for searching.)



There are a couple of confusing things here:



a) It appears that "for" is missing before "indexing".

b) Name variants aren't really "found".  They are recorded.

c) It's odd to discuss an individual in the abstract and then immediately move to a specific example, and the use of "from" and "to" implies that the two forms given are at opposite ends of a continuum, which is irrelevant.

d) It sounds like "primary" and "index" are the only two forms you'd use, but they actually sound like they'd be used for nearly the same purposes.

e) The reference to the PubMed DTD is odd.  It would be clearer to explain how one might accomplish this within JATS.

Submitter Proposed Solution

I suggest revising to the following:



* An alternate name for indexing (For example, an XML database may need to record all name variants for an individual, with @specific-use used to mark one of them as “primary” or “index”.); or

* Either validated and known-to-be-incorrect names. (This can be useful in the case of encoding previously published content, where those validated and those known to be errors are recorded using certain values of @specific-use.)

Ms. B. Tommie Usdin
2015-07-09 09:24:12

This is not, technically, a comment on the Standard; it is a comment about the non-normative/informal documentation. That said, the text in the Tag Library will be revised.