Re: [link-relations] NEW APP DATA
Julian Reschke <julian.reschke@gmx.de> Wed, 21 July 2010 21:22 UTC
Return-Path: <julian.reschke@gmx.de>
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 344273A6B4A for <link-relations@core3.amsl.com>; Wed, 21 Jul 2010 14:22:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.829
X-Spam-Level:
X-Spam-Status: No, score=-3.829 tagged_above=-999 required=5 tests=[AWL=-1.230, 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 jYsDvEkkyWXp for <link-relations@core3.amsl.com>; Wed, 21 Jul 2010 14:22:47 -0700 (PDT)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id C46723A6BBA for <link-relations@ietf.org>; Wed, 21 Jul 2010 14:22:46 -0700 (PDT)
Received: (qmail invoked by alias); 21 Jul 2010 21:23:01 -0000
Received: from p508FFB72.dip.t-dialin.net (EHLO [192.168.178.33]) [80.143.251.114] by mail.gmx.net (mp070) with SMTP; 21 Jul 2010 23:23:01 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1+yQqZzWKKy7llcJ85zQe3hzAZkqTR6Bb4K2dNX4V gLhpY8bxLKfzJ/
Message-ID: <4C47652D.9000608@gmx.de>
Date: Wed, 21 Jul 2010 23:22:53 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.11) Gecko/20100711 Lightning/1.0b1 Thunderbird/3.0.6
MIME-Version: 1.0
To: Ian Hickson <ian@hixie.ch>
References: <Pine.LNX.4.64.1007142313280.24444@ps20323.dreamhostps.com> <75A9B632-BED0-41C6-8042-EF93E7146235@mnot.net> <Pine.LNX.4.64.1007150746170.24444@ps20323.dreamhostps.com> <4C3EC34C.6070209@gmx.de> <Pine.LNX.4.64.1007212057560.24444@ps20323.dreamhostps.com>
In-Reply-To: <Pine.LNX.4.64.1007212057560.24444@ps20323.dreamhostps.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: link-relations@ietf.org
Subject: Re: [link-relations] NEW APP DATA
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: Wed, 21 Jul 2010 21:22:48 -0000
On 21.07.2010 23:03, Ian Hickson wrote: > On Thu, 15 Jul 2010, Julian Reschke wrote: >> On 15.07.2010 09:54, Ian Hickson wrote: >>> ... >>> The registration process doesn't mention a specification requirement, so >>> I'm not sure exactly what to provide here. > ... > It's not clear to me if the quotes above were intended to answer my > question or were just helpful background, but since no other reply has You asked about where the specification requirement was, and I pointed to that text. > been forthcoming, I should reiterate that I have no idea what is needed as > part of the registration of fields in terms of a specification. > > Would an equivalent of this section but for this registry be suitable?: > > http://www.whatwg.org/specs/web-apps/current-work/complete.html#other-link-types > > Any help would be most welcome. I thought I had completed the template as > described in the "Link Relation Application Data Registry" section. What's needed is a stable spec that defines the two flags you want to register, and a URI for that spec. Best regards, Julian
- [link-relations] NEW APP DATA Ian Hickson
- Re: [link-relations] NEW APP DATA Mark Nottingham
- Re: [link-relations] NEW APP DATA Ian Hickson
- Re: [link-relations] NEW APP DATA Julian Reschke
- Re: [link-relations] NEW APP DATA Ian Hickson
- Re: [link-relations] NEW APP DATA Julian Reschke
- Re: [link-relations] NEW APP DATA Ian Hickson
- Re: [link-relations] NEW APP DATA Julian Reschke
- [link-relations] NEW APP DATA Ian Hickson
- Re: [link-relations] NEW APP DATA Julian Reschke
- Re: [link-relations] NEW APP DATA Ian Hickson
- Re: [link-relations] NEW APP DATA Julian Reschke
- Re: [link-relations] NEW APP DATA Ian Hickson
- Re: [link-relations] NEW APP DATA Julian Reschke
- Re: [link-relations] NEW APP DATA Ian Hickson
- Re: [link-relations] NEW APP DATA Julian Reschke
- Re: [link-relations] NEW APP DATA Ian Hickson
- Re: [link-relations] NEW APP DATA Julian Reschke
- Re: [link-relations] NEW APP DATA Ian Hickson
- Re: [link-relations] NEW APP DATA Julian Reschke
- Re: [link-relations] NEW APP DATA Mark Nottingham
- Re: [link-relations] NEW APP DATA Mark Nottingham
- Re: [link-relations] NEW APP DATA Philippe Le Hegaret
- Re: [link-relations] NEW APP DATA Ian Hickson
- Re: [link-relations] NEW APP DATA Ian Hickson
- Re: [link-relations] NEW APP DATA Julian Reschke
- [link-relations] app data wrt HTML usage, was: NE… Julian Reschke
- Re: [link-relations] NEW APP DATA Philippe Le Hegaret
- Re: [link-relations] NEW APP DATA Bjoern Hoehrmann
- Re: [link-relations] app data wrt HTML usage, was… Ian Hickson
- Re: [link-relations] app data wrt HTML usage, was… Julian Reschke
- Re: [link-relations] app data wrt HTML usage, was… Ian Hickson
- Re: [link-relations] app data wrt HTML usage, was… Julian Reschke
- Re: [link-relations] NEW APP DATA Mark Nottingham
- Re: [link-relations] NEW APP DATA Mark Nottingham