- From: Ivan Herman <ivan@w3.org>
- Date: Sat, 27 Mar 2010 04:55:42 -0400
- To: Shane McCarron <shane@aptest.com>
- Cc: Toby Inkster <tai@g5n.co.uk>, Manu Sporny <msporny@digitalbazaar.com>, RDFa WG <public-rdfa-wg@w3.org>
- Message-Id: <DC7CEFC7-00AD-47D7-8F40-FF775BE6C749@w3.org>
On Mar 27, 2010, at 24:27 , Shane McCarron wrote: > > > Toby Inkster wrote: >> On Fri, 2010-03-26 at 17:32 -0400, Ivan Herman wrote: >> >> >>> - there _is_ a default @vocab, conceptually set on the <html> element, >>> which is set to the value of >>> "http://www.w3.org/1999/xhtml/vocab#" >>> . >>> >>> >> >> This would result in rel="next" and rel="NEXT" generating different >> predicates. In RDFa 1.0 they generate the same predicate. >> >> > Why? Surely we can just declare that keywords are always case-insensitive... or, more likely, always mapped to lower-case. I agree >> Quick question: what about CURIEs of the form ":foo" which are currently >> expanded using the prefix >> <http://www.w3.org/1999/xhtml/vocab#> >> ? Are >> those also effected by @vocab, or do they remain grounded in the XHTML >> vocabulary? >> >> >> > Hmmm... I had not considered this. I think it would be nice if those were always mapped to the XHTML vocab, but I can imagine some people objecting to that. That would be my preference. Thoughts? Why the XHTML? That might be acceptable for HTML, but not for RDFa Core... In fact, is there any reason to treat ':foo' and 'foo' differently? Ivan > > -- > Shane P. McCarron Phone: +1 763 786-8160 x120 > Managing Director Fax: +1 763 786-8180 > ApTest Minnesota Inet: > shane@aptest.com > > > ---- Ivan Herman, W3C Semantic Web Activity Lead Home: http://www.w3.org/People/Ivan/ mobile: +31-641044153 PGP Key: http://www.ivan-herman.net/pgpkey.html FOAF: http://www.ivan-herman.net/foaf.rdf
Attachments
- application/pkcs7-signature attachment: smime.p7s
Received on Saturday, 27 March 2010 08:54:37 UTC