ODRL and RightsML: Permissions and Restrictions for the Publishing Industry

724 views
654 views

Published on

Three principles and three adoption strategies for ODRL and RightsML. Presented at IPTC's March 13th 2013 conference on Machine Readable Rights http://www.iptc.org/goto?rights2013

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
724
On SlideShare
0
From Embeds
0
Number of Embeds
6
Actions
Shares
0
Downloads
3
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

ODRL and RightsML: Permissions and Restrictions for the Publishing Industry

  1. 1. ODRL and RightsML Permissions and Restrictions for the Publishing Industry Stuart Myles The Associated Pressrightsml.org @smyles
  2. 2. rightsml.org @smyles
  3. 3. rightsml.org @smyles
  4. 4. The News Industry Needs Machine Readable Rights Increasing automation of workflows Less opportunity for editors to read notes, the traditional means of indicating restrictions and duties Sophisticated publishing relationships Fewer single purpose, static connectionsMore (need for) flexible, ad hoc uses of content which respect rights IPTC decided to tackle rights expressionrightsml.org @smyles
  5. 5. IPTC RightsML Founded on ODRL Open Digital Rights Language 2.0 Selected by IPTC after evaluating several alternatives http://www.w3.org/community/odrl/RightsML is a news industry specific vocabulary Plugs into ODRL framework RighstML 1.0 currently in an “experimental phase” http://rightsml.org http://linkedcontentcoalition.orgrightsml.org @smyles
  6. 6. IPTC RightsML Three Principles andThree Adoption Strategiesrightsml.org @smyles
  7. 7. Principle #1 A publishing specific REL and Don’t reinvent the wheel The needs of the publishing industry are not entirely unique (What is the publishing industry?)ODRL quite willing to incorporate feedback into the core vocabulary Tool support paves the way for adoption Vendors are loathe to adopt yet another standardrightsml.org @smyles
  8. 8. Principle #2 Support today’s restrictions and Build for likely future requirements IPTC examined many existing rights expressions Translated from editor’s notes into machine readable form Extrapolated likely future needs and extensionsrightsml.org @smyles
  9. 9. Principle #3 Sophisticated (not too complex) and Simple (not too simplistic) Permissions, restrictions and duties can get quite complex A complicated-looking standard is a hurdle for adoptionrightsml.org @smyles
  10. 10. Adoption Strategy #1 Start at the edge If you have any kind of structured rights expression internally Map your internal rights mechanisms into RightsML At the point of delivery to clientsrightsml.org @smyles
  11. 11. Adoption Strategy #2 Start in the middle You need to handle rights internally Adopt RigthsML for your own rights clearance mechanismsrightsml.org @smyles
  12. 12. Adoption Strategy #3 Start somewhere Not everything needs to be converted at the same time You can gain value from working with Particular media types Particular customer types Start somewhere and grow the adoptionrightsml.org @smyles
  13. 13. Thank yourightsml.org @smyles

×