From mnot@mnot.net Tue Nov 2 21:08:16 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 64E5B3A6A55 for ; Tue, 2 Nov 2010 21:08:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.599 X-Spam-Level: X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=-4.000, 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 U4KYECaZRVAc for ; Tue, 2 Nov 2010 21:08:15 -0700 (PDT) Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by core3.amsl.com (Postfix) with ESMTP id 3915F3A6868 for ; Tue, 2 Nov 2010 21:08:15 -0700 (PDT) Received: from chancetrain-lm.mnot.net (unknown [118.209.39.135]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id F2082509DC; Wed, 3 Nov 2010 00:08:19 -0400 (EDT) From: Mark Nottingham Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Wed, 3 Nov 2010 15:08:16 +1100 Message-Id: To: opensearch@googlegroups.com Mime-Version: 1.0 (Apple Message framework v1081) X-Mailer: Apple Mail (2.1081) Cc: link-relations@ietf.org Subject: [link-relations] Registering the 'search' link relation type 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, 03 Nov 2010 04:08:16 -0000 Hello OpenSearchers, I'm acting as a Designated Expert for the IANA Link Relation Type = registry, defined by RFC5988 . We've had a request from the W3C = HTML WG to register the 'search' link relation type.=20 =20 Since OpenSearch has defined the 'search' relation type, and HTML5 = refers to your specification to define its semantics, we wanted to make = sure this registration was OK with the OpenSearch community before = proceeding. Do you have any objections to them doing so? Additionally, we (the Designated Experts) wanted to double-check with = you that the reference they give is a) appropriate, and b) stable. I.e., = it's not going to change gratuitously.=20 We'd appreciate a response as soon as possible, so that we can proceed = with the registration. Cheers, -- Mark Nottingham http://www.mnot.net/ From dewitt@unto.net Tue Nov 2 21:21:25 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 C52033A6867 for ; Tue, 2 Nov 2010 21:21:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.598 X-Spam-Level: X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4] 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 aPLSJ9z6l3+2 for ; Tue, 2 Nov 2010 21:21:24 -0700 (PDT) Received: from exprod7og118.obsmtp.com (exprod7og118.obsmtp.com [64.18.2.8]) by core3.amsl.com (Postfix) with SMTP id D35703A6A55 for ; Tue, 2 Nov 2010 21:21:23 -0700 (PDT) Received: from source ([209.85.214.41]) by exprod7ob118.postini.com ([64.18.6.12]) with SMTP ID DSNKTNDjSYjgSvGpVd8noC0XgRs7YzGveHwU@postini.com; Tue, 02 Nov 2010 21:21:30 PDT Received: by bwz16 with SMTP id 16so196123bwz.28 for ; Tue, 02 Nov 2010 21:21:29 -0700 (PDT) Received: by 10.204.15.146 with SMTP id k18mr7104270bka.98.1288758088627; Tue, 02 Nov 2010 21:21:28 -0700 (PDT) MIME-Version: 1.0 Sender: dewitt@unto.net Received: by 10.204.57.147 with HTTP; Tue, 2 Nov 2010 21:21:08 -0700 (PDT) In-Reply-To: References: From: DeWitt Clinton Date: Tue, 2 Nov 2010 21:21:08 -0700 X-Google-Sender-Auth: ygaHjYcF3WvpssRY6OkCuY4t9V0 Message-ID: To: opensearch@googlegroups.com Content-Type: multipart/alternative; boundary=00032555a46e12f4a904941e600a X-Mailman-Approved-At: Tue, 02 Nov 2010 21:42:42 -0700 Cc: link-relations@ietf.org Subject: Re: [link-relations] [opensearch:393] Registering the 'search' link relation type 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, 03 Nov 2010 04:21:25 -0000 --00032555a46e12f4a904941e600a Content-Type: text/plain; charset=ISO-8859-1 No objection at all, (speaking as unofficial spec editor). Very glad to see this happen, and thank you to Michael Smith and the W3C HTML WG for making the proposal. That URL is stable, and has not changed in several years, and we would of course be sure to preserve it with a redirect in the event anything ever moved. That said, the full URL appears truncated in the registration application. It currently reads: http://www.opensearch.org/Specifications/OpenSearch/1.1#Autodiscovery_in_HTML.2FXH Should be: http://www.opensearch.org/Specifications/OpenSearch/1.1#Autodiscovery_in_HTML.2FXHTML Thanks, Mark! -DeWitt On Tue, Nov 2, 2010 at 9:08 PM, Mark Nottingham wrote: > Hello OpenSearchers, > > I'm acting as a Designated Expert for the IANA Link Relation Type registry, > defined by RFC5988 . > > We've had a request from the W3C HTML > WG to register the 'search' link relation type. > > Since OpenSearch has defined the 'search' relation type, and HTML5 refers > to your specification to define its semantics, we wanted to make sure this > registration was OK with the OpenSearch community before proceeding. Do you > have any objections to them doing so? > > Additionally, we (the Designated Experts) wanted to double-check with you > that the reference they give is a) appropriate, and b) stable. I.e., it's > not going to change gratuitously. > > We'd appreciate a response as soon as possible, so that we can proceed with > the registration. > > Cheers, > > -- > Mark Nottingham http://www.mnot.net/ > > > > -- > You received this message because you are subscribed to the Google Groups > "OpenSearch" group. > To post to this group, send email to opensearch@googlegroups.com. > To unsubscribe from this group, send email to > opensearch+unsubscribe@googlegroups.com > . > For more options, visit this group at > http://groups.google.com/group/opensearch?hl=en. > > --00032555a46e12f4a904941e600a Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable No objection at all, (speaking as unofficial spec editor). =A0Very glad to = see this happen, and thank you to Michael Smith and the W3C HTML WG for mak= ing the proposal.

That URL is stable, and has not change= d in several years, and we=A0would=A0of course be sure to preserve it with = a redirect in the event anything ever moved.

That said, the full URL appears= truncated in the registration application. =A0It currently reads:


Should be:


Thanks, Mark!

-DeWitt

<= div class=3D"gmail_quote">On Tue, Nov 2, 2010 at 9:08 PM, Mark Nottingham <= span dir=3D"ltr"><mnot@mnot.net>= wrote:
Hello OpenSearchers,

I'm acting as a Designated Expert for the IANA Link Relation Type regis= try, defined by RFC5988 <http://tools.ietf.org/html/rfc5988>.

We've had a request <http://paramsr.us/tracker/issue18> from the W3C HTM= L WG to register the 'search' link relation type.

Since OpenSearch has defined the 'search' relation type, and HTML5 = refers to your specification to define its semantics, we wanted to make sur= e this registration was OK with the OpenSearch community before proceeding.= Do you have any objections to them doing so?

Additionally, we (the Designated Experts) wanted to double-check with you t= hat the reference they give is a) appropriate, and b) stable. I.e., it'= s not going to change gratuitously.

We'd appreciate a response as soon as possible, so that we can proceed = with the registration.

Cheers,

--
Mark Nottingham =A0 http= ://www.mnot.net/



--
You received this message because you are subscribed to the Google Groups &= quot;OpenSearch" group.
To post to this group, send email to opensearch@googlegroups.com.
To unsubscribe from this group, send email to opensearch+unsubscribe@googlegroups.com= .
For more options, visit this group at http://groups.google.com/group/o= pensearch?hl=3Den.


--00032555a46e12f4a904941e600a-- From mnot@mnot.net Tue Nov 2 21:47:32 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 67D6428C0E6 for ; Tue, 2 Nov 2010 21:47:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -105.799 X-Spam-Level: X-Spam-Status: No, score=-105.799 tagged_above=-999 required=5 tests=[AWL=-3.200, 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 xuDplLhJHaBp for ; Tue, 2 Nov 2010 21:47:31 -0700 (PDT) Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by core3.amsl.com (Postfix) with ESMTP id D7C9E3A635F for ; Tue, 2 Nov 2010 21:47:30 -0700 (PDT) Received: from chancetrain-lm.mnot.net (unknown [118.209.39.135]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 4AAF7509B3; Wed, 3 Nov 2010 00:47:26 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v1081) Content-Type: text/plain; charset=us-ascii From: Mark Nottingham In-Reply-To: Date: Wed, 3 Nov 2010 15:47:24 +1100 Content-Transfer-Encoding: quoted-printable Message-Id: <2BCEFDD3-2A6A-49F8-99B0-EC68F9D09FB6@mnot.net> References: To: DeWitt Clinton , "Michael(tm) Smith" X-Mailer: Apple Mail (2.1081) Cc: link-relations@ietf.org, opensearch@googlegroups.com Subject: Re: [link-relations] [opensearch:393] Registering the 'search' link relation type 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, 03 Nov 2010 04:47:32 -0000 Thanks, DeWitt. One thing; I'm wondering if it makes more sense to list the OpenSearch = link directly as the reference, rather than going through the HTML5 one.=20= E.g., the registration could be: Relation Name: search Description: Gives a link to a resource that can be used to search through the current document and its related pages. Reference: = http://www.opensearch.org/Specifications/OpenSearch/1.1#Autodiscovery_in_H= TML.2FXHTML=20 Notes: See also: http://www.w3.org/TR/html5/links.html#link-type-search Thoughts? Mike? On 03/11/2010, at 3:21 PM, DeWitt Clinton wrote: > No objection at all, (speaking as unofficial spec editor). Very glad = to see this happen, and thank you to Michael Smith and the W3C HTML WG = for making the proposal. >=20 > That URL is stable, and has not changed in several years, and we would = of course be sure to preserve it with a redirect in the event anything = ever moved. >=20 > That said, the full URL appears truncated in the registration = application. It currently reads: >=20 > = http://www.opensearch.org/Specifications/OpenSearch/1.1#Autodiscovery_in_H= TML.2FXH >=20 > Should be: >=20 > = http://www.opensearch.org/Specifications/OpenSearch/1.1#Autodiscovery_in_H= TML.2FXHTML >=20 > Thanks, Mark! >=20 > -DeWitt >=20 > On Tue, Nov 2, 2010 at 9:08 PM, Mark Nottingham wrote: > Hello OpenSearchers, >=20 > I'm acting as a Designated Expert for the IANA Link Relation Type = registry, defined by RFC5988 . >=20 > We've had a request from the W3C = HTML WG to register the 'search' link relation type. >=20 > Since OpenSearch has defined the 'search' relation type, and HTML5 = refers to your specification to define its semantics, we wanted to make = sure this registration was OK with the OpenSearch community before = proceeding. Do you have any objections to them doing so? >=20 > Additionally, we (the Designated Experts) wanted to double-check with = you that the reference they give is a) appropriate, and b) stable. I.e., = it's not going to change gratuitously. >=20 > We'd appreciate a response as soon as possible, so that we can proceed = with the registration. >=20 > Cheers, >=20 > -- > Mark Nottingham http://www.mnot.net/ >=20 >=20 >=20 > -- > You received this message because you are subscribed to the Google = Groups "OpenSearch" group. > To post to this group, send email to opensearch@googlegroups.com. > To unsubscribe from this group, send email to = opensearch+unsubscribe@googlegroups.com. > For more options, visit this group at = http://groups.google.com/group/opensearch?hl=3Den. >=20 >=20 > _______________________________________________ > link-relations mailing list > link-relations@ietf.org > https://www.ietf.org/mailman/listinfo/link-relations -- Mark Nottingham http://www.mnot.net/ From dewitt@unto.net Tue Nov 2 21:59:10 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 CAD033A6A70 for ; Tue, 2 Nov 2010 21:59:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.598 X-Spam-Level: X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4] 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 2KNha+iQqhrc for ; Tue, 2 Nov 2010 21:59:09 -0700 (PDT) Received: from exprod7og103.obsmtp.com (exprod7og103.obsmtp.com [64.18.2.159]) by core3.amsl.com (Postfix) with SMTP id 996D73A6A6E for ; Tue, 2 Nov 2010 21:59:08 -0700 (PDT) Received: from source ([209.85.214.46]) by exprod7ob103.postini.com ([64.18.6.12]) with SMTP ID DSNKTNDsIow0aqgQocsYmnsknsI1pe5HqWMA@postini.com; Tue, 02 Nov 2010 21:59:15 PDT Received: by bwz11 with SMTP id 11so237611bwz.5 for ; Tue, 02 Nov 2010 21:59:14 -0700 (PDT) Received: by 10.204.73.1 with SMTP id o1mr7152781bkj.71.1288760353472; Tue, 02 Nov 2010 21:59:13 -0700 (PDT) MIME-Version: 1.0 Sender: dewitt@unto.net Received: by 10.204.57.147 with HTTP; Tue, 2 Nov 2010 21:58:53 -0700 (PDT) In-Reply-To: <2BCEFDD3-2A6A-49F8-99B0-EC68F9D09FB6@mnot.net> References: <2BCEFDD3-2A6A-49F8-99B0-EC68F9D09FB6@mnot.net> From: DeWitt Clinton Date: Tue, 2 Nov 2010 21:58:53 -0700 X-Google-Sender-Auth: ru8IBjkdelJIvIykWG3qTW_COeM Message-ID: To: Mark Nottingham Content-Type: multipart/alternative; boundary=0016368e224b11bf1404941ee75b Cc: "Michael\(tm\) Smith" , link-relations@ietf.org, opensearch@googlegroups.com Subject: Re: [link-relations] [opensearch:393] Registering the 'search' link relation type 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, 03 Nov 2010 04:59:11 -0000 --0016368e224b11bf1404941ee75b Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable If the designated experts are comfortable with that approach =97 and it sou= nds like you might be, otherwise you wouldn't have asked =97 I'd personally pre= fer that, considering the 'search' relation name is used in multiple contexts for the same purpose, not exclusively HTML(5). Thanks for asking, -DeWitt On Tue, Nov 2, 2010 at 9:47 PM, Mark Nottingham wrote: > Thanks, DeWitt. > > One thing; I'm wondering if it makes more sense to list the OpenSearch li= nk > directly as the reference, rather than going through the HTML5 one. > > E.g., the registration could be: > > Relation Name: > search > > Description: > Gives a link to a resource that can be used to search through > the current document and its related pages. > > Reference: > > http://www.opensearch.org/Specifications/OpenSearch/1.1#Autodiscovery_in_= HTML.2FXHTML > > Notes: > See also: http://www.w3.org/TR/html5/links.html#link-type-search > > > Thoughts? Mike? > > > On 03/11/2010, at 3:21 PM, DeWitt Clinton wrote: > > > No objection at all, (speaking as unofficial spec editor). Very glad t= o > see this happen, and thank you to Michael Smith and the W3C HTML WG for > making the proposal. > > > > That URL is stable, and has not changed in several years, and we would = of > course be sure to preserve it with a redirect in the event anything ever > moved. > > > > That said, the full URL appears truncated in the registration > application. It currently reads: > > > > > http://www.opensearch.org/Specifications/OpenSearch/1.1#Autodiscovery_in_= HTML.2FXH > > > > Should be: > > > > > http://www.opensearch.org/Specifications/OpenSearch/1.1#Autodiscovery_in_= HTML.2FXHTML > > > > Thanks, Mark! > > > > -DeWitt > > > > On Tue, Nov 2, 2010 at 9:08 PM, Mark Nottingham wrote: > > Hello OpenSearchers, > > > > I'm acting as a Designated Expert for the IANA Link Relation Type > registry, defined by RFC5988 . > > > > We've had a request from the W3C > HTML WG to register the 'search' link relation type. > > > > Since OpenSearch has defined the 'search' relation type, and HTML5 refe= rs > to your specification to define its semantics, we wanted to make sure thi= s > registration was OK with the OpenSearch community before proceeding. Do y= ou > have any objections to them doing so? > > > > Additionally, we (the Designated Experts) wanted to double-check with y= ou > that the reference they give is a) appropriate, and b) stable. I.e., it's > not going to change gratuitously. > > > > We'd appreciate a response as soon as possible, so that we can proceed > with the registration. > > > > Cheers, > > > > -- > > Mark Nottingham http://www.mnot.net/ > > > > > > > > -- > > You received this message because you are subscribed to the Google Grou= ps > "OpenSearch" group. > > To post to this group, send email to opensearch@googlegroups.com. > > To unsubscribe from this group, send email to > opensearch+unsubscribe@googlegroups.com > . > > For more options, visit this group at > http://groups.google.com/group/opensearch?hl=3Den. > > > > > > _______________________________________________ > > link-relations mailing list > > link-relations@ietf.org > > https://www.ietf.org/mailman/listinfo/link-relations > > -- > Mark Nottingham http://www.mnot.net/ > > > > --0016368e224b11bf1404941ee75b Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable If the designated experts are comfortable with that approach =97 and it sou= nds like you might be, otherwise you wouldn't have asked =97 I'd pe= rsonally prefer that, considering the 'search' relation name is use= d in multiple contexts for the same purpose, not exclusively HTML(5).

Thanks for asking,

-DeWitt

<= div class=3D"gmail_quote">On Tue, Nov 2, 2010 at 9:47 PM, Mark Nottingham <= span dir=3D"ltr"><mnot@mnot.net>= wrote:
Thanks, DeWitt.

One thing; I'm wondering if it makes more sense to list the OpenSearch = link directly as the reference, rather than going through the HTML5 one.
E.g., the registration could be:

Relation Name:
=A0search

Description:
=A0Gives a link to a resource that can be used to search through
=A0the current document and its related pages.

Reference:
=A0http://www.o= pensearch.org/Specifications/OpenSearch/1.1#Autodiscovery_in_HTML.2FXHTML

Notes:
=A0See also: http://www.w3.org/TR/html5/links.html#link-type-sear= ch


Thoughts? Mike?


On 03/11/2010, at 3:21 PM, DeWitt Clinton wrote:

> No objection at all, (speaking as unofficial spec editor). =A0Very gla= d to see this happen, and thank you to Michael Smith and the W3C HTML WG fo= r making the proposal.
>
> That URL is stable, and has not changed in several years, and we would= of course be sure to preserve it with a redirect in the event anything eve= r moved.
>
> That said, the full URL appears truncated in the registration applicat= ion. =A0It currently reads:
>
> =A0http://www.opensearch.org/Spe= cifications/OpenSearch/1.1#Autodiscovery_in_HTML.2FXH
>
> Should be:
>
> =A0http://www.opensearch.org/= Specifications/OpenSearch/1.1#Autodiscovery_in_HTML.2FXHTML
>
> Thanks, Mark!
>
> -DeWitt
>
> On Tue, Nov 2, 2010 at 9:08 PM, Mark Nottingham <mnot@mnot.net> wrote:
> Hello OpenSearchers,
>
> I'm acting as a Designated Expert for the IANA Link Relation Type = registry, defined by RFC5988 <http://tools.ietf.org/html/rfc5988>.
>
> We've had a request <http://paramsr.us/tracker/issue18> from the W3= C HTML WG to register the 'search' link relation type.
>
> Since OpenSearch has defined the 'search' relation type, and H= TML5 refers to your specification to define its semantics, we wanted to mak= e sure this registration was OK with the OpenSearch community before procee= ding. Do you have any objections to them doing so?
>
> Additionally, we (the Designated Experts) wanted to double-check with = you that the reference they give is a) appropriate, and b) stable. I.e., it= 's not going to change gratuitously.
>
> We'd appreciate a response as soon as possible, so that we can pro= ceed with the registration.
>
> Cheers,
>
> --
> Mark Nottingham =A0 http://www.mnot.net/
>
>
>
> --
> You received this message because you are subscribed to the Google Gro= ups "OpenSearch" group.
> To post to this group, send email to opensearch@googlegroups.com.
> To unsubscribe from this group, send email to opensearch+unsubscribe@googlegroups.co= m.
> For more options, visit this group at http://groups.google.com/gr= oup/opensearch?hl=3Den.
>
>
> _______________________________________________
> link-relations mailing list
> link-relations@ietf.org=
> https://www.ietf.org/mailman/listinfo/link-relations

--
Mark Nottingham =A0 http= ://www.mnot.net/




