Re: [jats-list] access and license indicators

Subject: Re: [jats-list] access and license indicators
From: "B Tommie Usdin btusdin@xxxxxxxxxxxxxxxx" <jats-list-service@xxxxxxxxxxxxxxxxxxxxxx>
Date: Fri, 5 Jun 2015 16:57:05 -0000
Hi Richard b

The JATS Standing Committee has voted to submit draft 1.1d3 to NISO for
formalization as v1.1. The draft JATS 1.1 will go through the formal process
of becoming a NISO standard, which includes a public comment period followed
by Standing Committee consideration of any comments received.

We donbt know what the time line for the process will be, in part because we
donbt know how extensive public comments will be and thus how long it will
take to address those comments.

There is a possibility that a comment (or comments) will suggest changes and
there is a possibility that changes will be made in response to public
comments.

In my personal opinion, it seems likely that even if changes are made in
response to comments received during the public comment period, the standard
is likely to proceed to a vote, and not to another draft. It seems to me, that
only if comments received during the public comment period lead the committee
to make significant changes will another draft be needed. NOTE: I donbt know
what NISObs rules on this are, and we will follow all NISO rules and
procedures.

Having said that, I urge anyone looking at freezing guidance on tagging
information relating to permissions using JATS to consider the new structures
added in JATS 1.1d3. Structures specifically for encoding this information
were added, and I believe their use will significantly enhance long-term use
of this information.

b Tommie



> On Jun 5, 2015, at 12:42 PM, Rich Okeeffe rokeeffe@xxxxxxx
<jats-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:
>
> Thanks Chris/Evan,
>
> Part of our concern is the following:
>
> 1.       When is draft 1.1d3 going to be formalized as v1.1?
> 2.       Can it be guaranteed that the new markup will be included in v1.1
or is there a possibility it may be reconsidered and changed?
> 3.       Will there be further drafts before formal acceptance?
>
> Our organization, and no doubt others, need to consider the ramifications of
upgrading to a new version as we interact with many partners, such as content
compositors, platform hosts, A&I services, etc. The preference is to do this
once and not need to do it for a draft (which may change), and then the formal
version.
>
> This is compounded by some uncertainty in the community as to what
constitutes best practice and for some parties, seeking to comply with an
October 2015 DOE funding mandate within the context of CHORUS. In summary, we
are looking for a valid JATS 1.0 solution that can be implemented in the very
near future.
>
> Reorganizing the markup approach to contend with OA and licensing practices
is no small matter and of great import. Getting it right the first time is the
desired goal.
>
> On the positive, sign, we are very much appreciative of the comments and
examples this post will generate!
>
> Richard ObKeeffe
> Content Management Services
> AIP Publishing LLC
> 1305 Walt Whitman Road, Melville, NY 11747
>
> Tel: 516-576-2645
> Email: rokeeffe@xxxxxxx
>
>
> ***********
> I have been talking with Chuck Koscher of CrossRef about JATS and ALI.  An
issue that he raised was that the NISO ALI specification (now included in JATS
1.1d3) has no provision to indicate which article version the license applies
to (Accepted manuscript or Version of Record or Text Mining). That is part of
the CrossRef metadata that didn't get included in ALI and JATS.  The CrossRef
attribute is @applies_to on their <license_ref> element; values are "am" "vor"
and "tdm".
>
> So perhaps a JATS solution would be to use the @specific-use attribute on
<license> to document what version the license applies to; something like
this:
>
> <license  specific-use="am">
>    <ali:license_ref xmlns:ali="http://www.niso.org/schemas/ali/1.0";
start_date="2015-02-03">
>         http://www.examplesite.org/open_license.html
>    </ali:license_ref>
> </license>
>
> Which then would have all the information that needs to be exported to
CrossRef.  This is an industry challenge because CHORUS members are required
to document their licenses to CrossRef...and some may have multiple versions
and licenses to manage.
>
> Evan Owens  (member of JATS standing committee and CHORUS TWG)
>
> ***************
> 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
> EasyUnsubscribe (by email)

======================================================================
B. Tommie Usdin                        mailto:btusdin@xxxxxxxxxxxxxxxx
Mulberry Technologies, Inc.                http://www.mulberrytech.com
17 West Jefferson Street                           Phone: 301/315-9631
Suite 207                                    Direct Line: 301/315-9634
Rockville, MD  20850                                 Fax: 301/315-8285
----------------------------------------------------------------------
Mulberry Technologies: A Consultancy Specializing in XML and SGML
======================================================================

Current Thread