Re: [apps-discuss] Link rel uniqueness
Mark Nottingham <mnot@mnot.net> Sun, 21 October 2012 07:51 UTC
Return-Path: <mnot@mnot.net>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4AFE021F849A for <apps-discuss@ietfa.amsl.com>; Sun, 21 Oct 2012 00:51:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.134
X-Spam-Level:
X-Spam-Status: No, score=-104.134 tagged_above=-999 required=5 tests=[AWL=-1.535, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EZ-aGgoPPpB3 for <apps-discuss@ietfa.amsl.com>; Sun, 21 Oct 2012 00:51:16 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id B7F2221F848F for <apps-discuss@ietf.org>; Sun, 21 Oct 2012 00:51:16 -0700 (PDT)
Received: from [192.168.1.72] (unknown [118.209.87.82]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id B34F922E253; Sun, 21 Oct 2012 03:51:09 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <C110B151-67B0-4A0A-950F-8FBDF56607F7@nordsc.com>
Date: Sun, 21 Oct 2012 18:51:03 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <B29A0BD6-0E01-42DE-824E-65E134134A92@mnot.net>
References: <23E04C5A-2806-4D28-B90C-A547FB0B042E@nordsc.com> <E164D9C7-37E3-410F-B1AA-658B8E9DB953@mnot.net> <C110B151-67B0-4A0A-950F-8FBDF56607F7@nordsc.com>
To: Jan Algermissen <jan.algermissen@nordsc.com>
X-Mailer: Apple Mail (2.1499)
Cc: IETF Apps Discuss <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] Link rel uniqueness
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Sun, 21 Oct 2012 07:51:17 -0000
No. link-value is the syntactic construct of *one* link; see the ABNF. There can be multiple links with the same target; this is just saying that there can only be one "rel" parameter on each link. Cheers, On 21/10/2012, at 6:49 PM, Jan Algermissen <jan.algermissen@nordsc.com> wrote: > > On Oct 21, 2012, at 5:52 AM, Mark Nottingham wrote: > >> Hi Jan, >> >> What's the specific requirement you're referring to? > > Section 5.3.: > > "The relation type of a link is conveyed in the "rel" parameter's > value. The "rel" parameter MUST NOT appear more than once in a given > link-value; occurrences after the first MUST be ignored by parsers." > > I was unsure what the link-value refers to but from what you write below I understand that it refers to the combination of all header values of the same name. > > That would then mean that parsers, when seeing > >>> Link: </a>; rel="describedBy" >>> Link: </b>; rel="describedBy" > > would, per 5.3., have to produce only > >>> Link: </a>; rel="describedBy" > > (ignoring the Link to /b) > > Correct? > > > P.S. I find that a bit counter intuitive. Given that further links might occur elsewhere in the entity. > > Jan > > > > > > > >> >> Semantically, in ANY HTTP header defined using the "," list production, the following are equivalent: >> >> Foo: 1 >> Foo: 2 >> >> and >> >> Foo: 1, 2 >> >> Regards, >> >> >> On 21/10/2012, at 9:33 AM, Jan Algermissen <jan.algermissen@nordsc.com> wrote: >> >>> Hi, >>> >>> I am seeking a clarification ragarding link rel uniqueness in http://tools.ietf.org/html/rfc5988 >>> >>> AFAIU the required uniqueness of rel is 'per header' and thus, the following HTTP response headers in a single response would be valid according to RFC 5988: >>> >>> >>> Link: </a>; rel="describedBy" >>> Link: </b>; rel="describedBy" >>> >>> Correct? >>> >>> Jan >>> _______________________________________________ >>> apps-discuss mailing list >>> apps-discuss@ietf.org >>> https://www.ietf.org/mailman/listinfo/apps-discuss >> >> -- >> Mark Nottingham http://www.mnot.net/ >> >> >> > -- Mark Nottingham http://www.mnot.net/
- Re: [apps-discuss] Link rel uniqueness Paul E. Jones
- Re: [apps-discuss] Link rel uniqueness Mark Nottingham
- Re: [apps-discuss] Link rel uniqueness Jan Algermissen
- [apps-discuss] Link rel uniqueness Jan Algermissen
- Re: [apps-discuss] Link rel uniqueness Mark Nottingham