IPTC's Rights Expression Language Working Group discusses how to express machine-readable rights for news using RightsML and ODRL.

1. IPTCRights Expression LanguageWorking Group Stuart Myles Associated Press 5th October 2011

2. Rights 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 Traditionally, restrictions are human-readable text Such as special instructions or in captions, scripts Need to be suppressed before display, can skew autocoding Machine-readable rights are required Fewer editors touch content before it is published to consumers Technology changes - increased use of APIs Sophisticated combinations of permissions and restrictions © 2010 IPTC (www.iptc.org) All rights reserved 2

3. © 2010 IPTC (www.iptc.org) All rights reserved 3 Rights Examples “No New York” “Not for Yahoo” “No Canada mobile” “No sales” “Any non-commercial use, requires attribution” “No Internet/Mobile usage without Football Association Premier League (FAPL) license” “No mobile use until 2 hours after the match, website users are obliged to comply with DFL restrictions”

4. Usage Rights and News Looking at the examples of usage rights for news content, we see some common types of factors: Specific organizations Types of organizations Permitted or restricted actions (e.g. sales) Required actions (e.g. attribution) Time constraints Geographic locations Platforms (e.g. mobile) © 2010 IPTC (www.iptc.org) All rights reserved 4

5. Rights Expression Language? A machine-readable language to convey rights associated with a piece of content Automatically answer the question Can we use this content for this particular purpose? Rights: Permissions and restrictions on the use of a piece of content Granted by a rights holder to a user Basic Structure: {Party A} grants {Party B} the right to {Action C} with {Item D} under {Condition E} © 2010 IPTC (www.iptc.org) All rights reserved 5

6. IPTC and Rights In March 2010, IPTC reviewed rights support Looked at NITF, NewsML 1, the G2 Family Each offers semi-structured natural language statements Conclusion: a machine-readable solution is required IPTC decided to select an existing language, rather than developing a new REL entirely from scratch We evaluated candidate languages and selected ODRL IPTC worked with ACAP to create an ODRL Profile IPTC took over ACAP June 2011 ODRL became a W3C Community Group © 2010 IPTC (www.iptc.org) All rights reserved 6

7. The ODRL Approach Core model The basic framework for expressing rights and restrictions Domain-specific vocabularies Specific actions or constraints Designed to be used by a particular industry Terms and their definitions Common vocabulary Designing a vocabulary that is not aimed at a specific vertical Based on other RELs, including PLUS Encoding Expressing ODRL in XML, RDF (perhaps JSON, microformats) © 2010 IPTC (www.iptc.org) All rights reserved 7

8. ODRL v2 © 2010 IPTC (www.iptc.org) All rights reserved 8 The Core ODRL model supports permissions, restrictions and duties http://odrl.net/2.0/DS-ODRL-Model.html

9. RightsML 1.0 RightsML 1.0 is a profile of ODRL 2.0 Aimed specifically at the b2b news syndication use case Developed within ACAP, principle participants were AP, NLA, Getty, WSJ, IPTC RightsML 1.0 circulated in RightsML_1.0-spec_1D6 Specifies a subset of the ODRL v2 Common Vocabulary Specifies RightsML 1.0 Vocabulary Extension mechanisms for certain attributes Can be embedded within content (e.g. G2, ATOM) or stand alone © 2010 IPTC (www.iptc.org) All rights reserved 9

10. RightsML 1.0 Actions aggregate annotate attribute delete derive / modify display / present export / transform extract give include © 2010 IPTC (www.iptc.org) All rights reserved 10 index inform nextPolicy obtainConsent pay play / present print share translate

11. RightsML 1.0 Example © 2010 IPTC (www.iptc.org) All rights reserved 11 The Assignee is permitted to copy the Asset, but this entails a one-off Duty to obtain a license to do so before the Asset is copied.

12. RightsML MOTION – Standards Committee To adopt RightsMLversion 0.9 as specified by the document RightsML_1.0-spec_1D6 © 2010 IPTC (www.iptc.org) All rights reserved 12

13. Any Other Business? © 2010 IPTC (www.iptc.org) All rights reserved 13

14. Date and Place of Next Meeting London 19th – 21st March, 2012 Dankeund auf Wiedersehen! © 2010 IPTC (www.iptc.org) All rights reserved 14