ODRL Profile for Linked Data

Simon, Serena, Sabrina, all

We had scheduled a call at 15.00 CEST for the ODRL Linked Data profile. 
Are you at ESWC? If you prefer, we can also postpone it.

In any case, I have seen Simon's edition, and I have further edited the 
spec at: 
https://www.w3.org/community/odrl/wiki/ODRL_Linked_Data_Profile. In 
particular, I have included the SPARQL UPDATE actions as suggested, and 
further refined the description of assets.

*Small questions on Simon's edition:**
*1) Should odrl-ld:query be the superclass of odrl-ld:select, 
odrl-ld:construct, etc.?
2) Is our policy defining new classes (e.g. odrl-ld:License) or re-using 
existing ones (e.g. http://purl.org/dc/terms/LicenseDocument, 
cc:License). I advocate for the first one, so that the semantics is 
entirely under our control, but adding the due mappings.
3) I think the definition of odr-ld:AndRuleSet etc. overlaps that of the 
extened spec here: https://www.w3.org/community/odrl/model/2-1/#section-5
However, I would say that it is ill defined so I would prefer defining 
our odrl-ld:AndRuleSet etc. We have adopted similar solutions.
4) Is anyhow odrl-ld:precedenceOver related to odrl:conflict? Maybe we 
can explicitly say the odrl-ld precedence "precedes" odrl:conflict :)

*Big question: are we finally declaring RDF Shapes? *I am in favour.
Assuming sh stands for: http://www.w3.org/ns/shacl# we may include the 
following:
odrl:Rule a sh:Shape ;
sh:property [
         sh:predicate odrl:target;
         sh:valueType xsd:anyURI;
         sh:minCount 1 ; sh:maxCount 1
     ] ;
and contraints of the sort. What do you think?

Please confirm if you are attending today's call or we move it to the 
next week!

Regards,
Víctor