- From: Michael Steidl \(IPTC\) <mdirector@iptc.org>
- Date: Fri, 27 Feb 2015 16:50:55 +0100
- To: "'Agnese Farinelli'" <agnese.farinelli@studenti.unimi.it>, <public-odrl@w3.org>
- Message-ID: <017d01d052a5$2c0aa140$841fe3c0$@iptc.org>
Hi Agnese You are asking about how to extend the vocabulary which is quite different to extending a structure: - In the XML Encoding defined for ODRL 2.0 and the XML and JSON Encoding defined for ODRL 2.1 (see the draft section of https://www.w3.org/community/odrl/) an action is expressed by a URI identifying this property. - Such an action property URI is held in XML by the @name attribute and in JSON by the action property/field. - That means: you only have to provide a new URI for a new action; this has no impact on the structure, no XML or JSON schema needs to be changed for that purpose. - As just said you need to define a URI for the new action, as Jim outlined this could be e.g. http://www.example.com/odrl/action/derive for your special variant of derive. - Next you could consider to link this new action with the existing ODRL vocabulary: the ODRL action "derive" of the ODRL 2.1 Action vocabulary (see https://www.w3.org/community/odrl/work/2-0-common-vocabulary-constraint-draf t-changes/#section-22) is a narrower term of "use", so you might want to make the ODRL "use" also the broader term of your derive. In this case you have to set a broader relationship from your "derive" to the ODRL "use". This can be done by vocabulary management means like SKOS, see http://www.w3.org/TR/skos-primer/ Best, Michael From: Agnese Farinelli [mailto:agnese.farinelli@studenti.unimi.it] Sent: Wednesday, February 25, 2015 12:44 PM To: public-odrl@w3.org Subject: Question about ODRL 2.0 Common Vocabulary Good morning, I wrote you this email for clarify, if I am allowed, a few doubt about ODRL 2.0 Common Vocabulary and the possibility to extend this vocabulary with dedicated profiles. In your ODRL 2.0 Common Vocabulary final specification (https://www.w3.org/community/odrl/two/vocab/#section-3) I read that the possibility to extend the Common Vocabulary is concrete but I didn't find any technical implementation for this kind of extension (differently, I found all the informations what I need about the extension of Core Model in the Core Model concrete XML Schema). I forget to tell you that I am an Information Technology student in University of Milan: my purpose is to conduct a research about ODRL 1.1 and ODRL 2.0 for my graduation thesis, with some practical example about real and study cases. I need to extend the ODRL 2.0 Common Vocabulary with some specific permissions and constraints (and other stuff, of course) what are more adapted to define licences over my study cases. So, my question is: where can I find a concrete example about Common Vocabulary extension? Something like an .xsd file for ODRL 1.1 where I can use something like the ODRL 1.1 SubstitutionGroup to define new permissions or constraints. Always if this is possible, because I found several technical reports and specification documents about ideas or projects for future Community Profiles, but I didn't find any examples or implementations of this kind of projects. Thanks a lot for your attention, and I ask you to forgive me for my bad english. I am waiting for an answer. My best regards. Farinelli Agnese
Received on Friday, 27 February 2015 15:51:31 UTC