SyntaxHighlighter

SyntaxHighlighter

Showing posts with label odrl. Show all posts
Showing posts with label odrl. Show all posts

Wednesday, January 11, 2017

Developing the Digital Marketplace for Copyrighted Works

I recently spoke at "Developing the Digital Marketplace for Copyrighted Works", organized by the Commerce Department’s Internet Policy Taskforce. The goal of the public meeting was to "facilitate constructive, cross-industry dialogue among stakeholders about ways to promote a more robust and collaborative digital marketplace for copyrighted works". My impression of the roughly 80 attendees was of a mix of publishers and lawyers - who tended to be pretty conservatively dressed - and music people - who tended to be in more sparkly outfits. Most of the discussion revolved around music, photo and video, but it turned out that a lot of the problems and potential solutions were quite similar across industries and media types. I've linked to the video of the event at the end of this post.

I've been involved in rights work at the Associated Press, including adding rights and pricing metadata to AP's Image API. I lead the IPTC's Rights Working Group. And I'm working within the W3C's POE group to turn ODRL into an official standard.


I spoke on the first panel with the topic of "Unique Identifiers and Metadata". I was teased a bit about "fake news" (this was in Alexandria. VA on December 9th 2016, so close both in time and place to the U.S. Presidential Election). Amongst other things, I spoke about how apparently simple things - "let's agree on identifiers for photos" - turned out to be quite complicated - since a text item, a photo or a video is not really a single, simple atomic thing, but more like a molecule of information. (You can watch the entire panel - which turned out to be quite lively, despite the early hour - in the video linked below).