--0016368e224b11bf1404941ee75b-- From mnot@mnot.net Tue Nov 2 22:00:33 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 5BE6A3A6A74 for ; Tue, 2 Nov 2010 22:00:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -105.266 X-Spam-Level: X-Spam-Status: No, score=-105.266 tagged_above=-999 required=5 tests=[AWL=-2.667, 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 vwAwtalIa1ve for ; Tue, 2 Nov 2010 22:00:28 -0700 (PDT) Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by core3.amsl.com (Postfix) with ESMTP id 714883A6A7A for ; Tue, 2 Nov 2010 22:00:28 -0700 (PDT) Received: from chancetrain-lm.mnot.net (unknown [118.209.39.135]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 588BB509B3; Wed, 3 Nov 2010 01:00:32 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v1081) Content-Type: text/plain; charset=windows-1252 From: Mark Nottingham In-Reply-To: Date: Wed, 3 Nov 2010 16:00:29 +1100 Content-Transfer-Encoding: quoted-printable Message-Id: References: <2BCEFDD3-2A6A-49F8-99B0-EC68F9D09FB6@mnot.net> To: DeWitt Clinton X-Mailer: Apple Mail (2.1081) Cc: "Michael\(tm\) Smith" , link-relations@ietf.org, opensearch@googlegroups.com Subject: Re: [link-relations] [opensearch:393] Registering the 'search' link relation type 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, 03 Nov 2010 05:00:33 -0000 OK. If that's the case, should the registration just have: > Reference: > http://www.opensearch.org/Specifications/OpenSearch/1.1 ? Cheers, On 03/11/2010, at 3:58 PM, DeWitt Clinton wrote: > If the designated experts are comfortable with that approach =97 and = it sounds like you might be, otherwise you wouldn't have asked =97 I'd = personally prefer that, considering the 'search' relation name is used = in multiple contexts for the same purpose, not exclusively HTML(5). >=20 > Thanks for asking, >=20 > -DeWitt >=20 > On Tue, Nov 2, 2010 at 9:47 PM, Mark Nottingham wrote: > Thanks, DeWitt. >=20 > One thing; I'm wondering if it makes more sense to list the OpenSearch = link directly as the reference, rather than going through the HTML5 one. >=20 > E.g., the registration could be: >=20 > Relation Name: > search >=20 > Description: > Gives a link to a resource that can be used to search through > the current document and its related pages. >=20 > Reference: > = http://www.opensearch.org/Specifications/OpenSearch/1.1#Autodiscovery_in_H= TML.2FXHTML >=20 > Notes: > See also: http://www.w3.org/TR/html5/links.html#link-type-search >=20 >=20 > Thoughts? Mike? >=20 >=20 > On 03/11/2010, at 3:21 PM, DeWitt Clinton wrote: >=20 > > No objection at all, (speaking as unofficial spec editor). Very = glad to see this happen, and thank you to Michael Smith and the W3C HTML = WG for making the proposal. > > > > That URL is stable, and has not changed in several years, and we = would of course be sure to preserve it with a redirect in the event = anything ever moved. > > > > That said, the full URL appears truncated in the registration = application. It currently reads: > > > > = http://www.opensearch.org/Specifications/OpenSearch/1.1#Autodiscovery_in_H= TML.2FXH > > > > Should be: > > > > = http://www.opensearch.org/Specifications/OpenSearch/1.1#Autodiscovery_in_H= TML.2FXHTML > > > > Thanks, Mark! > > > > -DeWitt > > > > On Tue, Nov 2, 2010 at 9:08 PM, Mark Nottingham = wrote: > > Hello OpenSearchers, > > > > I'm acting as a Designated Expert for the IANA Link Relation Type = registry, defined by RFC5988 . > > > > We've had a request from the W3C = HTML WG to register the 'search' link relation type. > > > > Since OpenSearch has defined the 'search' relation type, and HTML5 = refers to your specification to define its semantics, we wanted to make = sure this registration was OK with the OpenSearch community before = proceeding. Do you have any objections to them doing so? > > > > Additionally, we (the Designated Experts) wanted to double-check = with you that the reference they give is a) appropriate, and b) stable. = I.e., it's not going to change gratuitously. > > > > We'd appreciate a response as soon as possible, so that we can = proceed with the registration. > > > > Cheers, > > > > -- > > Mark Nottingham http://www.mnot.net/ > > > > > > > > -- > > You received this message because you are subscribed to the Google = Groups "OpenSearch" group. > > To post to this group, send email to opensearch@googlegroups.com. > > To unsubscribe from this group, send email to = opensearch+unsubscribe@googlegroups.com. > > For more options, visit this group at = http://groups.google.com/group/opensearch?hl=3Den. > > > > > > _______________________________________________ > > link-relations mailing list > > link-relations@ietf.org > > https://www.ietf.org/mailman/listinfo/link-relations >=20 > -- > Mark Nottingham http://www.mnot.net/ >=20 >=20 >=20 >=20 -- Mark Nottingham http://www.mnot.net/ From dewitt@unto.net Tue Nov 2 22:04:01 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 1388C3A6A79 for ; Tue, 2 Nov 2010 22:04:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.598 X-Spam-Level: X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4] 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 FEQubs9eY3mJ for ; Tue, 2 Nov 2010 22:03:52 -0700 (PDT) Received: from exprod7og105.obsmtp.com (exprod7og105.obsmtp.com [64.18.2.163]) by core3.amsl.com (Postfix) with SMTP id 79D143A6A75 for ; Tue, 2 Nov 2010 22:03:28 -0700 (PDT) Received: from source ([209.85.214.44]) by exprod7ob105.postini.com ([64.18.6.12]) with SMTP ID DSNKTNDs2Xgz0VhKgS3DuF5TzK8QgbUeukgp@postini.com; Tue, 02 Nov 2010 22:03:35 PDT Received: by bwz12 with SMTP id 12so350432bwz.17 for ; Tue, 02 Nov 2010 22:02:16 -0700 (PDT) Received: by 10.204.78.81 with SMTP id j17mr9171233bkk.44.1288760535931; Tue, 02 Nov 2010 22:02:15 -0700 (PDT) MIME-Version: 1.0 Sender: dewitt@unto.net Received: by 10.204.57.147 with HTTP; Tue, 2 Nov 2010 22:01:55 -0700 (PDT) In-Reply-To: References: <2BCEFDD3-2A6A-49F8-99B0-EC68F9D09FB6@mnot.net> From: DeWitt Clinton Date: Tue, 2 Nov 2010 22:01:55 -0700 X-Google-Sender-Auth: S4SqU29zd6VJMUeroZujw-zh-PM Message-ID: To: Mark Nottingham Content-Type: multipart/alternative; boundary=001485f87d96f1dc8a04941ef13d Cc: "Michael\(tm\) Smith" , link-relations@ietf.org, opensearch@googlegroups.com Subject: Re: [link-relations] [opensearch:393] Registering the 'search' link relation type 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, 03 Nov 2010 05:04:01 -0000 --001485f87d96f1dc8a04941ef13d Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Yes, please. -DeWitt On Tue, Nov 2, 2010 at 10:00 PM, Mark Nottingham wrote: > OK. If that's the case, should the registration just have: > > > Reference: > > http://www.opensearch.org/Specifications/OpenSearch/1.1 > > > ? > > Cheers, > > > On 03/11/2010, at 3:58 PM, DeWitt Clinton wrote: > > > If the designated experts are comfortable with that approach =97 and it > sounds like you might be, otherwise you wouldn't have asked =97 I'd perso= nally > prefer that, considering the 'search' relation name is used in multiple > contexts for the same purpose, not exclusively HTML(5). > > > > Thanks for asking, > > > > -DeWitt > > > > On Tue, Nov 2, 2010 at 9:47 PM, Mark Nottingham wrote: > > Thanks, DeWitt. > > > > One thing; I'm wondering if it makes more sense to list the OpenSearch > link directly as the reference, rather than going through the HTML5 one. > > > > E.g., the registration could be: > > > > Relation Name: > > search > > > > Description: > > Gives a link to a resource that can be used to search through > > the current document and its related pages. > > > > Reference: > > > http://www.opensearch.org/Specifications/OpenSearch/1.1#Autodiscovery_in_= HTML.2FXHTML > > > > Notes: > > See also: http://www.w3.org/TR/html5/links.html#link-type-search > > > > > > Thoughts? Mike? > > > > > > On 03/11/2010, at 3:21 PM, DeWitt Clinton wrote: > > > > > No objection at all, (speaking as unofficial spec editor). Very glad > to see this happen, and thank you to Michael Smith and the W3C HTML WG fo= r > making the proposal. > > > > > > That URL is stable, and has not changed in several years, and we woul= d > of course be sure to preserve it with a redirect in the event anything ev= er > moved. > > > > > > That said, the full URL appears truncated in the registration > application. It currently reads: > > > > > > > http://www.opensearch.org/Specifications/OpenSearch/1.1#Autodiscovery_in_= HTML.2FXH > > > > > > Should be: > > > > > > > http://www.opensearch.org/Specifications/OpenSearch/1.1#Autodiscovery_in_= HTML.2FXHTML > > > > > > Thanks, Mark! > > > > > > -DeWitt > > > > > > On Tue, Nov 2, 2010 at 9:08 PM, Mark Nottingham wrote= : > > > Hello OpenSearchers, > > > > > > I'm acting as a Designated Expert for the IANA Link Relation Type > registry, defined by RFC5988 . > > > > > > We've had a request from the W3C > HTML WG to register the 'search' link relation type. > > > > > > Since OpenSearch has defined the 'search' relation type, and HTML5 > refers to your specification to define its semantics, we wanted to make s= ure > this registration was OK with the OpenSearch community before proceeding.= Do > you have any objections to them doing so? > > > > > > Additionally, we (the Designated Experts) wanted to double-check with > you that the reference they give is a) appropriate, and b) stable. I.e., > it's not going to change gratuitously. > > > > > > We'd appreciate a response as soon as possible, so that we can procee= d > with the registration. > > > > > > Cheers, > > > > > > -- > > > Mark Nottingham http://www.mnot.net/ > > > > > > > > > > > > -- > > > You received this message because you are subscribed to the Google > Groups "OpenSearch" group. > > > To post to this group, send email to opensearch@googlegroups.com. > > > To unsubscribe from this group, send email to > opensearch+unsubscribe@googlegroups.com > . > > > For more options, visit this group at > http://groups.google.com/group/opensearch?hl=3Den. > > > > > > > > > _______________________________________________ > > > link-relations mailing list > > > link-relations@ietf.org > > > https://www.ietf.org/mailman/listinfo/link-relations > > > > -- > > Mark Nottingham http://www.mnot.net/ > > > > > > > > > > -- > Mark Nottingham http://www.mnot.net/ > > > > --001485f87d96f1dc8a04941ef13d Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Yes, please.

-DeWitt

O= n Tue, Nov 2, 2010 at 10:00 PM, Mark Nottingham <mnot@mnot.net> wrote:
OK. If that's the case, should the registration just have:

> Reference:
> =A0http://www.opensearch.org/Specifications/OpenSearch/1.1<= /a>


?

Cheers,


On 03/11/2010, at 3:58 PM, DeWitt Clinton wrote:

> If the designated experts are comfortable with that approach =97 and i= t sounds like you might be, otherwise you wouldn't have asked =97 I'= ;d personally prefer that, considering the 'search' relation name i= s used in multiple contexts for the same purpose, not exclusively HTML(5).<= br> >
> Thanks for asking,
>
> -DeWitt
>
> On Tue, Nov 2, 2010 at 9:47 PM, Mark Nottingham <mnot@mnot.net> wrote:
> Thanks, DeWitt.
>
> One thing; I'm wondering if it makes more sense to list the OpenSe= arch link directly as the reference, rather than going through the HTML5 on= e.
>
> E.g., the registration could be:
>
> Relation Name:
> =A0search
>
> Description:
> =A0Gives a link to a resource that can be used to search through
> =A0the current document and its related pages.
>
> Reference:
> =A0http://www.opensearch.org/= Specifications/OpenSearch/1.1#Autodiscovery_in_HTML.2FXHTML
>
> Notes:
> =A0See also: http://www.w3.org/TR/html5/links.html#link-type= -search
>
>
> Thoughts? Mike?
>
>
> On 03/11/2010, at 3:21 PM, DeWitt Clinton wrote:
>
> > No objection at all, (speaking as unofficial spec editor). =A0Ver= y glad to see this happen, and thank you to Michael Smith and the W3C HTML = WG for making the proposal.
> >
> > That URL is stable, and has not changed in several years, and we = would of course be sure to preserve it with a redirect in the event anythin= g ever moved.
> >
> > That said, the full URL appears truncated in the registration app= lication. =A0It currently reads:
> >
> > =A0http://www.opensearch.or= g/Specifications/OpenSearch/1.1#Autodiscovery_in_HTML.2FXH
> >
> > Should be:
> >
> > =A0http://www.opensearch= .org/Specifications/OpenSearch/1.1#Autodiscovery_in_HTML.2FXHTML
> >
> > Thanks, Mark!
> >
> > -DeWitt
> >
> > On Tue, Nov 2, 2010 at 9:08 PM, Mark Nottingham <mnot@mnot.net> wrote:
> > Hello OpenSearchers,
> >
> > I'm acting as a Designated Expert for the IANA Link Relation = Type registry, defined by RFC5988 <http://tools.ietf.org/html/rfc5988>.
> >
> > We've had a request <http://paramsr.us/tracker/issue18> from t= he W3C HTML WG to register the 'search' link relation type.
> >
> > Since OpenSearch has defined the 'search' relation type, = and HTML5 refers to your specification to define its semantics, we wanted t= o make sure this registration was OK with the OpenSearch community before p= roceeding. Do you have any objections to them doing so?
> >
> > Additionally, we (the Designated Experts) wanted to double-check = with you that the reference they give is a) appropriate, and b) stable. I.e= ., it's not going to change gratuitously.
> >
> > We'd appreciate a response as soon as possible, so that we ca= n proceed with the registration.
> >
> > Cheers,
> >
> > --
> > Mark Nottingham =A0 http://www.mnot.net/
> >
> >
> >
> > --
> > You received this message because you are subscribed to the Googl= e Groups "OpenSearch" group.
> > To post to this group, send email to opensearch@googlegroups.com.
> > To unsubscribe from this group, send email to opensearch+unsubscribe@googlegrou= ps.com.
> > For more options, visit this group at http://groups.google.c= om/group/opensearch?hl=3Den.
> >
> >
> > _______________________________________________
> > link-relations mailing list
> > link-relations@ietf.or= g
> > https://www.ietf.org/mailman/listinfo/link-relations<= br> >
> --
> Mark Nottingham =A0 http://www.mnot.net/
>
>
>
>

--
Mark Nottingham =A0 http= ://www.mnot.net/




