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

Mark Nottingham <mnot@mnot.net> Thu, 04 February 2010 06:17 UTC

Return-Path: <mnot@mnot.net>
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 67E6D3A6CB1 for <apps-discuss@core3.amsl.com>; Wed, 3 Feb 2010 22:17:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.976
X-Spam-Level:
X-Spam-Status: No, score=-3.976 tagged_above=-999 required=5 tests=[AWL=-1.377, 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 Ea+bm-aYJVx5 for <apps-discuss@core3.amsl.com>; Wed, 3 Feb 2010 22:17:24 -0800 (PST)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by core3.amsl.com (Postfix) with ESMTP id 324003A69B4 for <discuss@apps.ietf.org>; Wed, 3 Feb 2010 22:17:23 -0800 (PST)
Received: from chancetrain-lm.mnot.net (unknown [118.209.26.233]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id BF61722E1F3; Thu, 4 Feb 2010 01:18:01 -0500 (EST)
Subject: Re: rev parameter - LC comment on draft-nottingham-http-link-header-07.txt
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset="us-ascii"
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <4B596B30.1030400@gmx.de>
Date: Thu, 04 Feb 2010 17:17:58 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <3FB0E494-EE9C-46F8-A924-2768C730763A@mnot.net>
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>
To: "Julian F. Reschke" <julian.reschke@gmx.de>, Roy Fielding <fielding@gbiv.com>
X-Mailer: Apple Mail (2.1077)
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: Thu, 04 Feb 2010 06:17:25 -0000

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). 



On 22/01/2010, at 8:09 PM, Julian Reschke wrote:

>>> Later on, in the section about HTML4 we find (<http://tools.ietf.org/html/draft-nottingham-http-link-header-07#appendix-B>):
>>> 
>>>  HTML4 also has a "rev" parameter for links that allows a link's
>>>  relation to be reversed.  The Link header does not define a
>>>  corresponding "rev" parameter to allow the expression of these links
>>>  in HTTP headers, due to the confusion this mechanism causes as well
>>>  as conflicting interpretations (briefly, some hold that rev reverses
>>>  the direction of the link, while others that it reverses the
>>>  semantics of the relation itself).
>>> 
>>> I have to admit that I'm still not sure what *in practice* the difference between reversing the link direction and reversing the link semantics actually is. (Example?)
>> I can add a brief example for the latter.
> 
> Please.
> 
>>> So my preference would be to actually define the rev parameter consistently with this, and then to discourage it's use due to the other good reasons we heard about that (such as HTML authors typing "rev" instead of "rel").
>> As previous discussed (quite a bit), HTML2 defines REV as having reversed *semantics*, while HTML4 talks about it creating a "reverse link" -- which are very different things. This feels like a rat hole to me (thus my attempts to navigate around it).
> 
> Again, HTML 2 defines it as:
> 
>    REV
>            same as the REL attribute, but the semantics of the
>            relationship are in the reverse direction. A link from A
>            to B with REL="X" expresses the same relationship as a
>            link from B to A with REV="X". An anchor may have both
>            REL and REV attributes.
> 
> (<http://tools.ietf.org/html/rfc1866#section-5.7.3>)
> 
> That totally sounds like "reverse link" to me. So, I really really think there's less confusion than some people claim.


--
Mark Nottingham     http://www.mnot.net/