Re: [link-relations] NEW RELATION REQUEST: canonical

Julian Reschke <julian.reschke@gmx.de> Sun, 05 December 2010 13:59 UTC

Return-Path: <julian.reschke@gmx.de>
X-Original-To: link-relations@core3.amsl.com
Delivered-To: link-relations@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 419C028C10D for <link-relations@core3.amsl.com>; 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 <link-relations@core3.amsl.com>; 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 <link-relations@ietf.org>; 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 <julian.reschke@gmx.de>
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 <ehs@pobox.com>
References: <AANLkTi=gB=M+gM5JheX1pcNrdvgsiCzT6qi9zaYyL5X=@mail.gmail.com> <4CE0FDD9.6090804@gmx.de> <4CE11398.5000508@gmx.de> <AANLkTim8eQiTLUawhvX1bJ-6ctkVJ9zLDFk4p0Qh5PtM@mail.gmail.com>
In-Reply-To: <AANLkTim8eQiTLUawhvX1bJ-6ctkVJ9zLDFk4p0Qh5PtM@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: link-relations@ietf.org
Subject: Re: [link-relations] NEW RELATION REQUEST: canonical
X-BeenThere: link-relations@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <link-relations.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/link-relations>, <mailto:link-relations-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/link-relations>
List-Post: <mailto:link-relations@ietf.org>
List-Help: <mailto:link-relations-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/link-relations>, <mailto:link-relations-request@ietf.org?subject=subscribe>
X-List-Received-Date: 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<julian.reschke@gmx.de>  wrote:
>> <http://googlewebmastercentral.blogspot.com/2009/02/specify-your-canonical.html>
>>
>> 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 
<http://tools.ietf.org/html/rfc5988#section-6.2.1>:

    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