1 / 69

Rights Metadata: XrML and ODRL for Digital Video

Rights Metadata: XrML and ODRL for Digital Video. Mairéad Martin University of Tennessee Doug Pearson Indiana University August 15, 2001. Overview. Digital Rights Management: Definition and current landscape XrML ODRL Q&A. SEAM: Secure Econtent Attribute Management.

heller
Télécharger la présentation

Rights Metadata: XrML and ODRL for Digital Video

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Rights Metadata: XrML and ODRL for Digital Video Mairéad Martin University of Tennessee Doug Pearson Indiana University August 15, 2001

  2. Overview • Digital Rights Management: Definition and current landscape • XrML • ODRL • Q&A

  3. SEAM: Secure Econtent Attribute Management • Goal: To develop a dynamic, portable and granular rights management tool that will ensure the security and integrity of digital objects • Integrates XML-based rights language, digital objects, and digital access technologies

  4. Digital Rights Management • Management vs. enforcement of rights • “Digital management of rights” vs. “Management of digital rights” • Players: <Indecs>,W3C, EBX, MPEG, ContentGuard, IPR Systems

  5. DRM Definition “DRM involves the description, layering, analysis, valuation, trading and monitoring of an enterprise’s assets; both in physical and digital form; and of tangible and intangible value.” - Renato Ianella, ODRL Version: 0.9

  6. DRM Languages • eXtensible Rights Markup Language (XrML) • Open Digital Rights Language (ODRL) • Extensible Media Commerce Language (XCML)

  7. Rights Language Requirements • Applicable and interoperable across media • Integration with descriptive metadata • Extensible • Efficient in open or trusted systems • Supports modularity and granularity • Capacity to be integrated with trust and tracking systems • Open and non-proprietary

  8. What is XrML? • eXtensible rights Markup Language • “A language in XML for describing specification of rights, fees and conditions for using digital contents (or properties), together with message integrity and entity authentication within these specifications.”

  9. Intent of XrML • “[XrML] is intended to support commerce in digital contents, that is, publishing and selling electronic books, digital movies, digital music, interactive games, computer software and other creations distributed in digital form. It is also intended to support specification of access and use controls for secure digital objects in cases were financial exchange is not part of the terms of use.”

  10. Trusted Systems • XrML enables trusted systems to exchange digital contents and interoperate. • A trusted system is a server, player or other device for holding or accessing digital content, which can be trusted to honor the rights, conditions and fees specified for digital contents.

  11. Who Controls XrML? • XrML is licensed to the industry royalty-free by the developer, ContentGuard, Inc. • ContentGuard is a spin-off from Xerox; with strategic alliances and investment from Xerox and Microsoft. Xerox is the majority investor. • Microsoft considers XrML a key component of its DRM strategy.

  12. Who’s using XrML? • Microsoft uses XrML to specify rights and content descriptions for licensing eBooks. The Microsoft Digital Asset Server uses the rights and content descriptions to issue a personalized LIT file to the consumer’s Microsoft Reader.

  13. http://www.xrml.org/about.htm “XrML -The Technology Standard for Trusted Systems…” “A mature eContent marketplace requires a standard language…” “XrML - forging the standard on which the eContent industry depends” “Trusted systems require a standard. That standard – XrML…” “Meeting the criteria demanded of an openstandard…” “An industry standard for creation of terms and conditions associated with the use and protection of eContent, XrML is licensed on a royalty-free basis…”

  14. Is XrML an Open Standard? • ContentGuard declares commitment to “promoting and supporting a standard language that will enable content creators, providers, distributors and retailers to express rights and specifications…”

  15. Is XrML an Open Standard? Guiding Principles: • Enable XrML to meet the needs of all stakeholders in the eContent industry • Establish a community of practice committed to develop a common rights language • Enable interoperability • Encourage interested parties to submit and share XrML Mods with the community of practice

  16. Is XrML an Open Standard? • XrML is not an “open standard”. • Rather, XrML is an attempt to build an industry standard with a published specification and encouragement to a community of practice.

  17. ContentGuard Patents • "System for Controlling the Distribution and Use of Digital Works Using Digital Tickets." (US Patent 6,236,971) • "System for Controlling the Distribution and Use of Digital Work Having Attached Usage Rights Where the Usage Rights are Defined by a Usage Rights Grammar" (US Patent 5,715,403) • "System for Controlling the Distribution and Use of Composite Digital Works" (US Patent 5,638,443) • "System for Controlling the Distribution and Use of Digital Works Having a Free Reporting Mechanism" (US Patent 5,634,012) • "System for Controlling the Distribution and Use of Digital Works" (US Patent 5,629,980) • "Interactive Contents Revealing Storage Device" (US Patent 5,530,235) • "System for Controlling the Distribution and Use of Rendered Digital Works through Watermarking" (US Patent 6,233,684)

  18. <XrML> <BODY> (ISSUED)? (TIME)? (DESCRIPTOR)? (ISSUER)? (ISSUEDPRINCIPALS)? (WORK)? (AUTHENTICATEDATA)? </BODY> (SIGNATURE)? </XrML>

  19. <XrML> <BODY> (ISSUED)? (TIME)? (DESCRIPTOR)? (ISSUER)? (ISSUEDPRINCIPALS)? (WORK)? (AUTHENTICATEDATA)? </BODY> (SIGNATURE)? </XrML> Within the root XrML is a mandatory element BODY and an optional element SIGNATURE.

  20. <XrML> <BODY> (ISSUED)? (TIME)? (DESCRIPTOR)? (ISSUER)? (ISSUEDPRINCIPALS)? (WORK)? (AUTHENTICATEDATA)? </BODY> (SIGNATURE)? </XrML> SIGNATURE is the digital signature to insure integrity of the XRML specification

  21. <XrML> <BODY> (ISSUED)? (TIME)? (DESCRIPTOR)? (ISSUER)? (ISSUEDPRINCIPALS)? (WORK)? (AUTHENTICATEDATA)? </BODY> (SIGNATURE)? </XrML> BODY consists of an optional description of the digital WORK and some optional metadata about the XrML document.

  22. <XrML> <BODY> (ISSUED)? (TIME)? (DESCRIPTOR)? (ISSUER)? (ISSUEDPRINCIPALS)? (WORK)? (AUTHENTICATEDATA)? </BODY> (SIGNATURE)? </XrML> ISSUED is the time at which the the XrML document was issued.

  23. <XrML> <BODY> (ISSUED)? (TIME)? (DESCRIPTOR)? (ISSUER)? (ISSUEDPRINCIPALS)? (WORK)? (AUTHENTICATEDATA)? </BODY> (SIGNATURE)? </XrML> TIME is the time interval over which the XrML document is valid.

  24. <XrML> <BODY> (ISSUED)? (TIME)? (DESCRIPTOR)? (ISSUER)? (ISSUEDPRINCIPALS)? (WORK)? (AUTHENTICATEDATA)? </BODY> (SIGNATURE)? </XrML> DESCRIPTOR is a description of the XrML document – what this document represents.

  25. <XrML> <BODY> (ISSUED)? (TIME)? (DESCRIPTOR)? (ISSUER)? (ISSUEDPRINCIPALS)? (WORK)? (AUTHENTICATEDATA)? </BODY> (SIGNATURE)? </XrML> ISSUER is the principle who issues the XrML document.

  26. <XrML> <BODY> (ISSUED)? (TIME)? (DESCRIPTOR)? (ISSUER)? (ISSUEDPRINCIPALS)? (WORK)? (AUTHENTICATEDATA)? </BODY> (SIGNATURE)? </XrML> ISSUED-PRINCIPALS is a list of the principals the XrML document is issued to.

  27. <XrML> <BODY> (ISSUED)? (TIME)? (DESCRIPTOR)? (ISSUER)? (ISSUEDPRINCIPALS)? (WORK)? (AUTHENTICATEDATA)? </BODY> (SIGNATURE)? </XrML> AUTHENTICATE-DATA captures data which is necessary for an application which processes a XrML document.

  28. <XrML> <BODY> (ISSUED)? (TIME)? (DESCRIPTOR)? (ISSUER)? (ISSUEDPRINCIPALS)? (WORK)? (AUTHENTICATEDATA)? </BODY> (SIGNATURE)? </XrML> WORK defines a digital work and its usage rights.

  29. <WORK> (OBJECT) (DESCRIPTION)? (CREATOR)? (OWNER)? (DIGEST)? (PARTS)? (CONTENTS)? (COPIES)? (COMMENT)? (SKU)? (RIGHTSGROUP | REFERENCEDRIGHTSGROUP)+ </WORK>

  30. <WORK> (OBJECT) (DESCRIPTION)? (CREATOR)? (OWNER)? (DIGEST)? (PARTS)? (CONTENTS)? (COPIES)? (COMMENT)? (SKU)? (RIGHTSGROUP | REFERENCEDRIGHTSGROUP)+ </WORK> OBJECT identifies the digital object of the WORK through a unique identifier such as ISBN or ISSN number.

  31. <WORK> (OBJECT) (DESCRIPTION)? (CREATOR)? (OWNER)? (DIGEST)? (PARTS)? (CONTENTS)? (COPIES)? (COMMENT)? (SKU)? (RIGHTSGROUP | REFERENCEDRIGHTSGROUP)+ </WORK> Self explanatory.

  32. <WORK> (OBJECT) (DESCRIPTION)? (CREATOR)? (OWNER)? (DIGEST)? (PARTS)? (CONTENTS)? (COPIES)? (COMMENT)? (SKU)? (RIGHTSGROUP | REFERENCEDRIGHTSGROUP)+ </WORK> DIGEST uses a cryptographic digest value of the work to insure integrity and originality of the work.

  33. <WORK> (OBJECT) (DESCRIPTION)? (CREATOR)? (OWNER)? (DIGEST)? (PARTS)? (CONTENTS)? (COPIES)? (COMMENT)? (SKU)? (RIGHTSGROUP | REFERENCEDRIGHTSGROUP)+ </WORK> PARTS specifies a list of works that are included as part of this WORK.

  34. <WORK> (OBJECT) (DESCRIPTION)? (CREATOR)? (OWNER)? (DIGEST)? (PARTS)? (CONTENTS)? (COPIES)? (COMMENT)? (SKU)? (RIGHTSGROUP | REFERENCEDRIGHTSGROUP)+ </WORK> CONTENTS gives the starting and stopping addresses which the rights in the WORK specification apply.

  35. <WORK> (OBJECT) (DESCRIPTION)? (CREATOR)? (OWNER)? (DIGEST)? (PARTS)? (CONTENTS)? (COPIES)? (COMMENT)? (SKU)? (RIGHTSGROUP | REFERENCEDRIGHTSGROUP)+ </WORK> COPIES specifies the number of copies of the digital work. It’s possible to transfer or loan a copy while exercising other rights on remaining copies.

  36. <WORK> (OBJECT) (DESCRIPTION)? (CREATOR)? (OWNER)? (DIGEST)? (PARTS)? (CONTENTS)? (COPIES)? (COMMENT)? (SKU)? (RIGHTSGROUP | REFERENCEDRIGHTSGROUP)+ </WORK> Stock Keeping Unit. Is included for extensibility; typically for use by retailer or distributor.

  37. <WORK> (OBJECT) (DESCRIPTION)? (CREATOR)? (OWNER)? (DIGEST)? (PARTS)? (CONTENTS)? (COPIES)? (COMMENT)? (SKU)? (RIGHTSGROUP | REFERENCEDRIGHTSGROUP)+ </WORK> Rights specification.

  38. <RIGHTSGROUP> (COMMENT)? (BUNDLE)? (RIGHTSLIST) </RIGHTGROUP> One or more RIGHTSGROUP may exist; according to logical collections of rights for groups of users.

  39. <RIGHTSGROUP> (COMMENT)? (BUNDLE)? (RIGHTSLIST) </RIGHTGROUP> Each right may separately specify parameters such as time limits, fees, access conditions. Shared parameters may be bundled.

  40. <!ELEMENT RIGHTSLIST (( COPY | TRANSFER | LOAN | PLAY | PRINT | EXPORT | VIEW | EDIT | EXTRACT | EMBED | BACKUP | RESTORE | VERIFY | FOLDER | DIRECTORY DELETE | INSTALL | UNINSTALL )+)>

  41. Classification of rights: Transport Render Derivative Work File Management Configuration

  42. Classification of rights: Transport Render Derivative Work File Management Configuration Governs the creation and movement of persistent copies of a work under the control of trusted repositories COPY – create a new copy of a work TRANSFER – an existing authorized copy moves to another repository LOAN – loan a copy for a period of time

  43. Classification of rights: Transport Render Derivative Work File Management Configuration Governs the creation of representations of a digital work outside of the control of trusted systems. PLAY – make an ephemeral copy available for use PRINT – make permanent copies to external media EXPORT – makes a digital source copy available outside of trusted system control

  44. Classification of rights: Transport Render Derivative Work File Management Configuration Governs the reuse of a digital work, in whole or part, to create a new composite work. Not intended to cover all possible forms of reuse; rather automate the simple case where the rights owner can pre-determine fees and repository-testable conditions on a work. EXTRACT, EDIT AND EMBED

  45. Classification of rights: Transport Render Derivative Work File Management Configuration Governs access to directory and file information in operations when two repositories are connected. E.g. when exercising rights that engage multiple repositories, such as TRANSFER or LOAN. Also, controls the making and restoring of backup copies. FOLDER, DIRECTORY, DELETE, VERIFY, BACKUP

  46. Classification of rights: Transport Render Derivative Work File Management Configuration Governs the adding and removing of system software from secure repositories. INSTALL, UNINSTALL

  47. <!ENTITY % termConditions “(TIME | ACCESS | FEE | TERRITORY | TRACK)+”>

  48. XrML Definition for Microsoft eBook Scenario: On August 9, I purchased and downloaded a Microsoft Reader formatted eBook, Telecosm by George Gilder, from Amazon. The following XrML was included inside the .LIT file.

  49. <XrML> <BODY type="LICENSE" version="2.0"> <ISSUED>2001-08-09T19:27</ISSUED> <DESCRIPTOR> <OBJECT type="self-proving-EUL"> <ID type="MS-GUID">{B536F0B2-8755-4CF5-AE80-6E1F41A15A99}</ID> </OBJECT> </DESCRIPTOR> <ISSUER> <OBJECT type="Licensor-Certificate"> <ID type="MS-GUID">{EF649DC9-29A9-4EA8-9CF7-49A76C394407}</ID> <NAME>Lightning Source, Inc.</NAME> <ADDRESS type="URL">www.lightningsource.com</ADDRESS> </OBJECT> <PUBLICKEY><ALGORITHM>RSA-512</ALGORITHM><PARAMETER name="public exponent"><VALUE encoding="integer32">65537</VALUE></PARAMETER><PARAMETER name="modulus"><VALUE encoding="base64" size="512"i7rWoC+dyg...</VALUE></PARAMETER></PUBLICKEY> </ISSUER>

More Related