W3C home > Mailing lists > Public > public-rdfa-wg@w3.org > October 2010

ISSUE-47 (case-sensitivity for terms): How should case-sensitivity be handled for terms specified via RDFa Profile documents? [RDFa 1.1 Core]

From: RDFa Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Mon, 18 Oct 2010 21:17:40 +0000
To: public-rdfa-wg@w3.org
Message-Id: <E1P7x5Q-00077l-H4@nelson.w3.org>

ISSUE-47 (case-sensitivity for terms): How should case-sensitivity be handled for terms specified via RDFa Profile documents? [RDFa 1.1 Core]

http://www.w3.org/2010/02/rdfa/track/issues/47

Raised by: Manu Sporny
On product: RDFa 1.1 Core

>From Gregg Kellogg:

The question regards case-insentive matching of terms to local term mappings. I understand that this is necessary for XHTML Vocabulary items, so that rel="next" is the same as rel ="NEXT", but this also has the consequence of not allowing the creation of terms from other vocabularies, where case sensitivity is essential. For example, I might want to create the following terms:

[ rdfa:term "agent"; rdfa:uri "http://purl.org/NET/c4dm/event.owl#agent" ] .
[ rdfa:term "Agent"; rdfa:uri "http://xmlns.com/foaf/0.1/Agent" ] .

As case-sensitivity of URIs, at least, is important in RDF, you could consider that case-sensitifity of terms would also be important, to allow use cases such as I just described. Certainly, I could get around this by changing the term name, but it makes it easy for someone to accidentally include two different terms that differ only in their case.

Full reference is here:

http://lists.w3.org/Archives/Public/public-rdfa-wg/2010Oct/0098.html
Received on Monday, 18 October 2010 21:17:43 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:05:21 UTC