elifesciences / JATs-xml

eLife upgrade to JATS xml
1 stars 2 forks source link

Convert mixed-citation to element-citation #29

Closed gnott closed 10 years ago

gnott commented 10 years ago

Re: commit https://github.com/elifesciences/JATs-xml/commit/dc31c9cb60d81de32f61375d8cc8eaeff5e57e69

At least one early article has an <ext-link> instead of a <pub-id> for a DOI of a reference

<ext-link ext-link-type="uri" xlink:href="http://dx.doi.org/10.1007/s00442-006-0365-8">10.1007/s00442-006-0365-8</ext-link>

Q. Is this ok, or should we convert the ext-link values to pub-id (if the href starts with dx.doi.org we can set the pub-id-type="doi")

Melissa37 commented 10 years ago

From TNQ:

I have consulted with the XML experts here and it is fine to proceed with the going forward. But we have used the below options previously.

(1) If we receive DOI with prefix http://dx.doi.org then we would tag them as .

(2) If we receive DOI like 10.1007/s00442-006-0365-8 then we would tag them as .

Melissa37 commented 10 years ago

Question out with JATS-list

Melissa37 commented 10 years ago

From JATS: Comment 00535 - Linking attributes for element

Request: The current JATS reference models ( and ) allow a unique global identifier such as a DOI, ARC, or Handle to be tagged using the element . But many publishers are tagging the DOIs in their reference lists using the element because they want the identifier to be a live link and the element does not take linking attributes. It would be better if the DOIs were both tagged as elements and linked.

Submitter Proposed Solution:

Add the might-link attributes to the element , so that a DOI or similar identifier can be made into a live link.

10.6070/H4WM1BBQ Standing Committee Recommendation Add linking attributes (optionally) to , so that a pub-id that is a DOI can carry the linking attribute to be turned into a link. Such a ## acts as both an identifier and a link. So you will soon be able to call something a because it is, and link it, as CrossRef recommends.