--001485f87d96f1dc8a04941ef13d-- From julian.reschke@gmx.de Wed Nov 3 01:37:57 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 4A8BA3A6AA6 for ; Wed, 3 Nov 2010 01:37:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.33 X-Spam-Level: X-Spam-Status: No, score=-106.33 tagged_above=-999 required=5 tests=[AWL=-3.731, 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 AbD8MdBelk3O for ; Wed, 3 Nov 2010 01:37:54 -0700 (PDT) Received: from mail.gmx.net (mailout-de.gmx.net [213.165.64.22]) by core3.amsl.com (Postfix) with SMTP id EA0883A6AA8 for ; Wed, 3 Nov 2010 01:37:52 -0700 (PDT) Received: (qmail invoked by alias); 03 Nov 2010 08:37:58 -0000 Received: from mail.greenbytes.de (EHLO [127.0.0.1]) [217.91.35.233] by mail.gmx.net (mp010) with SMTP; 03 Nov 2010 09:37:58 +0100 X-Authenticated: #1915285 X-Provags-ID: V01U2FsdGVkX1+8RvQ3/UK83tlyXkECHfF0xFcacuD3x8uI+XXG1s 881s3a4y3iZOA7 Message-ID: <4CD11F5E.202@gmx.de> Date: Wed, 03 Nov 2010 09:37:50 +0100 From: Julian Reschke User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.12) Gecko/20101027 Lightning/1.0b2 Thunderbird/3.1.6 MIME-Version: 1.0 To: "Michael(tm) Smith" References: <20100902082048.GW58403@sideshowbarker> In-Reply-To: <20100902082048.GW58403@sideshowbarker> 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 RELATION REQUEST: Relation name: "help" 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, 03 Nov 2010 08:37:57 -0000 On 02.09.2010 10:20, Michael(tm) Smith wrote: > Relation Name: > help > > Description: > Provides a link to context-sensitive help. > > Reference: > http://www.w3.org/TR/html5/links.html#link-type-help > > Notes: > Template to be added to W3C HTML5 specification before > publication of next Working Draft Sounds good to me. From julian.reschke@gmx.de Wed Nov 3 01:40:24 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 0AD6F3A6AAE for ; Wed, 3 Nov 2010 01:40:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.123 X-Spam-Level: X-Spam-Status: No, score=-106.123 tagged_above=-999 required=5 tests=[AWL=-3.524, 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 t5RHMFGdFBpp for ; Wed, 3 Nov 2010 01:40:22 -0700 (PDT) Received: from mail.gmx.net (mailout-de.gmx.net [213.165.64.22]) by core3.amsl.com (Postfix) with SMTP id 4A02D3A6AA6 for ; Wed, 3 Nov 2010 01:40:20 -0700 (PDT) Received: (qmail invoked by alias); 03 Nov 2010 08:40:25 -0000 Received: from mail.greenbytes.de (EHLO [127.0.0.1]) [217.91.35.233] by mail.gmx.net (mp072) with SMTP; 03 Nov 2010 09:40:25 +0100 X-Authenticated: #1915285 X-Provags-ID: V01U2FsdGVkX1/vvuEF7J7vphzQctu4MnOA4AVLPZO1i8La+unsBI CPL8Y0Mp58tscF Message-ID: <4CD11FF2.2060003@gmx.de> Date: Wed, 03 Nov 2010 09:40:18 +0100 From: Julian Reschke User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.12) Gecko/20101027 Lightning/1.0b2 Thunderbird/3.1.6 MIME-Version: 1.0 To: "Michael(tm) Smith" References: <20100902081545.GI58403@sideshowbarker> In-Reply-To: <20100902081545.GI58403@sideshowbarker> 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 RELATION REQUEST: Relation name: "bookmark" 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, 03 Nov 2010 08:40:24 -0000 On 02.09.2010 10:15, Michael(tm) Smith wrote: > Relation Name: > bookmark > > Description: > Gives the permalink for the nearest ancestor section. > > Reference: > http://www.w3.org/TR/html5/links.html#link-type-bookmark > > Notes: > Template to be added to W3C HTML5 specification before > publication of next Working Draft I believe this needs to be phrased in a way that it depends on HTML concepts. See also . Best regards, Julian From julian.reschke@gmx.de Wed Nov 3 01:42:20 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 EB8B03A6AA6 for ; Wed, 3 Nov 2010 01:42:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -105.937 X-Spam-Level: X-Spam-Status: No, score=-105.937 tagged_above=-999 required=5 tests=[AWL=-3.338, 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 aZT8m+G4wy1M for ; Wed, 3 Nov 2010 01:42:20 -0700 (PDT) Received: from mail.gmx.net (mailout-de.gmx.net [213.165.64.23]) by core3.amsl.com (Postfix) with SMTP id B7AEE3A6866 for ; Wed, 3 Nov 2010 01:42:19 -0700 (PDT) Received: (qmail invoked by alias); 03 Nov 2010 08:42:25 -0000 Received: from mail.greenbytes.de (EHLO [127.0.0.1]) [217.91.35.233] by mail.gmx.net (mp021) with SMTP; 03 Nov 2010 09:42:25 +0100 X-Authenticated: #1915285 X-Provags-ID: V01U2FsdGVkX1/goTJVxBPg4fK36bCqIgzmZ4GDqnExX81N99mDMa J3o35Ent2UDWk9 Message-ID: <4CD1206B.90904@gmx.de> Date: Wed, 03 Nov 2010 09:42:19 +0100 From: Julian Reschke User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.12) Gecko/20101027 Lightning/1.0b2 Thunderbird/3.1.6 MIME-Version: 1.0 To: "Michael(tm) Smith" References: <20100902081850.GQ58403@sideshowbarker> In-Reply-To: <20100902081850.GQ58403@sideshowbarker> 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 RELATION REQUEST: Relation name: "stylesheet" 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, 03 Nov 2010 08:42:21 -0000 On 02.09.2010 10:18, Michael(tm) Smith wrote: > Relation Name: > stylesheet > > Description: > Imports a stylesheet. > > Reference: > http://www.w3.org/TR/html5/links.html#link-type-stylesheet > > Notes: > Template to be added to W3C HTML5 specification before > publication of next Working Draft I think this needs minor rephrasing, why "import"? Best regards, Julian From julian.reschke@gmx.de Wed Nov 3 01:46:46 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 8AB053A68A3 for ; Wed, 3 Nov 2010 01:46:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -105.77 X-Spam-Level: X-Spam-Status: No, score=-105.77 tagged_above=-999 required=5 tests=[AWL=-3.171, 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 tiaNZf7J83-Z for ; Wed, 3 Nov 2010 01:46:45 -0700 (PDT) Received: from mail.gmx.net (mailout-de.gmx.net [213.165.64.23]) by core3.amsl.com (Postfix) with SMTP id 4DB5C3A6882 for ; Wed, 3 Nov 2010 01:46:44 -0700 (PDT) Received: (qmail invoked by alias); 03 Nov 2010 08:46:50 -0000 Received: from mail.greenbytes.de (EHLO [127.0.0.1]) [217.91.35.233] by mail.gmx.net (mp057) with SMTP; 03 Nov 2010 09:46:50 +0100 X-Authenticated: #1915285 X-Provags-ID: V01U2FsdGVkX18I6Ks5IWsI5P7dyqKTcG83VS86798eJDpxcQVQX0 O7PtdcvrMaqCeD Message-ID: <4CD12176.1030809@gmx.de> Date: Wed, 03 Nov 2010 09:46:46 +0100 From: Julian Reschke User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.12) Gecko/20101027 Lightning/1.0b2 Thunderbird/3.1.6 MIME-Version: 1.0 To: "Michael(tm) Smith" References: <20100902081326.GC58403@sideshowbarker> In-Reply-To: <20100902081326.GC58403@sideshowbarker> 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 RELATION REQUEST: Relation name: "alternate" 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, 03 Nov 2010 08:46:46 -0000 On 02.09.2010 10:13, Michael(tm) Smith wrote: > Relation Name: > alternate > > Description: > Gives alternate representations of the current document. > > Reference: > http://www.w3.org/TR/html5/links.html#link-type-alternate > > Notes: > Template to be added to W3C HTML5 specification before > publication of next Working Draft This used to say: "Designates a substitute for the link's context." This avoids saying "representations", when it's really "resource", and avoids "current document", which may be misleading outside things like HTML. Best regards, Julian From mnot@mnot.net Wed Nov 3 03:10:40 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 374663A68FA for ; Wed, 3 Nov 2010 03:10:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -105.099 X-Spam-Level: X-Spam-Status: No, score=-105.099 tagged_above=-999 required=5 tests=[AWL=-2.500, 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 eAY5W0cSgx57 for ; Wed, 3 Nov 2010 03:10:34 -0700 (PDT) Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by core3.amsl.com (Postfix) with ESMTP id 708FA3A68A3 for ; Wed, 3 Nov 2010 03:10:34 -0700 (PDT) Received: from chancetrain-lm.mnot.net (unknown [118.209.39.135]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 6941F509D9; Wed, 3 Nov 2010 06:10:34 -0400 (EDT) From: Mark Nottingham Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Wed, 3 Nov 2010 21:10:31 +1100 Message-Id: <25AFE76B-66B5-4C91-9C21-12B0072EE212@mnot.net> To: "Michael(tm) Smith" Mime-Version: 1.0 (Apple Message framework v1081) X-Mailer: Apple Mail (2.1081) Cc: link-relations@ietf.org Subject: [link-relations] Link relation registrations from HTML5 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, 03 Nov 2010 10:10:40 -0000 Mike, Now that the RFC has been published, I'm going to start processing of = these requests.=20 1) The first batch have already been approved, and I'll send a request = to IANA shortly. prefetch noreferrer nofollow icon archives author help stylesheet Note that the description of 'icon' has been slightly re-worded to make = it more generic: Links to an icon representing the current document. Likewise, stylesheet is re-worded to: Links to a stylesheet. Tell us if either is an issue for you. 2) I think we can also register next prev ... but before we do, we should clarify the status of 'previous', which = is currently a synonym to 'prev'. The simplest thing to do would be to = copy its text from 'prev', but the HTML document doesn't currently define it = AIUI, so the reference wouldn't be correct. Alternatively, we could deprecate it and point to prev.=20 Thoughts? 3) The following are still in-process, but waiting for the discussion = on-list to finish: bookmark alternate 4) I've temporarily deferred the following, as they appear to be still = under discussion in the HTML WG: sidebar tag external index first=20 last (because it's so closely tied to 'first') 5) Likewise, I've deferred the following until I hear back from you = regarding whether it's acceptable to keep the current description and = reference, updating the notes to point to HTML5 for HTML-specific = concerns: up license 6) We're still processing search. As you've hopefully seen, we've gotten = in touch with OpenSearch and see if they're happy to have HTML5 register = the relation that points to their spec. They say that's OK, but see my = question in that thread re: appropriate references. 7) We've deferred pingback as well. The biggest issue is that it is on a = personal Web site, with no continuity. We really need to see something a = bit more stable, e.g., on the W3C Web site as a Note, or on a stable = community site like microformats.org. Can you look into this?=20 Finally, you can also see the current state of your requests in our = tracker: http://paramsr.us/tracker/ Cheers, -- Mark Nottingham http://www.mnot.net/ From julian.reschke@gmx.de Wed Nov 3 03:46:13 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 B33793A68C4 for ; Wed, 3 Nov 2010 03:46:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -105.619 X-Spam-Level: X-Spam-Status: No, score=-105.619 tagged_above=-999 required=5 tests=[AWL=-3.020, 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 onmF7f2kXv72 for ; Wed, 3 Nov 2010 03:46:13 -0700 (PDT) Received: from mail.gmx.net (mailout-de.gmx.net [213.165.64.22]) by core3.amsl.com (Postfix) with SMTP id 69B3C3A68A3 for ; Wed, 3 Nov 2010 03:46:11 -0700 (PDT) Received: (qmail invoked by alias); 03 Nov 2010 10:46:17 -0000 Received: from mail.greenbytes.de (EHLO [127.0.0.1]) [217.91.35.233] by mail.gmx.net (mp026) with SMTP; 03 Nov 2010 11:46:17 +0100 X-Authenticated: #1915285 X-Provags-ID: V01U2FsdGVkX18u7IQmbHouJPrjPK8fpw565frlHZlqJAEbp51qxb 5f5eFAuVrzGhGY Message-ID: <4CD13D74.8080607@gmx.de> Date: Wed, 03 Nov 2010 11:46:12 +0100 From: Julian Reschke User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.12) Gecko/20101027 Lightning/1.0b2 Thunderbird/3.1.6 MIME-Version: 1.0 To: Mark Nottingham References: <25AFE76B-66B5-4C91-9C21-12B0072EE212@mnot.net> In-Reply-To: <25AFE76B-66B5-4C91-9C21-12B0072EE212@mnot.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Cc: "Michael\(tm\) Smith" , link-relations@ietf.org Subject: Re: [link-relations] Link relation registrations from HTML5 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, 03 Nov 2010 10:46:13 -0000 On 03.11.2010 11:10, Mark Nottingham wrote: > ... > 2) I think we can also register > > next > prev > > ... but before we do, we should clarify the status of 'previous', which is currently a synonym to 'prev'. The simplest thing to do would be to copy > its text from 'prev', but the HTML document doesn't currently define it AIUI, so the reference wouldn't be correct. > > Alternatively, we could deprecate it and point to prev. > > Thoughts? > ... Depends a bit on how popular the synonym is. I'd recommend to update the existing registrations, and treat "previous" separately. > ... Best regards, Julian From julian.reschke@gmx.de Wed Nov 3 08:43:45 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 3D06128C0E5 for ; Wed, 3 Nov 2010 08:43:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -105.524 X-Spam-Level: X-Spam-Status: No, score=-105.524 tagged_above=-999 required=5 tests=[AWL=-2.925, 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 FpMtWgRYaXyw for ; Wed, 3 Nov 2010 08:43:44 -0700 (PDT) Received: from mail.gmx.net (mailout-de.gmx.net [213.165.64.23]) by core3.amsl.com (Postfix) with SMTP id E135128C0DE for ; Wed, 3 Nov 2010 08:43:42 -0700 (PDT) Received: (qmail invoked by alias); 03 Nov 2010 15:43:49 -0000 Received: from mail.greenbytes.de (EHLO [127.0.0.1]) [217.91.35.233] by mail.gmx.net (mp005) with SMTP; 03 Nov 2010 16:43:49 +0100 X-Authenticated: #1915285 X-Provags-ID: V01U2FsdGVkX19hCNEyWNhhZGph5gfWplp6OOhKHdB77VugwMHGCT xnRINom46qvbwF Message-ID: <4CD18330.7040301@gmx.de> Date: Wed, 03 Nov 2010 16:43:44 +0100 From: Julian Reschke User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.12) Gecko/20101027 Lightning/1.0b2 Thunderbird/3.1.6 MIME-Version: 1.0 To: "Michael(tm) Smith" References: <20100902081450.GF58403@sideshowbarker> In-Reply-To: <20100902081450.GF58403@sideshowbarker> 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 RELATION REQUEST: Relation name: "up" 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, 03 Nov 2010 15:43:45 -0000 On 02.09.2010 10:14, Michael(tm) Smith wrote: > Relation Name: > up > > Description: > Provides a link to a document giving the context for the current > document. > > Reference: > http://www.w3.org/TR/html5/links.html#link-type-up > > Notes: > Template to be added to W3C HTML5 specification before > publication of next Working Draft This currently says "Refers to a parent document in a hierarchy of documents." which I think is slightly clearer. Furthermore, the HTML5 spec text being referenced currently has the fancy "up up up" rule for which we have an open HTML WG issue (), so I'd recommend to defer it. Best regards, Julian From julian.reschke@gmx.de Wed Nov 3 08:49:32 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 BBBD63A69B8 for ; Wed, 3 Nov 2010 08:49:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -105.402 X-Spam-Level: X-Spam-Status: No, score=-105.402 tagged_above=-999 required=5 tests=[AWL=-2.803, 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 E+Rtfr2p8eKD for ; Wed, 3 Nov 2010 08:49:31 -0700 (PDT) Received: from mail.gmx.net (mailout-de.gmx.net [213.165.64.22]) by core3.amsl.com (Postfix) with SMTP id 6853F28C0DE for ; Wed, 3 Nov 2010 08:49:30 -0700 (PDT) Received: (qmail invoked by alias); 03 Nov 2010 15:49:36 -0000 Received: from mail.greenbytes.de (EHLO [127.0.0.1]) [217.91.35.233] by mail.gmx.net (mp008) with SMTP; 03 Nov 2010 16:49:36 +0100 X-Authenticated: #1915285 X-Provags-ID: V01U2FsdGVkX1/Qqpovr6HQjnfyofFsM0aU9xheVPSpKm5+yMFWOb YxVSdRWb7KdeWl Message-ID: <4CD18487.8010201@gmx.de> Date: Wed, 03 Nov 2010 16:49:27 +0100 From: Julian Reschke User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.12) Gecko/20101027 Lightning/1.0b2 Thunderbird/3.1.6 MIME-Version: 1.0 To: "Michael(tm) Smith" References: <20100902081545.GI58403@sideshowbarker> <4CD11FF2.2060003@gmx.de> In-Reply-To: <4CD11FF2.2060003@gmx.de> 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 RELATION REQUEST: Relation name: "bookmark" 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, 03 Nov 2010 15:49:32 -0000 On 03.11.2010 09:40, Julian Reschke wrote: > On 02.09.2010 10:15, Michael(tm) Smith wrote: >> Relation Name: >> bookmark >> >> Description: >> Gives the permalink for the nearest ancestor section. >> >> Reference: >> http://www.w3.org/TR/html5/links.html#link-type-bookmark >> >> Notes: >> Template to be added to W3C HTML5 specification before >> publication of next Working Draft > > I believe this needs to be phrased in a way that it depends on HTML > concepts. > ... ...does not depend... BR, Julian From mike@jay.w3.org Wed Nov 3 08:51:10 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 66C5A28C0F8 for ; Wed, 3 Nov 2010 08:51:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.599 X-Spam-Level: X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8] 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 SHjMCYszZNqa for ; Wed, 3 Nov 2010 08:51:09 -0700 (PDT) Received: from jay.w3.org (ssh.w3.org [128.30.52.60]) by core3.amsl.com (Postfix) with ESMTP id 8717828C0DE for ; Wed, 3 Nov 2010 08:51:09 -0700 (PDT) Received: from localhost ([127.0.0.1] helo=MikeSmith.local) by jay.w3.org with esmtp (Exim 4.69) (envelope-from ) id 1PDfcJ-0004kK-2S; Wed, 03 Nov 2010 11:51:15 -0400 Date: Thu, 4 Nov 2010 00:51:11 +0900 From: "Michael(tm) Smith" To: Julian Reschke Message-ID: <20101103155108.GA3616@sideshowbarker> References: <20100902081326.GC58403@sideshowbarker> <4CD12176.1030809@gmx.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4CD12176.1030809@gmx.de> User-Agent: Mutt/r6164+poontang (2010-10-13 07:38:30+09:00) Cc: link-relations@ietf.org Subject: Re: [link-relations] NEW RELATION REQUEST: Relation name: "alternate" 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, 03 Nov 2010 15:51:10 -0000 Julian Reschke , 2010-11-03 09:46 +0100: > On 02.09.2010 10:13, Michael(tm) Smith wrote: > >Description: > > Gives alternate representations of the current document. > > This used to say: > > "Designates a substitute for the link's context." > > This avoids saying "representations", when it's really "resource", and > avoids "current document", which may be misleading outside things like HTML. Fine. Here's the updated request: Relation Name: alternate Description: Designates a substitute for the link's context. Reference: http://www.w3.org/TR/html5/links.html#link-type-alternate Notes: Template to be added to W3C HTML5 specification before publication of next Working Draft -- Michael(tm) Smith http://people.w3.org/mike From mike@jay.w3.org Wed Nov 3 08:53:58 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 038E83A6AC6 for ; Wed, 3 Nov 2010 08:53:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.599 X-Spam-Level: X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8] 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 xk7pw8diwoMn for ; Wed, 3 Nov 2010 08:53:57 -0700 (PDT) Received: from jay.w3.org (ssh.w3.org [128.30.52.60]) by core3.amsl.com (Postfix) with ESMTP id 3FB1C3A69D4 for ; Wed, 3 Nov 2010 08:53:57 -0700 (PDT) Received: from localhost ([127.0.0.1] helo=MikeSmith.local) by jay.w3.org with esmtp (Exim 4.69) (envelope-from ) id 1PDff2-0004sv-61; Wed, 03 Nov 2010 11:54:04 -0400 Date: Thu, 4 Nov 2010 00:54:02 +0900 From: "Michael(tm) Smith" To: Julian Reschke Message-ID: <20101103155402.GB3616@sideshowbarker> References: <20100902081450.GF58403@sideshowbarker> <4CD18330.7040301@gmx.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4CD18330.7040301@gmx.de> User-Agent: Mutt/r6164+poontang (2010-10-13 07:38:30+09:00) Cc: link-relations@ietf.org Subject: Re: [link-relations] NEW RELATION REQUEST: Relation name: "up" 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, 03 Nov 2010 15:53:58 -0000 Julian Reschke , 2010-11-03 16:43 +0100: > On 02.09.2010 10:14, Michael(tm) Smith wrote: > >Relation Name: > > up > > > >Description: > > Provides a link to a document giving the context for the current > > document. > > > >Reference: > > http://www.w3.org/TR/html5/links.html#link-type-up > > > >Notes: > > Template to be added to W3C HTML5 specification before > > publication of next Working Draft > > This currently says "Refers to a parent document in a hierarchy of > documents." which I think is slightly clearer. > > Furthermore, the HTML5 spec text being referenced currently has the fancy > "up up up" rule for which we have an open HTML WG issue > (), so I'd recommend to defer > it. I agree it should be deferred. --Mike -- Michael(tm) Smith http://people.w3.org/mike From mike@jay.w3.org Wed Nov 3 09:24:12 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 5A7753A69CF for ; Wed, 3 Nov 2010 09:24:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.599 X-Spam-Level: X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8] 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 Kewrnrx+mHl7 for ; Wed, 3 Nov 2010 09:24:11 -0700 (PDT) Received: from jay.w3.org (ssh.w3.org [128.30.52.60]) by core3.amsl.com (Postfix) with ESMTP id A53E73A69AB for ; Wed, 3 Nov 2010 09:24:11 -0700 (PDT) Received: from localhost ([127.0.0.1] helo=MikeSmith.local) by jay.w3.org with esmtp (Exim 4.69) (envelope-from ) id 1PDg8I-0007g5-6f; Wed, 03 Nov 2010 12:24:18 -0400 Date: Thu, 4 Nov 2010 01:24:17 +0900 From: "Michael(tm) Smith" To: Julian Reschke Message-ID: <20101103162416.GC3616@sideshowbarker> References: <20100902081850.GQ58403@sideshowbarker> <4CD1206B.90904@gmx.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4CD1206B.90904@gmx.de> User-Agent: Mutt/r6164+poontang (2010-10-13 07:38:30+09:00) Cc: link-relations@ietf.org Subject: Re: [link-relations] NEW RELATION REQUEST: Relation name: "stylesheet" 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, 03 Nov 2010 16:24:12 -0000 Julian Reschke , 2010-11-03 09:42 +0100: > On 02.09.2010 10:18, Michael(tm) Smith wrote: > >Relation Name: > > stylesheet > > > >Description: > > Imports a stylesheet. > > > >Reference: > > http://www.w3.org/TR/html5/links.html#link-type-stylesheet > > > >Notes: > > Template to be added to W3C HTML5 specification before > > publication of next Working Draft > > I think this needs minor rephrasing, why "import"? Updated request: Relation Name: stylesheet Description: Specifies a stylesheet. Reference: http://www.w3.org/TR/html5/links.html#link-type-stylesheet Notes: Template to be added to W3C HTML5 specification before publication of next Working Draft -- Michael(tm) Smith http://people.w3.org/mike From mike@jay.w3.org Wed Nov 3 09:29: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 5EAAB3A6AD5 for ; Wed, 3 Nov 2010 09:29:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.599 X-Spam-Level: X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8] 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 e6JmeymKcIDZ for ; Wed, 3 Nov 2010 09:29:41 -0700 (PDT) Received: from jay.w3.org (ssh.w3.org [128.30.52.60]) by core3.amsl.com (Postfix) with ESMTP id 8B05D3A6AD2 for ; Wed, 3 Nov 2010 09:29:41 -0700 (PDT) Received: from localhost ([127.0.0.1] helo=MikeSmith.local) by jay.w3.org with esmtp (Exim 4.69) (envelope-from ) id 1PDgDc-00085y-JV; Wed, 03 Nov 2010 12:29:48 -0400 Date: Thu, 4 Nov 2010 01:29:47 +0900 From: "Michael(tm) Smith" To: Julian Reschke Message-ID: <20101103162946.GD3616@sideshowbarker> References: <20100902081545.GI58403@sideshowbarker> <4CD11FF2.2060003@gmx.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4CD11FF2.2060003@gmx.de> User-Agent: Mutt/r6164+poontang (2010-10-13 07:38:30+09:00) Cc: link-relations@ietf.org Subject: Re: [link-relations] NEW RELATION REQUEST: Relation name: "bookmark" 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, 03 Nov 2010 16:29:42 -0000 Julian Reschke , 2010-11-03 09:40 +0100: > On 02.09.2010 10:15, Michael(tm) Smith wrote: > >Relation Name: > > bookmark > > > >Description: > > Gives the permalink for the nearest ancestor section. > > > >Reference: > > http://www.w3.org/TR/html5/links.html#link-type-bookmark > > > >Notes: > > Template to be added to W3C HTML5 specification before > > publication of next Working Draft > > I believe this needs to be phrased in a way that it does not depend on > HTML concepts. > > See also . Updated request: Relation Name: bookmark Description: Gives a permanent link to use for bookmarking purposes. Reference: http://www.w3.org/TR/html5/links.html#link-type-bookmark Notes: Template to be added to W3C HTML5 specification before publication of next Working Draft -- Michael(tm) Smith http://people.w3.org/mike From mike@jay.w3.org Wed Nov 3 09:32:31 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 F2B943A6AD8 for ; Wed, 3 Nov 2010 09:32:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.599 X-Spam-Level: X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8] 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 qCJHVTb67dH5 for ; Wed, 3 Nov 2010 09:32:29 -0700 (PDT) Received: from jay.w3.org (ssh.w3.org [128.30.52.60]) by core3.amsl.com (Postfix) with ESMTP id 016E23A6AC9 for ; Wed, 3 Nov 2010 09:32:29 -0700 (PDT) Received: from localhost ([127.0.0.1] helo=MikeSmith.local) by jay.w3.org with esmtp (Exim 4.69) (envelope-from ) id 1PDgGJ-0008Oi-UP; Wed, 03 Nov 2010 12:32:36 -0400 Date: Thu, 4 Nov 2010 01:32:34 +0900 From: "Michael(tm) Smith" To: Julian Reschke Message-ID: <20101103163234.GE3616@sideshowbarker> References: <20100902081934.GS58403@sideshowbarker> <4CCD6EF7.4010902@gmx.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4CCD6EF7.4010902@gmx.de> User-Agent: Mutt/r6164+poontang (2010-10-13 07:38:30+09:00) Cc: link-relations@ietf.org Subject: Re: [link-relations] NEW RELATION REQUEST: Relation name: "prefetch" 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, 03 Nov 2010 16:32:31 -0000 Julian Reschke , 2010-10-31 14:28 +0100: > On 02.09.2010 10:19, Michael(tm) Smith wrote: > I'd say that this really is something like an annotation keyword augmenting > another link relation. > > I have no problem with this being registered, but maybe the HTML5 spec > should clarify that? Yes, but that's something that should be handled separately (by somebody raising an HTML5 spec bug for it). --Mike -- Michael(tm) Smith http://people.w3.org/mike From mike@jay.w3.org Wed Nov 3 09:34: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 234A63A6AD9 for ; Wed, 3 Nov 2010 09:34:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.599 X-Spam-Level: X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8] 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 2o+yE2Odgaxq for ; Wed, 3 Nov 2010 09:34:17 -0700 (PDT) Received: from jay.w3.org (ssh.w3.org [128.30.52.60]) by core3.amsl.com (Postfix) with ESMTP id 78A633A6AD8 for ; Wed, 3 Nov 2010 09:34:17 -0700 (PDT) Received: from localhost ([127.0.0.1] helo=MikeSmith.local) by jay.w3.org with esmtp (Exim 4.69) (envelope-from ) id 1PDgI4-0000Cl-Oh; Wed, 03 Nov 2010 12:34:24 -0400 Date: Thu, 4 Nov 2010 01:34:24 +0900 From: "Michael(tm) Smith" To: Julian Reschke Message-ID: <20101103163423.GF3616@sideshowbarker> References: <20100902081612.GJ58403@sideshowbarker> <4CCD6E16.7040301@gmx.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4CCD6E16.7040301@gmx.de> User-Agent: Mutt/r6164+poontang (2010-10-13 07:38:30+09:00) Cc: link-relations@ietf.org Subject: Re: [link-relations] NEW RELATION REQUEST: Relation name: "noreferrer" 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, 03 Nov 2010 16:34:19 -0000 Julian Reschke , 2010-10-31 14:24 +0100: > On 02.09.2010 10:16, Michael(tm) Smith wrote: > >Relation Name: > > noreferrer > > > >Description: > > Requires that the user agent not send an HTTP "Referer" (sic) > > header if the user follows the hyperlink. > > > >Reference: > > http://www.w3.org/TR/html5/links.html#link-type-noreferrer > > > >Notes: > > Template to be added to W3C HTML5 specification before > > publication of next Working Draft > > Sounds good to me, except it might be good to be less specific about HTTP > (it should be applicable to other protocols in theory as well). > > Indeed, HTML5 says: > > "It indicates that no referrer information is to be leaked when following > the link." Updated request: Relation Name: noreferrer Description: Indicates that no referrer information is to be leaked when following the link. Reference: http://www.w3.org/TR/html5/links.html#link-type-noreferrer Notes: Template to be added to W3C HTML5 specification before publication of next Working Draft -- Michael(tm) Smith http://people.w3.org/mike From mike@jay.w3.org Wed Nov 3 09:35:56 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 D35A428C0FA for ; Wed, 3 Nov 2010 09:35:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.599 X-Spam-Level: X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8] 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 zVU1VFPRjiOM for ; Wed, 3 Nov 2010 09:35:55 -0700 (PDT) Received: from jay.w3.org (ssh.w3.org [128.30.52.60]) by core3.amsl.com (Postfix) with ESMTP id 98A4228C107 for ; Wed, 3 Nov 2010 09:35:55 -0700 (PDT) Received: from localhost ([127.0.0.1] helo=MikeSmith.local) by jay.w3.org with esmtp (Exim 4.69) (envelope-from ) id 1PDgJe-0000Op-Lx; Wed, 03 Nov 2010 12:36:02 -0400 Date: Thu, 4 Nov 2010 01:36:02 +0900 From: "Michael(tm) Smith" To: Julian Reschke Message-ID: <20101103163601.GG3616@sideshowbarker> References: <20100902081806.GN58403@sideshowbarker> <4CCD6D45.2070306@gmx.de> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-2022-jp Content-Disposition: inline In-Reply-To: <4CCD6D45.2070306@gmx.de> User-Agent: Mutt/r6164+poontang (2010-10-13 07:38:30+09:00) Cc: link-relations@ietf.org Subject: Re: [link-relations] NEW RELATION REQUEST: Relation name: "nofollow" 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, 03 Nov 2010 16:35:56 -0000 Julian Reschke , 2010-10-31 14:21 +0100: > On 02.09.2010 10:18, Michael(tm) Smith wrote: > > Relation Name: > > nofollow > > > > Description: > > Indicates that the current document$B!G(Bs original author or > > publisher does not endorse the referenced document. > > > > Reference: > > http://www.w3.org/TR/html5/links.html#link-type-nofollow > > > > Notes: > > Template to be added to W3C HTML5 specification before > > publication of next Working Draft > > Sounds good to me (maybe substiture document with resource, though). Updated request: Relation Name: nofollow Description: Indicates that the current resources$B!G(Bs original author or publisher does not endorse the referenced resource. Reference: http://www.w3.org/TR/html5/links.html#link-type-nofollow Notes: Template to be added to W3C HTML5 specification before publication of next Working Draft -- Michael(tm) Smith http://people.w3.org/mike From mike@jay.w3.org Wed Nov 3 09:38:24 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 82D3C28C112 for ; Wed, 3 Nov 2010 09:38:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.599 X-Spam-Level: X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8] 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 zDSeSuGEbxN9 for ; Wed, 3 Nov 2010 09:38:23 -0700 (PDT) Received: from jay.w3.org (ssh.w3.org [128.30.52.60]) by core3.amsl.com (Postfix) with ESMTP id B8B3328C10F for ; Wed, 3 Nov 2010 09:38:22 -0700 (PDT) Received: from localhost ([127.0.0.1] helo=MikeSmith.local) by jay.w3.org with esmtp (Exim 4.69) (envelope-from ) id 1PDgM1-0000bo-KR; Wed, 03 Nov 2010 12:38:29 -0400 Date: Thu, 4 Nov 2010 01:38:28 +0900 From: "Michael(tm) Smith" To: Julian Reschke Message-ID: <20101103163828.GH3616@sideshowbarker> References: <20100902081506.GG58403@sideshowbarker> <4CCD6B6A.1050805@gmx.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4CCD6B6A.1050805@gmx.de> User-Agent: Mutt/r6164+poontang (2010-10-13 07:38:30+09:00) Cc: link-relations@ietf.org Subject: Re: [link-relations] NEW RELATION REQUEST: Relation name: "icon" 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, 03 Nov 2010 16:38:24 -0000 Julian Reschke , 2010-10-31 14:13 +0100: > On 02.09.2010 10:15, Michael(tm) Smith wrote: > >Relation Name: > > icon > > > >Description: > > Imports an icon to represent the current document. > > > >Reference: > > http://www.w3.org/TR/html5/links.html#link-type-icon > > > >Notes: > > Template to be added to W3C HTML5 specification before > > publication of next Working Draft > > "Imports"? Did you mean "Identifies"? > > I think the spec actually has a slightly better wording: > > "The specified resource is an icon representing the page or site, and should > be used by the user agent when representing the page in the user interface." Updated request: Relation Name: icon Description: The specified resource is an icon representing the page or site, and should be used by the user agent when representing the page in the user interface. Reference: http://www.w3.org/TR/html5/links.html#link-type-icon Notes: Template to be added to W3C HTML5 specification before publication of next Working Draft -- Michael(tm) Smith http://people.w3.org/mike From mike@jay.w3.org Wed Nov 3 09:45:12 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 94FD528C10F for ; Wed, 3 Nov 2010 09:45:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.599 X-Spam-Level: X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8] 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 HXsY4NwnDMa3 for ; Wed, 3 Nov 2010 09:45:11 -0700 (PDT) Received: from jay.w3.org (ssh.w3.org [128.30.52.60]) by core3.amsl.com (Postfix) with ESMTP id 35D8B28C0FF for ; Wed, 3 Nov 2010 09:45:11 -0700 (PDT) Received: from localhost ([127.0.0.1] helo=MikeSmith.local) by jay.w3.org with esmtp (Exim 4.69) (envelope-from ) id 1PDgSb-0001NN-G8; Wed, 03 Nov 2010 12:45:17 -0400 Date: Thu, 4 Nov 2010 01:45:16 +0900 From: "Michael(tm) Smith" To: Mark Nottingham Message-ID: <20101103164516.GI3616@sideshowbarker> References: <2BCEFDD3-2A6A-49F8-99B0-EC68F9D09FB6@mnot.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/r6164+poontang (2010-10-13 07:38:30+09:00) Cc: DeWitt Clinton , link-relations@ietf.org, opensearch@googlegroups.com Subject: Re: [link-relations] [opensearch:393] Registering the 'search' link relation type 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, 03 Nov 2010 16:45:12 -0000 Updated request (in full): Relation Name: search Description: Gives a link to a resource that can be used to search through the current document and its related pages. Reference: http://www.opensearch.org/Specifications/OpenSearch/1.1#Autodiscovery_in_HTML.2FXHTML DeWitt Clinton , 2010-11-02 22:01 -0700: > Yes, please. > > -DeWitt > > On Tue, Nov 2, 2010 at 10:00 PM, Mark Nottingham wrote: > > > OK. If that's the case, should the registration just have: > > > > > Reference: > > > http://www.opensearch.org/Specifications/OpenSearch/1.1 > > > > > > ? > > > > Cheers, > > > > > > On 03/11/2010, at 3:58 PM, DeWitt Clinton wrote: > > > > > If the designated experts are comfortable with that approach — and it > > sounds like you might be, otherwise you wouldn't have asked — I'd personally > > prefer that, considering the 'search' relation name is used in multiple > > contexts for the same purpose, not exclusively HTML(5). > > > > > > Thanks for asking, > > > > > > -DeWitt > > > > > > On Tue, Nov 2, 2010 at 9:47 PM, Mark Nottingham wrote: > > > Thanks, DeWitt. > > > > > > One thing; I'm wondering if it makes more sense to list the OpenSearch > > link directly as the reference, rather than going through the HTML5 one. > > > > > > E.g., the registration could be: > > > > > > Relation Name: > > > search > > > > > > Description: > > > Gives a link to a resource that can be used to search through > > > the current document and its related pages. > > > > > > Reference: > > > > > http://www.opensearch.org/Specifications/OpenSearch/1.1#Autodiscovery_in_HTML.2FXHTML > > > > > > Notes: > > > See also: http://www.w3.org/TR/html5/links.html#link-type-search > > > > > > > > > Thoughts? Mike? > > > > > > > > > On 03/11/2010, at 3:21 PM, DeWitt Clinton wrote: > > > > > > > No objection at all, (speaking as unofficial spec editor). Very glad > > to see this happen, and thank you to Michael Smith and the W3C HTML WG for > > making the proposal. > > > > > > > > That URL is stable, and has not changed in several years, and we would > > of course be sure to preserve it with a redirect in the event anything ever > > moved. > > > > > > > > That said, the full URL appears truncated in the registration > > application. It currently reads: > > > > > > > > > > http://www.opensearch.org/Specifications/OpenSearch/1.1#Autodiscovery_in_HTML.2FXH > > > > > > > > Should be: > > > > > > > > > > http://www.opensearch.org/Specifications/OpenSearch/1.1#Autodiscovery_in_HTML.2FXHTML > > > > > > > > Thanks, Mark! > > > > > > > > -DeWitt > > > > > > > > On Tue, Nov 2, 2010 at 9:08 PM, Mark Nottingham wrote: > > > > Hello OpenSearchers, > > > > > > > > I'm acting as a Designated Expert for the IANA Link Relation Type > > registry, defined by RFC5988 . > > > > > > > > We've had a request from the W3C > > HTML WG to register the 'search' link relation type. > > > > > > > > Since OpenSearch has defined the 'search' relation type, and HTML5 > > refers to your specification to define its semantics, we wanted to make sure > > this registration was OK with the OpenSearch community before proceeding. Do > > you have any objections to them doing so? > > > > > > > > Additionally, we (the Designated Experts) wanted to double-check with > > you that the reference they give is a) appropriate, and b) stable. I.e., > > it's not going to change gratuitously. > > > > > > > > We'd appreciate a response as soon as possible, so that we can proceed > > with the registration. > > > > > > > > Cheers, > > > > > > > > -- > > > > Mark Nottingham http://www.mnot.net/ > > > > > > > > > > > > > > > > -- > > > > You received this message because you are subscribed to the Google > > Groups "OpenSearch" group. > > > > To post to this group, send email to opensearch@googlegroups.com. > > > > To unsubscribe from this group, send email to > > opensearch+unsubscribe@googlegroups.com > > . > > > > For more options, visit this group at > > http://groups.google.com/group/opensearch?hl=en. > > > > > > > > > > > > _______________________________________________ > > > > link-relations mailing list > > > > link-relations@ietf.org > > > > https://www.ietf.org/mailman/listinfo/link-relations > > > > > > -- > > > Mark Nottingham http://www.mnot.net/ > > > > > > > > > > > > > > -- Michael(tm) Smith http://people.w3.org/mike From mike@jay.w3.org Wed Nov 3 10:07:32 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 E09023A69C2 for ; Wed, 3 Nov 2010 10:07:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.599 X-Spam-Level: X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8] 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 dh-YAaLDpqjF for ; Wed, 3 Nov 2010 10:07:31 -0700 (PDT) Received: from jay.w3.org (ssh.w3.org [128.30.52.60]) by core3.amsl.com (Postfix) with ESMTP id 811A728C0FA for ; Wed, 3 Nov 2010 10:07:31 -0700 (PDT) Received: from localhost ([127.0.0.1] helo=MikeSmith.local) by jay.w3.org with esmtp (Exim 4.69) (envelope-from ) id 1PDgoD-0003Rt-AF; Wed, 03 Nov 2010 13:07:37 -0400 Date: Thu, 4 Nov 2010 02:07:36 +0900 From: "Michael(tm) Smith" To: Mark Nottingham Message-ID: <20101103170736.GJ3616@sideshowbarker> References: <25AFE76B-66B5-4C91-9C21-12B0072EE212@mnot.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <25AFE76B-66B5-4C91-9C21-12B0072EE212@mnot.net> User-Agent: Mutt/r6164+poontang (2010-10-13 07:38:30+09:00) Cc: link-relations@ietf.org Subject: Re: [link-relations] Link relation registrations from HTML5 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, 03 Nov 2010 17:07:33 -0000 Mark Nottingham , 2010-11-03 21:10 +1100: > 1) The first batch have already been approved, and I'll send a request to IANA shortly. > > prefetch > noreferrer > nofollow > icon > archives > author > help > stylesheet > > Note that the description of 'icon' has been slightly re-worded to make it more generic: > > Links to an icon representing the current document. I just sent an updated request with that changed to: The specified resource is an icon representing the page or site, and should be used by the user agent when representing the page in the user interface. But I think "Links to an icon representing the current document." is also fine. I leave it up to the DEs to discuss and make a final decision on. > Likewise, stylesheet is re-worded to: > > Links to a stylesheet. I sent an updated request with the wording "Specifies a stylesheet." but I think "Links to a stylesheet." is also fine. I leave it up to the DEs to discuss and make a final decision on. > Tell us if either is an issue for you. No issues for me, but as noted above, I leave it up to you all to decide the final wording. > 2) I think we can also register > > next > prev > > ... but before we do, we should clarify the status of 'previous', which is currently a synonym to 'prev'. The simplest thing to do would be to copy > its text from 'prev', but the HTML document doesn't currently define it AIUI, so the reference wouldn't be correct. > > Alternatively, we could deprecate it and point to prev. > > Thoughts? I agree with Julian -- I think we should go ahead an register "prev" and deal with follow-up about "previous" in parallel. > 3) The following are still in-process, but waiting for the discussion on-list to finish: > > bookmark > alternate See my updated requests for those - http://www.ietf.org/mail-archive/web/link-relations/current/msg00110.html http://www.ietf.org/mail-archive/web/link-relations/current/msg00111.html > 4) I've temporarily deferred the following, as they appear to be still under discussion in the HTML WG: > > sidebar > tag > external > index > first > last (because it's so closely tied to 'first') Yep > 5) Likewise, I've deferred the following until I hear back from you > regarding whether it's acceptable to keep the current description and > reference, updating the notes to point to HTML5 for HTML-specific > concerns: > > up I agree with Julian that is makes sense to defer that one. > license Here's an updated request (in full): Relation Name: license Description: Refers to a license associated with the link's context. Reference: [RFC4946] Notes: For implications of use in HTML, see: http://www.w3.org/TR/html5/links.html#link-type-license > 6) We're still processing search. As you've hopefully seen, we've gotten > in touch with OpenSearch and see if they're happy to have HTML5 register > the relation that points to their spec. They say that's OK, but see my > question in that thread re: appropriate references. See my updated request: http://www.ietf.org/mail-archive/web/link-relations/current/msg00119.html > 7) We've deferred pingback as well. The biggest issue is that it is on a > personal Web site, with no continuity. We really need to see something a > bit more stable, e.g., on the W3C Web site as a Note, or on a stable > community site like microformats.org. Can you look into this? Yes, I will. > Finally, you can also see the current state of your requests in our tracker: > http://paramsr.us/tracker/ Thanks --Mike -- Michael(tm) Smith http://people.w3.org/mike From mnot@mnot.net Wed Nov 3 15:44:33 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 C6EB93A687D for ; Wed, 3 Nov 2010 15:44:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -104.821 X-Spam-Level: X-Spam-Status: No, score=-104.821 tagged_above=-999 required=5 tests=[AWL=-2.222, 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 ULqQQhAunSX2 for ; Wed, 3 Nov 2010 15:44:32 -0700 (PDT) Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by core3.amsl.com (Postfix) with ESMTP id E97D83A6774 for ; Wed, 3 Nov 2010 15:44:31 -0700 (PDT) Received: from chancetrain-lm.mnot.net (unknown [118.209.39.135]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 78E94509D9; Wed, 3 Nov 2010 18:44:37 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v1081) Content-Type: text/plain; charset=us-ascii From: Mark Nottingham In-Reply-To: <20101103170736.GJ3616@sideshowbarker> Date: Thu, 4 Nov 2010 09:44:35 +1100 Content-Transfer-Encoding: quoted-printable Message-Id: References: <25AFE76B-66B5-4C91-9C21-12B0072EE212@mnot.net> <20101103170736.GJ3616@sideshowbarker> To: Michael(tm) Smith X-Mailer: Apple Mail (2.1081) Cc: link-relations@ietf.org Subject: Re: [link-relations] Link relation registrations from HTML5 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, 03 Nov 2010 22:44:34 -0000 Thanks for the reply, Mike. Followups inline. On 04/11/2010, at 4:07 AM, Michael(tm) Smith wrote: >>=20 >> Note that the description of 'icon' has been slightly re-worded to = make it more generic: >>=20 >> Links to an icon representing the current document. >=20 > I just sent an updated request with that changed to: >=20 > The specified resource is an icon representing the page or site, and > should be used by the user agent when representing the page in the = user > interface. >=20 > But I think "Links to an icon representing the current document." is = also > fine. I leave it up to the DEs to discuss and make a final decision = on. >=20 >> Likewise, stylesheet is re-worded to: >>=20 >> Links to a stylesheet. >=20 > I sent an updated request with the wording "Specifies a stylesheet." = but I > think "Links to a stylesheet." is also fine. I leave it up to the DEs = to > discuss and make a final decision on. >=20 >> Tell us if either is an issue for you. >=20 > No issues for me, but as noted above, I leave it up to you all to = decide > the final wording. Right. I'm inclined to do a light edit of the request descriptions to = bring them into a bit more alignment, if it's OK with you. I.e., right now they use phrases like: "provides a link" "gives a link to the current document's..." "links to an..." "indicates that the current resource's..." "specifies that the target resource..." "specifies a..." "designates a..." "refers to a..." whereas the registry entries tend to use "refers to a...", "context" and = "resource." I'd suggest we: - use "refers to..." instead of "provides..." "gives..." and similar - use "indicates..." instead of "designates" - use "current resource" or "link's context" instead of "current = document" - use "link target" instead of "referenced resource" To be clear -- this is all completely optional, and I'm not going to = hold up registration by splitting hairs over terminology.=20 I'll send a summary of the edits for review separately if you agree. >> 2) I think we can also register >>=20 >> next >> prev >>=20 >> ... but before we do, we should clarify the status of 'previous', = which is currently a synonym to 'prev'. The simplest thing to do would = be to copy >> its text from 'prev', but the HTML document doesn't currently define = it AIUI, so the reference wouldn't be correct. >>=20 >> Alternatively, we could deprecate it and point to prev.=20 >>=20 >> Thoughts? >=20 > I agree with Julian -- I think we should go ahead an register "prev" = and > deal with follow-up about "previous" in parallel. Will do. >> 3) The following are still in-process, but waiting for the discussion = on-list to finish: >>=20 >> bookmark >> alternate >=20 > See my updated requests for those - >=20 > = http://www.ietf.org/mail-archive/web/link-relations/current/msg00110.html > = http://www.ietf.org/mail-archive/web/link-relations/current/msg00111.html Approved, keeping in mind the terminology question above. > Here's an updated request (in full): >=20 > Relation Name: = = =20 > license = = =20 >=20 > Description: = = =20 > Refers to a license associated with the link's context. = = =20 >=20 > Reference: = = =20 > [RFC4946] = = =20 >=20 > Notes: = = =20 > For implications of use in HTML, see: > http://www.w3.org/TR/html5/links.html#link-type-license Approved. >> 6) We're still processing search. As you've hopefully seen, we've = gotten >> in touch with OpenSearch and see if they're happy to have HTML5 = register >> the relation that points to their spec. They say that's OK, but see = my >> question in that thread re: appropriate references. >=20 > See my updated request: >=20 > = http://www.ietf.org/mail-archive/web/link-relations/current/msg00119.html Will follow up there. Cheers, -- Mark Nottingham http://www.mnot.net/ From mnot@mnot.net Wed Nov 3 17:46:58 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 E76B83A69E8 for ; Wed, 3 Nov 2010 17:46:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -104.599 X-Spam-Level: X-Spam-Status: No, score=-104.599 tagged_above=-999 required=5 tests=[AWL=-2.000, 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 cph5X18EjJHz for ; Wed, 3 Nov 2010 17:46:57 -0700 (PDT) Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by core3.amsl.com (Postfix) with ESMTP id 5EE903A69CE for ; Wed, 3 Nov 2010 17:46:57 -0700 (PDT) Received: from chancetrain-lm.mnot.net (unknown [118.209.39.135]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id B53C1509D9; Wed, 3 Nov 2010 20:46:58 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v1081) Content-Type: text/plain; charset=windows-1252 From: Mark Nottingham In-Reply-To: <20101103164516.GI3616@sideshowbarker> Date: Thu, 4 Nov 2010 11:46:55 +1100 Content-Transfer-Encoding: quoted-printable Message-Id: References: <2BCEFDD3-2A6A-49F8-99B0-EC68F9D09FB6@mnot.net> <20101103164516.GI3616@sideshowbarker> To: Michael(tm) Smith X-Mailer: Apple Mail (2.1081) Cc: DeWitt Clinton , link-relations@ietf.org, opensearch@googlegroups.com Subject: Re: [link-relations] [opensearch:393] Registering the 'search' link relation type 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, 04 Nov 2010 00:46:59 -0000 Mike, are you requesting the link with the fragid on purpose? Clinton = and I seem to agree that going without makes more sense. Cheers, On 04/11/2010, at 3:45 AM, Michael(tm) Smith wrote: > Updated request (in full): >=20 > Relation Name: > search >=20 > Description: > Gives a link to a resource that can be used to search through > the current document and its related pages. >=20 > Reference: > = http://www.opensearch.org/Specifications/OpenSearch/1.1#Autodiscovery_in_H= TML.2FXHTML >=20 > DeWitt Clinton , 2010-11-02 22:01 -0700: >=20 >> Yes, please. >>=20 >> -DeWitt >>=20 >> On Tue, Nov 2, 2010 at 10:00 PM, Mark Nottingham = wrote: >>=20 >>> OK. If that's the case, should the registration just have: >>>=20 >>>> Reference: >>>> http://www.opensearch.org/Specifications/OpenSearch/1.1 >>>=20 >>>=20 >>> ? >>>=20 >>> Cheers, >>>=20 >>>=20 >>> On 03/11/2010, at 3:58 PM, DeWitt Clinton wrote: >>>=20 >>>> If the designated experts are comfortable with that approach =97 = and it >>> sounds like you might be, otherwise you wouldn't have asked =97 I'd = personally >>> prefer that, considering the 'search' relation name is used in = multiple >>> contexts for the same purpose, not exclusively HTML(5). >>>>=20 >>>> Thanks for asking, >>>>=20 >>>> -DeWitt >>>>=20 >>>> On Tue, Nov 2, 2010 at 9:47 PM, Mark Nottingham = wrote: >>>> Thanks, DeWitt. >>>>=20 >>>> One thing; I'm wondering if it makes more sense to list the = OpenSearch >>> link directly as the reference, rather than going through the HTML5 = one. >>>>=20 >>>> E.g., the registration could be: >>>>=20 >>>> Relation Name: >>>> search >>>>=20 >>>> Description: >>>> Gives a link to a resource that can be used to search through >>>> the current document and its related pages. >>>>=20 >>>> Reference: >>>>=20 >>> = http://www.opensearch.org/Specifications/OpenSearch/1.1#Autodiscovery_in_H= TML.2FXHTML >>>>=20 >>>> Notes: >>>> See also: http://www.w3.org/TR/html5/links.html#link-type-search >>>>=20 >>>>=20 >>>> Thoughts? Mike? >>>>=20 >>>>=20 >>>> On 03/11/2010, at 3:21 PM, DeWitt Clinton wrote: >>>>=20 >>>>> No objection at all, (speaking as unofficial spec editor). Very = glad >>> to see this happen, and thank you to Michael Smith and the W3C HTML = WG for >>> making the proposal. >>>>>=20 >>>>> That URL is stable, and has not changed in several years, and we = would >>> of course be sure to preserve it with a redirect in the event = anything ever >>> moved. >>>>>=20 >>>>> That said, the full URL appears truncated in the registration >>> application. It currently reads: >>>>>=20 >>>>>=20 >>> = http://www.opensearch.org/Specifications/OpenSearch/1.1#Autodiscovery_in_H= TML.2FXH >>>>>=20 >>>>> Should be: >>>>>=20 >>>>>=20 >>> = http://www.opensearch.org/Specifications/OpenSearch/1.1#Autodiscovery_in_H= TML.2FXHTML >>>>>=20 >>>>> Thanks, Mark! >>>>>=20 >>>>> -DeWitt >>>>>=20 >>>>> On Tue, Nov 2, 2010 at 9:08 PM, Mark Nottingham = wrote: >>>>> Hello OpenSearchers, >>>>>=20 >>>>> I'm acting as a Designated Expert for the IANA Link Relation Type >>> registry, defined by RFC5988 . >>>>>=20 >>>>> We've had a request from the = W3C >>> HTML WG to register the 'search' link relation type. >>>>>=20 >>>>> Since OpenSearch has defined the 'search' relation type, and HTML5 >>> refers to your specification to define its semantics, we wanted to = make sure >>> this registration was OK with the OpenSearch community before = proceeding. Do >>> you have any objections to them doing so? >>>>>=20 >>>>> Additionally, we (the Designated Experts) wanted to double-check = with >>> you that the reference they give is a) appropriate, and b) stable. = I.e., >>> it's not going to change gratuitously. >>>>>=20 >>>>> We'd appreciate a response as soon as possible, so that we can = proceed >>> with the registration. >>>>>=20 >>>>> Cheers, >>>>>=20 >>>>> -- >>>>> Mark Nottingham http://www.mnot.net/ >>>>>=20 >>>>>=20 >>>>>=20 >>>>> -- >>>>> You received this message because you are subscribed to the Google >>> Groups "OpenSearch" group. >>>>> To post to this group, send email to opensearch@googlegroups.com. >>>>> To unsubscribe from this group, send email to >>> = opensearch+unsubscribe@googlegroups.com >>> . >>>>> For more options, visit this group at >>> http://groups.google.com/group/opensearch?hl=3Den. >>>>>=20 >>>>>=20 >>>>> _______________________________________________ >>>>> link-relations mailing list >>>>> link-relations@ietf.org >>>>> https://www.ietf.org/mailman/listinfo/link-relations >>>>=20 >>>> -- >>>> Mark Nottingham http://www.mnot.net/ >>>>=20 >>>>=20 >>>>=20 >>>>=20 >>>=20 >=20 > --=20 > Michael(tm) Smith > http://people.w3.org/mike -- Mark Nottingham http://www.mnot.net/ From mike@jay.w3.org Thu Nov 4 00:47:21 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 5DBCC3A68F5 for ; Thu, 4 Nov 2010 00:47:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.599 X-Spam-Level: X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8] 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 KyyhbGrD5J+L for ; Thu, 4 Nov 2010 00:47:20 -0700 (PDT) Received: from jay.w3.org (ssh.w3.org [128.30.52.60]) by core3.amsl.com (Postfix) with ESMTP id F28663A691A for ; Thu, 4 Nov 2010 00:47:19 -0700 (PDT) Received: from localhost ([127.0.0.1] helo=MikeSmith.local) by jay.w3.org with esmtp (Exim 4.69) (envelope-from ) id 1PDuXf-00058U-EJ; Thu, 04 Nov 2010 03:47:27 -0400 Date: Thu, 4 Nov 2010 16:47:24 +0900 From: "Michael(tm) Smith" To: Mark Nottingham Message-ID: <20101104074723.GA5043@sideshowbarker> References: <2BCEFDD3-2A6A-49F8-99B0-EC68F9D09FB6@mnot.net> <20101103164516.GI3616@sideshowbarker> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/r6164+poontang (2010-10-13 07:38:30+09:00) Cc: DeWitt Clinton , link-relations@ietf.org, opensearch@googlegroups.com Subject: Re: [link-relations] [opensearch:393] Registering the 'search' link relation type 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, 04 Nov 2010 07:47:21 -0000 Hi Mark, > Mike, are you requesting the link with the fragid on purpose? No, just inadvertently copied and pasted the URL with the fragid instead of the one without (sorry, was in a kind of a hurry yesterday to get mail sent before the battery ran out on my laptop). > Clinton and I seem to agree that going without makes more sense. Yeah, I agree as well -- sorry for the confusion. --Mike Mark Nottingham , 2010-11-04 11:46 +1100: > Mike, are you requesting the link with the fragid on purpose? Clinton and I seem to agree that going without makes more sense. > > Cheers, > > > On 04/11/2010, at 3:45 AM, Michael(tm) Smith wrote: > > > Updated request (in full): > > > > Relation Name: > > search > > > > Description: > > Gives a link to a resource that can be used to search through > > the current document and its related pages. > > > > Reference: > > http://www.opensearch.org/Specifications/OpenSearch/1.1#Autodiscovery_in_HTML.2FXHTML > > > > DeWitt Clinton , 2010-11-02 22:01 -0700: > > > >> Yes, please. > >> > >> -DeWitt > >> > >> On Tue, Nov 2, 2010 at 10:00 PM, Mark Nottingham wrote: > >> > >>> OK. If that's the case, should the registration just have: > >>> > >>>> Reference: > >>>> http://www.opensearch.org/Specifications/OpenSearch/1.1 > >>> > >>> > >>> ? > >>> > >>> Cheers, > >>> > >>> > >>> On 03/11/2010, at 3:58 PM, DeWitt Clinton wrote: > >>> > >>>> If the designated experts are comfortable with that approach — and it > >>> sounds like you might be, otherwise you wouldn't have asked — I'd personally > >>> prefer that, considering the 'search' relation name is used in multiple > >>> contexts for the same purpose, not exclusively HTML(5). > >>>> > >>>> Thanks for asking, > >>>> > >>>> -DeWitt > >>>> > >>>> On Tue, Nov 2, 2010 at 9:47 PM, Mark Nottingham wrote: > >>>> Thanks, DeWitt. > >>>> > >>>> One thing; I'm wondering if it makes more sense to list the OpenSearch > >>> link directly as the reference, rather than going through the HTML5 one. > >>>> > >>>> E.g., the registration could be: > >>>> > >>>> Relation Name: > >>>> search > >>>> > >>>> Description: > >>>> Gives a link to a resource that can be used to search through > >>>> the current document and its related pages. > >>>> > >>>> Reference: > >>>> > >>> http://www.opensearch.org/Specifications/OpenSearch/1.1#Autodiscovery_in_HTML.2FXHTML > >>>> > >>>> Notes: > >>>> See also: http://www.w3.org/TR/html5/links.html#link-type-search > >>>> > >>>> > >>>> Thoughts? Mike? > >>>> > >>>> > >>>> On 03/11/2010, at 3:21 PM, DeWitt Clinton wrote: > >>>> > >>>>> No objection at all, (speaking as unofficial spec editor). Very glad > >>> to see this happen, and thank you to Michael Smith and the W3C HTML WG for > >>> making the proposal. > >>>>> > >>>>> That URL is stable, and has not changed in several years, and we would > >>> of course be sure to preserve it with a redirect in the event anything ever > >>> moved. > >>>>> > >>>>> That said, the full URL appears truncated in the registration > >>> application. It currently reads: > >>>>> > >>>>> > >>> http://www.opensearch.org/Specifications/OpenSearch/1.1#Autodiscovery_in_HTML.2FXH > >>>>> > >>>>> Should be: > >>>>> > >>>>> > >>> http://www.opensearch.org/Specifications/OpenSearch/1.1#Autodiscovery_in_HTML.2FXHTML > >>>>> > >>>>> Thanks, Mark! > >>>>> > >>>>> -DeWitt > >>>>> > >>>>> On Tue, Nov 2, 2010 at 9:08 PM, Mark Nottingham wrote: > >>>>> Hello OpenSearchers, > >>>>> > >>>>> I'm acting as a Designated Expert for the IANA Link Relation Type > >>> registry, defined by RFC5988 . > >>>>> > >>>>> We've had a request from the W3C > >>> HTML WG to register the 'search' link relation type. > >>>>> > >>>>> Since OpenSearch has defined the 'search' relation type, and HTML5 > >>> refers to your specification to define its semantics, we wanted to make sure > >>> this registration was OK with the OpenSearch community before proceeding. Do > >>> you have any objections to them doing so? > >>>>> > >>>>> Additionally, we (the Designated Experts) wanted to double-check with > >>> you that the reference they give is a) appropriate, and b) stable. I.e., > >>> it's not going to change gratuitously. > >>>>> > >>>>> We'd appreciate a response as soon as possible, so that we can proceed > >>> with the registration. > >>>>> > >>>>> Cheers, > >>>>> -- Michael(tm) Smith http://people.w3.org/mike From mike@jay.w3.org Thu Nov 4 00:48:36 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 EC2A53A691A for ; Thu, 4 Nov 2010 00:48:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.599 X-Spam-Level: X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8] 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 new0yGLRpeBj for ; Thu, 4 Nov 2010 00:48:33 -0700 (PDT) Received: from jay.w3.org (ssh.w3.org [128.30.52.60]) by core3.amsl.com (Postfix) with ESMTP id DC5563A68F5 for ; Thu, 4 Nov 2010 00:48:32 -0700 (PDT) Received: from localhost ([127.0.0.1] helo=MikeSmith.local) by jay.w3.org with esmtp (Exim 4.69) (envelope-from ) id 1PDuYr-0005F4-RJ; Thu, 04 Nov 2010 03:48:42 -0400 Date: Thu, 4 Nov 2010 16:48:38 +0900 From: "Michael(tm) Smith" To: Mark Nottingham Message-ID: <20101104074838.GB5043@sideshowbarker> References: <25AFE76B-66B5-4C91-9C21-12B0072EE212@mnot.net> <20101103170736.GJ3616@sideshowbarker> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/r6164+poontang (2010-10-13 07:38:30+09:00) Cc: link-relations@ietf.org Subject: Re: [link-relations] Link relation registrations from HTML5 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, 04 Nov 2010 07:48:37 -0000 Mark Nottingham , 2010-11-04 09:44 +1100: > Thanks for the reply, Mike. Followups inline. > On 04/11/2010, at 4:07 AM, Michael(tm) Smith wrote: > Right. I'm inclined to do a light edit of the request descriptions to > bring them into a bit more alignment, if it's OK with you. OK by me, in principle. > I.e., right now they use phrases like: > "provides a link" > "gives a link to the current document's..." > "links to an..." > "indicates that the current resource's..." > "specifies that the target resource..." > "specifies a..." > "designates a..." > "refers to a..." > > whereas the registry entries tend to use "refers to a...", "context" and "resource." I see. > I'd suggest we: > - use "refers to..." instead of "provides..." "gives..." and similar I assume that's the way you want to do it for purposes of stylistic consistency in the registry, so I'm objecting. But I can't say that I think it's an actual improvement. For example, I think "Provides a link to context-sensitive help" is fine as-is, and I don't think "Refers to a link to context-sensitive help" is an improvement at all. If anything, if you wanted to choose something for stylistic consistency or, really, even for reasons of precision in wording, I think "represents" would be much better. For example, "Represents a link to context-sensitive help". Anyway, I don't object to "refers to". > - use "indicates..." instead of "designates" Yeah, that is a clear improvement. (FWIW, I did not have "designates" originally -- I requested it that way because "Designates a substitute for the link's context is what HTML4 had, and it was suggested to me that it should be changed back to that.) > - use "current resource" or "link's context" instead of "current document" I'm fine with replacing "document" with "resource." (I might have written it that way to begin with except that I now completely avoid using the word "resource" at all because of the problem that has been created by whatever historical chain of events led to the standards community ever having agreed to begin with to take a really useful real word for which we don't have any suitable synonyms, and permanently turn it into a specialized term of art.) While I understand the motivation for changing to "context", I don't think the result is big improvement for clarity. But I don't have anything better to suggest, so I won't object. > - use "link target" instead of "referenced resource" Yeah, that is definitely better. > To be clear -- this is all completely optional, and I'm not going to hold > up registration by splitting hairs over terminology. > > I'll send a summary of the edits for review separately if you agree. That would be great if you can make time to do it, but I don't think it's absolutely necessary. Thanks, --Mike -- Michael(tm) Smith http://people.w3.org/mike From mnot@mnot.net Thu Nov 4 01:09:15 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 590303A691D for ; Thu, 4 Nov 2010 01:09:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -104.599 X-Spam-Level: X-Spam-Status: No, score=-104.599 tagged_above=-999 required=5 tests=[AWL=-2.000, 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 1dDre6sUyXkc for ; Thu, 4 Nov 2010 01:09:14 -0700 (PDT) Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by core3.amsl.com (Postfix) with ESMTP id 03C023A67F1 for ; Thu, 4 Nov 2010 01:09:13 -0700 (PDT) Received: from chancetrain-lm.mnot.net (unknown [118.209.39.135]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 88DAF509B3; Thu, 4 Nov 2010 04:09:16 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v1081) Content-Type: text/plain; charset=us-ascii From: Mark Nottingham In-Reply-To: <20101104074838.GB5043@sideshowbarker> Date: Thu, 4 Nov 2010 19:09:13 +1100 Content-Transfer-Encoding: quoted-printable Message-Id: <58042BF4-37C7-4B52-AAF4-E94A6DD28B9B@mnot.net> References: <25AFE76B-66B5-4C91-9C21-12B0072EE212@mnot.net> <20101103170736.GJ3616@sideshowbarker> <20101104074838.GB5043@sideshowbarker> To: "Michael(tm) Smith" X-Mailer: Apple Mail (2.1081) Cc: link-relations@ietf.org Subject: Re: [link-relations] Link relation registrations from HTML5 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, 04 Nov 2010 08:09:15 -0000 On 04/11/2010, at 6:48 PM, Michael(tm) Smith wrote: >=20 >> I'd suggest we: >> - use "refers to..." instead of "provides..." "gives..." and similar >=20 > I assume that's the way you want to do it for purposes of stylistic > consistency in the registry, so I'm objecting. Did you mean 'not objecting'? =20 > But I can't say that I think > it's an actual improvement. For example, I think "Provides a link to > context-sensitive help" is fine as-is, and I don't think "Refers to a = link > to context-sensitive help" is an improvement at all. Fair enough. I don't disagree with your observations; I think the best = thing to do is just send an followup email with suggested edits -- = taking your feedback into account -- and see if we can agree on = something. Cheers, -- Mark Nottingham http://www.mnot.net/ From mike@jay.w3.org Thu Nov 4 01:34: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 4CA643A6892 for ; Thu, 4 Nov 2010 01:34:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.599 X-Spam-Level: X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8] 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 RhbLI4Dx8PXX for ; Thu, 4 Nov 2010 01:34:35 -0700 (PDT) Received: from jay.w3.org (ssh.w3.org [128.30.52.60]) by core3.amsl.com (Postfix) with ESMTP id 8A1963A688F for ; Thu, 4 Nov 2010 01:34:35 -0700 (PDT) Received: from localhost ([127.0.0.1] helo=MikeSmith.local) by jay.w3.org with esmtp (Exim 4.69) (envelope-from ) id 1PDvHQ-0000qh-BG; Thu, 04 Nov 2010 04:34:44 -0400 Date: Thu, 4 Nov 2010 17:34:43 +0900 From: "Michael(tm) Smith" To: Mark Nottingham Message-ID: <20101104083443.GD5043@sideshowbarker> References: <25AFE76B-66B5-4C91-9C21-12B0072EE212@mnot.net> <20101103170736.GJ3616@sideshowbarker> <20101104074838.GB5043@sideshowbarker> <58042BF4-37C7-4B52-AAF4-E94A6DD28B9B@mnot.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <58042BF4-37C7-4B52-AAF4-E94A6DD28B9B@mnot.net> User-Agent: Mutt/r6164+poontang (2010-10-13 07:38:30+09:00) Cc: link-relations@ietf.org Subject: Re: [link-relations] Link relation registrations from HTML5 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, 04 Nov 2010 08:34:37 -0000 Mark Nottingham , 2010-11-04 19:09 +1100: > On 04/11/2010, at 6:48 PM, Michael(tm) Smith wrote: > > > >> I'd suggest we: > >> - use "refers to..." instead of "provides..." "gives..." and similar > > > > I assume that's the way you want to do it for purposes of stylistic > > consistency in the registry, so I'm objecting. > > Did you mean 'not objecting'? Yes, I did mean "not objecting" (sorry for the carelessness) > > But I can't say that I think > > it's an actual improvement. For example, I think "Provides a link to > > context-sensitive help" is fine as-is, and I don't think "Refers to a link > > to context-sensitive help" is an improvement at all. > > Fair enough. I don't disagree with your observations; I think the best > thing to do is just send an followup email with suggested edits -- taking > your feedback into account -- and see if we can agree on something. OK --Mike -- Michael(tm) Smith http://people.w3.org/mike From mnot@mnot.net Mon Nov 8 16:57:22 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 92CBF3A67E3 for ; Mon, 8 Nov 2010 16:57:22 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -104.784 X-Spam-Level: X-Spam-Status: No, score=-104.784 tagged_above=-999 required=5 tests=[AWL=-2.185, 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 In2LnLMJeCTl for ; Mon, 8 Nov 2010 16:57:21 -0800 (PST) Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by core3.amsl.com (Postfix) with ESMTP id 16B053A67D6 for ; Mon, 8 Nov 2010 16:57:21 -0800 (PST) Received: from chancetrain-lm.mnot.net (unknown [118.209.39.135]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 6A740509B3; Mon, 8 Nov 2010 19:57:37 -0500 (EST) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Apple Message framework v1081) From: Mark Nottingham Date: Tue, 9 Nov 2010 11:57:33 +1100 Content-Transfer-Encoding: quoted-printable Message-Id: References: To: link-relations@ietf.org X-Mailer: Apple Mail (2.1081) Cc: "Michael\(tm\) Smith" Subject: [link-relations] Fwd: A go at a rough edit 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: Tue, 09 Nov 2010 00:57:22 -0000 I didn't get a response from Mike to these, and he had previously said = that he didn't object to such editing (in general), so in the interest = of getting these into the registry I'm going to go ahead and forward to = IANA.=20 Mike, if you have objections (even small ones), please yell and we'll = get them fixed. Regards, =09 Begin forwarded message: > From: Mark Nottingham > Date: 4 November 2010 11:52:10 PM AEDT > To: "Michael(tm) Smith" > Subject: A go at a rough edit >=20 > Hey Mike, >=20 > Just thought I'd run these by you to get a reaction... e.g., using = "refers to" here but NOT "refers to a link..." which I agree doesn't = work. >=20 > I use 'context' here because in some (e.g., icon) it seems to work = better than "resource or site" which seems a bit arbitrary. However, if = you don't like it (even a bit) I'm happy to go for "resource" as you = indicated. >=20 > Cheers, >=20 >=20 > ------------ >=20 > Relation Name: > archives >=20 > Description: > Refers to a collection of records, documents, or other > materials of historical interest. >=20 > Reference:=20 > http://www.w3.org/TR/html5/links.html#link-type-archives >=20 > Notes: >=20 > -------------- >=20 > Relation Name: > author >=20 > Description: > Refers to the context=92s author. >=20 > Reference:=20 > http://www.w3.org/TR/html5/links.html#link-type-author >=20 > Notes: >=20 > -------------------- >=20 > Relation Name: > icon >=20 > Description: > Refers to an icon representing the link's context. >=20 > Reference: > http://www.w3.org/TR/html5/links.html#link-type-icon >=20 > Notes: >=20 >=20 > -------------------- >=20 > Relation Name: > nofollow >=20 > Description: > Indicates that the context=92s original author or > publisher does not endorse the link target. >=20 > Reference: > http://www.w3.org/TR/html5/links.html#link-type-nofollow >=20 > Notes: >=20 >=20 > ----------------- >=20 > Relation Name: > noreferrer >=20 > Description: > Indicates that no referrer information is to be leaked when following = the link. >=20 > Reference: > http://www.w3.org/TR/html5/links.html#link-type-noreferrer >=20 > Notes: >=20 >=20 > -------------------- >=20 > Relation Name: > prefetch >=20 > Description: > Indicates that the link target should be preemptively cached. >=20 > Reference:=20 > http://www.w3.org/TR/html5/links.html#link-type-prefetch >=20 > Notes: >=20 > ------------------------ >=20 > Relation Name: > help >=20 > Description: > Refers to context-sensitive help. >=20 > Reference: > http://www.w3.org/TR/html5/links.html#link-type-help >=20 > Notes: >=20 > -------------------------- >=20 > Relation Name: > stylesheet >=20 > Description: > Refers to a stylesheet. >=20 > Reference:=20 > http://www.w3.org/TR/html5/links.html#link-type-stylesheet >=20 > Notes: >=20 > --------------------------- >=20 > Relation Name: > alternate >=20 > Description: > Refers to a substitute for this context. >=20 > Reference: > http://www.w3.org/TR/html5/links.html#link-type-alternate >=20 > Notes: >=20 > --------------------------- >=20 > Relation Name: = = =20 > license = = =20 >=20 > Description: = = =20 > Refers to a license associated with this context. >=20 > Reference: = = =20 > [RFC4946] = = =20 >=20 > Notes: = = =20 > For implications of use in HTML, see: > http://www.w3.org/TR/html5/links.html#link-type-license =20 >=20 > ------------------------- -- Mark Nottingham http://www.mnot.net/ From mnot@mnot.net Mon Nov 8 16:58:46 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 59CD53A6817 for ; Mon, 8 Nov 2010 16:58:46 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -104.68 X-Spam-Level: X-Spam-Status: No, score=-104.68 tagged_above=-999 required=5 tests=[AWL=-2.081, 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 t0TyuqdDC-Ls for ; Mon, 8 Nov 2010 16:58:45 -0800 (PST) Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by core3.amsl.com (Postfix) with ESMTP id 1ED9F3A67D6 for ; Mon, 8 Nov 2010 16:58:45 -0800 (PST) Received: from chancetrain-lm.mnot.net (unknown [118.209.39.135]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 209CE509D9; Mon, 8 Nov 2010 19:59:01 -0500 (EST) From: Mark Nottingham Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Date: Tue, 9 Nov 2010 11:58:58 +1100 Message-Id: To: IANA Mime-Version: 1.0 (Apple Message framework v1081) X-Mailer: Apple Mail (2.1081) Cc: "Michael\(tm\) Smith" , link-relations@ietf.org Subject: [link-relations] link relation type registrations 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: Tue, 09 Nov 2010 00:58:46 -0000 IANA folks, Please add/update (as appropriate) the following entries to the Link = Relation Types registry = : ------------ Relation Name: archives Description: Refers to a collection of records, documents, or other materials of historical interest. Reference:=20 http://www.w3.org/TR/html5/links.html#link-type-archives Notes: -------------- Relation Name: author Description: Refers to the context=92s author. Reference:=20 http://www.w3.org/TR/html5/links.html#link-type-author Notes: -------------------- Relation Name: icon Description: Refers to an icon representing the link's context. Reference: http://www.w3.org/TR/html5/links.html#link-type-icon Notes: -------------------- Relation Name: nofollow Description: Indicates that the context=92s original author or publisher does not endorse the link target. Reference: http://www.w3.org/TR/html5/links.html#link-type-nofollow Notes: ----------------- Relation Name: noreferrer Description: Indicates that no referrer information is to be leaked when following = the link. Reference: http://www.w3.org/TR/html5/links.html#link-type-noreferrer Notes: -------------------- Relation Name: prefetch Description: Indicates that the link target should be preemptively cached. Reference:=20 http://www.w3.org/TR/html5/links.html#link-type-prefetch Notes: ------------------------ Relation Name: help Description: Refers to context-sensitive help. Reference: http://www.w3.org/TR/html5/links.html#link-type-help Notes: -------------------------- Relation Name: stylesheet Description: Refers to a stylesheet. Reference:=20 http://www.w3.org/TR/html5/links.html#link-type-stylesheet Notes: --------------------------- Relation Name: alternate Description: Refers to a substitute for this context. Reference: http://www.w3.org/TR/html5/links.html#link-type-alternate Notes: --------------------------- Relation Name: = = =20 license = = =20 Description: = = =20 Refers to a license associated with this context. Reference: = = =20 [RFC4946] = = =20 Notes: = = =20 For implications of use in HTML, see: http://www.w3.org/TR/html5/links.html#link-type-license =20 ------------------------- Regards, -- Mark Nottingham http://www.mnot.net/ From mnot@mnot.net Mon Nov 8 17:01:02 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 2F1713A67D6 for ; Mon, 8 Nov 2010 17:01:02 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -104.585 X-Spam-Level: X-Spam-Status: No, score=-104.585 tagged_above=-999 required=5 tests=[AWL=-1.986, 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 D3uQotcFJqI1 for ; Mon, 8 Nov 2010 17:01:01 -0800 (PST) Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by core3.amsl.com (Postfix) with ESMTP id 381F63A67B7 for ; Mon, 8 Nov 2010 17:01:01 -0800 (PST) Received: from chancetrain-lm.mnot.net (unknown [118.209.39.135]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 1214D509D9; Mon, 8 Nov 2010 20:01:21 -0500 (EST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1081) From: Mark Nottingham Date: Tue, 9 Nov 2010 12:01:18 +1100 Content-Transfer-Encoding: 7bit Message-Id: References: <20101103164516.GI3616@sideshowbarker> To: IANA X-Mailer: Apple Mail (2.1081) Cc: DeWitt Clinton , "Michael\(tm\) Smith" , link-relations@ietf.org Subject: [link-relations] Fwd: [opensearch:393] Registering the 'search' link relation type 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: Tue, 09 Nov 2010 01:01:02 -0000 Iana folks: Please add the following to the link relations registry. ---------------- Relation Name: search Description: Refers to a resource that can be used to search through the link's context and related resources. Reference: http://www.opensearch.org/Specifications/OpenSearch/1.1 Notes: ------------------- -- Mark Nottingham http://www.mnot.net/ From mnot@mnot.net Mon Nov 8 17:05:03 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 F1BF93A690E for ; Mon, 8 Nov 2010 17:05:02 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -104.499 X-Spam-Level: X-Spam-Status: No, score=-104.499 tagged_above=-999 required=5 tests=[AWL=-1.900, 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 SaxddNtjXUcx for ; Mon, 8 Nov 2010 17:05:01 -0800 (PST) Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by core3.amsl.com (Postfix) with ESMTP id E5A333A6817 for ; Mon, 8 Nov 2010 17:05:00 -0800 (PST) Received: from chancetrain-lm.mnot.net (unknown [118.209.39.135]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 9BE3F509DC; Mon, 8 Nov 2010 20:05:22 -0500 (EST) From: Mark Nottingham Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Tue, 9 Nov 2010 12:05:19 +1100 Message-Id: <7D0DB83E-A927-47F4-AEB8-BC145BC28B4E@mnot.net> To: "Michael(tm) Smith" Mime-Version: 1.0 (Apple Message framework v1081) X-Mailer: Apple Mail (2.1081) Cc: link-relations@ietf.org Subject: [link-relations] prev / next / bookmark 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: Tue, 09 Nov 2010 01:05:03 -0000 Mike, Just a heads-up: these are what I intend to submit to IANA, based on = previous discussion. If you'd like a different wording, please says so. Regards, ----------- Relation Name: prev Description: Indicates that the link's context is a part of a series, and that the previous in the series is the link target. Reference: http://www.w3.org/TR/html5/links.html#link-type-prev Notes: ---------------- Relation Name: next Description: Indicates that the link's context is a part of a series, and that the next in the series is the link target. Reference: http://www.w3.org/TR/html5/links.html#link-type-next Notes: --------------- Relation Name: bookmark Description: Gives a permanent link to use for bookmarking purposes. Reference: =20 http://www.w3.org/TR/html5/links.html#link-type-bookmark Notes: --------------- -- Mark Nottingham http://www.mnot.net/ From mike@jay.w3.org Mon Nov 8 18:01:54 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 3F7CD3A68A9 for ; Mon, 8 Nov 2010 18:01:54 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.599 X-Spam-Level: X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8] 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 meN5xGnPeLuR for ; Mon, 8 Nov 2010 18:01:53 -0800 (PST) Received: from jay.w3.org (ssh.w3.org [128.30.52.60]) by core3.amsl.com (Postfix) with ESMTP id 799333A67EC for ; Mon, 8 Nov 2010 18:01:53 -0800 (PST) Received: from localhost ([127.0.0.1] helo=MikeSmith.local) by jay.w3.org with esmtp (Exim 4.69) (envelope-from ) id 1PFdXL-0000tY-2r; Mon, 08 Nov 2010 21:02:15 -0500 Date: Tue, 9 Nov 2010 11:02:13 +0900 From: "Michael(tm) Smith" To: Mark Nottingham Message-ID: <20101109020212.GC12423@sideshowbarker> References: <7D0DB83E-A927-47F4-AEB8-BC145BC28B4E@mnot.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7D0DB83E-A927-47F4-AEB8-BC145BC28B4E@mnot.net> User-Agent: Mutt/r6164+poontang (2010-10-13 07:38:30+09:00) Cc: link-relations@ietf.org Subject: Re: [link-relations] prev / next / bookmark 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: Tue, 09 Nov 2010 02:01:54 -0000 Mark Nottingham , 2010-11-09 12:05 +1100: > ----------- > > Relation Name: > prev > > Description: > Indicates that the link's context is a part of a series, and > that the previous in the series is the link target. Looks fine. > ---------------- > > Relation Name: > next > > Description: > Indicates that the link's context is a part of a series, and > that the next in the series is the link target. Looks fine. > --------------- > > Relation Name: > bookmark > > Description: > Gives a permanent link to use for bookmarking purposes. Looks fine. I have a general comment about the use of "context" that I'll send in another message. --Mike -- Michael(tm) Smith http://people.w3.org/mike From mike@jay.w3.org Mon Nov 8 18:05: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 8CE4D28C129 for ; Mon, 8 Nov 2010 18:05:08 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.599 X-Spam-Level: X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8] 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 jhFlyUBTriM4 for ; Mon, 8 Nov 2010 18:05:07 -0800 (PST) Received: from jay.w3.org (ssh.w3.org [128.30.52.60]) by core3.amsl.com (Postfix) with ESMTP id 675D728C119 for ; Mon, 8 Nov 2010 18:05:07 -0800 (PST) Received: from localhost ([127.0.0.1] helo=MikeSmith.local) by jay.w3.org with esmtp (Exim 4.69) (envelope-from ) id 1PFdaT-00010X-Uc; Mon, 08 Nov 2010 21:05:30 -0500 Date: Tue, 9 Nov 2010 11:05:28 +0900 From: "Michael(tm) Smith" To: Mark Nottingham Message-ID: <20101109020527.GD12423@sideshowbarker> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/r6164+poontang (2010-10-13 07:38:30+09:00) Cc: link-relations@ietf.org Subject: Re: [link-relations] Fwd: A go at a rough edit 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: Tue, 09 Nov 2010 02:05:08 -0000 Mark Nottingham , 2010-11-09 11:57 +1100: > I didn't get a response from Mike to these, and he had previously said > that he didn't object to such editing (in general), so in the interest of > getting these into the registry I'm going to go ahead and forward to > IANA. > > Mike, if you have objections (even small ones), please yell and we'll get them fixed. No objections. And I see that you've got it on out to IANA, so thanks. --Mike -- Michael(tm) Smith http://people.w3.org/mike From mike@jay.w3.org Mon Nov 8 18:43:40 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 A64E83A6941 for ; Mon, 8 Nov 2010 18:43:39 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.599 X-Spam-Level: X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8] 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 Ks2XhrfC3sdb for ; Mon, 8 Nov 2010 18:43:31 -0800 (PST) Received: from jay.w3.org (ssh.w3.org [128.30.52.60]) by core3.amsl.com (Postfix) with ESMTP id AE2B228C1D2 for ; Mon, 8 Nov 2010 18:43:05 -0800 (PST) Received: from localhost ([127.0.0.1] helo=MikeSmith.local) by jay.w3.org with esmtp (Exim 4.69) (envelope-from ) id 1PFeAx-0002LL-0O; Mon, 08 Nov 2010 21:43:11 -0500 Date: Tue, 9 Nov 2010 11:43:09 +0900 From: "Michael(tm) Smith" To: Mark Nottingham Message-ID: <20101109024308.GE12423@sideshowbarker> References: <7D0DB83E-A927-47F4-AEB8-BC145BC28B4E@mnot.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7D0DB83E-A927-47F4-AEB8-BC145BC28B4E@mnot.net> User-Agent: Mutt/r6164+poontang (2010-10-13 07:38:30+09:00) Cc: link-relations@ietf.org Subject: Re: [link-relations] prev / next / bookmark 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: Tue, 09 Nov 2010 02:43:40 -0000 Hi Mark, > @2010-11-09 12:05 +1100: > Just a heads-up: these are what I intend to submit to IANA, based on > previous discussion. If you'd like a different wording, please says so. I have a question: How is a user of the registry expected to know what is meant by the by the term "the link's context"? Would you consider defining that term somewhere within the registry itself? http://www.iana.org/assignments/link-relations/link-relations.xhtml For example, a Notes or Terminology subheading after the Reference subheading might be an appropriate place. If that term were unambiguously defined somewhere in RFC 5988, it might be adequate (but still suboptimal IMHO) to just expect that users of the registry had read the RFC. However, I can't see that it is unambiguously defined in the RFC. What I can find is that there's a section titled "Context IRI" that starts with this paragraph: http://tools.ietf.org/html/rfc5988#section-5.2 By default, the context of a link conveyed in the Link header field is the IRI of the requested resource. So that defines "the context of a link conveyed in the Link header field". But what about links that are not conveyed in the Link header field? For that case, the closest I can find to a definition is in Appendix A, "Notes on Using the Link Header with the HTML4 Format" http://tools.ietf.org/html/rfc5988#appendix-A In HTML4, the link element can be mapped to links as specified here by using the "href" attribute for the target URI, and "rel" to convey the relation type, as in the Link header. The context of the link is the URI associated with the entire HTML document. So that's clear enough as far as the case of HTML4 documents go. And I think readers are capable of inferring that applies to XHTML1 and HTML5 and XHTML5 documents as well. But what about for non-HTML documents? I'm really not trying to split hairs here -- I just don't think the meaning of the term "the link's context" is going to be obvious to users of the registry, and I don't think it's unreasonable for users of the registry to expect to have the term explicitly defined. And I think the optimal place to define it is somewhere in the "front matter" (for lack of a better term) of the registry itself. --Mike -- Michael(tm) Smith http://people.w3.org/mike From anthonybryan@gmail.com Thu Nov 11 16:27:27 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 D4B7B3A67FD for ; Thu, 11 Nov 2010 16:27:27 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.67 X-Spam-Level: X-Spam-Status: No, score=-1.67 tagged_above=-999 required=5 tests=[AWL=-0.930, BAYES_20=-0.74] 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 AZyOEL6XuASh for ; Thu, 11 Nov 2010 16:27:26 -0800 (PST) Received: from mail-ew0-f44.google.com (mail-ew0-f44.google.com [209.85.215.44]) by core3.amsl.com (Postfix) with ESMTP id 844DC3A6804 for ; Thu, 11 Nov 2010 16:27:26 -0800 (PST) Received: by ewy27 with SMTP id 27so1667381ewy.31 for ; Thu, 11 Nov 2010 16:27:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type:content-transfer-encoding; bh=3u6UOFZZ6kD/xfDy6qF7rp7y/PqQ8if9DQ2vl+ssc1g=; b=nBVg8EM0GVGYT9zvyXS7ciQsWav19Zsg0/TzotDJr8OR7H17C3EPrYHEFqMh7R0lor 91h/NsVpta3BROdw+YSWVzL8p5ApE2S68FxkqL34Dir0iYJdo+DMIH7woxNmLLIgf1Yz z5osWqN7EgYLRZPiAiwR1HnxZHkeea8DGP20A= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=JtLgK+B63jGEk5fVcdlHNEO0WKFaNB10aI+Mb+OG36r/r5S2Qn6aDnJXxPPzemZoyd 0fJX3KQs4E9fUWOBcxqMSDUX03KDBhn/ifN+QNLXMrJ0BXzfayhNzhlDRzoLGyEgFFH5 C2aFwD+SvAecL0Ekh3detZB8/8isdgj0Z0FUg= MIME-Version: 1.0 Received: by 10.213.105.79 with SMTP id s15mr1486544ebo.76.1289521675608; Thu, 11 Nov 2010 16:27:55 -0800 (PST) Received: by 10.213.28.2 with HTTP; Thu, 11 Nov 2010 16:27:55 -0800 (PST) Date: Thu, 11 Nov 2010 19:27:55 -0500 Message-ID: From: Anthony Bryan To: link-relations@ietf.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Mailman-Approved-At: Thu, 11 Nov 2010 19:06:45 -0800 Subject: [link-relations] NEW RELATION REQUEST: Relation name: "duplicate" 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: Fri, 12 Nov 2010 00:27:27 -0000 Relation Name: duplicate Description: Refers to a resource whose available representations are byte-for-byte identical with the corresponding representations of the context IRI. Reference: http://tools.ietf.org/html/draft-bryan-metalinkhttp Notes: This relation is for static resources. That is, an HTTP GET request on any duplicate will return the same representation. It does not make sense for dynamic or POSTable resources and should not be used for them. --=20 (( Anthony Bryan ... Metalink [ http://www.metalinker.org ] =A0 )) Easier, More Reliable, Self Healing Downloads From mnot@mnot.net Thu Nov 11 20:56:24 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 F2BB43A6916 for ; Thu, 11 Nov 2010 20:56:23 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -105.203 X-Spam-Level: X-Spam-Status: No, score=-105.203 tagged_above=-999 required=5 tests=[AWL=-2.604, 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 eQ1DOX6v-Wak for ; Thu, 11 Nov 2010 20:56:15 -0800 (PST) Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by core3.amsl.com (Postfix) with ESMTP id A88FE3A691F for ; Thu, 11 Nov 2010 20:56:15 -0800 (PST) Received: from chancetrain-lm.mnot.net (unknown [118.209.2.20]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 8ED2A22E253; Thu, 11 Nov 2010 23:56:40 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v1081) Content-Type: text/plain; charset=us-ascii From: Mark Nottingham In-Reply-To: <20101109024308.GE12423@sideshowbarker> Date: Fri, 12 Nov 2010 15:56:37 +1100 Content-Transfer-Encoding: quoted-printable Message-Id: <71A01D88-D98D-483B-8FC1-CF929E82012F@mnot.net> References: <7D0DB83E-A927-47F4-AEB8-BC145BC28B4E@mnot.net> <20101109024308.GE12423@sideshowbarker> To: Michael(tm) Smith X-Mailer: Apple Mail (2.1081) Cc: link-relations@ietf.org Subject: Re: [link-relations] prev / next / bookmark 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: Fri, 12 Nov 2010 04:56:24 -0000 It's a good question. We're using "context" here as a shorthand for context IRI.=20 The long answer is that the context is defined by the application of the = link; i.e., if your define "stylesheet" to import a stylesheet into an = HTML page, you need to say where to look for links (e.g., the link = header, in the HTML) as well as what it applies to (in this case, the = whole HTML document). Contrast that to how XSLT would use stylesheet; it might not decide to = look into HTTP headers, and apply it to a different context (just for = the purpose of the example). As such, using 'context' is more about not misleading people into making = assumptions about the link's scope than it is about providing a firm = definition. However, as I said before, I'm not fixated on this = terminology. getting terminology up onto the registry page is an interesting idea; = I'll look into it. Cheers, On 09/11/2010, at 1:43 PM, Michael(tm) Smith wrote: > Hi Mark, >=20 >> @2010-11-09 12:05 +1100: >> Just a heads-up: these are what I intend to submit to IANA, based on >> previous discussion. If you'd like a different wording, please says = so. >=20 > I have a question: How is a user of the registry expected to know what = is > meant by the by the term "the link's context"? >=20 > Would you consider defining that term somewhere within the registry = itself? >=20 > http://www.iana.org/assignments/link-relations/link-relations.xhtml >=20 > For example, a Notes or Terminology subheading after the Reference > subheading might be an appropriate place. >=20 > If that term were unambiguously defined somewhere in RFC 5988, it = might be > adequate (but still suboptimal IMHO) to just expect that users of the > registry had read the RFC. >=20 > However, I can't see that it is unambiguously defined in the RFC. >=20 > What I can find is that there's a section titled "Context IRI" that = starts > with this paragraph: >=20 > http://tools.ietf.org/html/rfc5988#section-5.2 > By default, the context of a link conveyed in the Link header field = is > the IRI of the requested resource. >=20 > So that defines "the context of a link conveyed in the Link header = field". > But what about links that are not conveyed in the Link header field? >=20 > For that case, the closest I can find to a definition is in Appendix = A, > "Notes on Using the Link Header with the HTML4 Format" >=20 > http://tools.ietf.org/html/rfc5988#appendix-A > In HTML4, the link element can be mapped to links as specified here = by > using the "href" attribute for the target URI, and "rel" to convey = the > relation type, as in the Link header. The context of the link is the = URI > associated with the entire HTML document. >=20 > So that's clear enough as far as the case of HTML4 documents go. And I > think readers are capable of inferring that applies to XHTML1 and = HTML5 and > XHTML5 documents as well. But what about for non-HTML documents? >=20 > I'm really not trying to split hairs here -- I just don't think the = meaning > of the term "the link's context" is going to be obvious to users of = the > registry, and I don't think it's unreasonable for users of the = registry to > expect to have the term explicitly defined. And I think the optimal = place > to define it is somewhere in the "front matter" (for lack of a better = term) > of the registry itself. >=20 > --Mike >=20 > --=20 > Michael(tm) Smith > http://people.w3.org/mike -- Mark Nottingham http://www.mnot.net/ From mnot@mnot.net Thu Nov 11 20:59:52 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 ED3C33A693E for ; Thu, 11 Nov 2010 20:59:52 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -105.136 X-Spam-Level: X-Spam-Status: No, score=-105.136 tagged_above=-999 required=5 tests=[AWL=-2.537, 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 Abo+3GMvW8NZ for ; Thu, 11 Nov 2010 20:59:45 -0800 (PST) Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by core3.amsl.com (Postfix) with ESMTP id D4C593A688E for ; Thu, 11 Nov 2010 20:59:44 -0800 (PST) Received: from chancetrain-lm.mnot.net (unknown [118.209.2.20]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id A274B22E253; Fri, 12 Nov 2010 00:00:12 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v1081) Content-Type: text/plain; charset=us-ascii From: Mark Nottingham In-Reply-To: Date: Fri, 12 Nov 2010 16:00:09 +1100 Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Anthony Bryan X-Mailer: Apple Mail (2.1081) Cc: link-relations@ietf.org Subject: Re: [link-relations] NEW RELATION REQUEST: Relation name: "duplicate" 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: Fri, 12 Nov 2010 04:59:53 -0000 Seems reasonable to me.=20 I see you have Standards Track as the intended status -- have to talked = to an AD about its future? Regards, On 12/11/2010, at 11:27 AM, Anthony Bryan wrote: > Relation Name: > duplicate >=20 > Description: > Refers to a resource whose available representations > are byte-for-byte identical with the corresponding representations = of > the context IRI. >=20 > Reference: > http://tools.ietf.org/html/draft-bryan-metalinkhttp >=20 > Notes: > This relation is for static resources. That is, an HTTP GET > request on any duplicate will return the same representation. It > does not make sense for dynamic or POSTable resources and should not > be used for them. >=20 > --=20 > (( Anthony Bryan ... Metalink [ http://www.metalinker.org ] > )) Easier, More Reliable, Self Healing Downloads > _______________________________________________ > link-relations mailing list > link-relations@ietf.org > https://www.ietf.org/mailman/listinfo/link-relations -- Mark Nottingham http://www.mnot.net/ From bortzmeyer@nic.fr Sat Nov 13 04:51: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 EB8673A69EF for ; Sat, 13 Nov 2010 04:51:00 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.377 X-Spam-Level: X-Spam-Status: No, score=-102.377 tagged_above=-999 required=5 tests=[AWL=0.178, BAYES_00=-2.599, DATE_IN_PAST_03_06=0.044, 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 tS5zZvGnwc7i for ; Sat, 13 Nov 2010 04:51:00 -0800 (PST) Received: from mail.bortzmeyer.org (aetius.bortzmeyer.org [217.70.190.232]) by core3.amsl.com (Postfix) with ESMTP id 2F4043A6999 for ; Sat, 13 Nov 2010 04:51:00 -0800 (PST) Received: by mail.bortzmeyer.org (Postfix, from userid 10) id 2288395EFB; Sat, 13 Nov 2010 13:51:33 +0100 (CET) Received: by horcrux (Postfix, from userid 1000) id 728CB157992; Sat, 13 Nov 2010 16:40:26 +0800 (CST) Date: Sat, 13 Nov 2010 16:40:26 +0800 From: Stephane Bortzmeyer To: Anthony Bryan Message-ID: <20101113084026.GB23318@laperouse.bortzmeyer.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Transport: UUCP rules X-Operating-System: Ubuntu 10.04 (lucid) User-Agent: Mutt/1.5.20 (2009-06-14) Cc: link-relations@ietf.org Subject: Re: [link-relations] NEW RELATION REQUEST: Relation name: "duplicate" 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: Sat, 13 Nov 2010 12:51:01 -0000 On Thu, Nov 11, 2010 at 07:27:55PM -0500, Anthony Bryan wrote a message of 25 lines which said: > Refers to a resource whose available representations are > byte-for-byte Was there any discussion (pointer, please) on this choice of defining it as a byte-for-byte equivalence? Because it will be quite strict, meaning that two very same XML documents, with the same infoset but different representations (for instance, UTF-8 + NFC and UTF-8 without NFC), will not be regarded as "duplicate". From mnot@mnot.net Sat Nov 13 20:27:01 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 D51D63A6B62 for ; Sat, 13 Nov 2010 20:27:01 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -105.03 X-Spam-Level: X-Spam-Status: No, score=-105.03 tagged_above=-999 required=5 tests=[AWL=-2.431, 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 hTpQX0r7etVz for ; Sat, 13 Nov 2010 20:26:54 -0800 (PST) Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by core3.amsl.com (Postfix) with ESMTP id C83EF3A6A9B for ; Sat, 13 Nov 2010 20:26:54 -0800 (PST) Received: from chancetrain-lm.mnot.net (unknown [118.209.2.20]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 57F8122E1F4; Sat, 13 Nov 2010 23:27:21 -0500 (EST) From: Mark Nottingham Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Sun, 14 Nov 2010 15:27:18 +1100 Message-Id: To: IANA Mime-Version: 1.0 (Apple Message framework v1081) X-Mailer: Apple Mail (2.1081) Cc: "Michael\(tm\) Smith" , link-relations@ietf.org Subject: [link-relations] link relation type registrations 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: Sun, 14 Nov 2010 04:27:01 -0000 IANA folks, Please add/update (as appropriate) the following entries to the Link = Relation Types registry = : ----------- Relation Name: prev Description: Indicates that the link's context is a part of a series, and that the previous in the series is the link target. Reference: http://www.w3.org/TR/html5/links.html#link-type-prev Notes: ---------------- Relation Name: next Description: Indicates that the link's context is a part of a series, and that the next in the series is the link target. Reference: http://www.w3.org/TR/html5/links.html#link-type-next Notes: --------------- Relation Name: bookmark Description: Gives a permanent link to use for bookmarking purposes. Reference: =20 http://www.w3.org/TR/html5/links.html#link-type-bookmark Notes: --------------- Regards, -- Mark Nottingham http://www.mnot.net/ From ed.summers@gmail.com Sun Nov 14 18:33: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 779E23A6B4F for ; Sun, 14 Nov 2010 18:33:00 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.374 X-Spam-Level: X-Spam-Status: No, score=-1.374 tagged_above=-999 required=5 tests=[AWL=0.603, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622] 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 XvjlQX3uJKlD for ; Sun, 14 Nov 2010 18:32:59 -0800 (PST) Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id 9217F3A693A for ; Sun, 14 Nov 2010 18:32:59 -0800 (PST) Received: by iwn40 with SMTP id 40so6531185iwn.31 for ; Sun, 14 Nov 2010 18:33:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=IhMv6wbYv2mb5zH9dl0pQXJ+3HQowEy69ubtZZHk3R4=; b=i4AbFQ/ZDuUAlVF5pvmYxbH9JkwsA8yqgQCxyaYo2/B/S5jyHjL/gZYxh7WCGVPXNG Mo4naT2Gu4km6JSwz8g0xmro3hhEYE2Dzr1pxARalZlqKTU2L7LV3qcVUTFy7aIKH0OJ gZ97gk0ZYuaAz6Ma3hZ0me6piUMkjoIRNqeeo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; b=sJKulE/n3g/exZcwndTkL5ppnFZwqOyZG1KbOrXWZ+Jv5+TggdlSaurP19nAECP8SZ 27tNDuZO7Z+H7oQU5I2zwTtdWSSHU6Wnw/BX6ZSJiwKkWQ4gqRnNRRauxhEOc+U5AZOS 7fEExVZAY2ENktrcAuyq2wNGKs0iDQM0FC7vY= MIME-Version: 1.0 Received: by 10.231.34.8 with SMTP id j8mr3760387ibd.121.1289788419477; Sun, 14 Nov 2010 18:33:39 -0800 (PST) Sender: ed.summers@gmail.com Received: by 10.231.152.211 with HTTP; Sun, 14 Nov 2010 18:33:39 -0800 (PST) Date: Sun, 14 Nov 2010 21:33:39 -0500 X-Google-Sender-Auth: Nb4CFy-6DScFmOVsno-yWTcnukk Message-ID: From: Ed Summers To: link-relations@ietf.org Content-Type: text/plain; charset=ISO-8859-1 Subject: [link-relations] NEW RELATION REQUEST: canonical 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: Mon, 15 Nov 2010 02:34:16 -0000 Relation Name: canonical Description: A canonical page is the preferred version of a set of pages with highly similar content. Reference: http://www.google.com/support/webmasters/bin/answer.py?hl=en&answer=139394 Notes: This relation is used by web crawlers to prefer a particular URI when multiple URIs are available for similar content. For example, when a URL contains a tracking number or sort parameters. From julian.reschke@gmx.de Mon Nov 15 01:30:30 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 6B51C3A6C59 for ; Mon, 15 Nov 2010 01:30:30 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -105.08 X-Spam-Level: X-Spam-Status: No, score=-105.08 tagged_above=-999 required=5 tests=[AWL=-3.081, BAYES_00=-2.599, J_CHICKENPOX_39=0.6, 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 35-S8-QP1w8v for ; Mon, 15 Nov 2010 01:30:29 -0800 (PST) Received: from mail.gmx.net (mailout-de.gmx.net [213.165.64.23]) by core3.amsl.com (Postfix) with SMTP id 385D73A69B9 for ; Mon, 15 Nov 2010 01:30:28 -0800 (PST) Received: (qmail invoked by alias); 15 Nov 2010 09:31:08 -0000 Received: from p508FC5A2.dip.t-dialin.net (EHLO [192.168.178.33]) [80.143.197.162] by mail.gmx.net (mp009) with SMTP; 15 Nov 2010 10:31:08 +0100 X-Authenticated: #1915285 X-Provags-ID: V01U2FsdGVkX1/xSNhUazTxMO5F8LeuNhqw7fav/1c8i6VpI1+Lms PJvJZbqED+eJ5Z Message-ID: <4CE0FDD9.6090804@gmx.de> Date: Mon, 15 Nov 2010 10:31:05 +0100 From: Julian Reschke User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.12) Gecko/20101027 Lightning/1.0b2 Thunderbird/3.1.6 MIME-Version: 1.0 To: Ed Summers References: 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 RELATION REQUEST: canonical 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: Mon, 15 Nov 2010 09:30:30 -0000 On 15.11.2010 03:33, Ed Summers wrote: > Relation Name: > canonical > > Description: > A canonical page is the preferred version of a set of pages with > highly similar content. > > Reference: > http://www.google.com/support/webmasters/bin/answer.py?hl=en&answer=139394 > > Notes: > This relation is used by web crawlers to prefer a particular URI when > multiple URIs are available for similar content. For example, when a > URL contains a tracking number or sort parameters. Hi Ed, registering "canonical" would be a good thing, yes. Questions: 1) are you doing this on behalf of Google, or as an individual? 2) Do we have confidence that the URI is stable (well, it uses rel=canonical to declare itself as canonical, but who knows :-)? Best regards, Julian From julian.reschke@gmx.de Mon Nov 15 03:03:17 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 C22BE3A6C68 for ; Mon, 15 Nov 2010 03:03:17 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -105.08 X-Spam-Level: X-Spam-Status: No, score=-105.08 tagged_above=-999 required=5 tests=[AWL=-3.081, BAYES_00=-2.599, J_CHICKENPOX_39=0.6, 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 RNx-u5G+nAhx for ; Mon, 15 Nov 2010 03:03:17 -0800 (PST) Received: from mail.gmx.net (mailout-de.gmx.net [213.165.64.22]) by core3.amsl.com (Postfix) with SMTP id 96D413A6C6D for ; Mon, 15 Nov 2010 03:03:16 -0800 (PST) Received: (qmail invoked by alias); 15 Nov 2010 11:03:56 -0000 Received: from mail.greenbytes.de (EHLO [192.168.1.133]) [217.91.35.233] by mail.gmx.net (mp062) with SMTP; 15 Nov 2010 12:03:56 +0100 X-Authenticated: #1915285 X-Provags-ID: V01U2FsdGVkX1+5w3pnK5W536DlAOlOuAu054hjRHfZSyEnID8VqG 1s2a95I5/P/mOG Message-ID: <4CE11398.5000508@gmx.de> Date: Mon, 15 Nov 2010 12:03:52 +0100 From: Julian Reschke User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.12) Gecko/20101027 Lightning/1.0b2 Thunderbird/3.1.6 MIME-Version: 1.0 To: Ed Summers References: <4CE0FDD9.6090804@gmx.de> In-Reply-To: <4CE0FDD9.6090804@gmx.de> 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 RELATION REQUEST: canonical 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: Mon, 15 Nov 2010 11:03:17 -0000 On 15.11.2010 10:31, Julian Reschke wrote: > On 15.11.2010 03:33, Ed Summers wrote: >> Relation Name: >> canonical >> >> Description: >> A canonical page is the preferred version of a set of pages with >> highly similar content. >> >> Reference: >> http://www.google.com/support/webmasters/bin/answer.py?hl=en&answer=139394 >> >> >> Notes: >> This relation is used by web crawlers to prefer a particular URI when >> multiple URIs are available for similar content. For example, when a >> URL contains a tracking number or sort parameters. > > Hi Ed, > > registering "canonical" would be a good thing, yes. > > Questions: > > 1) are you doing this on behalf of Google, or as an individual? > > 2) Do we have confidence that the URI is stable (well, it uses > rel=canonical to declare itself as canonical, but who knows :-)? Also, maybe is a better reference? Best regards, Julian From ed.summers@gmail.com Mon Nov 15 03:18: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 BF30C3A6BF2 for ; Mon, 15 Nov 2010 03:18:00 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.659 X-Spam-Level: X-Spam-Status: No, score=-1.659 tagged_above=-999 required=5 tests=[AWL=0.318, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622] 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 OXEzi+bU136q for ; Mon, 15 Nov 2010 03:18:00 -0800 (PST) Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id 084403A6AFE for ; Mon, 15 Nov 2010 03:17:59 -0800 (PST) Received: by iwn40 with SMTP id 40so6991480iwn.31 for ; Mon, 15 Nov 2010 03:18:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type; bh=THTfQbtvePuiZqufjKYPrmXK1RxsRVdPNI/wkJa1EOc=; b=HSTFC/7BWUE3sPPKaO39A80wZUC0nGwV3s4loqLwJo+y6P6gowXm5OOHtb1z5ynBih 4POpYnpj6GWOTWOvCsBA9KC6we4c/cTs4qc4ABDbVZEi8yotWH5M6QkxGLroFnhKKCUx yly6zlO9XHnoqNYPsPaK7Rb5CDTCYn1aIGvuc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=e6ZXPFf5VcI8vJThL19bMr8N4k09HTmm7+ypvQizRQIspW5D5Hf8J6gPs6m9Fvml8L dJ76HJJSkzQTGUq/5lkYaPDyuxsFJY8LAkkdtDwD+sKEdbu4H1S3IjPrEEE4YKS4zW/B O5jykto3zj3kY2ZK9Ptln/9D4jXNsnxhaAkfg= MIME-Version: 1.0 Received: by 10.231.12.139 with SMTP id x11mr3975104ibx.196.1289819920898; Mon, 15 Nov 2010 03:18:40 -0800 (PST) Sender: ed.summers@gmail.com Received: by 10.231.152.211 with HTTP; Mon, 15 Nov 2010 03:18:40 -0800 (PST) In-Reply-To: <4CE11398.5000508@gmx.de> References: <4CE0FDD9.6090804@gmx.de> <4CE11398.5000508@gmx.de> Date: Mon, 15 Nov 2010 06:18:40 -0500 X-Google-Sender-Auth: CaMp8Daw6LClGdoE1YwXvyUeGZs Message-ID: From: Ed Summers To: Julian Reschke Content-Type: text/plain; charset=ISO-8859-1 Cc: link-relations@ietf.org Subject: Re: [link-relations] NEW RELATION REQUEST: canonical 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: Mon, 15 Nov 2010 11:18:00 -0000 On Mon, Nov 15, 2010 at 6:03 AM, Julian Reschke wrote: > > > is a better reference? Thanks Julian, I like that reference better. I'm definitely not doing this on behalf of Google, I just thought I would suggest it for the registry since it is being used. The discussion about 'duplicate' reminded me of it :-) //Ed From mnot@mnot.net Mon Nov 15 19:21:57 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 215DC3A6C5F for ; Mon, 15 Nov 2010 19:21:57 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -104.976 X-Spam-Level: X-Spam-Status: No, score=-104.976 tagged_above=-999 required=5 tests=[AWL=-2.377, 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 J1Y0EahKbVAM for ; Mon, 15 Nov 2010 19:21:56 -0800 (PST) Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by core3.amsl.com (Postfix) with ESMTP id EEAF73A6B4C for ; Mon, 15 Nov 2010 19:21:55 -0800 (PST) Received: from chancetrain-lm.mnot.net (unknown [118.209.2.20]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 7C61B22E253; Mon, 15 Nov 2010 22:22:31 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v1082) Content-Type: text/plain; charset=us-ascii From: Mark Nottingham In-Reply-To: Date: Tue, 16 Nov 2010 14:22:28 +1100 Content-Transfer-Encoding: quoted-printable Message-Id: References: <4CE0FDD9.6090804@gmx.de> <4CE11398.5000508@gmx.de> To: Ed Summers X-Mailer: Apple Mail (2.1082) Cc: link-relations@ietf.org Subject: Re: [link-relations] NEW RELATION REQUEST: canonical 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: Tue, 16 Nov 2010 03:21:57 -0000 FWIW -- I discussed registering 'canonical' with someone from Google a = while back. Let me see if I can get their take... Cheers, On 15/11/2010, at 10:18 PM, Ed Summers wrote: > On Mon, Nov 15, 2010 at 6:03 AM, Julian Reschke = wrote: >> = >>=20 >> is a better reference? >=20 > Thanks Julian, I like that reference better. I'm definitely not doing > this on behalf of Google, I just thought I would suggest it for the > registry since it is being used. The discussion about 'duplicate' > reminded me of it :-) >=20 > //Ed > _______________________________________________ > link-relations mailing list > link-relations@ietf.org > https://www.ietf.org/mailman/listinfo/link-relations -- Mark Nottingham http://www.mnot.net/ From anthonybryan@gmail.com Tue Nov 16 00:09:45 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 7ECD73A6D81 for ; Tue, 16 Nov 2010 00:09:45 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.289 X-Spam-Level: X-Spam-Status: No, score=-2.289 tagged_above=-999 required=5 tests=[AWL=0.310, 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 Qw3yBLZkvsC7 for ; Tue, 16 Nov 2010 00:09:44 -0800 (PST) Received: from mail-ew0-f44.google.com (mail-ew0-f44.google.com [209.85.215.44]) by core3.amsl.com (Postfix) with ESMTP id 2122C3A6BDE for ; Tue, 16 Nov 2010 00:09:43 -0800 (PST) Received: by ewy27 with SMTP id 27so136851ewy.31 for ; Tue, 16 Nov 2010 00:10:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=G7ZEnHhtFqgwCHp4EknP2Ze6SK+cG6pdVSjg7QftopA=; b=gfRlprLflssoRoXC0RXkuJ4vB50pJOYw3JIv6PjtN1J+LqfdP2Qldh8PwohfVVSZS7 pDru64Ebr9bT61l0Hzx+3gMa7ozHkxjo2EQ7JJW7hfFYmCBMqjYAamc/I6w+a6Vaqa0a 5b2Q43D62CcqzwP/UhyUmMxfMtWqYxPdb+MMg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=CuJyUEBEQfvOa0fzMH88J/WkEawrSztFmS16rxYkk7LiOdis0PFRqoh3Gap551sjnN wynuUOK1DbRpaH1qcu8UX5Sd3PVjPQpwsVrQYUVGTs7Akapr4OcF3G4QTOJcGqAvt6Bj SATYydn0+BwlREKzpFeQdj/iivjePnDPSrglo= MIME-Version: 1.0 Received: by 10.213.4.135 with SMTP id 7mr3204145ebr.89.1289895026573; Tue, 16 Nov 2010 00:10:26 -0800 (PST) Received: by 10.213.28.2 with HTTP; Tue, 16 Nov 2010 00:10:26 -0800 (PST) In-Reply-To: <20101113084026.GB23318@laperouse.bortzmeyer.org> References: <20101113084026.GB23318@laperouse.bortzmeyer.org> Date: Tue, 16 Nov 2010 03:10:26 -0500 Message-ID: From: Anthony Bryan To: Stephane Bortzmeyer Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Mailman-Approved-At: Tue, 16 Nov 2010 00:27:52 -0800 Cc: link-relations@ietf.org Subject: Re: [link-relations] NEW RELATION REQUEST: Relation name: "duplicate" 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: Tue, 16 Nov 2010 08:09:45 -0000 On Sat, Nov 13, 2010 at 3:40 AM, Stephane Bortzmeyer wr= ote: > On Thu, Nov 11, 2010 at 07:27:55PM -0500, > =A0Anthony Bryan wrote > =A0a message of 25 lines which said: > >> =A0 =A0Refers to a resource whose available representations are >> =A0 =A0byte-for-byte > > Was there any discussion (pointer, please) on this choice of defining > it as a byte-for-byte equivalence? Because it will be quite strict, > meaning that two very same XML documents, with the same infoset but > different representations (for instance, UTF-8 + NFC and UTF-8 without > NFC), will not be regarded as "duplicate". for what we're doing, it needs to be byte-for-byte identical. metalink clients usually deal with large file downloads, and under certain conditions, might request byte ranges from different servers and patch em together. http://lists.w3.org/Archives/Public/ietf-http-wg/2009JulSep/0746.html --=20 (( Anthony Bryan ... Metalink [ http://www.metalinker.org ] =A0 )) Easier, More Reliable, Self Healing Downloads From anthonybryan@gmail.com Tue Nov 16 00:11:36 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 173B33A6DB9 for ; Tue, 16 Nov 2010 00:11:36 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.367 X-Spam-Level: X-Spam-Status: No, score=-2.367 tagged_above=-999 required=5 tests=[AWL=0.232, 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 2LT-Nq5wxZNI for ; Tue, 16 Nov 2010 00:11:34 -0800 (PST) Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by core3.amsl.com (Postfix) with ESMTP id 423FA3A6DB3 for ; Tue, 16 Nov 2010 00:11:34 -0800 (PST) Received: by eyd10 with SMTP id 10so135612eyd.31 for ; Tue, 16 Nov 2010 00:12:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=pEkqWmQQRw466QbG/LEXplEXd8vE1fNigHthlaX1esk=; b=EORS9y6LdtVKu3a1x66qf6Rvr7ON448DIbtgVbAc8rJVaH+4iU1ZaqtR3a9jDNdOcT yf+oQSUZz+ISEEQma1t6bmn2D6vH/CnrZPsO3xsjH7IlfQVhkW6dKfmn3f8jav63txWR DMfo2n9ve67o+W/wKpXWocapFpBO1zWeS2yYU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=ZV3EjUZVbDnjm1zj2Ac+2OSjTsxq57ZHeG+eLo0uV/P4X0oGcxlWsQ+bJ/0TlTzmDA we36o2XgA3FH4drp5Pl69FWvFhvjgjtGlTm4I+TvnKqktiN9DKeIA1xazVgzRFHDtKUg B+PhxzivKE3fqJN2vGi7IAgyHQJQVOj2h7V8o= MIME-Version: 1.0 Received: by 10.213.7.18 with SMTP id b18mr6392230ebb.63.1289895136509; Tue, 16 Nov 2010 00:12:16 -0800 (PST) Received: by 10.213.28.2 with HTTP; Tue, 16 Nov 2010 00:12:16 -0800 (PST) In-Reply-To: References: Date: Tue, 16 Nov 2010 03:12:16 -0500 Message-ID: From: Anthony Bryan To: Mark Nottingham Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Mailman-Approved-At: Tue, 16 Nov 2010 00:27:53 -0800 Cc: link-relations@ietf.org Subject: Re: [link-relations] NEW RELATION REQUEST: Relation name: "duplicate" 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: Tue, 16 Nov 2010 08:11:36 -0000 yes, I have. are you asking about intended document status or about moving the document forward? On Fri, Nov 12, 2010 at 12:00 AM, Mark Nottingham wrote: > Seems reasonable to me. > > I see you have Standards Track as the intended status -- have to talked t= o an AD about its future? > > Regards, > > > On 12/11/2010, at 11:27 AM, Anthony Bryan wrote: > >> Relation Name: >> =A0 duplicate >> >> Description: >> =A0 Refers to a resource whose available representations >> =A0 are byte-for-byte identical with the corresponding representations o= f >> =A0 the context IRI. >> >> Reference: >> =A0 http://tools.ietf.org/html/draft-bryan-metalinkhttp >> >> Notes: >> =A0 This relation is for static resources. =A0That is, an HTTP GET >> =A0 request on any duplicate will return the same representation. =A0It >> =A0 does not make sense for dynamic or POSTable resources and should not >> =A0 be used for them. >> >> -- >> (( Anthony Bryan ... Metalink [ http://www.metalinker.org ] >> =A0 )) Easier, More Reliable, Self Healing Downloads >> _______________________________________________ >> link-relations mailing list >> link-relations@ietf.org >> https://www.ietf.org/mailman/listinfo/link-relations > > -- > Mark Nottingham =A0 http://www.mnot.net/ > > > > --=20 (( Anthony Bryan ... Metalink [ http://www.metalinker.org ] =A0 )) Easier, More Reliable, Self Healing Downloads From derhoermi@gmx.net Tue Nov 16 00:45:40 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 2E5993A69CE for ; Tue, 16 Nov 2010 00:45:40 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.429 X-Spam-Level: X-Spam-Status: No, score=-4.429 tagged_above=-999 required=5 tests=[AWL=-1.830, 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 1wWMHn8S3F7N for ; Tue, 16 Nov 2010 00:45:39 -0800 (PST) Received: from mail.gmx.net (mailout-de.gmx.net [213.165.64.23]) by core3.amsl.com (Postfix) with SMTP id 8AD553A6DB3 for ; Tue, 16 Nov 2010 00:45:38 -0800 (PST) Received: (qmail invoked by alias); 16 Nov 2010 08:46:21 -0000 Received: from dslb-094-223-178-207.pools.arcor-ip.net (EHLO xn--bjrn-6qa.xn--hhrmann-90a.de) [94.223.178.207] by mail.gmx.net (mp001) with SMTP; 16 Nov 2010 09:46:21 +0100 X-Authenticated: #723575 X-Provags-ID: V01U2FsdGVkX196xQ9UICR6TfCCYtL9Tfddo5q6LNp+S0gLk4Tk8r VvqvAW2U7U6iU9 From: Bjoern Hoehrmann To: Stephane Bortzmeyer Date: Tue, 16 Nov 2010 09:46:40 +0100 Message-ID: References: <20101113084026.GB23318@laperouse.bortzmeyer.org> In-Reply-To: <20101113084026.GB23318@laperouse.bortzmeyer.org> X-Mailer: Forte Agent 3.3/32.846 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Y-GMX-Trusted: 0 Cc: Anthony Bryan , link-relations@ietf.org Subject: Re: [link-relations] NEW RELATION REQUEST: Relation name: "duplicate" 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: Tue, 16 Nov 2010 08:45:40 -0000 * Stephane Bortzmeyer wrote: >On Thu, Nov 11, 2010 at 07:27:55PM -0500, > Anthony Bryan wrote > a message of 25 lines which said: > >> Refers to a resource whose available representations are >> byte-for-byte > >Was there any discussion (pointer, please) on this choice of defining >it as a byte-for-byte equivalence? Because it will be quite strict, >meaning that two very same XML documents, with the same infoset but >different representations (for instance, UTF-8 + NFC and UTF-8 without >NFC), will not be regarded as "duplicate". (That is a very bad example, an XML document that is in NFC cannot have the same Infoset as an XML document that is not in NFC, even Canonical XML does not emply character normalization if the input is UTF-8.) -- Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de 25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ From bortzmeyer@nic.fr Wed Nov 17 01:02:03 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 BE7EB3A68B9 for ; Wed, 17 Nov 2010 01:02:03 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -105.295 X-Spam-Level: X-Spam-Status: No, score=-105.295 tagged_above=-999 required=5 tests=[AWL=-0.804, BAYES_00=-2.599, FR_3TAG_3TAG=1.758, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4, 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 w8JWJtjLDtaE for ; Wed, 17 Nov 2010 01:02:02 -0800 (PST) Received: from mx2.nic.fr (mx2.nic.fr [IPv6:2001:660:3003:2::4:11]) by core3.amsl.com (Postfix) with ESMTP id 5B01A3A680C for ; Wed, 17 Nov 2010 01:02:02 -0800 (PST) Received: from mx2.nic.fr (localhost [127.0.0.1]) by mx2.nic.fr (Postfix) with SMTP id 9CF631C0145; Wed, 17 Nov 2010 10:02:46 +0100 (CET) Received: from relay2.nic.fr (relay2.nic.fr [192.134.4.163]) by mx2.nic.fr (Postfix) with ESMTP id 9886B1C00DF; Wed, 17 Nov 2010 10:02:46 +0100 (CET) Received: from bortzmeyer.nic.fr (batilda.nic.fr [192.134.4.69]) by relay2.nic.fr (Postfix) with ESMTP id 8C31A7B0037; Wed, 17 Nov 2010 10:02:46 +0100 (CET) Date: Wed, 17 Nov 2010 10:02:46 +0100 From: Stephane Bortzmeyer To: Bjoern Hoehrmann Message-ID: <20101117090246.GA29352@nic.fr> References: <20101113084026.GB23318@laperouse.bortzmeyer.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: Debian GNU/Linux squeeze/sid X-Kernel: Linux 2.6.26-2-686 i686 Organization: NIC France X-URL: http://www.nic.fr/ User-Agent: Mutt/1.5.20 (2009-06-14) Cc: Anthony Bryan , link-relations@ietf.org Subject: Re: [link-relations] NEW RELATION REQUEST: Relation name: "duplicate" 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, 17 Nov 2010 09:02:03 -0000 On Tue, Nov 16, 2010 at 09:46:40AM +0100, Bjoern Hoehrmann wrote a message of 21 lines which said: > (That is a very bad example, an XML document that is in NFC cannot have > the same Infoset as an XML document that is not in NFC, even Canonical > XML does not emply character normalization if the input is UTF-8.) OK, I did not use the word Infoset properly. I should have say "the same content" (where Content is not defined formally). A better example: is not a "duplicate" of: which may be disconcerting.