RE: [jats-list] Metadata: version number of an article

Subject: RE: [jats-list] Metadata: version number of an article
From: "Lizzi, Vincent" <Vincent.Lizzi@xxxxxxxxxxxxxxxxxxxx>
Date: Fri, 11 Apr 2014 15:29:45 +0000

This seems like a good use case for the <history> element. The next question
is how to tag version number using the elements allowed in <history>. If your
version numbering scheme happens to use timestamps this might work for you:

<history><date date-type="article-version"

A different approach that would probably work better could be to use
<article-id>. Versioning is related to identifying a document so this seems
like a reasonable use of the article-id tag. In this usage the id is a
"Identifier assigned to a version of an article." instead of a "Unique
identifier assigned to an article." One might use the article-version
identifier in combination with an article identifier (such as DOI) to locate a
version of an article. For example:

<article-id pub-id-type="article-version">1.0</article-id>

An example with version numbers automatically assigned by subversion:

<article-id pub-id-type="article-version">$Revision: 42 $</article-id>

Another option that you could do is customize your local version of JATS to
add an element to hold article version. There is no tag in JATS currently to
capture the version of an article so this would be a reasonable extension.


-----Original Message-----
From: Alf Eaton [mailto:eaton.alf@xxxxxxxxx]
Sent: Thursday, April 10, 2014 8:51 AM
To: jats-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: [jats-list] Metadata: version number of an article

I've been looking for a suitable tag for marking up the version number of an
article that can undergo multiple revisions. Is there anything more
appropriate than



The information contained in this email message may be confidential. If you
are not the intended recipient, any use, interference with, disclosure or
copying of this material is unauthorised and prohibited. Although this message
and any attachments are believed to be free of viruses, no responsibility is
accepted by Informa for any loss or damage arising in any way from receipt or
use thereof. Messages to and from the company are monitored for operational
reasons and in accordance with lawful business practices.
If you have received this message in error, please notify us by return and
delete the message and any attachments. Further enquiries/returns can be sent
to postmaster@xxxxxxxxxxx

Current Thread