I also moderated a round table, with the topic "What are the practical steps to adopting standards for identifying and controlling copyrighted works?". As everyone at my table introduced themselves, they mostly said "oh, I'm just here to learn, I don't have much to contribute" but, in fact, we had a very vigorous discussion, which covered *lots* of topics! I summarized them during the "Plenary" session (again, I've linked to the video below). We talked about three areas. First, was why we need standards - creators and rights holders should be compensated for their work, which could be financial compensation or it could be getting distribution and recognition. Second, we talked about the big barriers - technology, the culture of the Internet and human nature itself. Finally, we talked about concrete steps which the government and other organizations could take to get standards developed and adopted. (For the details, you'll need to watch the video. My segment runs from about 39:30 to about 45:55 but I recommend watching everyone's summary of their individual breakout sessions)

If you're interested in rights, then you should consider coming to London for the week of May 15th. That's because the BBC is hosting a Rights Day on May 15th, the IPTC will be holding its Spring Meeting (including discussing RightsML) on May 16th and 17th and W3C will hold its face-to-face meeting on May 18th and 19th. If you're interested in any or all, contact me and I will put you in touch with the right rights people.

Opening Remarks and Panel Session 1: Unique Identifiers and Metadata
Panel Session 2: Registries and Rights Expression Languages


Panel Session 3: Digital Marketplaces

Plenary Session



Tuesday, July 26, 2016

Making Progress on Rights - W3C Permissions Obligations and Expressions First Public Working Drafts


I've been working within W3C's Permissions & Obligations Expression (POE) Working Group as an Invited Expert. We have just issued our First Public Working Drafts:
"one" by Andre Chinn
https://flic.kr/p/5pGcyx
The W3C POE WG aims to create recommendations for permissions, obligations and licensing statements for digital content. The WG is using the W3C ODRL Community Group specifications as the starting point for its work. These are the same specifications which form the foundation of IPTC's RightsML work.
"poe" by 为民 王
https://flic.kr/p/gp2Bc
If you're interested in digital content, then I recommend looking at - and commenting on - the W3C POE drafts. The ODRL Information Model describes the foundational concepts, entities and relationships of ODRL. The ODRL Vocabulary & Expression describes how to encode the ODRL model in XML, JSON and RDF.
"Use in case of emergency" by Katia Sosnowiez
https://flic.kr/p/5MMhFz
The POE WG has also published the Use Case and Requirements Note. I have contributed one of the Use Cases: News Permissions and Restrictions. Again, the Working Group is looking for feedback on - and contributions to - the Use Cases, so that it can derive a detailed set of requirements for the POE work.

Friday, April 17, 2015

More Concise ODRL and RightsML Expressions in XML using DRY Asset Patterns

DRY

Don't repeat yourself (DRY) is a much-loved principle of software engineering.

Essentially, the DRY principle states that you should strive to express any particular piece of information only once. This simplification typically improves maintainability and understandability. Systems which require you to repeat information are known by DRY-adherents as "WET" systems (for "We Enjoy Typing" or "Write Everything Twice").

DRY ODRL

In ODRL (and hence RightsML) every permission or prohibition refers to a particular asset.

When you have more than one permission or prohibition to express for a particular asset, this means you need to repeatedly refer to the same asset. How do you avoid repeating more than absolutely necessary to identify which asset the permission or prohibition constrains?

XML Linking

One solution for minimizing the amount of XML Markup is to use XML Linking. Here's an example where you identify an asset o:asset/@id=as1 and then use an @idref to refer to it in other permission or prohibition blocks.

<o:Policy xmlns:o="http://www.w3.org/ns/odrl/2/" type="http://www.w3.org/ns/odrl/2/Set" uid="http://example.com/policy:Z1XZ">
  <o:permission>
    <o:asset id="as1" uid="http://example.com/music:1234908" relation="http://www.w3.org/ns/odrl/2/target"/>
    <o:action id="ac1" name="http://www.w3.org/ns/odrl/2/play"/>
    <o:constraint id="c1" name="http://www.w3.org/ns/odrl/2/spatial" operator="http://www.w3.org/ns/odrl/2/eq" rightOperand="http://www.itu.int/tML/tML-ISO-3166:it"/>
    <o:party id="p1" uid="http://example.com/sony:10" function="http://www.w3.org/ns/odrl/2/assigner"/>
    <o:party id= "p2" uid="http://example.com/billie:888" function="http://www.w3.org/ns/odrl/2/assignee"/>
  </o:permission>

  <o:prohibition>
    <o:asset idref="as1"/>
    <o:action idref="ac1"/>
    <o:constraint name="http://www.w3.org/ns/odrl/2/spatial" operator="http://www.w3.org/ns/odrl/2/eq" rightOperand="http://www.itu.int/tML/tML-ISO-3166:fr"/>
    <o:party idref="p1"/>
    <o:party idref="p2"/>
  </o:prohibition>
</o:Policy>


Embed the ODRL inside the Asset Markup

The other thing you can do is to have markup for the asset itself (rnews:Article in the below example) embed the ODRL policy. This means that the ODRL is even more concise, as it only needs to refer to the ID of the asset.

<rnews:Article xml:id="item8HEX">
  <rnews:title>Allies are Split<rnews:title>
  <rnews:description>Rebel fighters take control...<rnews:description>

...

  <o:Policy xmlns:o="http://www.w3.org/ns/odrl/2/" type="http://www.w3.org/ns/odrl/2/Set" uid="http://example.com/policy:ABAABA">
  <o:permission>
    <o:asset uid="#item8HEX"/>
    <o:action name="http://w3.org/ns/odrl/vocab#distribute"/>
    <o:constraint name="http://www.w3.org/ns/odrl/2/dateTime" operator="http://www.w3.org/ns/odrl/2/gteq" rightOperand="2011-11-11"/>
  </o:permission>
</o:policy>

...

</rnews:Article>





Wednesday, November 17, 2010

IPTC and Rights Expression Languages

IPTC has been looking at how to express rights for news content. At the Rome IPTC meeting, I presented the work to date (slides are on slideshare). And Daniel Pähler presented ODRL, the Open Digital Rights Language.

The News Industry Need for Machine Readable Rights
Various news publishers have identified the ability to be able to express rights in a machine readable way as being a priority. In part, this reflects the fundamental changes that have been transforming the news industry. Once, an agency such as the Associated Press distributed content to editors at newspapers and broadcasters, who would select which items they would use. In the process of this selection, they would be able to read any editors' notes, which could include any restrictions that needed to be observed. However, increasingly, news outlets are fully automated, with very little - if any - editorial oversight of what is published. Amongst other things, this drives the need for the expression of rights and restrictions in a way that can be evaluated automatically. This automation would allow the editorial process to be more efficient. In general, an editor still needs to exercise their judgement as to whether a particular restriction applies in a particular context. But, automatic evaluation of rights and restrictions can identify the items that need those decisions, rather than having editors inspect every single item. (This exercise of editorial judgement means that these systems are not like DRM, in which particular actions are forbidden and typically enforced by the devices involved).

IPTC and Rights Expression
IPTC reviewed how the various news formats that it maintains allow for the expression of rights. In every case, there are currently semi-structured ways to express rights using natural language, which wouldn't easily allow for the fully machine-readable rights expressions that member companies need to express. On the other hand, the IPTC has consistently decided that it didn't want to develop a machine-readable rights expression itself - members of the IPTC have felt qualified to develop news formats, whereas legal matters are a different domain.

ODRL and ACAP
After reviewing several candidates, we felt that ODRL v2 was the best fit for an existing (though not quite yet complete) rights expression language. In particular, it offers the ability to create an industry-specific rights vocabulary that can be "plugged in" to the ODRL framework. The IPTC has been working with ACAP on developing this vocabulary and with the ODRL group to help refine the ODRL v2 framework itself.

Daniel's slides can be downloaded from the ODRL Wiki.  They give a nice introduction to the ODRL effort and the ODRL v2 approach.

Questions on Rights and ODRL
Daniel and I were asked several questions about rights for news in general and ODRL in particular. For example, there was some discussion about whether rights are really only applicable to photographs (the consensus was no - every media type has increasing amounts of rights being applied). There were questions about how to apply rights to the parts of an item (such as the frames within a video). The partMeta structure of NewsML-G2 handles this nicely (assuming we were to include ODRL within the partMeta structure, which I think we would). There were also questions about what industries are using ODRL today. Chiefly, the mobile phone industry uses ODRL v1 as part of the OMA DRM system (http://xml.coverpages.org/ni2004-05-31-a.html). Daniel explained that there are several academic projects that are using or working on ODRL v2 (Daniel himself is from the University of Koblenz).

Get Involved
You can find out more about the ACAP ODRL profile - and even participate in the work - by visiting the a special Wiki page set up by ODRL for ACAP:

http://odrl.net/wiki/tiki-index.php?page=ACAP+Profile