Subject: Re: [jats-list] Open Access types From: "Mike Eden meden@xxxxxxxxxxxxx" <jats-list-service@xxxxxxxxxxxxxxxxxxxxxx> Date: Thu, 14 Aug 2014 15:09:51 -0000 |
Hi Chris, Thanks, we are already capturing the full uri as per your example, but left it out for space. Initially I thought we needed to extract the "by" etc from this uri, however looking at this again, we could probably just pass the uri as a parameter value in the feed as it does indeed describe the type of OA licence. Regards Mike Eden Operations Manager Content Services Cambridge University Press Cambridge CB2 8RU U.K. +44 (0)1223 326435 From: "Maloney, Christopher (NIH/NLM/NCBI) [C] maloneyc@xxxxxxxxxxxxxxxx" <jats-list-service@xxxxxxxxxxxxxxxxxxxxxx> To: "jats-list@xxxxxxxxxxxxxxxxxxxxxx" <jats-list@xxxxxxxxxxxxxxxxxxxxxx>, Date: 14/08/2014 15:08 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 it?s 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 you?re 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 aren?t any universally-adopted set of values with defined definitions, it wouldn?t 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<>)
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [jats-list] Open Access types, Maloney, Christopher | Thread | [jats-list] Fwd: [FoRCnet.org] Peer, Kevin Hawkins kevin. |
Re: [jats-list] Open Access types, Good, Linda linda.go | Date | Re: [jats-list] Open Access types, Maloney, Christopher |
Month |