Re: [jats-list] Open Access types

["Maloney, Christopher (NIH/NLM/NCBI) [C] maloneyc@xxxxxxxxxxxxxxxx" <jats-list-service@xxxxxxxxxxxxxxxxxxxxxx>]

Ibm not very familiar with CCC, but I think thatbs more oriented towards
individual licenses that are negotiated per customer or user, whereas
Creative Commons are blanket licenses that are granted to everyone.  So
Ibm not sure it makes sense to encode a CCC license in the document
itself.  Someone else might be better able to address that question.


--
Chris Maloney
NIH/NLM/NCBI (Contractor)
Building 45, 4AN36D-12
301-594-2842







"Good, Linda linda.good@xxxxxxxxxx" wrote:

>Chris, do you have an example of using <license license-type="ccc">
>statement? What can you share about RightsLink (Copyright Clearance
>Center)?
>
>
>Linda J. Good
>Phone: 717-285-6815
>Cell: 717-475-5379
>Email Address: Linda.Good@xxxxxxxxxx
>
>
>-----Original Message-----
>From: Maloney, Christopher (NIH/NLM/NCBI) [C] maloneyc@xxxxxxxxxxxxxxxx
>[mailto:jats-list-service@xxxxxxxxxxxxxxxxxxxxxx]
>Sent: Thursday, August 14, 2014 10:09 AM
>To: jats-list@xxxxxxxxxxxxxxxxxxxxxx
>Subject: Re: [jats-list] Open Access types
>
>The best way to indicate the license is to include the definitive full
>license URI in the @xlink:href attribute of the <license> element, the
>way itbs shown in the example on the license page of the tag library
>(http://jatspan.org/niso/publishing-1.1d1/#p=elem-license):
>
>
>
><license license-type="open-access"
>
>         xlink:href="http://creativecommons.org/licenses/by/2.0/";>
>
>  <license-p>This is an open-access article distributed under the terms of
>
>the Creative Commons Attribution License, which permits unrestricted
>
>use, distribution, and reproduction in any medium, provided the original
>
>work is properly cited.</license-p>
>
></license>
>
>
>
>In your examples, it looks like youbre just referring to the various
>Creative Commons licenses, and those all have full URIs that you can use.
>
>
>
>The problem with the @license-type attribute is that, since there arenbt
>any universally-adopted set of values with defined definitions, it
>wouldnbt really support machine-readability by, for example, other groups
>wanting to re-use the content.
>
>
>
>
>
>--
>
>Chris Maloney
>
>NIH/NLM/NCBI (Contractor)
>
>Building 45, 4AN36D-12
>
>301-594-2842
>
>
>
>
>
>"Mike Eden meden@xxxxxxxxxxxxx<mailto:meden@xxxxxxxxxxxxx>" wrote:
>
>
>
>Hi,
>
>
>
>Is anyone capturing the type of Open Access (by, by-nc-sa, by-nc-nd  etc
>) in anything other than in @licence-type  in the <licence> element?
>
>We are currently only capturing licence-type="open-access" as per
>documentation examples , but have requirement now to identify type of OA.
>
>
>
>The options I see are
>
>
>
>1.  Capture<licence licence-type="by"  or "by-nc-nd" etc
>
>2.  Capture<licence licence-type="open-access-by"  or
>"open-access-by-nc-nd" etc
>
>3. Capture oa type in <licence licence-type="open-access"><licence-p
>content-type="by">  etc
>
>4. Capture <licence licence-type="by-nc-nd"><licence-p
>content-type="open-access">
>
>5. Capture  <licence licence-type="open-access"><licence-p> and pattern
>match for "by-nc-sa" in the URL declared in xlink:href  or in the URL
>declared in the <licence-p>  e.g.
>http://creativecommons.org/licenses/by-nc-sa/2.5/
>
>
>
>
>
>Any thoughts?
>
>
>
>
>
>Regards
>
>Mike Eden
>
>
>
>JATS-List info and archive<http://www.mulberrytech.com/JATS/JATS-List/>
>
>EasyUnsubscribe<-list/281881> (by email<>)
>
>
>****
>
>****