Rights Expression LanguageWorking Group

Stuart Myles

18th March 2012

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

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

Traditional PublishingA feed per publication

A tuned content

set

Licensed for one outlet

Editors review notes

Often by media type

One Publishing HouseWith many publications

Content still licensed per

outlet

Newspapers, magazines, broadcast channels

Websites and apps for

desktop, smartphone,

tablet

Content duplication

Enshrines legacy

relationships

Most Publishing HouseTake Content from Multiple Providers

Lots of complexity

and waste for publishers and

providers.

Harder for publishers to respond to

new opportunities

RightsML Enables Automated Publishing That Respects Rights

Content still licensed per

outlet

Automatically route content

Less editorial intervention to

check restrictionsNo content

duplication

Apply restrictions per content

item

New uses for content without

a duplicate feed

Not Just Feeds:APIs

Content still licensed per

outlet

One API key rather than one per outlet

Apply restrictions per content

item

RightsML

RightsML is an IPTC standard, based on ODRLIPTC 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 dutiesDerived from media industry requirements

Mainly from AP, NLA, Getty, WSJ, Newsright

Can be embedded within content (e.g. G2, ATOM) or stand alone

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

ODRL v2

© 2012 IPTC (www.iptc.org) All rights reserved 11

The Core ODRL model supports permissions, restrictions and duties

http://www.w3.org/community/odrl/two/model/

RightsML 1.0 Actions

• aggregate • annotate • attribute • delete • derive / modify • display / present • export / transform • extract • give • include

© 2012 IPTC (www.iptc.org) All rights reserved 12

• index• inform • nextPolicy • obtainConsent • pay • play / present • print • share • translate

RightsML 1.0 Example

© 2012 IPTC (www.iptc.org) All rights reserved 13

• 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.

How Can You Take the Plunge into RightsML?

We Propose to Launch theRightsML “Experimental Phase”

http://dev.iptc.org/RightsML

RightsML Experimental Phase1. Publishers try RightsML

2. Give IPTC feedback3. 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

RightsML Conference Calls

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

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

Date and Place of Next Meeting

New York

11 - 13 June, 2012

Thank you!

© 2012 IPTC (www.iptc.org) All rights reserved 19