2. RightsML
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
RightsML is an IPTC standard, based on ODRL
http://dev.iptc.org/RightsML
http://www.w3.org/community/odrl
Express machine readable 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
Designed for automatic evaluation
3. Traditional Publishing
A feed per publication
A tuned
Licensed
content
for one
set
outlet
Editors
Often by review
media notes
type
4. One Publishing House
With many publications
Newspapers,
Content still
magazines,
licensed per
broadcast
outlet
channels
Websites
and apps for
Content
desktop,
duplication
smartphone,
tablet
Enshrines
legacy
relationships
5. 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
6. 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
7. Not Just Feeds:
APIs
Content still
licensed per
outlet
One API
key rather
than one
per outlet
Apply
restrictions
per content
item
11. At the Last Meeting We Launched the
RightsML “Experimental Phase”
http://dev.iptc.org/RightsML
12. 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