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 3C9661323D4
 for <link-relations@ietfa.amsl.com>; Wed,  9 Aug 2017 09:18:02 -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 nqRhKr8uGHdg for <link-relations@ietfa.amsl.com>;
 Wed,  9 Aug 2017 09:18:00 -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 AC6CA13240E
 for <link-relations@ietf.org>; Wed,  9 Aug 2017 09:18:00 -0700 (PDT)
Received: from sasl.smtp.pobox.com (unknown [127.0.0.1])
 by pb-smtp2.pobox.com (Postfix) with ESMTP id EF1B7ACD52;
 Wed,  9 Aug 2017 12:17:56 -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=
 SPqB28WEEa8aJK0AGDu6vbQvkYY=; b=V4U2jGw3qWl7Aa2EDkyv/HnkRwdyMMJs
 whQvIWDKezfBbLmQtrBnrbsHwqbs4KlBaFEMeVNm9YO4mNpWrjv438sC4cihG1S6
 j27TcFHOm3OgiDi+2cFTiINj8JVWzxVn5mw+VkQezN3D4IsZQsLI4vsyszMn4FvA
 akJyVv3E2Rc=
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=GHyAKqzycaUk+YEhvndOBdCsZ61Qgn0K/XNfBecP5DKIaFmEF58m1xs8
 507FrMboUq3N56B5oCW5EUF/2bd+BUoPEVbWTiGMiu9jEPgpIvdof5bHDvdVNNyl
 +yU3hCJGIeqEzemLUk2vk9qDwpzEAqq8mzK8EsDWFQ3l18OuIXs=
Received: from pb-smtp2.nyi.icgroup.com (unknown [127.0.0.1])
 by pb-smtp2.pobox.com (Postfix) with ESMTP id E74FEACD50;
 Wed,  9 Aug 2017 12:17:56 -0400 (EDT)
Received: from wireless-10-104-179-255.umd.edu (unknown [129.2.180.182])
 (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 597DAACD4D;
 Wed,  9 Aug 2017 12:17:56 -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: <CAOywMHf5JqQoFXLOi5cuD+HWTxMKu-JcjL_Zp0NWM7wqmBqSbQ@mail.gmail.com>
Date: Wed, 9 Aug 2017 12:17:55 -0400
Cc: link-relations <link-relations@ietf.org>,
 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>
Content-Transfer-Encoding: quoted-printable
Message-Id: <32B88620-D166-4078-8721-8EFCB818E1FE@pobox.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>
 <D933EB1A-CB2F-4BD3-9747-C03A0D78CACC@gmail.com>
 <CAOywMHf5JqQoFXLOi5cuD+HWTxMKu-JcjL_Zp0NWM7wqmBqSbQ@mail.gmail.com>
To: Herbert Van de Sompel <hvdsomp@gmail.com>
X-Mailer: Apple Mail (2.3273)
X-Pobox-Relay-ID: 4DB91E42-7D1E-11E7-A261-9D2B0D78B957-07615111!pb-smtp2.pobox.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/link-relations/c2A1Nc8N7kNRadWLpz2o2qxWWd8>
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: Wed, 09 Aug 2017 16:18:02 -0000

Hi Herbert,

> On Aug 9, 2017, at 10:35 AM, Herbert Van de Sompel <hvdsomp@gmail.com> =
wrote:
>=20
> * On August 5, Ed Summers posted a question regarding applying =
"bookmark" to <link> to the WHATWG list, see =
https://lists.w3.org/Archives/Public/public-whatwg-archive/2017Aug/0001.ht=
ml. There are no responses to this post, so far.

There have been a few responses if you look at the list of emails for =
August:

    https://lists.w3.org/Archives/Public/public-whatwg-archive/2017Aug/

> * On August 9, Ed Summer posted a similar question to WHATWG/HTML =
GitHub, see https://github.com/whatwg/html/issues/2899. There is a =
reaction from @annevk who (1) speculates that the reason "bookmark" is =
not to be used with <link> might be in order not to overlap with =
"canonical" (2) suggests the use of "canonical" :-)=20

Yes, canonical seems to be the relation that most people are reaching =
for initially. I did myself on reading your I-D. The fact that seasoned =
hands like Kevin Marks and Anne van Kesteren are as well says something.

> * Michael Nelson has further explored "bookmark" and has confirmed =
that there effectively is a reason for not allowing "bookmark" in =
<link>. It is related to its target use case: surfacing a link for =
content contained in a *part* of a page. Hence, Michael concludes that =
making "bookmark" usable with <link> will most likely not happen. =
@annevk's GitHub response does not seem to contradict that. Michael =
based his findings on studying =
http://tantek.com/log/2002/11.html#L20021128t1352 and =
https://html.spec.whatwg.org/multipage/links.html#link-type-bookmark. He =
may write another blog post about this, but, for now, here's how he =
explained on Twitter https://twitter.com/i/moments/895081563653902336

Yes, it looks like that's probably where things will sit. As Anne =
indicated it's likely that rel=3Dbookmark cannot be used with <link> =
because of perceived confusion it would cause with canonical. The =
semantics of parts of pages vs the page itself don't seem terribly =
significant to me from an implementation perspective. Unfortunately =
'identifier' will also probably cause some confusion as well. As systems =
that rely on 'identifier' get developed that will be something for them =
to deal with.

Thanks for considering all the questions and tracking the conversation =
over on the WHATWG list. It speaks to the spirit of what you all are =
trying to achieve with this I-D.

//Ed=

