W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2010

Re: Link Relation Registry initial contents

From: Julian Reschke <julian.reschke@gmx.de>
Date: Fri, 24 Sep 2010 16:01:26 +0200
Message-ID: <4C9CAF36.4090101@gmx.de>
To: nathan@webr3.org
CC: Mark Nottingham <mnot@mnot.net>, HTTP Working Group <ietf-http-wg@w3.org>
On 23.09.2010 13:29, Nathan wrote:
> cc ietf-http, apologies if this is the wrong list associate with Link
> header
> Hi Mark,
> I'm wondering why 'stylesheet' is registered as a link relation, out of
> all of them this seems very media type specific and can't see what use
> or role it has in an HTTP header.

1) It's in HTML4.

2) It actually is supported by a few browsers (in HTTP link).

I agree that it would be nice to re-register it in the future, for 
instance considering both HTML and XML.

> Is there any guidance associated with link relations (and the registry
> of) which specifies they should be usable across a broad range of media
> types / work with any media type?


"...Well-defined relation types can be registered as tokens for 
convenience and/or to promote reuse by other applications. This 
specification establishes an IANA registry of such relation types; see 
Section 6.2.

Registered relation type names MUST conform to the reg-rel-type rule, 
and MUST be compared character-by-character in a case-insensitive 
fashion. They SHOULD be appropriate to the specificity of the relation 
type; i.e., if the semantics are highly specific to a particular 
application, the name should reflect that, so that more general names 
are available for less specific use.

Registered relation types MUST NOT constrain the media type of the 
context IRI, and MUST NOT constrain the available representation media 
types of the target IRI. However, they can specify the behaviours and 
properties of the target resource (e.g., allowable HTTP methods, request 
and response media types which must be supported)...."

Best regards, Julian
Received on Friday, 24 September 2010 14:02:07 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:10:54 UTC