From ian@hixie.ch Wed Jul 14 16:13:37 2010 Return-Path: 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 C9FBE3A6893 for ; Wed, 14 Jul 2010 16:13:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 2.078 X-Spam-Level: ** X-Spam-Status: No, score=2.078 tagged_above=-999 required=5 tests=[BAYES_50=0.001, SUBJ_ALL_CAPS=2.077] 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 yA7-TfeC4Ix0 for ; Wed, 14 Jul 2010 16:13:36 -0700 (PDT) Received: from looneymail-a4.g.dreamhost.com (caibbdcaaaaf.dreamhost.com [208.113.200.5]) by core3.amsl.com (Postfix) with ESMTP id 41F4B3A6979 for ; Wed, 14 Jul 2010 16:13:36 -0700 (PDT) Received: from ps20323.dreamhostps.com (ps20323.dreamhost.com [69.163.222.251]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by looneymail-a4.g.dreamhost.com (Postfix) with ESMTP id 61AE783E3 for ; Wed, 14 Jul 2010 16:13:46 -0700 (PDT) Date: Wed, 14 Jul 2010 23:13:46 +0000 (UTC) From: Ian Hickson To: link-relations@ietf.org Message-ID: Content-Language: en-GB-hixie Content-Style-Type: text/css MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Mailman-Approved-At: Wed, 14 Jul 2010 16:38:01 -0700 Subject: [link-relations] NEW APP DATA X-BeenThere: link-relations@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jul 2010 23:13:37 -0000 o Application Name: HTML o Description: Allowed on and ? o Default Value: No o Notes: The following values should have "Yes" for this field: alternate, appendix, bookmark, chapter, contents, copyright, first, glossary, help, index, first [sic - it's listed twice?], last, license, next, prev, previous, section, start, subsection, up o Application Name: HTML o Description: Allowed on ? o Default Value: No o Notes: The following values should have "Yes" for this field: alternate, appendix, chapter, contents, copyright, first, glossary, help, index, first [sic - it's listed twice?], last, license, next, prev, previous, section, start, subsection, up -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.' From mnot@mnot.net Wed Jul 14 17:36:55 2010 Return-Path: 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 4B3223A69E4 for ; Wed, 14 Jul 2010 17:36:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.625 X-Spam-Level: X-Spam-Status: No, score=-5.625 tagged_above=-999 required=5 tests=[AWL=-3.026, 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 icZF6LcTe3Mq for ; Wed, 14 Jul 2010 17:36:24 -0700 (PDT) Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by core3.amsl.com (Postfix) with ESMTP id 62CF93A69D8 for ; Wed, 14 Jul 2010 17:36:08 -0700 (PDT) Received: from chancetrain-lm.mnot.net (unknown [118.209.91.138]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id E5AE4509DB; Wed, 14 Jul 2010 20:36:05 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v1081) Content-Type: text/plain; charset=us-ascii From: Mark Nottingham In-Reply-To: Date: Thu, 15 Jul 2010 10:36:02 +1000 Content-Transfer-Encoding: 7bit Message-Id: <75A9B632-BED0-41C6-8042-EF93E7146235@mnot.net> References: To: Ian Hickson X-Mailer: Apple Mail (2.1081) 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Jul 2010 00:36:55 -0000 X-List-Received-Date: Thu, 15 Jul 2010 00:36:55 -0000 Hi Ian, Can you give a link back to where you specify these in HTML5? Cheers, On 15/07/2010, at 9:13 AM, Ian Hickson wrote: > > o Application Name: HTML > o Description: Allowed on and ? > o Default Value: No > o Notes: The following values should have "Yes" for this field: > alternate, appendix, bookmark, chapter, contents, copyright, > first, glossary, help, index, first [sic - it's listed > twice?], last, license, next, prev, previous, section, start, > subsection, up > > o Application Name: HTML > o Description: Allowed on ? > o Default Value: No > o Notes: The following values should have "Yes" for this field: > alternate, appendix, chapter, contents, copyright, first, > glossary, help, index, first [sic - it's listed twice?], last, > license, next, prev, previous, section, start, subsection, up > > -- > Ian Hickson U+1047E )\._.,--....,'``. fL > http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. > Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.' > _______________________________________________ > link-relations mailing list > link-relations@ietf.org > https://www.ietf.org/mailman/listinfo/link-relations -- Mark Nottingham http://www.mnot.net/ From julian.reschke@gmx.de Wed Jul 14 22:44:43 2010 Return-Path: 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 8FDCC3A6990 for ; Wed, 14 Jul 2010 22:44:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.969 X-Spam-Level: X-Spam-Status: No, score=-3.969 tagged_above=-999 required=5 tests=[AWL=-1.370, 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 YhFrEqEe5L4Q for ; Wed, 14 Jul 2010 22:44:40 -0700 (PDT) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id 83CE73A684D for ; Wed, 14 Jul 2010 22:44:39 -0700 (PDT) Received: (qmail invoked by alias); 15 Jul 2010 05:44:48 -0000 Received: from p508FD8A0.dip.t-dialin.net (EHLO [192.168.178.33]) [80.143.216.160] by mail.gmx.net (mp018) with SMTP; 15 Jul 2010 07:44:48 +0200 X-Authenticated: #1915285 X-Provags-ID: V01U2FsdGVkX18WbCIWb0AW1D8BNTBIqPKwrM8EHiMRttSBlN2jqC 4F6PDI41YGComL Message-ID: <4C3EA047.8030807@gmx.de> Date: Thu, 15 Jul 2010 07:44:39 +0200 From: Julian Reschke User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.10) Gecko/20100512 Lightning/1.0b1 Thunderbird/3.0.5 MIME-Version: 1.0 To: link-relations@ietf.org References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Subject: [link-relations] app data for HTML, was: NEW APP DATA X-BeenThere: link-relations@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Jul 2010 05:44:43 -0000 > o Application Name: HTML > o Description: Allowed on and ? > o Default Value: No > o Notes: The following values should have "Yes" for this field: > alternate, appendix, bookmark, chapter, contents, copyright, > first, glossary, help, index, first [sic - it's listed > twice?], last, license, next, prev, previous, section, start, > subsection, up > > o Application Name: HTML > o Description: Allowed on ? > o Default Value: No > o Notes: The following values should have "Yes" for this field: > alternate, appendix, chapter, contents, copyright, first, > glossary, help, index, first [sic - it's listed twice?], last, > license, next, prev, previous, section, start, subsection, up I don't understand the purpose of these flags; it sounds like you're trying to disallow use of the other link relations (those not mentioned above) in HTML. For instance, why disallow "version-history", defined in RFC 5829? Why would anybody want to define a link relation and *not* have it be usable in link/@rel? Could you please clarify? (Also, I believe "Application Name" is supposed to be unique, so it can be used as identifier). Best regards, Julian From ian@hixie.ch Thu Jul 15 00:54:00 2010 Return-Path: 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 316E33A6A9C for ; Thu, 15 Jul 2010 00:54:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.261 X-Spam-Level: X-Spam-Status: No, score=-0.261 tagged_above=-999 required=5 tests=[AWL=2.338, 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 7fr5i5ZzXtJR for ; Thu, 15 Jul 2010 00:53:59 -0700 (PDT) Received: from looneymail-a2.g.dreamhost.com (caibbdcaaaaf.dreamhost.com [208.113.200.5]) by core3.amsl.com (Postfix) with ESMTP id 3F3A33A6A9B for ; Thu, 15 Jul 2010 00:53:59 -0700 (PDT) Received: from ps20323.dreamhostps.com (ps20323.dreamhost.com [69.163.222.251]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by looneymail-a2.g.dreamhost.com (Postfix) with ESMTP id 3E69716D424; Thu, 15 Jul 2010 00:54:09 -0700 (PDT) Date: Thu, 15 Jul 2010 07:54:08 +0000 (UTC) From: Ian Hickson To: Mark Nottingham In-Reply-To: <75A9B632-BED0-41C6-8042-EF93E7146235@mnot.net> Message-ID: References: <75A9B632-BED0-41C6-8042-EF93E7146235@mnot.net> Content-Language: en-GB-hixie Content-Style-Type: text/css MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Jul 2010 07:54:00 -0000 On Thu, 15 Jul 2010, Mark Nottingham wrote: > > Can you give a link back to where you specify these in HTML5? It's not specified in HTML5 at all yet since there's nothing to point to. Currently HTML5 uses its own registry which has this built-in. It's not clear to me how I would specify this without the registry having the field defined. Could you elaborate on what you are looking for? The registration process doesn't mention a specification requirement, so I'm not sure exactly what to provide here. -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.' From julian.reschke@gmx.de Thu Jul 15 01:14:08 2010 Return-Path: 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 4C2D73A6897 for ; Thu, 15 Jul 2010 01:14:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.855 X-Spam-Level: X-Spam-Status: No, score=-3.855 tagged_above=-999 required=5 tests=[AWL=-1.256, 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 5lkcmbGc3+is for ; Thu, 15 Jul 2010 01:14:05 -0700 (PDT) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id D1B553A67ED for ; Thu, 15 Jul 2010 01:14:04 -0700 (PDT) Received: (qmail invoked by alias); 15 Jul 2010 08:14:13 -0000 Received: from p508FD8A0.dip.t-dialin.net (EHLO [192.168.178.33]) [80.143.216.160] by mail.gmx.net (mp050) with SMTP; 15 Jul 2010 10:14:13 +0200 X-Authenticated: #1915285 X-Provags-ID: V01U2FsdGVkX19Xl7Nv+K5Xh4xXCDWrXtg4HotaOsHCaG4Y0Ggpsm 5E1O7xUxORDpzm Message-ID: <4C3EC34C.6070209@gmx.de> Date: Thu, 15 Jul 2010 10:14:04 +0200 From: Julian Reschke User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.10) Gecko/20100512 Lightning/1.0b1 Thunderbird/3.0.5 MIME-Version: 1.0 To: Ian Hickson References: <75A9B632-BED0-41C6-8042-EF93E7146235@mnot.net> In-Reply-To: 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Jul 2010 08:14:08 -0000 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. > ... : Application data is registered on the advice of a Designated Expert (appointed by the IESG or their delegate), with a Specification Required (using terminology from [RFC5226]). : Specification Required - Values and their meanings must be documented in a permanent and readily available public specification, in sufficient detail so that interoperability between independent implementations is possible. When used, Specification Required also implies use of a Designated Expert, who will review the public specification and evaluate whether it is sufficiently clear to allow interoperable implementations. The intention behind "permanent and readily available" is that a document can reasonably be expected to be findable and retrievable long after IANA assignment of the requested value. Publication of an RFC is an ideal means of achieving this requirement, but Specification Required is intended to also cover the case of a document published outside of the RFC path. For RFC publication, the normal RFC review process is expected to provide the necessary review for interoperability, though the Designated Expert may be a particularly well-qualified person to perform such a review. Examples: Diffserv-aware TE Bandwidth Constraints Model Identifiers [RFC4124], TLS ClientCertificateType Identifiers [RFC4346], ROHC Profile Identifiers [RFC4995]. From ian@hixie.ch Wed Jul 21 14:03:42 2010 Return-Path: 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 B691E3A6B78 for ; Wed, 21 Jul 2010 14:03:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.373 X-Spam-Level: X-Spam-Status: No, score=-2.373 tagged_above=-999 required=5 tests=[AWL=0.226, 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 j33W10ADwpfc for ; Wed, 21 Jul 2010 14:03:38 -0700 (PDT) Received: from looneymail-a1.g.dreamhost.com (caibbdcaaaaf.dreamhost.com [208.113.200.5]) by core3.amsl.com (Postfix) with ESMTP id 68C2A3A6BBE for ; Wed, 21 Jul 2010 14:03:37 -0700 (PDT) Received: from ps20323.dreamhostps.com (ps20323.dreamhost.com [69.163.222.251]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by looneymail-a1.g.dreamhost.com (Postfix) with ESMTP id A292215D577 for ; Wed, 21 Jul 2010 14:03:52 -0700 (PDT) Date: Wed, 21 Jul 2010 21:03:52 +0000 (UTC) From: Ian Hickson To: link-relations@ietf.org In-Reply-To: <4C3EC34C.6070209@gmx.de> Message-ID: References: <75A9B632-BED0-41C6-8042-EF93E7146235@mnot.net> <4C3EC34C.6070209@gmx.de> Content-Language: en-GB-hixie Content-Style-Type: text/css MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: [link-relations] NEW APP DATA X-BeenThere: link-relations@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jul 2010 21:03:42 -0000 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. > > : > > Application data is registered on the advice of a Designated Expert > (appointed by the IESG or their delegate), with a Specification > Required (using terminology from [RFC5226]). > > : > > Specification Required - Values and their meanings must be > documented in a permanent and readily available public > specification, in sufficient detail so that interoperability > between independent implementations is possible. When used, > Specification Required also implies use of a Designated > Expert, who will review the public specification and > evaluate whether it is sufficiently clear to allow > interoperable implementations. The intention behind > "permanent and readily available" is that a document can > reasonably be expected to be findable and retrievable long > after IANA assignment of the requested value. Publication > of an RFC is an ideal means of achieving this requirement, > but Specification Required is intended to also cover the > case of a document published outside of the RFC path. For > RFC publication, the normal RFC review process is expected > to provide the necessary review for interoperability, though > the Designated Expert may be a particularly well-qualified > person to perform such a review. > > Examples: Diffserv-aware TE Bandwidth Constraints Model > Identifiers [RFC4124], TLS ClientCertificateType Identifiers > [RFC4346], ROHC Profile Identifiers [RFC4995]. 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 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. -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.' From julian.reschke@gmx.de Wed Jul 21 14:22:48 2010 Return-Path: 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 ; 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 ; 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 ; 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 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 References: <75A9B632-BED0-41C6-8042-EF93E7146235@mnot.net> <4C3EC34C.6070209@gmx.de> In-Reply-To: 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 From ian@hixie.ch Wed Jul 21 16:02:19 2010 Return-Path: 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 7EC953A6818 for ; Wed, 21 Jul 2010 16:02:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.468 X-Spam-Level: X-Spam-Status: No, score=-2.468 tagged_above=-999 required=5 tests=[AWL=0.131, 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 C7JTOHI3V3Gv for ; Wed, 21 Jul 2010 16:02:17 -0700 (PDT) Received: from looneymail-a1.g.dreamhost.com (caibbdcaaaaf.dreamhost.com [208.113.200.5]) by core3.amsl.com (Postfix) with ESMTP id 995273A659C for ; Wed, 21 Jul 2010 16:02:17 -0700 (PDT) Received: from ps20323.dreamhostps.com (ps20323.dreamhost.com [69.163.222.251]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by looneymail-a1.g.dreamhost.com (Postfix) with ESMTP id 5F4A915D577 for ; Wed, 21 Jul 2010 16:02:34 -0700 (PDT) Date: Wed, 21 Jul 2010 23:02:34 +0000 (UTC) From: Ian Hickson To: link-relations@ietf.org In-Reply-To: <4C47652D.9000608@gmx.de> Message-ID: References: <75A9B632-BED0-41C6-8042-EF93E7146235@mnot.net> <4C3EC34C.6070209@gmx.de> <4C47652D.9000608@gmx.de> Content-Language: en-GB-hixie Content-Style-Type: text/css MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: [link-relations] NEW APP DATA X-BeenThere: link-relations@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jul 2010 23:02:19 -0000 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. -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.' From julian.reschke@gmx.de Wed Jul 21 22:11:28 2010 Return-Path: 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 ; 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 ; 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 ; 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 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 References: <75A9B632-BED0-41C6-8042-EF93E7146235@mnot.net> <4C3EC34C.6070209@gmx.de> <4C47652D.9000608@gmx.de> In-Reply-To: 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 element (see ). Best regards, Julian