Actually, I don't like this at all. I don't want to lose the ability
to have mixed case relationships - it would violate the specific use
case we are trying to satisfy (make foaf the default vocabulary in a
Maybe this was said already - I don't remember. Can't we just say that
references to the XHTML vocabulary are mapped to lower case and any
other vocabularies are not? I know it is sort of a hack, but it would
mean that we don't need to to any remote retrieval to know if the vocab
is case insensitive or not.
Toby Inkster wrote:
On Sat, 2010-03-27 at 21:29 -0400, Manu Sporny wrote:
We may want to say that rel/rev are always mapped to lower-case since
they are legacy attributes. Everything else is case-sensitive.
Assuming we're just talking about rel/rev values that do not contain a
colon, I could support that. It does break e.g.
<a vocab="http://xmlns.com/foaf/0.1/" rel="primaryTopic" ...>
<a vocab="http://www.w3.org/2000/01/rdf-schema#" rel="seeAlso" ...>
Shane P. McCarron Phone: +1 763 786-8160 x120
Managing Director Fax: +1 763 786-8180
ApTest Minnesota Inet: firstname.lastname@example.org