- From: Mo McRoberts <Mo.McRoberts@bbc.co.uk>
- Date: Wed, 6 Aug 2014 17:05:28 +0000
- To: Víctor Rodríguez Doncel <vrodriguez@fi.upm.es>
- CC: Renato Iannella <ri@semanticidentity.com>, "ODRL Community Group (Contrib)" <public-odrl-contrib@w3.org>
This was discussed in here at the time… However, the rationale was that for the cases where the Set is a simple license grant, then using a property which is already widely used for exactly that purpose made more sense than inventing a new one for the purpose. There wasn’t an odrl:policy proposal because as Renato notes, the ODRL model’s approach was to attach the asset to the policy, not the other way around — and that makes sense if you think about it; if it’s *not* a simple license grant, then it’s much more likely that it would be specific to the asset. M. On 2014-Aug-06, at 17:54, Víctor Rodríguez Doncel <vrodriguez@fi.upm.es> wrote: > > Yes, I support the idea of having such a property because I believe it can become a common case in non ODRL-centric settings... > > Víctor > > El 04/08/2014 8:59, Renato Iannella escribió: >> >> On 31 Jul 2014, at 22:17, Víctor Rodríguez Doncel <vrodriguez@fi.upm.es> wrote: >> >>> Dear all, >>> >>> In the Draft Open Digital Rights Language (ODRL) Ontology, there is an example of the utmost importance, which I copy here for your convenience (boldface and red is mine). >>> >>> @prefix odrl: <http://www.w3.org/ns/odrl/2/> >>> . >>> @prefix dct: >>> <http://purl.org/dc/terms/> >>> . >>> >>> >>> <http://example.com/asset:9898> dct:license <http://example.com/policy:0099> >>> . >>> >>> >>> <http://example.com/policy:0099> >>> >>> a odrl:Set; >>> odrl:permission odrl:reproduce ; >>> odrl:prohibition odrl:modify . >>> >>> I wonder myself about the following issues: >>> 1. Why are we choosing dct:license? Shouldn't we have had a property called: "odrl:policy"? >>> 2. Why not others? (dct:accessRights etc.)? >> >> Hi Victor...I think the reason we do not have a odrl:policy property is that our model has always assigned the asset from within the Policy. >> >> Having said that, it might be useful to also have an odrl:policy property to support the use case in the example. >> >> And, odrl:policy can then be made more specific in other communities (eg a DC licence). >> >> >> Cheers... >> Renato Iannella >> Semantic Identity >> http://semanticidentity.com >> Mobile: +61 4 1313 2206 >> > -- Mo McRoberts - Chief Technical Architect - Archives & Digital Public Space, Zone 2.12, BBC Scotland, 40 Pacific Quay, Glasgow G51 1DA. Inside the BBC? My movements this week: http://neva.li/where-is-mo
Received on Wednesday, 6 August 2014 17:14:08 UTC