W3C home > Mailing lists > Public > public-rdf-wg@w3.org > May 2011

Proposed text on replacing URIref with IRI

From: Richard Cyganiak <richard@cyganiak.de>
Date: Thu, 26 May 2011 20:20:10 +0100
Message-Id: <4BBF387F-FC13-470C-93FC-8C167E26CEED@cyganiak.de>
To: RDF Working Group WG <public-rdf-wg@w3.org>
Hi all,

I put some text on the wiki, intended as a replacement for the section of RDF Concepts that defines RDF URI References.

Current section from RDF Concepts:

Proposed replacement:

There are some notable consequences:

1. The characters “<”, “>”, “{”, “}”, “|”, “\”, “^”, “`”, ‘“’ (double quote), and “ ” (space) were allowed in URIrefs, and are not allowed in IRIs, so any data containing these characters *unescaped* is now invalid. Data containing these characters in %-encoded form is fine.

2. There was a note in the old text stating that URIrefs are compatible with the anyURI datatype. This is no longer the case as anyURI allows the characters above, but IRIs don't, so I simply removed the note.

3. A note in the old text said: “The use of %-escaped characters in RDF URI references is strongly discouraged.” This is a problem. There are many completely reasonable URIs the cannot be expressed as IRIs without %-encoding, for example this one: http://google.com/search?q=rdf%20semantics … I removed the note, and subsumed it into another note that discourages the use of %-encoding *iff the unencoded char is allowed in an IRI*.

4. SPARQL 1.1 Query should perhaps update Section 4.1.1. As we have already resolved to use IRIs as the basis of RDF 1.1, perhaps it can simply be dropped.

Received on Thursday, 26 May 2011 19:20:39 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:04:07 UTC