IETF Logo Mail Archive

Re: Request to register "identifier" relation type

Ed Summers <ehs@pobox.com> Sat, 05 August 2017 12:00 UTC

Return-Path: <ehs@pobox.com>
X-Original-To: link-relations@ietfa.amsl.com
Delivered-To: link-relations@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F28C6131CDC for <link-relations@ietfa.amsl.com>; Sat, 5 Aug 2017 05:00:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=pobox.com; domainkeys=pass (1024-bit key) header.from=ehs@pobox.com header.d=pobox.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ag_u1I2QAtZD for <link-relations@ietfa.amsl.com>; Sat, 5 Aug 2017 05:00:18 -0700 (PDT)
Received: from sasl.smtp.pobox.com (pb-smtp2.pobox.com [64.147.108.71]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AAFA1131CB5 for <link-relations@ietf.org>; Sat, 5 Aug 2017 04:59:57 -0700 (PDT)
Received: from sasl.smtp.pobox.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id BCE148AD0B; Sat, 5 Aug 2017 07:59:53 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=content-type :mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=sasl; bh= /V8UC+5IUottf+19SmakzkY38CA=; b=i13ofF+KLe5GULfBWIt8ky3bd2PnDrAA B09jeFJNDs1JxG0gdR8awtYmSNPw2DFL5Xm63Rvglsnd8P7gTQ+mGteZ0o8Wk6Qc IZhBPqrJ9cuUHh2FNbEGZfo+5o2jvNQcJaEUPm9RliQK7L9aARWN12Glw875fZ4G OQrRcKag8pI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=content-type :mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; q=dns; s= sasl; b=mGI0VraKoNPJzrGTsRpoZ5yi9zEsuhJELCtIeXbkQT3Qzk7iGJh0Q989 bERJELSUwlb9Tzvf/ywYAkvgl7WoorOv6ZVjUWg6MBhkV2cmKUtu9ib4ku7eda8l OkTvhVJGwOxXa+rH/cgtjtz5pl80ON0zaEV2L4HdoPuxgBhKeto=
Received: from pb-smtp2.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id B5D3C8AD0A; Sat, 5 Aug 2017 07:59:53 -0400 (EDT)
Received: from prajna.fios-router.home (unknown [96.241.216.54]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pb-smtp2.pobox.com (Postfix) with ESMTPSA id AD1D28AD04; Sat, 5 Aug 2017 07:59:52 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Request to register "identifier" relation type
From: Ed Summers <ehs@pobox.com>
In-Reply-To: <54CA5E71-F469-4FD9-AF29-21985B454CAE@gmail.com>
Date: Sat, 05 Aug 2017 07:59:58 -0400
Cc: Peter Williams <pezra@barelyenough.org>, Geoffrey Bilder <gbilder@crossref.org>, Michael Nelson <mln@cs.odu.edu>, Simeon Warner <simeon.warner@cornell.edu>, "John A. Kunze" <jak@ucop.edu>, link-relations <link-relations@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <DEE2ABBF-1146-4E17-875F-3F5EFFB540FB@pobox.com>
References: <CAOywMHeHcwP5h4vzbTY+q00AEYn85F0E+LKqnx0aWpK1kcA1AA@mail.gmail.com> <CAK5Vdzz8=+6pfEDA2gGvtYU8kNx4pPKmsme71szP-JrvhpoTdw@mail.gmail.com> <54CA5E71-F469-4FD9-AF29-21985B454CAE@gmail.com>
To: Herbert Van de Sompel <hvdsomp@gmail.com>
X-Mailer: Apple Mail (2.3273)
X-Pobox-Relay-ID: 9757458E-79D5-11E7-9951-9D2B0D78B957-07615111!pb-smtp2.pobox.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/link-relations/uzDmAklrJgdI2O7QzZFNSlchvVA>
X-BeenThere: link-relations@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: <link-relations.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/link-relations>, <mailto:link-relations-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Sat, 05 Aug 2017 12:00:21 -0000

> On Aug 5, 2017, at 3:38 AM, Herbert Van de Sompel <hvdsomp@gmail.com> wrote:
> 
> The answer is in the I-D and in a blog post that is referenced in the I-D. Please have a look. 

I think a crisp one or two sentence reply to Peter's question ought to be possible. He rightly points out that the shared use of 'preferred' by your I-D and canonical could cause some confusion for web publishers. It also begs the question of preferred *for what*.

The core issue with canonical seems to be less a matter of semantics and more a practical matter of web publishers not wanting to assign a canonical or bookmark link to another domain (e.g. dx.doi.org) because of uncertainty about what this would mean for their Google juice. There is an SEO infrastructure built up around canonical, which has led to it being used quite a bit.

I wonder if rather than adding another link relation to the mix if the HTML folks would be willing to update rel=bookmark to allow for usage with <link> which ought to make it amenable to use in an HTTP header as some other HTML relations are (e.g. alternate). The semantics of bookmark speak directly to the issue of persistence that your I-D seems to be addressing.

Also, while the name 'identifier' is elegant in some ways, I find it a bit hard to swallow since all link targets are technically identifiers.

//Ed

v2.23.0 | Report a Bug | By Email