RE: Help with ODRL

Hi Renato,

Thank you very much for your reply and offer of support!

The current work on NISO Access & License Indicators is to support a new use case for social platforms to automatically identify the conditions under which copyrighted articles can be shared legally in accordance with publisher policies. We have made some progress on an approach that uses a combination of ALI, ODRL, and Crossref DOIs to create sharing policies that are machine actionable. It would be very helpful to receive your advice about this use of ODRL.

In this use case, every article has metadata stored in Crossref. The article metadata will include one or more <ali:license_ref> elements that hold a DOI URL that points to a sharing policy page. Each sharing policy page describes what kind of sharing is allowed, and can be identified by its DOI URL and contains metadata in ODRL JSON-LD format. In this way, a social platform can use the article metadata to automatically find out if an article has a sharing policy and the conditions for legal sharing that are allowed by the policy. There are some overviews that contain more details at https://www.stm-assoc.org/asf/ and at https://gitlab.com/vincentml/asf#asf-sharing-policy-generator

A draft of a sharing policy that has metadata in ODRL JSON-LD format is available at https://vincentml.gitlab.io/asf/policy-001-v1-0.html. The ODRL JSON-LD metadata is in a <script> tag and can be seen by viewing the HTML source. The @context of the JSON-LD uses a DOI URL https://doi.org/10.15223/asf-vocabulary that has not been created yet but will redirect to https://vincentml.gitlab.io/asf/asf-vocabulary.jsonld. The ODRL in this draft has been tested using https://json-ld.org/playground/ and some standard JSON parsers. However, this draft is based on what I have learned by reading the ODRL 2.2 specifications. It would be helpful to receive advice from someone like yourself who has more knowledge about ODRL.

One challenge that we have is how to use ODRL to represent a sharing policy that has an embargo. For example, a policy that has an embargo might allow an article to be shared only after 12 months past the date when the article was published. A constraint could be written as elapsedTime gt P12M, or a constraint could be written as delayPeriod gt P12M. How can a constraint indicate that publication date is the basis for the duration, and is it better to use elapsedTime or delayPeriod?

Kind regards,
Vincent

_____________________________________________
Vincent M. Lizzi
Head of Information Standards | Taylor & Francis Group
vincent.lizzi@taylorandfrancis.com<mailto:vincent.lizzi@taylorandfrancis.com>




Information Classification: General
From: Renato Iannella <r@iannel.la>
Sent: Wednesday, April 7, 2021 9:22 AM
To: Lizzi, Vincent <Vincent.Lizzi@taylorandfrancis.com>
Cc: public-odrl@w3.org
Subject: Re: Help with ODRL

Hi Vincent, we believe that ODRL would provide a strong basis for the foundation for the updated NISO standards for Access & License Indicators.

As a Community Group we would be happy to support this adoption and provide our expertise and experience towards the development of the Profile.

For the use cases described in section 5 of the current spec at: https://groups.niso.org/apps/group_public/download.php/14226/rp-22-2015_ALI.pdf<https://groups.niso.org/apps/group_public/download.php/14226/rp-22-2015_ALI.pdf>
would be relatively easy to implement with appropriate (open source) tools and systems.

Please let us know if you have any further questions and next steps?

Cheers - Renato



On 27 Feb 2021, at 05:02, Lizzi, Vincent <Vincent.Lizzi@taylorandfrancis.com<mailto:Vincent.Lizzi@taylorandfrancis.com>> wrote:

Hello,

I hope this day finds you well. I am a member of a working group at NISO helping to update the Access & License Indicators recommendation. There is some information about the working group athttps://www.niso.org/niso-io/2020/10/help-us-update-recommended-practice-access-and-license-indicators-ali<https://www.niso.org/niso-io/2020/10/help-us-update-recommended-practice-access-and-license-indicators-ali> and I would be glad to share more information. The reason for this email is that I am researching ODRL for its potential to help with certain use cases. It looks like ODRL is able to support the use cases that we are trying to address. However, it also looks like a system that processes ODRL would need to be very complex unless only a subset of ODRL is being used. I want to ensure that the recommendation for ALI can be implemented by a developer with commonly available skills. The purpose of this email is to start a conversation and find out where to ask questions and get help. Do you have any general advice on how to make implementing ODRL easy, and what is the best way to ask for help regarding ODRL?

Thank you,
Vincent

______________________________________________
Vincent M. Lizzi
Head of Information Standards | Taylor & Francis Group
530 Walnut St., Suite 850, Philadelphia, PA 19106
E-Mail: vincent.lizzi@taylorandfrancis.com<mailto:vincent.lizzi@taylorandfrancis.com>
Web: www.tandfonline.com<http://www.tandfonline.com/>

Taylor & Francis is a trading name of Informa UK Limited,
registered in England under no. 1072954

"Everything should be made as simple as possible, but not simpler."


Information Classification: General