IETF Logo Mail Archive

Re: anchor parameter - LC comment on draft-nottingham-http-link-header-07.txt

Julian Reschke <julian.reschke@gmx.de> Fri, 19 February 2010 09:29 UTC

Return-Path: <julian.reschke@gmx.de>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BE87328C0E0 for <apps-discuss@core3.amsl.com>; Fri, 19 Feb 2010 01:29:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.374
X-Spam-Level:
X-Spam-Status: No, score=-3.374 tagged_above=-999 required=5 tests=[AWL=-0.775, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1PBf2rWvTJNG for <apps-discuss@core3.amsl.com>; Fri, 19 Feb 2010 01:29:40 -0800 (PST)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id 93EF23A7946 for <discuss@apps.ietf.org>; Fri, 19 Feb 2010 01:29:39 -0800 (PST)
Received: (qmail invoked by alias); 19 Feb 2010 09:31:23 -0000
Received: from p508FC732.dip.t-dialin.net (EHLO [192.168.178.33]) [80.143.199.50] by mail.gmx.net (mp005) with SMTP; 19 Feb 2010 10:31:23 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1//J7thhqn/d9rF6XCpz/WVv5cPNUXnO3gvy1yNT5 EtcUvBYE8Mm8e1
Message-ID: <4B7E5A62.6080304@gmx.de>
Date: Fri, 19 Feb 2010 10:31:14 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.0.4) Gecko/20060516 Thunderbird/1.5.0.4 Mnenhy/0.7.4.666
MIME-Version: 1.0
To: Mark Nottingham <mnot@mnot.net>
Subject: Re: anchor parameter - LC comment on draft-nottingham-http-link-header-07.txt
References: <20100119053002.5CD613A683B@core3.amsl.com> <E4FF7733-D744-4AC3-AB99-66A12868E4CE@mnot.net> <4B56E27D.800@gmx.de> <4B584E46.7000405@gmx.de> <2C94E45E-3373-4694-BFA3-FA7B595EAF65@mnot.net> <4B596450.7020001@gmx.de> <F1BF65AA-AE8F-435D-9097-AD629488E134@mnot.net> <4B62D875.102@gmx.de> <7B248F44-44D9-4054-84A2-E9C4C5C251E1@mnot.net> <4B6C1144.4090502@gmx.de> <5C1BFD92-7E8D-4ABF-A986-03ADC50A18CD@mnot.net>
In-Reply-To: <5C1BFD92-7E8D-4ABF-A986-03ADC50A18CD@mnot.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-FuHaFi: 0.63
Cc: Apps Discuss <discuss@apps.ietf.org>, HTTP Working Group <ietf-http-wg@w3.org>
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Feb 2010 09:29:40 -0000

On 19.02.2010 03:03, Mark Nottingham wrote:
> OLD:
>    The anchor parameter MUST be ignored by consuming implementations, unless its use is specified by the application in use.
>
> NEW:
>    Links with the anchor parameter MUST be ignored by consuming implementations, unless its use is specified by the application and/or relation type in use.
>
> works?

That's better, in that it clarifies that the anchor parameter never ever 
can be ignored.

However, it still delegates the decision to the "fuzzy" term 
"application" or the relation type registration (why would that be 
involved?).

How about:

"The presence of the anchor parameter affects the context IRI. Thus, 
consumers either MUST ignore all links that include the anchor 
parameter, or process it according to <ref>. In the latter case, the 
resulting context IRI can identify an entirely different resource, in 
which case consumers MAY choose to ignore the link."

Best regards, Julian

v2.23.0 | Report a Bug | By Email