- From: Mark Birbeck <mark.birbeck@webbackplane.com>
- Date: Wed, 21 Apr 2010 20:32:32 +0100
- To: Shane McCarron <shane@aptest.com>
- Cc: RDFa WG <public-rdfa-wg@w3.org>
Good work Shane. I think we need to clarify how we arrive at the subject of the triples when @role is used with RDFa, though. First, I think we need to explain how "@id gives the subject". I.e., we need to explain that we take the value of the document's 'base', append a fragment identifier, and then append @id. (There will no doubt be an algorithm for that in HTML already.) And second, if @id is not present, whilst it's true that we need a fresh bnode, that bnode needs to be distinct from any bnode that ordinary RDFa processing generates. I.e., if an element has a value for @role, as well as one of @typeof, @rel, or @rev, but has no @about, then we need *two* bnodes to be generated. Regards, Mark On Wed, Apr 21, 2010 at 6:31 PM, Shane McCarron <shane@aptest.com> wrote: > There is a draft of the Role Attribute spec available at > http://www.w3.org/WAI/PF/role-attribute - this specification includes ties > to RDFa Core and describes how triples should be raised when @role is > encountered in languages that incorporate @role and RDFa Core. Please > review this document, in particular Appendix A, so that you understand what > we are trying to do and that you agree with the direction I am taking that > spec in. > > Thanks! > > -- > Shane P. McCarron Phone: +1 763 786-8160 x120 > Managing Director Fax: +1 763 786-8180 > ApTest Minnesota Inet: shane@aptest.com > > > >
Received on Wednesday, 21 April 2010 21:19:57 UTC