W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2008

Re: Feedback for draft-nottingham-http-link-header-03

From: Julian Reschke <julian.reschke@gmx.de>
Date: Tue, 02 Dec 2008 08:43:22 +0100
Message-ID: <4934E71A.3020505@gmx.de>
To: Eran Hammer-Lahav <eran@hueniverse.com>
CC: "ietf-http-wg@w3.org Group" <ietf-http-wg@w3.org>

Eran Hammer-Lahav wrote:
> ...
>> 5.  The Link Header Field
>>        Link           = "Link" ":" #link-value
> The '#' operator is not defined in the referenced ABNF provided (it is defined in the original spec).

RFC 2616, Section 2.1.

> ...
>>    Each link-value conveys one target URI inside angle brackets ("<>").
>>    If it is relative, it MUST be resolved as per [RFC3986].  Note that
>>    because it is conveyed in a header, base URIs from content are not
>>    applied to it.
> Just confirming that URI-Reference can be an empty string, i.e.: Link: <>; rel="something". It is needed for using links with URI-templates [1] where the link value is constructed using a template that does not fit in the URI-Reference space (using a link header extension).

Sorry? If the URI-Reference is empty, then the target URI is the one of 
the context.

If you want to introduce an extension point for URI templates, we'll 
need to specify it explicitly.

> ...

BR, Julian
Received on Tuesday, 2 December 2008 07:44:08 UTC

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