Re: [link-relations] NEW RELATION REQUEST: Relation name: "next"
Mark Nottingham <mnot@mnot.net> Thu, 02 September 2010 11:34 UTC
Return-Path: <mnot@mnot.net>
X-Original-To: link-relations@core3.amsl.com
Delivered-To: link-relations@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0037A3A6A93 for <link-relations@core3.amsl.com>; Thu, 2 Sep 2010 04:34:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.87
X-Spam-Level:
X-Spam-Status: No, score=-104.87 tagged_above=-999 required=5 tests=[AWL=-2.271, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 J4QMeFsyA8Px for <link-relations@core3.amsl.com>; Thu, 2 Sep 2010 04:34:49 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by core3.amsl.com (Postfix) with ESMTP id 6340C3A6954 for <link-relations@ietf.org>; Thu, 2 Sep 2010 04:34:49 -0700 (PDT)
Received: from chancetrain-lm.mnot.net (unknown [118.209.83.112]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 7303422E254; Thu, 2 Sep 2010 07:34:45 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset="us-ascii"
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <20100902081410.GD58403@sideshowbarker>
Date: Thu, 02 Sep 2010 21:34:41 +1000
Content-Transfer-Encoding: quoted-printable
Message-Id: <31E56538-C14F-40A7-92FC-C2D05E6AF7E1@mnot.net>
References: <20100902081410.GD58403@sideshowbarker>
To: Michael Smith <mike@w3.org>
X-Mailer: Apple Mail (2.1081)
Cc: link-relations@ietf.org
Subject: Re: [link-relations] NEW RELATION REQUEST: Relation name: "next"
X-BeenThere: link-relations@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <link-relations.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/link-relations>, <mailto:link-relations-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/link-relations>
List-Post: <mailto:link-relations@ietf.org>
List-Help: <mailto:link-relations-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/link-relations>, <mailto:link-relations-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Sep 2010 11:35:22 -0000
Hi Mike, Just to start discussion, I'll give initial thoughts in one e-mail, for now. One general observation - relations that are potentially usable in formats other than HTML should be defined in such a way that they're not HTML specific. The only reason I mention this is that the specification links go directly into HTML-specific text, without any definition of semantics, etc. E.g., with 'alternate', the link goes to: > 4.12.3.1 Link type "alternate" > > The alternate keyword may be used with link, a, and area elements. > > The meaning of this keyword depends on the values of the other attributes. > > If the element is a link element and the rel attribute also contains the keyword stylesheet [...] It would be helpful (especially since alternate is already used by Atom) if this were rewritten to something like: > 4.12.3.1 Link type "alternate" > > The 'alternate' link type gives alternate representations of the current document. > > In HTML documents, the alternate keyword may be used with link, a, and area elements. > > The meaning of this keyword depends on the values of the other attributes. > > If the element is a link element and the rel attribute also contains the keyword stylesheet [...] See what I mean? Beyond that, I see three groups of relations here; 1) Updating HTML4 registrations, including: next / alternate / bookmark / index / prev / stylesheet / help There shouldn't be any issues with these. The only thing I'd note is that 'alternate' is also used by Atom, but it's already registered by HTML4, so it shouldn't be a problem. 2) Registering new relations, including: archives / icon / noreferer / tag / pingback / prefetch / sidebar / external / author / nofollow / search 'pingback' and 'search' refer to external specifications. We'll need to talk through the implications of that. 3) Updating registrations from other sources, including: license / up / last / first These might need a bit more discussion, especially license, which is currently defined by RFC4946. Is there any reason that its definition isn't adequate for HTML5? The others need to be coordinated with the individuals who originally registered the relations -- Noah Slater for up, and myself for first and last. I don't think there will be any problem for mine, at least. Cheers, On 02/09/2010, at 6:14 PM, Michael(tm) Smith wrote: > Relation Name: > next > > Description: > Indicates that the current document is a part of a series, and > that the next document in the series is the referenced document. > > Reference: > http://www.w3.org/TR/html5/links.html#link-type-next > > Notes: > Template to be added to W3C HTML5 specification before > publication of next Working Draft > > -- > Michael(tm) Smith > http://people.w3.org/mike > > > _______________________________________________ > link-relations mailing list > link-relations@ietf.org > https://www.ietf.org/mailman/listinfo/link-relations -- Mark Nottingham http://www.mnot.net/
- [link-relations] NEW RELATION REQUEST: Relation n… Michael(tm) Smith
- Re: [link-relations] NEW RELATION REQUEST: Relati… Mark Nottingham
- Re: [link-relations] NEW RELATION REQUEST: Relati… Leif Halvard Silli
- Re: [link-relations] NEW RELATION REQUEST: Relati… Michael(tm) Smith
- [link-relations] where to spec the "license" link… Michael(tm) Smith
- Re: [link-relations] NEW RELATION REQUEST: Relati… Michael(tm) Smith
- Re: [link-relations] where to spec the "license" … Mark Nottingham
- Re: [link-relations] NEW RELATION REQUEST: Relati… Mark Nottingham