Developing and Applying Rights Expressions Using ODRL and RightsML: 3 Dilemmas, 3 Adoption Strategies

560 views
490 views

Published on

Developing and Applying Rights Expressions Using ODRL and RightsML: Three Dilemmas and Three Adoption Strategies

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

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

No notes for slide

Developing and Applying Rights Expressions Using ODRL and RightsML: 3 Dilemmas, 3 Adoption Strategies

  1. 1. Developing and Applying Rights Expressions Using ODRL and RightsML Three Dilemmas Three Adoption Strategies 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’s RightsML experimental phase has revealed Three Dilemmas andThree Adoption Strategiesrightsml.org @smyles
  7. 7. Dilemma #1 A general purpose REL? or A news industry specific REL? Does more control mean less risk? Are the needs of the news industry actually that specific? (What is the news industry?)ODRL quite willing to incorporate feedback into the core vocabularyrightsml.org @smyles
  8. 8. Dilemma #2 Sophistication (too complex)? or Simplicity (too simplistic)? Permissions, restrictions and duties can get quite complex A complicated-looking standard is a hurdle for adoptionrightsml.org @smyles
  9. 9. Dilemma #3 Tool support paves the way for adoption but Vendors are loathe to implement a new standard There’s more than one standard already for rights expression Is it better to back an inferior but somewhat adopted REL? Or to promote a superior but unknown REL?rightsml.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

×