W3C home > Mailing lists > Public > www-tag@w3.org > September 2008

Re: rel=CURIE in RDFa, but rel=URI in Link:

From: Roy T. Fielding <fielding@gbiv.com>
Date: Sun, 28 Sep 2008 22:42:07 -0700
Message-Id: <B87388E5-FDB3-471E-8E2A-4E9000C973F6@gbiv.com>
Cc: "Julian Reschke" <julian.reschke@gmx.de>, "Shane McCarron" <shane@aptest.com>, "www-tag@w3.org WG" <www-tag@w3.org>
To: Anne van Kesteren <annevk@opera.com>

On Sep 28, 2008, at 1:33 AM, Anne van Kesteren wrote:
> On Sun, 28 Sep 2008 09:41:49 +0200, Julian Reschke  
> <julian.reschke@gmx.de> wrote:
>> I think the other point Roy was making that link relations are  
>> URIs, not IRIs, so new specs that allow non-ASCII characters in  
>> link relations should deal with the information the loss when  
>> transferred as URI.
> To my knowledge HTML4 was the first specification to define link  
> relations and they were not URIs and could contain non-ASCII  
> characters if you defined one yourself if you declared a profile:
>   http://www.w3.org/TR/html4/types.html#type-links

Link types have been in HTML for as long as the WWW has been an open  
They were defined by the type attribute in


as strings. "Strings for types with particular semantics will be
registered by the W3 team."  That registration was in hypertext.


and have been defined many times in many places over the years


> Also, they are case-insensitive and therefore might need to be  
> normalized if you want to "bind" them to a URIs.

The definition has changed so many times that it doesn't really matter
what we do to normalize them.  Only singleton short strings work today.
The decision to lowercase the short string and, if a URI is needed,
treat it as relative to the IANA registry, supports backwards  
for singleton relationships while satisfying the crowd that thinks
they need arbitrary URIs.

Received on Monday, 29 September 2008 05:42:53 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:32:58 UTC