Re: [link-relations] NEW APP DATA

Julian Reschke <julian.reschke@gmx.de> Thu, 22 July 2010 05:11 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 11BA83A67AE for <link-relations@core3.amsl.com>; Wed, 21 Jul 2010 22:11:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.776
X-Spam-Level:
X-Spam-Status: No, score=-3.776 tagged_above=-999 required=5 tests=[AWL=-1.177, 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 v2BiU1Z9WInx for <link-relations@core3.amsl.com>; Wed, 21 Jul 2010 22:11:22 -0700 (PDT)
Received: from mail.gmx.net (mailout-de.gmx.net [213.165.64.22]) by core3.amsl.com (Postfix) with SMTP id 927DB3A69BE for <link-relations@ietf.org>; Wed, 21 Jul 2010 22:11:21 -0700 (PDT)
Received: (qmail invoked by alias); 22 Jul 2010 05:11:36 -0000
Received: from p508FF1FC.dip.t-dialin.net (EHLO [192.168.178.33]) [80.143.241.252] by mail.gmx.net (mp012) with SMTP; 22 Jul 2010 07:11:36 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1+uUxVRhzyuXyFFp5/yGWkmo/xeM/WbltYBYFkzYk NxbZhbzzFM/Lr1
Message-ID: <4C47D2FF.8060507@gmx.de>
Date: Thu, 22 Jul 2010 07:11:27 +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> <4C47652D.9000608@gmx.de> <Pine.LNX.4.64.1007212301280.24444@ps20323.dreamhostps.com>
In-Reply-To: <Pine.LNX.4.64.1007212301280.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: Thu, 22 Jul 2010 05:11:29 -0000

On 22.07.2010 01:02, Ian Hickson wrote:
> On Wed, 21 Jul 2010, Julian Reschke wrote:
>>
>> What's needed is a stable spec that defines the two flags you want to
>> register, and a URI for that spec.
>
> 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
>
> It's hard to know exactly what you want since the registry has no
> examples.

I don't understand what you mean by "equivalent of this section but for 
this registry".

What's needed is referenceable text that fully describes the metadata 
you want to add to the link relations registry. Yes, that can be a 
section within a larger spec (if this was your question).

In particular it should have sufficient detail so that people defining 
new link relations can understand what to set the value to. So, for 
example, in this case it would need to answer why you would ever want to 
define a link relation and have it *not* allowed in an HTML <link> 
element (see 
<http://www.ietf.org/mail-archive/web/link-relations/current/msg00002.html>).

Best regards, Julian