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

Julian Reschke <julian.reschke@gmx.de> Thu, 04 February 2010 15:57 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 2B43E3A6C4E for <apps-discuss@core3.amsl.com>; Thu, 4 Feb 2010 07:57:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.682
X-Spam-Level:
X-Spam-Status: No, score=-4.682 tagged_above=-999 required=5 tests=[AWL=-2.083, 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 rAj96ZRbhasB for <apps-discuss@core3.amsl.com>; Thu, 4 Feb 2010 07:57:41 -0800 (PST)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id EE2B628C0FA for <discuss@apps.ietf.org>; Thu, 4 Feb 2010 07:57:40 -0800 (PST)
Received: (qmail invoked by alias); 04 Feb 2010 15:58:25 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.105]) [217.91.35.233] by mail.gmx.net (mp056) with SMTP; 04 Feb 2010 16:58:25 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX196mSgstBt6hSEFXZZoNNQPLgVVJeh4AZcDSpmEjf 21MZmcAya2rAtI
Message-ID: <4B6AEE99.4080901@gmx.de>
Date: Thu, 04 Feb 2010 16:58:17 +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: rev 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> <4B58574B.4050204@gmx.de> <FE77FC83-4137-421B-9511-02B13642AE1A@mnot.net> <4B596B30.1030400@gmx.de> <3FB0E494-EE9C-46F8-A924-2768C730763A@mnot.net>
In-Reply-To: <3FB0E494-EE9C-46F8-A924-2768C730763A@mnot.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-FuHaFi: 0.70999999999999996
Cc: Apps Discuss <discuss@apps.ietf.org>, Roy Fielding <fielding@gbiv.com>, 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: Thu, 04 Feb 2010 15:57:42 -0000

Mark Nottingham wrote:
> I think perhaps you need to talk to Roy about that...
> 
> At the moment, my intent is to remove 'rev' from the BNF and state how new parameters can be added (either by updating the document, for parameters common to many relation types, or on a per-type / per-application basis). 

-1 / +1

Yes, the extensibility point should be documented.

But no, rev should be documented. RFC 2068 already defines what it is, 
so the only thing an extension could ever do is to re-introduce that 
definition.

There may be good reasons to *discourage* it's use, but that's really 
different from not defining it at all.

I think we should park this issue until we know what happens with the 
anchor parameter; after all, a link relation using rel= can always be 
rewritten into one using anchor=.

Best regards, Julian