Re: Request to register "identifier" relation type

Herbert Van de Sompel <hvdsomp@gmail.com> Sat, 05 August 2017 12:58 UTC

Return-Path: <hvdsomp@gmail.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 A4523131EB3 for <link-relations@ietfa.amsl.com>; Sat, 5 Aug 2017 05:58:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 cWfUivfYg6eO for <link-relations@ietfa.amsl.com>; Sat, 5 Aug 2017 05:58:54 -0700 (PDT)
Received: from mail-wm0-x22e.google.com (mail-wm0-x22e.google.com [IPv6:2a00:1450:400c:c09::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DE662131DAC for <link-relations@ietf.org>; Sat, 5 Aug 2017 05:57:02 -0700 (PDT)
Received: by mail-wm0-x22e.google.com with SMTP id m85so37729306wma.0 for <link-relations@ietf.org>; Sat, 05 Aug 2017 05:57:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=z06F5C9EBUAVRX2lNgE27znFuZSTffaHQKm/+u5BA44=; b=eBS0usP1XrxZ8t3EMDX35R7wZYtGPxcSg3GZyIUWp0i4L5tg1DyjVjxhRL7swKQY5t Uka4IqpsibaG1vtxjxAvhrWoxPg24v7uQE57/wR2BIGBnsAvx7qSqz2MitwBTJeZLCq+ C1WccOZvrU3BWEmin1ZzkOY392p9j+fvTU6iZzLdR+8+LU1fHLIP7YfdgX+TG2C6hOft LAU8VkVb+cSKIXV2yjqln8ANXmGO/jUFITNPvxY9XijKH/bEGEHH7SBdFKOEpuP3/fVG p195gAdztZtQAE8N0e/4BPIWPiezsRXDK8YIY2QmfYW3EHKPfEo1I9nJHRDr4kgPMusl JhiA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=z06F5C9EBUAVRX2lNgE27znFuZSTffaHQKm/+u5BA44=; b=LqOC8uXtGCBySf5PFXCmUKW0jmMjDtw/ZgSBg8p4Ji4NGgovuTAb/qAqXzc3orW9sl 2Zb/QtXSCapgiYXDBGPMTftR1rgn5ZurxetPB1Xl8MLZOFpA7XpkhTdKgF2HOOB4UgSw nrYKaTlyQwHDJH/6iMLR/J0BvzaYL4296Zed7iaFWlfMAJ5FXt4MGi95rPwP7B6wobEr Ndv+CC+Zi47zcLoTr5+T4DZWCtEV+mrJKkH3tYfUc6MGwqbZkEQlrF1XWbV9krNti0Jx fvkYBr9N4IS6cZk7q1Q98Nj+4UPsqAmRkpGJ1Eswz+oGI6RTtxTAKReHeqMFIMX2pQeI M0oQ==
X-Gm-Message-State: AIVw112W17NE1sYQe3QDYqoDeU0jg8nYmhWkIozx1zSr5/DJRZtyRtKX yzzT9xoxl8PnMT/bRpY=
X-Received: by 10.80.193.2 with SMTP id l2mr5657039edf.177.1501937821153; Sat, 05 Aug 2017 05:57:01 -0700 (PDT)
Received: from [192.168.2.6] ([77.172.247.152]) by smtp.gmail.com with ESMTPSA id e9sm4992062eda.52.2017.08.05.05.56.59 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 05 Aug 2017 05:56:59 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
Subject: Re: Request to register "identifier" relation type
From: Herbert Van de Sompel <hvdsomp@gmail.com>
X-Mailer: iPad Mail (14E304)
In-Reply-To: <DEE2ABBF-1146-4E17-875F-3F5EFFB540FB@pobox.com>
Date: Sat, 5 Aug 2017 14:56:59 +0200
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: <D933EB1A-CB2F-4BD3-9747-C03A0D78CACC@gmail.com>
References: <CAOywMHeHcwP5h4vzbTY+q00AEYn85F0E+LKqnx0aWpK1kcA1AA@mail.gmail.com> <CAK5Vdzz8=+6pfEDA2gGvtYU8kNx4pPKmsme71szP-JrvhpoTdw@mail.gmail.com> <54CA5E71-F469-4FD9-AF29-21985B454CAE@gmail.com> <DEE2ABBF-1146-4E17-875F-3F5EFFB540FB@pobox.com>
To: Ed Summers <ehs@pobox.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/link-relations/mu0rX8X6qPYUiY0GGxagtTTVNMc>
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:59:00 -0000

On Aug 5, 2017, at 13:59, Ed Summers <ehs@pobox.com>; wrote:
> 
>> 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*.
> 

Good point. Here's my take on it:
- canonical: preferred for content indexing 
- identifier: preferred for referencing

> 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.
> 

Publishers indeed use canonical to point to pages on their own site.  This rel type is intended eg for reference manager applications: use the target URI not the context URI in a reference. Our research (referenced in the I-D) has shown that landing page URIs (instead of HTTP DOI) are frequently used for referencing. 

> 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.
> 

Our I-D acknowledges that the semantics of "identifier" are similar to "bookmark". But "bookmark" is explicitly not allowed in <link> (and hence Link). One has to assume there were/are reasons for that choice because other rel types declared in HTML can be used in <link>.

> 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.
> 

Indeed. Then again, this relation type indicates that the target URI should be used as identifier. We have done several presentations at conferences, workshops, etc over the past months in which "identifier" was floated. It's been on the Signposting web site (which has an associated mailing list) for almost a year, see http://signposting.org/identifier/ . We have not received negative reactions to the choice of term.  Some implementations are meanwhile already out there. 

Cheers

Herbert



> //Ed