IPTC Rights Expression Working Group 2013 June AGM


Published on

Rights expression for the news industry, using RightsML and ODRL. Updates on the IPTC's Machine Readable Rights Day and the Rights 1.0 spec. Plus documentation and examples of using RightsML and the work so far to embed rights in photo binaries, using JSON.

Published in: Technology, News & Politics
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

IPTC Rights Expression Working Group 2013 June AGM

  1. 1. Rights Expression Working GroupStuart Myles * Associated Press * 24th June 2013http://www.flickr.com/photos/anirudhkoul/3536413126/
  2. 2. Machine Readable Rights and theNews Industry• Rights day as part of IPTC’s Amsterdam meeting• Good mix of people– technologists, standards bearers, photographers, lawyers ...• Particular focus on photo metadata• Embedding rights or use an identifier to link to a registry?• Various consortia trying to tackle rights– LCC, PLUS, CEPIC ...• Summary of meeting, presentations, videoshttp://www.iptc.org/goto?rights2013© 2013 IPTC (www.iptc.org) All rights reserved 2
  3. 3. RightsMLPublishers need to express rights on the uses of contentOften need to enforce rights on behalf of 3rd partiesClients need to know permissions and restrictionsRights are a key criteria for selecting contentRightsML is an IPTC standard, based on ODRLhttp://dev.iptc.org/RightsMLhttp://www.w3.org/community/odrlMachine processable permissions, restrictions and dutiesDerived from media industry requirementsCan be embedded within content (e.g. G2, ATOM) or stand aloneDesigned for automatic evaluation
  4. 4. ODRL v2© 2013 IPTC (www.iptc.org) All rights reserved 4The Core ODRL model supports permissions, restrictions and dutieshttp://www.w3.org/community/odrl/two/model/
  5. 5. ODRL Encoding© 2013 IPTC (www.iptc.org) All rights reserved 5The ODRL model is designed to be encoded in various formatsSo far, only the XML encoding has been standardizedhttp://www.w3.org/community/odrl/two/xml/Experiments in RDF / OWLhttp://www.w3.org/community/odrl/wiki/SemanticWebAnd JSONhttp://www.w3.org/community/odrl/work/json/
  6. 6. Driving Adoption• How do we drive adoption of RightsML?• Finish the RightsML 1.0 spec• Provide examples and templates• Solve RightsML in binaries© 2013 IPTC (www.iptc.org) All rights reserved 6
  7. 7. Finish the RightsML 1.0 Spec• Updated RightsML 1.0 Experimental Phase draft– RightsML_1.0EP1-revisionDRAFTclean+dirty_2013-06-19.pdf• Clarify relationship between ODRLv2 and RightsML 1.0– RightsML as a standard– RightsML as an implementation guide– Founded on ODRL, but only need to read RightsML docs• Validating RightsML 1.0– ODRL XSD alone is insufficient– We propose to also validate vocabularies and business rules• Probably using Schematron http://www.schematron.com/spec.html© 2013 IPTC (www.iptc.org) All rights reserved 7
  8. 8. Examples and Templates• Documentation and examples– http://dev.iptc.org/RightsML– http://dev.iptc.org/RightsML-10-Implementation-Examples– Spec is important but implementation is often by copying theexamples• Additional restrictions examples being developed– Geography– Time– Distribution channel– Default “read the editors’ notes”• MRR Survey– http://www.surveymonkey.com/s/iptcmrr2013© 2013 IPTC (www.iptc.org) All rights reserved 8
  9. 9. Rights in Binaries• Clear theme: rights metadata for photos– An id linking to a registry with rights metadata is one approach– Embedding rights metadata in binaries needs to be supported• IPTC experimented with embedding ODRL in XMP– Quickly determined that XMP won’t support arbitrary RDF– We toyed with using double-escaped XML• But concluded that it was a bit inelegant• Express ODRL model (and hence RightsML) in JSON– Work within W3C ODRL Community Group– http://www.w3.org/community/odrl/work/json/© 2013 IPTC (www.iptc.org) All rights reserved 9
  10. 10. ODRL in JSON: An Initial Draft{ "Permission":["Asset":[{"id":"as1","uid":"http://example.com/music:1234908","relation":"http://w3.org/ns/odrl/vocab#target"}],"Action":{"id":"ac1","name":"http://w3.org/ns/odrl/vocab#play"},"Constraint":[{"name":"http://w3.org/ns/odrl/vocab#spatial","operator":"http://w3.org/ns/odrl/vocab#eq","rightOperand":"http://www.itu.int/tML/tML-ISO-3166:it"}],"Party":[{"id":"p1","uid":"http://example.com/sony:10","function":"http://w3.org/ns/odrl/vocab#assigner"},{"id":"p2","uid":"http://example.com/billie:888","function":"http://w3.org/ns/odrl/vocab#assignee"}],],"Prohibition":["Asset":[{"idref":"as1"}],"Action":{"idref":"ac1"},"Constraint":[{"name":"http://w3.org/ns/odrl/vocab#spatial","operator":"http://w3.org/ns/odrl/vocab#eq","rightOperand":"http://www.itu.int/tML/tML-ISO-3166:fr"}],"Party":[{"idref":"p1"},{"idref":"p2"}]]}http://www.w3.org/community/odrl/work/json/© 2013 IPTC (www.iptc.org) All rights reserved 10
  11. 11. Date and Place of Next MeetingWashington, DC 21 - 23 October, 2013http://www.flickr.com/photos/pcscheid/4351707431/Merci et à bientôt!© 2013 IPTC (www.iptc.org) All rights reserved 11