Update on rights for publishers - including the roadmap for RightsML, software to automatically evaluate rights and W3C's plans for the POE group.

1. Rights Expression Working Group
Stuart Myles * Associated Press * 7th March 2016
© 2016 IPTC (www.iptc.org) All rights reserved
https://flic.kr/p/81HXTG
http://dev.iptc.org/RightsML
iptc-rightsml-dev@yahoogroups.com

2. RightsML
Publishers need to express rights on the uses of content
Often need to enforce rights on behalf of 3rd parties
Clients need to know permissions and restrictions
Rights are a key criteria for selecting content
RightsML is an IPTC standard, based on ODRL
http://dev.iptc.org/RightsML
http://www.w3.org/community/odrl
Express machine readable permissions, restrictions and duties
Derived from media industry requirements
Including AP, TR, NLA, Getty, WSJ, Newsright
Implemented by AP in XML and JSON
http://www.slideshare.net/smyles/iptcap-rights-api201506stuartmyles
© 2016 IPTC (www.iptc.org) All rights reserved

3. IPTC Rights Roadmap
• Photo and Video binaries
– Latest IPTC Photo Metadata update allows for rights policies
– Implementation guide for embedding policy IDs in XMP
• Rights evaluation engines
– Some open source software exists for representing ODRL
– Creating an open source evaluation engine
• Identifiers
– For content items, rights holders, other involved parties
– Which will work across organizational boundaries
• Rights statements
– Reusable packages of rights
– Human readable descriptions and additional metadata

4. Rights in Binaries
• Rights metadata for photo and video
– An id linking to a registry with rights metadata
– Embedding rights metadata directly in binaries
• IPTC updated photo metadata to support both
– Embedded metadata has an indication of the encoding scheme
• IPTC recommendation is ODRL in JSON
– Easy to embed in XMP - unlike RDF or XML (we tried)
• All the technical pieces are there
– Now we plan to write the guidelines for providers and clients
© 2016 IPTC (www.iptc.org) All rights reserved 4

5. Rights Evaluation Engine
• Reference implementation of an evaluation engine
– http://dev.iptc.org/RightsML-Implementation-Guide
– http://dev.iptc.org/RIghtsML-Processing-Model
• Proposal to build JSON API built on top of licensed
– https://github.com/iptc/rightsml-dev/tree/master/licensed
– http://www.slideshare.net/smyles/licensed-the-open-source-
rightsml-engine
• Demo
© 2016 IPTC (www.iptc.org) All rights reserved 5

6. Identifiers
• Standardization for interoperability
• Decentralization for agility
• ODRL’s Common Vocabulary
– Actions, Constraints, Party Roles
• What schemes should IPTC create or recommend?
– Assets
– Content creators
– Rights holders
– Client organizations (parts of organizations)
– Geography – beyond ISO 3166-1 and 3166-2
© 2016 IPTC (www.iptc.org) All rights reserved 6

7. Beyond Policies:
Rights Statements
• RightsML is aimed precisely at describing policies
– Machine readable permissions, restrictions and duties
• But what about everything else, such as …
– Human readable descriptions
– Re-usable packages of rights
– Links between sets of rights
• rightsstatements.org Europeana, DPLA
– For licensing and reuse of cultural objects
– Directly incorporates ODRL ontology
• Should IPTC create and/or host news rights statements?
© 2016 IPTC (www.iptc.org) All rights reserved 7

8. W3C POE
• W3C Permissions and Obligations Expression WG
– https://www.w3.org/2016/poe/wiki/Main_Page
– https://www.w3.org/2016/poe/charter
• What does this mean for ODRL?
– ODRL being “only” a CG has been a barrier for some
– Stated intent is to formalize ODRL 2.1 specs
– Due date is December 2017
– ODRL Community Group will live on
• What does this mean for RightsML?
– Initial meeting was very positive
© 2016 IPTC (www.iptc.org) All rights reserved 8

9. Date and Place of Next Meeting
Stockholm, Sweden 13 – 15 June 2016
https://flic.kr/p/tgYcsA
‫خيرا‬ ‫هللا‬ ‫جزاكم‬
© 2016 IPTC (www.iptc.org) All rights reserved 9
https://flic.kr/p/81HXTG