Upload
stuart-myles
View
3.113
Download
0
Embed Size (px)
DESCRIPTION
Expressing permissions and restrictions for news content. IPTC has been working on a formal language for machine-readable expression of rights. This presentation reviews the requirements, the landscape of rights expression languages and the work we've been doing to establish a standard using ODRL and ACAP.
Citation preview
IPTC andRights Expression Languages
Stuart Myles
Associated Press
8th March 2011
© 2010 IPTC (www.iptc.org) All rights reserved 2
Rights Examples
• “No New York”• “Not for Yahoo”• “No Canada mobile”• “No sales”• “Any non-commercial use, requires attribution”• “No Internet/Mobile usage without Football
Association Premier League (FAPL) license”• “No mobile use until 2 hours after the match,
website users are obliged to comply with DFL restrictions”
Usage Rights and News
Looking at the examples of usage rights for news content, we see some common types of factors:
• Specific organizations• Types of organizations• Permitted or restricted actions (e.g. sales)• Required actions (e.g. attribution)• Time constraints• Geographic locations• Platforms (e.g. mobile)
© 2010 IPTC (www.iptc.org) All rights reserved 3
IPTC and Rights• In March 2010, we reviewed IPTC rights support
– NITF, NewsML 1, the G2 Family– Each offers semi-structured natural language statements
• Conclusion a machine-readable solution is required– Principally for use within the G2 family of standards
• IPTC would prefer to select an existing language, rather than developing a new REL entirely from scratch– We conducted a survey of IPTC members– We evaluated candidate languages and decided that ODRL was
the best option– We are working within ACAP v2 to create an ODRL Profile
© 2010 IPTC (www.iptc.org) All rights reserved 4
Rights Use Cases
• The survey was structured as five suggested use cases, to see if there was any commonality:– Four use cases concerning applying rights metadata within an
editorial system– One use case about rights metadata being sent from or received
from clients
• We got three responses, with little commonality• Interestingly, the main consensus was that the sending
and receiving rights metadata is important but that enforcement in editorial tools is not
• This appears to be contradictory– Why is it important to transmit rights if they aren’t to be acted
on?
© 2010 IPTC (www.iptc.org) All rights reserved 5
Rights Expression Language?• A machine-readable language to convey rights
associated with a piece of content• Automatically answer the question
– Can we use this content for this particular purpose?
• Rights:– Permissions and restrictions on the use of a piece of content– Granted by a rights holder to a user
• Basic Structure:– {Party A} grants {Party B} the right to {Action C} with {Item D}
under {Condition E}
© 2010 IPTC (www.iptc.org) All rights reserved 6
IPTC and Rights ExpressionsNewsML 1 and NITF support a
semi-structured model
© 2010 IPTC (www.iptc.org) All rights reserved 7
IPTC and Rights Expressions
© 2010 IPTC (www.iptc.org) All rights reserved 8
• The G2 standards (NewsML-G2 et al) have a RightsInfo block
• Allows natural language statements
• Different model than NITF or NewsML1
MPEG-21 / ISO REL
© 2010 IPTC (www.iptc.org) All rights reserved 9
MPEG-21 expresses requirements for a Rights Expression LanguageImplemented as ISO/IEC21000/5:2004
A relatively simple data model, implemented as XML
PLUS
• PLUS Licensing Data Format• Provides standard vocabularies for creating licenses• Similar data model to ISO REL and ODRL• Specific vocabularies aimed at publishers of images• PLUS has a relationship with IPTC
© 2010 IPTC (www.iptc.org) All rights reserved 10
CCREL
• Creative Commons• Grant of rights beyond “fair use”, to promote re-use• http://wiki.creativecommons.org/CC_REL• Widely implemented, used in certain Yahoo! and Google
applications (chiefly to find rights cleared content)
© 2010 IPTC (www.iptc.org) All rights reserved 11
ODRL v2
© 2010 IPTC (www.iptc.org) All rights reserved 12
The Core ODRL model supports permissions, restrictions and duties
http://odrl.net/2.0/DS-ODRL-Model.html
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)
© 2010 IPTC (www.iptc.org) All rights reserved 13
ODRL and ACAP
• ACAP v2 has been developing a set of news vocabularies for use in the ODRL v2 framework– Principle participants have been AP, Getty, NLA, WSJ– Not too late to join…
• ODRL v2 and ACAP v2 are on track to complete by early Q3– NLA and AP each preparing experimental implementations
• To see the current status– Sign up to the ODRL/ACAP wiki– http://odrl.net/wiki/tiki-index.php?page=ACAP+Profile
© 2010 IPTC (www.iptc.org) All rights reserved 14