From mca@amundsen.com Wed Dec 1 21:02: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 823063A68A4 for ; Wed, 1 Dec 2010 21:02:52 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.88 X-Spam-Level: X-Spam-Status: No, score=-3.88 tagged_above=-999 required=5 tests=[AWL=-3.800, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, FORGED_YAHOO_RCVD=2.297, J_CHICKENPOX_46=0.6, RCVD_IN_DNSWL_LOW=-1] 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 ih6uuZcJjXVF for ; Wed, 1 Dec 2010 21:02:51 -0800 (PST) Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id 2807E3A68A2 for ; Wed, 1 Dec 2010 21:02:50 -0800 (PST) Received: by fxm9 with SMTP id 9so6500256fxm.31 for ; Wed, 01 Dec 2010 21:04:05 -0800 (PST) MIME-Version: 1.0 Received: by 10.223.72.14 with SMTP id k14mr20711faj.45.1291266243006; Wed, 01 Dec 2010 21:04:03 -0800 (PST) Sender: mca@amundsen.com Received: by 10.223.122.77 with HTTP; Wed, 1 Dec 2010 21:04:02 -0800 (PST) Date: Thu, 2 Dec 2010 00:04:02 -0500 X-Google-Sender-Auth: bMnNEzuOr6a4ofuuefX0CLawAsM Message-ID: From: mike amundsen To: link-relations@ietf.org Content-Type: text/plain; charset=ISO-8859-1 Subject: [link-relations] error on paramsr.us account confirmation 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, 02 Dec 2010 05:02:52 -0000 Just a heads up... When i followed the link (see below) i got a runtime error: *********************************************************************** NameError: global name 'urllib' is not defined Python 2.7 /usr/bin/python A problem occurred while running a Python script. Here is the sequence of function calls leading up to the error, with the most recent (innermost) call first. The exception attributes are: /usr/lib/python2.7/site-packages/roundup/cgi/actions.py in finishRego(self=) 799 message = self._('You are now registered, welcome!') 800 url = '%suser%s?@ok_message=%s'%(self.base, self.userid, 801 urllib._quote(message)) global urllib = undefined, global _quote = undefined, message = 'You are now registered, welcome!' 802 803 # redirect to the user's page (but not 302, as some email clients seem *********************************************************************** It looks like this is just a bug in the rendering of the response to a successful confirmation. I am able to login just fine now. mca http://amundsen.com/blog/ http://twitter.com@mamund http://mamund.com/foaf.rdf#me #RESTFest 2010 http://rest-fest.googlecode.com ---------- Forwarded message ---------- From: paramsr.us request tracker Date: Wed, Dec 1, 2010 at 23:20 Subject: Complete your registration to paramsr.us request tracker To: mamund@yahoo.com To complete your registration of the user "mamund" with paramsr.us request tracker, please visit the following URL: http://paramsr.us/tracker/?@action=confrego&otk=cxbAmXxFNnvWO2ZDTwMp2jmkQbjsOBUY From mnot@mnot.net Thu Dec 2 02:02: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 AFDC33A68E9 for ; Thu, 2 Dec 2010 02:02:00 -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=-2.500, BAYES_00=-2.599, J_CHICKENPOX_46=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 2VeAKbluNuO2 for ; Thu, 2 Dec 2010 02:01:59 -0800 (PST) Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by core3.amsl.com (Postfix) with ESMTP id 5EAF23A68E8 for ; Thu, 2 Dec 2010 02:01:59 -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 9133322E253; Thu, 2 Dec 2010 05:03:06 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v1082) Content-Type: text/plain; charset=us-ascii From: Mark Nottingham In-Reply-To: Date: Thu, 2 Dec 2010 21:03:03 +1100 Content-Transfer-Encoding: quoted-printable Message-Id: <2021F713-053E-4D86-A963-197E2DBF712B@mnot.net> References: To: mike amundsen X-Mailer: Apple Mail (2.1082) Cc: link-relations@ietf.org Subject: Re: [link-relations] error on paramsr.us account confirmation 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, 02 Dec 2010 10:02:00 -0000 That's bizarre.. sorry for the hassle, will look into it. Cheers and thanks, On 02/12/2010, at 4:04 PM, mike amundsen wrote: > Just a heads up... >=20 > When i followed the link (see below) i got a runtime error: > = *********************************************************************** > NameError: global name 'urllib' is not defined Python 2.7 > /usr/bin/python > A problem occurred while running a Python script. Here is the sequence > of function calls leading up to the error, with the most recent > (innermost) call first. The exception attributes are: >=20 > /usr/lib/python2.7/site-packages/roundup/cgi/actions.py in > finishRego(self=3D) > 799 message =3D self._('You are now registered, welcome!') > 800 url =3D '%suser%s?@ok_message=3D%s'%(self.base, = self.userid, > 801 urllib._quote(message)) > global urllib =3D undefined, global _quote =3D undefined, message = =3D > 'You are now registered, welcome!' > 802 > 803 # redirect to the user's page (but not 302, as some > email clients seem > = *********************************************************************** >=20 > It looks like this is just a bug in the rendering of the response to a > successful confirmation. >=20 > I am able to login just fine now. >=20 >=20 > mca > http://amundsen.com/blog/ > http://twitter.com@mamund > http://mamund.com/foaf.rdf#me >=20 >=20 > #RESTFest 2010 > http://rest-fest.googlecode.com >=20 >=20 >=20 >=20 >=20 > ---------- Forwarded message ---------- > From: paramsr.us request tracker > Date: Wed, Dec 1, 2010 at 23:20 > Subject: Complete your registration to paramsr.us request tracker > To: mamund@yahoo.com >=20 >=20 > To complete your registration of the user "mamund" with > paramsr.us request tracker, please visit the following URL: >=20 > = http://paramsr.us/tracker/?@action=3Dconfrego&otk=3DcxbAmXxFNnvWO2ZDTwMp2j= mkQbjsOBUY > _______________________________________________ > link-relations mailing list > link-relations@ietf.org > https://www.ietf.org/mailman/listinfo/link-relations -- Mark Nottingham http://www.mnot.net/ From mca@amundsen.com Thu Dec 2 08:05:44 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 62EC528C152 for ; Thu, 2 Dec 2010 08:05:44 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.98 X-Spam-Level: X-Spam-Status: No, score=-1.98 tagged_above=-999 required=5 tests=[AWL=-1.900, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, FORGED_YAHOO_RCVD=2.297, J_CHICKENPOX_46=0.6, RCVD_IN_DNSWL_LOW=-1] 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 kmEgxyfOUEm4 for ; Thu, 2 Dec 2010 08:05:43 -0800 (PST) Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by core3.amsl.com (Postfix) with ESMTP id 1E2BC28C0CE for ; Thu, 2 Dec 2010 08:05:43 -0800 (PST) Received: by gyb13 with SMTP id 13so4671293gyb.31 for ; Thu, 02 Dec 2010 08:06:58 -0800 (PST) MIME-Version: 1.0 Received: by 10.223.72.14 with SMTP id k14mr784063faj.45.1291306017613; Thu, 02 Dec 2010 08:06:57 -0800 (PST) Sender: mca@amundsen.com Received: by 10.223.122.77 with HTTP; Thu, 2 Dec 2010 08:06:57 -0800 (PST) In-Reply-To: <2021F713-053E-4D86-A963-197E2DBF712B@mnot.net> References: <2021F713-053E-4D86-A963-197E2DBF712B@mnot.net> Date: Thu, 2 Dec 2010 11:06:57 -0500 X-Google-Sender-Auth: uXQ73kMCdYkiwik_moHrp2f1ppI Message-ID: From: mike amundsen To: Mark Nottingham Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: link-relations@ietf.org Subject: Re: [link-relations] error on paramsr.us account confirmation 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, 02 Dec 2010 16:05:44 -0000 No worries. I was using Chrome browser, if that helps at all. If you need to, feel free to use my account to test this bug; I don't have any immediate need to post requests yet. mca http://amundsen.com/blog/ http://twitter.com@mamund http://mamund.com/foaf.rdf#me #RESTFest 2010 http://rest-fest.googlecode.com On Thu, Dec 2, 2010 at 05:03, Mark Nottingham wrote: > That's bizarre.. sorry for the hassle, will look into it. > > Cheers and thanks, > > > On 02/12/2010, at 4:04 PM, mike amundsen wrote: > >> Just a heads up... >> >> When i followed the link (see below) i got a runtime error: >> *********************************************************************** >> NameError: global name 'urllib' is not defined =A0 =A0 =A0 =A0Python 2.7 >> /usr/bin/python >> A problem occurred while running a Python script. Here is the sequence >> of function calls leading up to the error, with the most recent >> (innermost) call first. The exception attributes are: >> >> /usr/lib/python2.7/site-packages/roundup/cgi/actions.py in >> finishRego(self=3D) >> =A0799 =A0 =A0 =A0 =A0 message =3D self._('You are now registered, welco= me!') >> =A0800 =A0 =A0 =A0 =A0 url =3D '%suser%s?@ok_message=3D%s'%(self.base, s= elf.userid, >> =A0801 =A0 =A0 =A0 =A0 =A0 =A0 urllib._quote(message)) >> =A0 =A0 =A0global urllib =3D undefined, global _quote =3D undefined, mes= sage =3D >> 'You are now registered, welcome!' >> =A0802 >> =A0803 =A0 =A0 =A0 =A0 # redirect to the user's page (but not 302, as so= me >> email clients seem >> *********************************************************************** >> >> It looks like this is just a bug in the rendering of the response to a >> successful confirmation. >> >> I am able to login just fine now. >> >> >> mca >> http://amundsen.com/blog/ >> http://twitter.com@mamund >> http://mamund.com/foaf.rdf#me >> >> >> #RESTFest 2010 >> http://rest-fest.googlecode.com >> >> >> >> >> >> ---------- Forwarded message ---------- >> From: paramsr.us request tracker >> Date: Wed, Dec 1, 2010 at 23:20 >> Subject: Complete your registration to paramsr.us request tracker >> To: mamund@yahoo.com >> >> >> To complete your registration of the user "mamund" with >> paramsr.us request tracker, please visit the following URL: >> >> http://paramsr.us/tracker/?@action=3Dconfrego&otk=3DcxbAmXxFNnvWO2ZDTwMp= 2jmkQbjsOBUY >> _______________________________________________ >> link-relations mailing list >> link-relations@ietf.org >> https://www.ietf.org/mailman/listinfo/link-relations > > -- > Mark Nottingham =A0 http://www.mnot.net/ > > > > From julian.reschke@gmx.de Sun Dec 5 05:59:06 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 419C028C10D for ; Sun, 5 Dec 2010 05:59:06 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -104.606 X-Spam-Level: X-Spam-Status: No, score=-104.606 tagged_above=-999 required=5 tests=[AWL=-2.007, 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 Pa-+XGs8qQRN for ; Sun, 5 Dec 2010 05:59:05 -0800 (PST) Received: from mail.gmx.net (mailout-de.gmx.net [213.165.64.22]) by core3.amsl.com (Postfix) with SMTP id 0E6C828C10A for ; Sun, 5 Dec 2010 05:59:04 -0800 (PST) Received: (qmail invoked by alias); 05 Dec 2010 14:00:23 -0000 Received: from p508FB6B0.dip.t-dialin.net (EHLO [192.168.178.33]) [80.143.182.176] by mail.gmx.net (mp066) with SMTP; 05 Dec 2010 15:00:23 +0100 X-Authenticated: #1915285 X-Provags-ID: V01U2FsdGVkX19RVSImghxRBSQDzR2beSdDTIeQ5EfqN0Uwllyb01 ruUC+8I/Aj3m6x Message-ID: <4CFB9AF0.4020708@gmx.de> Date: Sun, 05 Dec 2010 15:00:16 +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> <4CE11398.5000508@gmx.de> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Cc: link-relations@ietf.org Subject: Re: [link-relations] NEW 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: Sun, 05 Dec 2010 13:59:06 -0000 On 15.11.2010 12:18, Ed Summers wrote: > 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 :-) OK, (writing just for me, not the other DEs) I have tried to get in contact with Google with respect to this, and have failed. I see the following options (just mentioning them all). a) do not register b) register as proposed c) register, but create a standalone spec defining it Let's consult the spec, see : Note that relation types can be registered by third parties, if the Designated Expert determines that an unregistered relation type is widely deployed and not likely to be registered in a timely manner. This appears to be the case here. At this point, I'd suggest option c): write a small spec we can publish as RFC, and give Google another opportunity to give feedback when it goes through the process (for instance as a Informational RFC, maybe as direct RFC Editor submission). Ed -- would you be interested in either authoring or co-authoring that spec? (I'll help with the formatting mechanics). Feedback appreciated, Julian From julian.reschke@gmx.de Sun Dec 5 07:12: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 E423228B56A for ; Sun, 5 Dec 2010 07:12:16 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -104.573 X-Spam-Level: X-Spam-Status: No, score=-104.573 tagged_above=-999 required=5 tests=[AWL=-1.974, 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 USmd+j1HWdiK for ; Sun, 5 Dec 2010 07:12:15 -0800 (PST) Received: from mail.gmx.net (mailout-de.gmx.net [213.165.64.22]) by core3.amsl.com (Postfix) with SMTP id D561C3A6ADE for ; Sun, 5 Dec 2010 07:12:14 -0800 (PST) Received: (qmail invoked by alias); 05 Dec 2010 15:13:35 -0000 Received: from p508FB6B0.dip.t-dialin.net (EHLO [192.168.178.33]) [80.143.182.176] by mail.gmx.net (mp072) with SMTP; 05 Dec 2010 16:13:35 +0100 X-Authenticated: #1915285 X-Provags-ID: V01U2FsdGVkX19++jhJyp1+clkIslFTEfx0C15hAzZAZa5ncoB7UC brDdrml0ckMejk Message-ID: <4CFBAC1D.5090604@gmx.de> Date: Sun, 05 Dec 2010 16:13:33 +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: link-relations@ietf.org Content-Type: multipart/mixed; boundary="------------030609080003030100050306" X-Y-GMX-Trusted: 0 Subject: [link-relations] An Internet Draft template for writing a Link Relation specification 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, 05 Dec 2010 15:12:17 -0000 This is a multi-part message in MIME format. --------------030609080003030100050306 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi, to make it easier to write an Internet Draft defining a Link Relation (with the goal of publishing as RFC), I have created a small template. It uses the RFC2629-syntax, as consumed by xml2rfc.tcl (web service at xml.resource.org) and rfc2629.xslt (). (*) Additional material: Slides created by the RFC Production Center: and "Guidelines to Authors of Internet-Drafts": Feedback about the template appreciated... Julian (*) For RFC2629/xml2rfc related questions, the best place to start is ; feel free to cc me on questions. --------------030609080003030100050306 Content-Type: text/xml; name="link-relation-id-template.xml" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="link-relation-id-template.xml" PD94bWwtc3R5bGVzaGVldCB0eXBlPSd0ZXh0L3hzbCcgaHJlZj0ncmZjMjYyOS54c2x0Jz8+ DQo8P3JmYyBjb21tZW50cz0ieWVzIj8+DQo8P3JmYyBpbmxpbmU9InllcyI/Pg0KPD9yZmMg cmZjZWRzdHlsZT0ieWVzIj8+DQo8IS0tIEJFTE9XIFlPVSBNQVkgTkVFRCBUTyBNT0RJRlkg VEhFIEFUVFJJQlVURTsgSUYgTk9UIFNVUkUgQ09OU1VMVCBXSVRIIFRIRSBNQUlMSU5HIExJ U1QtLT4NCjxyZmMgZG9jTmFtZT0iZHJhZnQtTEFTVE5BTUUtRk9PQkFSLWxpbmstcmVsYXRp b24tbGF0ZXN0IiBpcHI9InRydXN0MjAwOTAyIj4NCjxmcm9udD4NCjx0aXRsZT5UaGUgRk9P QkFSIExpbmsgUmVsYXRpb248L3RpdGxlPg0KPGF1dGhvciBmdWxsbmFtZT0iRklSU1ROQU1F IExBU1ROQU1FIiBzdXJuYW1lPSJMQVNUTkFNRSIgaW5pdGlhbHM9IkYuIj4NCiAgPGFkZHJl c3M+DQogICAgPGVtYWlsPkZJUlNUTkFNRS5MQVNUTkFNRUBFWEFNUExFLkNPTTwvZW1haWw+ DQogIDwvYWRkcmVzcz4NCjwvYXV0aG9yPg0KPGRhdGUvPg0KPGFic3RyYWN0Pg0KPHQ+DQog IDxjcmVmPlNIT1JUIERFU0NSSVBUSU9OIE9GIExJTksgUkVMQVRJT048L2NyZWY+DQo8L3Q+ DQo8L2Fic3RyYWN0Pg0KPG5vdGUgdGl0bGU9IkVkaXRvcmlhbCBOb3RlIChUbyBiZSByZW1v dmVkIGJ5IFJGQyBFZGl0b3IpIj4NCjx0Pg0KICA8Y3JlZj5TVEFURSBBIFZFTlVFIEZPUiBE SVNDVVNTSU9OLCBPUFRJTUFMTFkgQSBQVUJMSUMsIEFSQ0hJVkVEIElFVEYgTUFJTElORyBM SVNULCBTVUNIIEFTLi4uOjwvY3JlZj4NCjwvdD4NCjx0Pg0KICBEaXN0cmlidXRpb24gb2Yg dGhpcyBkb2N1bWVudCBpcyB1bmxpbWl0ZWQuIENvbW1lbnRzIHNob3VsZCBiZSBzZW50IHRv IHRoZSANCiAgSUVURiBBcHBzLURpc2N1c3MgbWFpbGluZyBsaXN0IChzZWUgPGVyZWYgdGFy Z2V0PSJodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2FwcHMtZGlzY3Vz cyIvPikuDQo8L3Q+IA0KPC9ub3RlPg0KPC9mcm9udD4NCjxtaWRkbGU+DQo8c2VjdGlvbiB0 aXRsZT0iSW50cm9kdWN0aW9uIj4NCjx0Pg0KICA8Y3JlZj5JTlNFUlQgSU5UUk9EVUNUSU9O PC9jcmVmPg0KPC90Pg0KPC9zZWN0aW9uPg0KPHNlY3Rpb24gdGl0bGU9Ik5vdGF0aW9uYWwg Q29udmVudGlvbnMiPg0KPHQ+DQogICBUaGUga2V5IHdvcmRzICJNVVNUIiwgIk1VU1QgTk9U IiwgIlJFUVVJUkVEIiwgIlNIQUxMIiwgIlNIQUxMIE5PVCIsDQogICAiU0hPVUxEIiwgIlNI T1VMRCBOT1QiLCAiUkVDT01NRU5ERUQiLCAiTUFZIiwgYW5kICJPUFRJT05BTCIgaW4gdGhp cw0KICAgZG9jdW1lbnQgYXJlIHRvIGJlIGludGVycHJldGVkIGFzIGRlc2NyaWJlZCBpbiA8 eHJlZiB0YXJnZXQ9IlJGQzIxMTkiLz4uDQo8L3Q+DQo8L3NlY3Rpb24+DQo8c2VjdGlvbiB0 aXRsZT0iVGhlIEZPT0JBUiBMaW5rIFJlbGF0aW9uIj4NCjx0Pg0KICA8Y3JlZj5ERVNDUklC RSBUSEUgU0VNQU5USUNTIE9GIFRIRSBMSU5LIFJFTEFUSU9OPC9jcmVmPg0KPC90Pg0KPC9z ZWN0aW9uPg0KPHNlY3Rpb24gdGl0bGU9IklBTkEgQ29uc2lkZXJhdGlvbnMiPg0KPHQ+DQog IElBTkEgaXMgYXNrZWQgdG8gcmVnaXN0ZXIgdGhlIEZPT0JBUiBMaW5rIFJlbGF0aW9uIGJl bG93IGFzIHBlciANCiAgPHhyZWYgdGFyZ2V0PSJSRkM1OTg4Ii8+Lg0KPC90Pg0KPHQ+DQog IFJlbGF0aW9uIE5hbWU6DQogIDxsaXN0Pg0KICAgIDx0Pg0KICAgICAgRk9PQkFSDQogICAg PC90Pg0KICA8L2xpc3Q+DQo8L3Q+DQo8dD4NCiAgRGVzY3JpcHRpb246DQogIDxsaXN0Pg0K ICAgIDx0Pg0KICAgICAgPGNyZWY+U0hPUlQgREVTQ1JJUFRJT04gVEhBVCBXSUxMIEFQUEVB UiBJTiBUSEUgUkVHSVNUUlk8L2NyZWY+DQogICAgPC90Pg0KICA8L2xpc3Q+DQo8L3Q+DQo8 dD4NCiAgUmVmZXJlbmNlOg0KICA8bGlzdD4NCiAgICA8dD4NCiAgICAgIFRoaXMgc3BlY2lm aWNhdGlvbi4NCiAgICA8L3Q+DQogIDwvbGlzdD4NCjwvdD4NCjx0Pg0KICBOb3RlczoNCiAg PGxpc3Q+DQogICAgPHQ+DQogICAgICA8Y3JlZj5BRERJVElPTkFMIE5PVEVTIChPUFRJT05B TCk8L2NyZWY+DQogICAgPC90Pg0KICA8L2xpc3Q+DQo8L3Q+DQo8dD4NCiAgQXBwbGljYXRp b24gRGF0YToNCiAgPGxpc3Q+DQogICAgPHQ+DQogICAgICA8Y3JlZj5DT05TVUxUIFdJVEgg VEhFIE1BSUxJTkcgTElTVCAoT1BUSU9OQUwpPC9jcmVmPg0KICAgIDwvdD4NCiAgPC9saXN0 Pg0KPC90Pg0KPC9zZWN0aW9uPg0KPHNlY3Rpb24gdGl0bGU9IlNlY3VyaXR5IENvbnNpZGVy YXRpb25zIj4NCjx0Pg0KICA8Y3JlZj5JTlNFUlQgVEVYVDwvY3JlZj4NCjwvdD4NCjwvc2Vj dGlvbj4NCjxzZWN0aW9uIHRpdGxlPSJJbnRlcm5hdGlvbmFsaXNhdGlvbiBDb25zaWRlcmF0 aW9ucyI+DQo8dD4NCiAgPGNyZWY+SU5TRVJUIFRFWFQgKENPTlNJREVSIFJGQyA1OTg3KTwv Y3JlZj4NCjwvdD4NCjwvc2VjdGlvbj4NCjwvbWlkZGxlPg0KPGJhY2s+DQo8cmVmZXJlbmNl cyB0aXRsZT0iTm9ybWF0aXZlIFJlZmVyZW5jZXMiPg0KPHJlZmVyZW5jZSBhbmNob3I9IlJG QzIxMTkiPg0KICA8ZnJvbnQ+DQogICAgPHRpdGxlPktleSB3b3JkcyBmb3IgdXNlIGluIFJG Q3MgdG8gSW5kaWNhdGUgUmVxdWlyZW1lbnQgTGV2ZWxzPC90aXRsZT4NCiAgICA8YXV0aG9y IGluaXRpYWxzPSJTLiIgc3VybmFtZT0iQnJhZG5lciIgZnVsbG5hbWU9IlNjb3R0IEJyYWRu ZXIiPg0KICAgICAgPG9yZ2FuaXphdGlvbj5IYXJ2YXJkIFVuaXZlcnNpdHk8L29yZ2FuaXph dGlvbj4NCiAgICAgIDxhZGRyZXNzPjxlbWFpbD5zb2JAaGFydmFyZC5lZHU8L2VtYWlsPjwv YWRkcmVzcz4NCiAgICA8L2F1dGhvcj4NCiAgICA8ZGF0ZSBtb250aD0iTWFyY2giIHllYXI9 IjE5OTciLz4NCiAgPC9mcm9udD4NCiAgPHNlcmllc0luZm8gbmFtZT0iQkNQIiB2YWx1ZT0i MTQiLz4NCiAgPHNlcmllc0luZm8gbmFtZT0iUkZDIiB2YWx1ZT0iMjExOSIvPg0KPC9yZWZl cmVuY2U+DQo8cmVmZXJlbmNlIGFuY2hvcj0iUkZDNTk4OCI+DQogIDxmcm9udD4NCiAgICA8 dGl0bGU+V2ViIExpbmtpbmc8L3RpdGxlPg0KICAgIDxhdXRob3IgZnVsbG5hbWU9Ik1hcmsg Tm90dGluZ2hhbSIgaW5pdGlhbHM9Ik0uIiBzdXJuYW1lPSJOb3R0aW5naGFtIj4NCiAgICAg IDxhZGRyZXNzPjxlbWFpbD5tbm90QG1ub3QubmV0PC9lbWFpbD48L2FkZHJlc3M+DQogICAg PC9hdXRob3I+DQogICAgPGRhdGUgbW9udGg9Ik9jdG9iZXIiIHllYXI9IjIwMTAiIC8+DQog IDwvZnJvbnQ+DQogIDxzZXJpZXNJbmZvIG5hbWU9IlJGQyIgdmFsdWU9IjU5ODgiLz4NCjwv cmVmZXJlbmNlPg0KPC9yZWZlcmVuY2VzPg0KPC9iYWNrPg0KPC9yZmM+ --------------030609080003030100050306-- From justin@specialbusservice.com Sun Dec 5 08:43:59 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 5D6223A69AF for ; Sun, 5 Dec 2010 08:43:59 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.599 X-Spam-Level: X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] 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 JrBAD7gnDxsF for ; Sun, 5 Dec 2010 08:43:57 -0800 (PST) Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 71CDC3A688D for ; Sun, 5 Dec 2010 08:43:57 -0800 (PST) Received: by wyf23 with SMTP id 23so10415296wyf.31 for ; Sun, 05 Dec 2010 08:45:18 -0800 (PST) Received: by 10.216.171.75 with SMTP id q53mr3791713wel.74.1291567517568; Sun, 05 Dec 2010 08:45:17 -0800 (PST) References: <4CFBAC1D.5090604@gmx.de> From: Justin Cormack In-Reply-To: <4CFBAC1D.5090604@gmx.de> Mime-Version: 1.0 (iPhone Mail 8B117) Date: Sun, 5 Dec 2010 16:48:02 +0000 Message-ID: <1669821023504269395@unknownmsgid> To: Julian Reschke Content-Type: text/plain; charset=UTF-8 Cc: "link-relations@ietf.org" Subject: Re: [link-relations] An Internet Draft template for writing a Link Relation specification 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, 05 Dec 2010 16:43:59 -0000 You are making it easy! I am happy to write 'canonical' if no one else wants to. Justin On 5 Dec 2010, at 15:13, Julian Reschke wrote: > Hi, > > to make it easier to write an Internet Draft defining a Link Relation (with the goal of publishing as RFC), I have created a small template. > > It uses the RFC2629-syntax, as consumed by xml2rfc.tcl (web service at xml.resource.org) and rfc2629.xslt (). (*) > > Additional material: > > Slides created by the RFC Production Center: and > > "Guidelines to Authors of Internet-Drafts": > > Feedback about the template appreciated... > > Julian > > (*) For RFC2629/xml2rfc related questions, the best place to start is ; feel free to cc me on questions. > > _______________________________________________ > link-relations mailing list > link-relations@ietf.org > https://www.ietf.org/mailman/listinfo/link-relations From mnot@mnot.net Sun Dec 5 22:34: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 C18A03A69F6 for ; Sun, 5 Dec 2010 22:34:02 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -104.342 X-Spam-Level: X-Spam-Status: No, score=-104.342 tagged_above=-999 required=5 tests=[AWL=-2.343, BAYES_00=-2.599, J_CHICKENPOX_46=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 7jmpMsbDk2Wr for ; Sun, 5 Dec 2010 22:34:01 -0800 (PST) Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by core3.amsl.com (Postfix) with ESMTP id C0AF93A69F1 for ; Sun, 5 Dec 2010 22:34:00 -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 4B22522E1F3; Mon, 6 Dec 2010 01:35:17 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v1082) Content-Type: text/plain; charset=us-ascii From: Mark Nottingham In-Reply-To: Date: Mon, 6 Dec 2010 17:35:13 +1100 Content-Transfer-Encoding: quoted-printable Message-Id: <59FB3E47-54ED-4EF6-90F3-83CF183B8E63@mnot.net> References: <2021F713-053E-4D86-A963-197E2DBF712B@mnot.net> To: mike amundsen X-Mailer: Apple Mail (2.1082) Cc: link-relations@ietf.org Subject: Re: [link-relations] error on paramsr.us account confirmation 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, 06 Dec 2010 06:34:03 -0000 Should be fixed; was a known bug in roundup. Cheers, On 03/12/2010, at 3:06 AM, mike amundsen wrote: > No worries. >=20 > I was using Chrome browser, if that helps at all. >=20 > If you need to, feel free to use my account to test this bug; I don't > have any immediate need to post requests yet. >=20 > mca > http://amundsen.com/blog/ > http://twitter.com@mamund > http://mamund.com/foaf.rdf#me >=20 >=20 > #RESTFest 2010 > http://rest-fest.googlecode.com >=20 >=20 >=20 >=20 > On Thu, Dec 2, 2010 at 05:03, Mark Nottingham wrote: >> That's bizarre.. sorry for the hassle, will look into it. >>=20 >> Cheers and thanks, >>=20 >>=20 >> On 02/12/2010, at 4:04 PM, mike amundsen wrote: >>=20 >>> Just a heads up... >>>=20 >>> When i followed the link (see below) i got a runtime error: >>> = *********************************************************************** >>> NameError: global name 'urllib' is not defined Python 2.7 >>> /usr/bin/python >>> A problem occurred while running a Python script. Here is the = sequence >>> of function calls leading up to the error, with the most recent >>> (innermost) call first. The exception attributes are: >>>=20 >>> /usr/lib/python2.7/site-packages/roundup/cgi/actions.py in >>> finishRego(self=3D) >>> 799 message =3D self._('You are now registered, welcome!') >>> 800 url =3D '%suser%s?@ok_message=3D%s'%(self.base, = self.userid, >>> 801 urllib._quote(message)) >>> global urllib =3D undefined, global _quote =3D undefined, = message =3D >>> 'You are now registered, welcome!' >>> 802 >>> 803 # redirect to the user's page (but not 302, as some >>> email clients seem >>> = *********************************************************************** >>>=20 >>> It looks like this is just a bug in the rendering of the response to = a >>> successful confirmation. >>>=20 >>> I am able to login just fine now. >>>=20 >>>=20 >>> mca >>> http://amundsen.com/blog/ >>> http://twitter.com@mamund >>> http://mamund.com/foaf.rdf#me >>>=20 >>>=20 >>> #RESTFest 2010 >>> http://rest-fest.googlecode.com >>>=20 >>>=20 >>>=20 >>>=20 >>>=20 >>> ---------- Forwarded message ---------- >>> From: paramsr.us request tracker >>> Date: Wed, Dec 1, 2010 at 23:20 >>> Subject: Complete your registration to paramsr.us request tracker >>> To: mamund@yahoo.com >>>=20 >>>=20 >>> To complete your registration of the user "mamund" with >>> paramsr.us request tracker, please visit the following URL: >>>=20 >>> = http://paramsr.us/tracker/?@action=3Dconfrego&otk=3DcxbAmXxFNnvWO2ZDTwMp2j= mkQbjsOBUY >>> _______________________________________________ >>> 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 eran@hueniverse.com Mon Dec 6 00:03: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 8FB0E3A698E for ; Mon, 6 Dec 2010 00:03:45 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.503 X-Spam-Level: X-Spam-Status: No, score=-2.503 tagged_above=-999 required=5 tests=[AWL=0.096, 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 FHmXc4s6FeuP for ; Mon, 6 Dec 2010 00:03:44 -0800 (PST) Received: from p3plex1out02.prod.phx3.secureserver.net (p3plex1out02.prod.phx3.secureserver.net [72.167.180.18]) by core3.amsl.com (Postfix) with SMTP id 3F5FB3A67CF for ; Mon, 6 Dec 2010 00:03:43 -0800 (PST) Received: (qmail 27647 invoked from network); 6 Dec 2010 08:05:06 -0000 Received: from unknown (HELO smtp.ex1.secureserver.net) (72.167.180.21) by p3plex1out02.prod.phx3.secureserver.net with SMTP; 6 Dec 2010 08:05:05 -0000 Received: from P3PW5EX1MB01.EX1.SECURESERVER.NET ([10.6.135.20]) by P3PW5EX1HT003.EX1.SECURESERVER.NET ([72.167.180.21]) with mapi; Mon, 6 Dec 2010 01:05:05 -0700 From: Eran Hammer-Lahav To: Anthony Bryan , Stephane Bortzmeyer Date: Mon, 6 Dec 2010 01:04:50 -0700 Thread-Topic: [link-relations] NEW RELATION REQUEST: Relation name: "duplicate" Thread-Index: AcuFaEkU/HIZ8r+RQtuz3C3ZeQHT1wPs8AOg Message-ID: <90C41DD21FB7C64BB94121FBBC2E72343D4B066037@P3PW5EX1MB01.EX1.SECURESERVER.NET> References: <20101113084026.GB23318@laperouse.bortzmeyer.org> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 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: Mon, 06 Dec 2010 08:03:45 -0000 > -----Original Message----- > From: link-relations-bounces@ietf.org [mailto:link-relations- > bounces@ietf.org] On Behalf Of Anthony Bryan > Sent: Tuesday, November 16, 2010 12:10 AM > On Sat, Nov 13, 2010 at 3:40 AM, Stephane Bortzmeyer > wrote: > > 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". >=20 > for what we're doing, it needs to be byte-for-byte identical. >=20 > metalink clients usually deal with large file downloads, and under certai= n > conditions, might request byte ranges from different servers and patch em > together. I think this explanation needs to be added to the note as it more properly = constrains the definition and deployment than the GET/POST discussion in th= e current template. EHL > 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 > _______________________________________________ > link-relations mailing list > link-relations@ietf.org > https://www.ietf.org/mailman/listinfo/link-relations From julian.reschke@gmx.de Mon Dec 6 04:39: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 311A03A6778 for ; Mon, 6 Dec 2010 04:39:37 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -104.906 X-Spam-Level: X-Spam-Status: No, score=-104.906 tagged_above=-999 required=5 tests=[AWL=-2.307, 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 yfOUzncvjjWg for ; Mon, 6 Dec 2010 04:39:33 -0800 (PST) Received: from mail.gmx.net (mailout-de.gmx.net [213.165.64.22]) by core3.amsl.com (Postfix) with SMTP id D373B3A6767 for ; Mon, 6 Dec 2010 04:39:31 -0800 (PST) Received: (qmail invoked by alias); 06 Dec 2010 12:40:50 -0000 Received: from mail.greenbytes.de (EHLO [192.168.1.133]) [217.91.35.233] by mail.gmx.net (mp068) with SMTP; 06 Dec 2010 13:40:50 +0100 X-Authenticated: #1915285 X-Provags-ID: V01U2FsdGVkX19K9SVHWWFKIRCKKlcklyuTfy70koQ1iJ28Zm15ax HiI4JDfNAegnEM Message-ID: <4CFCD9D1.8020003@gmx.de> Date: Mon, 06 Dec 2010 13:40:49 +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: Justin Cormack References: <4CFBAC1D.5090604@gmx.de> <1669821023504269395@unknownmsgid> In-Reply-To: <1669821023504269395@unknownmsgid> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Cc: "link-relations@ietf.org" Subject: Re: [link-relations] An Internet Draft template for writing a Link Relation specification 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, 06 Dec 2010 12:39:37 -0000 On 05.12.2010 17:48, Justin Cormack wrote: > You are making it easy! I am happy to write 'canonical' if no one else > wants to. > > Justin Hi Justin, That sounds like a very good idea to me. Best regards, Julian From williamstw@gmail.com Mon Dec 6 18:35: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 475E928C0CF for ; Mon, 6 Dec 2010 18:35:02 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -9.977 X-Spam-Level: X-Spam-Status: No, score=-9.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 fWm+1YD8MkV0 for ; Mon, 6 Dec 2010 18:35:02 -0800 (PST) Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by core3.amsl.com (Postfix) with ESMTP id E1B2B3A68E7 for ; Mon, 6 Dec 2010 18:35:01 -0800 (PST) Received: by yxt33 with SMTP id 33so3081269yxt.31 for ; Mon, 06 Dec 2010 18:36: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; bh=aNtuO3T0d4CxBEQK51oUIzIEMACX8N43lnPxW+kbVmQ=; b=pLQHDrD8MGl2nmCcrL0Y0PUy6qhhnuakgmOR0Bnoa0Uyb/okyxp+kwn2x0dJ+XHwVs mL3SzSXonh5WxgMnooJfUQYH+aoE19LeZFnbUXlFu1RJ8+scHXFeEQeSTZEPCBg/oPu6 1VZ/2Iqv1aib70GZax0aFIini89TB1nO98KlE= 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; b=LfaoX0svilvbvQwvCzL8SxYK8B5aCApTkNWdFx9cVg264MiwpI1eqUALN+0ju+CQM+ XsrM6cWKhMDzgMNr1aq0tmCtLqOW0FnfgFGN1tWi2vKAFmSgi9Rr3Lc1+T3T9uUkzjed /T8PSJSH0dclN7dg8SuiPlnYbVWt8NUlteKHo= MIME-Version: 1.0 Received: by 10.150.146.17 with SMTP id t17mr857641ybd.31.1291689385894; Mon, 06 Dec 2010 18:36:25 -0800 (PST) Received: by 10.151.150.2 with HTTP; Mon, 6 Dec 2010 18:36:25 -0800 (PST) In-Reply-To: <4CFBAC1D.5090604@gmx.de> References: <4CFBAC1D.5090604@gmx.de> Date: Mon, 6 Dec 2010 21:36:25 -0500 Message-ID: From: Tim Williams To: Julian Reschke Content-Type: text/plain; charset=ISO-8859-1 Cc: link-relations@ietf.org Subject: Re: [link-relations] An Internet Draft template for writing a Link Relation specification 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, 07 Dec 2010 02:35:02 -0000 Thanks for this Julian, this seems much more approachable. I'm curious about process with these. I gather there's two things that need to occur: 1) an Informational RFC through the Independent Submission process and 2) A mail here to ask for it to be added to the registry. What's the process for getting these reviewed/discussing prior to 1? Would it be appropriate to turn this mailing-list into a place for discussing candidate link relation types - with an appropriate subject label (e.g. [PROPOSAL])? Or is it typical to just submit it directly to through the form? Thanks, --tim On Sun, Dec 5, 2010 at 10:13 AM, Julian Reschke wrote: > Hi, > > to make it easier to write an Internet Draft defining a Link Relation (with > the goal of publishing as RFC), I have created a small template. > > It uses the RFC2629-syntax, as consumed by xml2rfc.tcl (web service at > xml.resource.org) and rfc2629.xslt > (). (*) > > Additional material: > > Slides created by the RFC Production Center: > and > > > "Guidelines to Authors of Internet-Drafts": > > > Feedback about the template appreciated... > > Julian > > (*) For RFC2629/xml2rfc related questions, the best place to start is > ; feel free to cc me > on questions. > From mnot@mnot.net Mon Dec 6 18:58: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 3987F3A68ED for ; Mon, 6 Dec 2010 18:58:16 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -104.683 X-Spam-Level: X-Spam-Status: No, score=-104.683 tagged_above=-999 required=5 tests=[AWL=-2.084, 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 UKg6g7yDokZ0 for ; Mon, 6 Dec 2010 18:58:14 -0800 (PST) Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by core3.amsl.com (Postfix) with ESMTP id 8ACFA3A68E5 for ; Mon, 6 Dec 2010 18:58:14 -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 1B11C22E257; Mon, 6 Dec 2010 21:59:36 -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, 7 Dec 2010 13:59:33 +1100 Content-Transfer-Encoding: quoted-printable Message-Id: References: <4CFBAC1D.5090604@gmx.de> To: Tim Williams X-Mailer: Apple Mail (2.1082) Cc: link-relations@ietf.org Subject: Re: [link-relations] An Internet Draft template for writing a Link Relation specification 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, 07 Dec 2010 02:58:16 -0000 We're happy to give advice about what makes a good relation, = specification text, etc. here, and asking for that advice early on, = rather than last minute, is much preferred. :)=20 Generally, though, the discussion of a relation itself should probably = happen within the community that's appropriate to it -- whether that's = HTML5, uFormats, RDF, etc. We will try to get the right people involved = if something starts here, of course, but it's easier when the community = hammers out the basics ahead of time, so we're not minting things that = aren't connected to running code. Cheers, On 07/12/2010, at 1:36 PM, Tim Williams wrote: > Thanks for this Julian, this seems much more approachable. I'm > curious about process with these. >=20 > I gather there's two things that need to occur: 1) an Informational > RFC through the Independent Submission process and 2) A mail here to > ask for it to be added to the registry. >=20 > What's the process for getting these reviewed/discussing prior to 1? > Would it be appropriate to turn this mailing-list into a place for > discussing candidate link relation types - with an appropriate subject > label (e.g. [PROPOSAL])? Or is it typical to just submit it directly > to through the form? >=20 > Thanks, > --tim >=20 > On Sun, Dec 5, 2010 at 10:13 AM, Julian Reschke = wrote: >> Hi, >>=20 >> to make it easier to write an Internet Draft defining a Link Relation = (with >> the goal of publishing as RFC), I have created a small template. >>=20 >> It uses the RFC2629-syntax, as consumed by xml2rfc.tcl (web service = at >> xml.resource.org) and rfc2629.xslt >> (). = (*) >>=20 >> Additional material: >>=20 >> Slides created by the RFC Production Center: >> and >> >>=20 >> "Guidelines to Authors of Internet-Drafts": >> >>=20 >> Feedback about the template appreciated... >>=20 >> Julian >>=20 >> (*) For RFC2629/xml2rfc related questions, the best place to start is >> ; feel free = to cc me >> on questions. >>=20 > _______________________________________________ > link-relations mailing list > link-relations@ietf.org > https://www.ietf.org/mailman/listinfo/link-relations -- Mark Nottingham http://www.mnot.net/ From julian.reschke@gmx.de Tue Dec 7 00:49: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 194053A6892 for ; Tue, 7 Dec 2010 00:49:03 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -104.449 X-Spam-Level: X-Spam-Status: No, score=-104.449 tagged_above=-999 required=5 tests=[AWL=-1.850, 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 S0OeDTIT2IT4 for ; Tue, 7 Dec 2010 00:49:02 -0800 (PST) Received: from mail.gmx.net (mailout-de.gmx.net [213.165.64.23]) by core3.amsl.com (Postfix) with SMTP id E9DC43A688B for ; Tue, 7 Dec 2010 00:49:01 -0800 (PST) Received: (qmail invoked by alias); 07 Dec 2010 08:50:26 -0000 Received: from p508FCB2C.dip.t-dialin.net (EHLO [192.168.178.33]) [80.143.203.44] by mail.gmx.net (mp027) with SMTP; 07 Dec 2010 09:50:26 +0100 X-Authenticated: #1915285 X-Provags-ID: V01U2FsdGVkX1/E980E2dLEXz65yy7V0Bn8P3EUQOKsHs91L0TOBb ENrcevD7JlqkT3 Message-ID: <4CFDF54F.7080603@gmx.de> Date: Tue, 07 Dec 2010 09:50:23 +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: <4CFBAC1D.5090604@gmx.de> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Cc: link-relations@ietf.org Subject: Re: [link-relations] An Internet Draft template for writing a Link Relation specification 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, 07 Dec 2010 08:49:03 -0000 On 07.12.2010 03:59, Mark Nottingham wrote: > We're happy to give advice about what makes a good relation, specification text, etc. here, and asking for that advice early on, rather than last minute, is much preferred. :) > > Generally, though, the discussion of a relation itself should probably happen within the community that's appropriate to it -- whether that's HTML5, uFormats, RDF, etc. We will try to get the right people involved if something starts here, of course, but it's easier when the community hammers out the basics ahead of time, so we're not minting things that aren't connected to running code. > ... Yup. If there's no other place, apps-discuss or the atom-syntax may be good choices. (The draft template says "apps-discuss"). However, if there are question with respect to how to phrase the definition, such as with respect to media formats or validity in certain contexts by all means post them here... Best regards, Julian From mnot@mnot.net Tue Dec 7 21:15:26 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 9C0333A689B for ; Tue, 7 Dec 2010 21:15:26 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -104.65 X-Spam-Level: X-Spam-Status: No, score=-104.65 tagged_above=-999 required=5 tests=[AWL=-2.051, 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 v2FStmuV9sDR for ; Tue, 7 Dec 2010 21:15:25 -0800 (PST) Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by core3.amsl.com (Postfix) with ESMTP id 71BC63A6875 for ; Tue, 7 Dec 2010 21:15:25 -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 3134B22E1F3; Wed, 8 Dec 2010 00:16:44 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v1082) Content-Type: text/plain; charset=us-ascii From: Mark Nottingham In-Reply-To: Date: Wed, 8 Dec 2010 16:16:42 +1100 Content-Transfer-Encoding: 7bit Message-Id: <9F2D0C6E-340B-4505-A506-6340E203CBF4@mnot.net> References: 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: Wed, 08 Dec 2010 05:15:26 -0000 Ed, Embarrassingly, I've overlooked a pre-existing draft: http://datatracker.ietf.org/doc/draft-johnston-addressing-link-relations/ In our defense, it predated the registry being approved... Perhaps you could work with Sam? Regards, On 15/11/2010, at 1:33 PM, 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. > _______________________________________________ > link-relations mailing list > link-relations@ietf.org > https://www.ietf.org/mailman/listinfo/link-relations -- Mark Nottingham http://www.mnot.net/