The document discusses RightsML, a standard developed by IPTC to express rights and permissions for digital content in a machine-readable format. It proposes launching RightsML in an experimental phase to get feedback from publishers on whether the current vocabulary adequately captures the rights needed and if partners can express and process those rights. The IPTC Rights Working Group will vote on adopting version 1.0 of RightsML and starting the experimental phase. Publishers are encouraged to try implementing RightsML during this phase and provide input to help IPTC improve the standard.

1. Rights Expression Language
Working Group
Stuart Myles
18th March 2012

2. IPTC Rights Working Group
• The business needs for rights expression
• The RightsML 1.0 experimental phase
© 2012 IPTC (www.iptc.org) All rights reserved 2

3. 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
© 2012 IPTC (www.iptc.org) All rights reserved 3

4. Traditional Publishing
A feed per publication
A tuned
Licensed
content
for one
set
outlet
Editors
Often by review
media notes
type

5. One Publishing House
With many publications
Content still Newspapers, ma
licensed per gazines, broadc
outlet ast channels
Websites
and apps for
Content
desktop, sm
duplication
artphone, ta
blet
Enshrines
legacy
relationships

6. Most Publishing House
Take Content from Multiple Providers
Lots of
complexity
and waste for
publishers and
providers.
Harder for
publishers to
respond to
new
opportunities

7. RightsML Enables Automated
Publishing That Respects Rights
Automatically
Content still route content
licensed per
outlet
Less editorial
intervention to
check
No content restrictions
duplication
Apply New uses for
restrictions content without
per content a duplicate
item feed

8. Not Just Feeds:
APIs
Content still
licensed per
outlet
One API
key rather
than one
per outlet
Apply
restrictions
per content
item

9. RightsML
RightsML is an IPTC standard, based on ODRL
IPTC took over ACAP, renamed ACAPv2 “RightsML”
http://developer.iptc.org/RightsML
ODRL now part of W3C
http://www.w3.org/community/odrl
Express permissions, restrictions and duties
Derived from media industry requirements
Mainly from AP, NLA, Getty, WSJ, Newsright
Can be embedded within content (e.g. G2, ATOM) or stand alone

10. 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)
© 2012 IPTC (www.iptc.org) All rights reserved 10

11. ODRL v2
The Core ODRL model supports permissions, restrictions and duties
http://www.w3.org/community/odrl/two/model/
© 2012 IPTC (www.iptc.org) All rights reserved 11

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

13. RightsML 1.0 Example
• 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.
© 2012 IPTC (www.iptc.org) All rights reserved 13

14. How Can You Take the Plunge into RightsML?

15. We Propose to Launch the
RightsML “Experimental Phase”
http://dev.iptc.org/RightsML

16. RightsML Experimental Phase
1. Publishers try RightsML
2. Give IPTC feedback
3. IPTC adjusts RightsML
Adequate vocabularies?
Rights, Restrictions, Duties
Can partners express and
process the rights they need?
How can IPTC make RightsML
better?
http://dev.iptc.org/RightsML

17. RightsML Conference Calls
© 2012 IPTC (www.iptc.org) All rights reserved 17

18. RightsML
MOTION – Standards Committee
Vote on Wednesday
To adopt RightsML version 1.0
as specified by the document
RightsML_1.0EP1-spec_1
and launch an experimental phase
© 2012 IPTC (www.iptc.org) All rights reserved 18

19. Date and Place of Next Meeting
New York
11 - 13 June, 2012
Thank you!
© 2012 IPTC (www.iptc.org) All rights reserved 19