Subject: Re: [jats-list] access and license indicators From: "Maloney, Christopher (NIH/NLM/NCBI) [C] maloneyc@xxxxxxxxxxxxxxxx" <jats-list-service@xxxxxxxxxxxxxxxxxxxxxx> Date: Thu, 4 Jun 2015 14:19:46 -0000 |
Hi, I have some questions and some comments. I'm not quite sure exactly what your tagged example is attempting to convey, but I'd make the following suggestions regardless: * Drop the `specific-use="metadata"` attributes -- I don't see that they add any information; the contents of the <license> elements are always metadata. * I see that your rights-and-permissions page (http://publishing.aip.org/authors/rights-and-permissions) mentions that at least two journals use a CC-BY license. In those cases, I'd suggest that it's important to use that URI (https://creativecommons.org/licenses/by/3.0/) in the license/@xlink:href directly. This is for machine-readability - so that bots and such could tell what the license of the article is, and thus maximize the re-use potential. So, what does this tag mean? <named-content specific-use=bmetadatab content-type=bam-start-dateb>2016-06-01</named-content> Have you seen NISO's recent recommended practice document on this topic? It's here: http://www.niso.org/apps/group_public/download.php/14226/rp-22-2015_ALI.pdf . That document provides two new XML elements that might be helpful, and the latest draft version of JATS (1.1d3) includes these: * <ali:free_to_read> (http://jatspan.org/niso/archiving-1.1d3/#p=elem-ali_free_to_read) - this might be what you're `license-type="public-access"` is attempting to convey * <ali:license_ref> (http://jatspan.org/niso/archiving-1.1d3/#p=elem-ali_license_ref) - this can be used to specify dates, if different licenses apply for different time periods. But, if you're stuck using a version of JATS earlier than 1.1d3, then I'd suggest coming up with a tagging scheme that mimics as closely as possible the NISO recommendations. In the JATS-for-reuse group, we have an open issue to address this question, here: https://github.com/JATS4R/elements/issues/50. We could use this as an example, and try to come up with best practices for this case, which we'd then roll into our next iteration of recommendations. -- Chris Maloney NIH/NLM/NCBI (Contractor) Building 45, 4AN36D-12 301-594-2842 "Jennifer McAndrews jmcandre@xxxxxxx<mailto:jmcandre@xxxxxxx>" wrote: Hello All, In anticipation of providing our users access to DOE funded articles this coming autumn, we are working to devise a sample JATS tagging structure that we can provide to our online hosting group so that they, in turn, can begin preparation on their end. Because we need to do this sooner rather than later, we are at present planning to use existing JATS green. As of right now, our markup would read: <license license-type="public-access" xlink:href="http://publishing.aip.org/authors/rights-and-permissions" specific-use=bmetadatab> <license-p> <named-content specific-use=bmetadatab content-type=bam-start-dateb>2016-06-01</named-content> </license-p> </license> Ibm curious if anyone else is planning to use existing elements and if so what that implementation might look like? I worry therebs a more precise or more elegant means of containing the information inside the xml that Ibm not considering. Thanks for any input! Jennifer Jennifer McAndrews Content Technology AIP Publishing LLC 1305 Walt Whitman Road Suite 300 Melville, NY 11747-4300 [AIPPublishinglogo] Tel. +1 516-576-2679 Email: jmcandre@xxxxxxx<mailto:jmcandre@xxxxxxx> JATS-List info and archive<http://www.mulberrytech.com/JATS/JATS-List/> EasyUnsubscribe<http://lists.mulberrytech.com/unsub/jats-list/281881> (by email<mailto:jats-list-unsub@xxxxxxxxxxxxxxxxxxxxxx?subject=remove>) [demime 1.01d removed an attachment of type image/jpeg which had a name of image002.jpg]
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
[jats-list] access and license indi, Jennifer McAndrews j | Thread | Re: [jats-list] access and license , Owens, Evan evan.owe |
[jats-list] access and license indi, Jennifer McAndrews j | Date | Re: [jats-list] access and license , Owens, Evan evan.owe |
Month |