- From: Shane McCarron <shane@aptest.com>
- Date: Wed, 15 Feb 2012 10:49:18 -0600
- To: W3C RDFWA WG <public-rdfa-wg@w3.org>
- CC: "'Protocols and Formats Working Group WG'" <w3c-wai-pf@w3.org>
As many of you are aware, the PFWG is responsible for development of the Role Attribute Module [1]. This document will soon enter CR review. Role is a very simple document, and it has a couple of dependencies on RDFa. One is the definition of CURIE. Right now the document points to RDFa Syntax because RDFa Core was not going to be ready in time. Given the current schedule, it is possible that we could change this to RDFa Core. I am pondering that now. The other is a dependency on the TERMorCURIEorAnyIRIs datatype. @role takes this type, and the type is defined in RDFa Core. The definition is not complicated, and we are of course able to just reproduce the definition in Role so that we have no dependency on RDFa Core. I am pondering this as well. Finally, there is a potentialy sticky issue. The document indicates that additional role values can be defined (of course) but it does not say how. It also does not say how such definitions would be referenced by a document written in a host language that uses @role. Obviously (to us) the references would be done with @vocab, and the vocabularies would be defined using RDFa so that entailment could happen. But this is not described at all in the Role spec. My question for the RDFWA WG is "should Role reference RDFa Core and should Role mention the use of @vocab and the implied format of vocabulary documents as an example?" Obviously if the answer to these questions is yes, then the Role spec should have a normative dependency on RDFa Core. Help? [1] http://www.w3.org/WAI/PF/src/role-attribute-src.html -- Shane McCarron Managing Director, Applied Testing and Technology, Inc. +1 763 786 8160 x120
Received on Wednesday, 15 February 2012 16:49:42 UTC