- From: Steven Pemberton <steven.pemberton@cwi.nl>
- Date: Thu, 05 Mar 2009 17:26:41 +0100
- To: "Julian Reschke" <julian.reschke@gmx.de>
- Cc: "Manu Sporny" <msporny@digitalbazaar.com>, "Maciej Stachowiak" <mjs@apple.com>, "Mark Nottingham" <mnot@mnot.net>, "www-tag@w3.org WG" <www-tag@w3.org>, "HTMLWG WG" <public-html@w3.org>, "RDFa mailing list" <public-rdf-in-xhtml-tf@w3.org>, public-xhtml2@w3.org
On Thu, 05 Mar 2009 17:15:07 +0100, Julian Reschke <julian.reschke@gmx.de> wrote: > Steven Pemberton wrote: >>> Yes. Using a safe-CURIE wouldn't have prevented that, but at least it >>> wouldn't break URIs in rel values. >> Wait, you can't use URIs as rel values, because "next" is just as >> valid a URI as "http://www.w3.org/foo". You would have to have a 'safe >> uri' format such as "<next>" and "<http://www.w3.org/foo>" to make it >> possible to interpret a rel directly as a URI. > > The string "next" is a URI reference > (<http://greenbytes.de/tech/webdav/rfc3986.html#rfc.section.4.1>), not a > URI (<http://greenbytes.de/tech/webdav/rfc3986.html#rfc.section.3>). Sorry, I was using the term URI as it is used as a datatype in HTML4. The datatype of @href in HTML4 is "URI", which as you point out, is called a URI reference in other contexts. Best wishes, Steven > > Best regards, Julian
Received on Thursday, 5 March 2009 16:26:58 UTC