- From: Renato Iannella <ri@semanticidentity.com>
- Date: Mon, 20 Jan 2014 11:47:56 +1000
- To: "ODRL Community Group (Contrib)" <public-odrl-contrib@w3.org>
- Message-Id: <347015D5-2DAD-4038-AE28-703EC9C18281@semanticidentity.com>
On 18 Jan 2014, at 00:52, Myles, Stuart <SMyles@ap.org> wrote: > Ř Yes, it is required. Since uid and type are mandatory attributes, it was assumed, but is mandatory in the XML Schema. > Ř Will make it more specific.... > > I think that including a policy element in every example would help. Especially for people (like me) who mainly use the examples and might not read every single line of the formal spec J Ok...draft spec has been updated: http://www.w3.org/community/odrl/work/2-0-xml-encoding-constraint-draft-changes/ [Note, there still seems to be a bug in Wordpress with the XML Highlighter plugin....switching between HTML/Visual mode kills the code....so beware for now..] > Ř That has been fixed in the Draft xml spec: http://www.w3.org/community/odrl/work/2-0-xml-encoding-constraint-draft-changes/ > > Oh... I missed (had forgotten) that there’s a Draft spec subsequent to the “Final” spec. Do we need to do something to move it from Draft to Final. There are some dependencies with some of the outstanding issues (#15, 17, 18) that effect the XML Spec: - single namespace - vocab term changes - identify profiles Cheers... Renato Iannella Semantic Identity http://semanticidentity.com Mobile: +61 4 1313 2206
Received on Monday, 20 January 2014 01:48:15 UTC