Re: [jats-list] Adopting the JATS<ali:license_ref> for open access

["Owens, Evan evan.owens@xxxxxxxxxx" <jats-list-service@xxxxxxxxxxxxxxxxxxxxxx>]

The other advantage to using <ali:license_ref> is that it has an attribute for
start_date which is a component  of  license metadata to be deposited with
Crossref.  So not just moving the URL attribute but adding a new bit of data.
This is a big issue for CHORUS publishers: registering open access license
info with Crossref.  Herebs the example that I included in the CHORUS
Publisher Implementation Guide

License Metadata XML Examples

Example 5. License Metadata in Crossref Schema (v4.3.4)

<ai:program name=bAccessIndicatorsb>
 <ai:license_ref applies_to="am" start_date="2015-07-01">
   http://creativecommons.org/licenses/by/4.0/
 </ai:license_ref>
</ai:program>

JATS version 1.1 added support for NISO Access License Indicator metadata,
which is related to the Crossref Access Indicators metadata but not exactly
the same. As part of the change to support NISO ALI, the URL for the license
moved from an attribute to an element content.

Example 6. License Metadata using JATS 1.1. There is no equivalent to the
Crossref applies_to attribute; specific_use is a suggestion as to how to
encode that in JATS 1.1.

<license>
 <ali:license_ref xmlns:ali=bhttp://www.niso.org/schemas/ali/1.0/b
         specific-use="am" start_date="2015-07-01">
    http://creativecommons.org/licenses/by/4.0/
 </ali:license_ref>
 b&
<license>


Evan Owens
Co-chair CHORUS Technical Working Group
VP Publishing Technologies, Cenveo Publisher Services
2905 Byrdhill Road, Richmond VA 23228
Office: (804) 515-5146   Mobile: (804) 380-3350


From: Beck, Jeff (NIH/NLM/NCBI) [E] beck@xxxxxxxxxxxxxxxx
[mailto:jats-list-service@xxxxxxxxxxxxxxxxxxxxxx]
Sent: Monday, April 04, 2016 5:18 PM
To: jats-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re: [jats-list] Adopting the JATS<ali:license_ref> for open access

Hi Michael,

Referencing the license URI is the most important thing; the translation
between /article/front/article-meta/permissions/license/ali:license_ref and
/article/front/article-meta/permissions/license/@xlink:href is trivial.
@license-type, which can be very useful within a publishing system, does not
have any meaning outside of that system.

The advantage to using the <ali:license_ref> is that the element (and the free
to read element) is that they were defined by a NISO  Recommended Practice for
bAccess and License Indicatorsb (http://www.niso.org/workrooms/ali/). You
are not going to realize any advantage in your existing workflow: referencing
/article/front/article-meta/permissions/license/ali:license_ref doesnbtb
cost you any less than referencing
/article/front/article-meta/permissions/license/@xlink:href. But it wonbt
cost you anything more, either. If the community moves to <ali:license_ref> as
a Best Practice, you wonbt have to update your content in the future.

If I were setting things up, I would use the <ali:license_ref>. It is  more
explicit, and there are other properties that you can use from the Access and
License Indicators RP.

Jeff

From: "Michael Cunningham
michael.cunningham@xxxxxxxxxxxxxxxxx<mailto:michael.cunningham@portlandpress.
com>"
<jats-list-service@xxxxxxxxxxxxxxxxxxxxxx<mailto:jats-list-service@xxxxxxxxxx
errytech.com>>
Reply-To:
"jats-list@xxxxxxxxxxxxxxxxxxxxxx<mailto:jats-list@xxxxxxxxxxxxxxxxxxxxxx>"
<jats-list@xxxxxxxxxxxxxxxxxxxxxx<mailto:jats-list@xxxxxxxxxxxxxxxxxxxxxx>>
Date: Monday, April 4, 2016 at 12:50 PM
To:
"jats-list@xxxxxxxxxxxxxxxxxxxxxx<mailto:jats-list@xxxxxxxxxxxxxxxxxxxxxx>"
<jats-list@xxxxxxxxxxxxxxxxxxxxxx<mailto:jats-list@xxxxxxxxxxxxxxxxxxxxxx>>
Subject: [jats-list] Adopting the JATS<ali:license_ref> for open access

Hello

As part of implementing a new journal production workflow, we will upgrading
to JATS from version 2.3 of the NLM Journal Publishing DTD.

I have been wondering whether there is a benefit to adopting the JATS
<ali:license_ref> for open access articles  in place of our current open
access tagging (which as I understand is still support by JATS), i.e.

<license license-type="open-access"
xlink:href="http://creativecommons.org/licenses/by/4.0/";<http://creativecommo
ns.org/licenses/by/4.0/%22>>
<licence-p>This is an open access article published by Portland Press Limited
and distributed under the <ext-link ext-link-type="uri"
xlink:href="http://creativecommons.org/licenses/by/4.0/";>Creative<http://crea
tivecommons.org/licenses/by/4.0/%22%3eCreative> Commons Attribution Licence
(CC BY) 4.0</ext-link>.</licence-p>
</license>

Any advice our thoughts gratefully received

Michael

Michael Cunningham
Publishing Operations Manager
Portland Press|Biochemical Society
Charles Darwin House, 12 Roger Street, London WC1N 2JU, UK
email:michael.cunningham@xxxxxxxxxxxxxxxxx<mailto:michael.cunningham@portland
press.com> Tel:+44 20 7685 2410


Portland Press Ltd registered in England and Wales No. 2453983.

Registered Office: Charles Darwin House, 12 Roger Street, Third Floor, London,
WC1N 2JU.

VAT registration number GB 523 2392 69.

The contents of this email are for the recipient only.

If you are not this person (or not responsible for delivery to this person),
then notify the sender and delete the email immediately.

Any opinions contained in this message are those of the author and are not
given or endorsed by Portland Press Ltd or the division through which this
message is sent unless otherwise clearly indicated in this message.

Charles Darwin House, 12 Roger Street, Third Floor, London, WC1N 2JU
JATS-List info and archive<http://www.mulberrytech.com/JATS/JATS-List/>
EasyUnsubscribe<-list/17344> (by email<>)

****

****