W3C home > Mailing lists > Public > public-publ-wg@w3.org > July 2017

Re: addressable identifier?

From: Romain <rdeltour@gmail.com>
Date: Thu, 27 Jul 2017 19:57:48 +0200
Cc: W3C Publishing Working Group <public-publ-wg@w3.org>
Message-Id: <A5BFC057-3798-4C14-81CB-12044ADD3E35@gmail.com>
To: Hadrien Gardeur <hadrien.gardeur@feedbooks.com>
> IMO the use case for an identifier is simple: we want to uniquely identify a WP.

But does it need to be addressable?

> For instance if I add multiple WP in a UA, this is the identifier that the UA will rely on internally to associate various attributes and settings to a WP.

For this use case, any identifier would work, not necessarily a dereferenceable one. Depending on the use case details, the UA could even generate one on the fly.

Romain.


> On 27 Jul 2017, at 18:36, Hadrien Gardeur <hadrien.gardeur@feedbooks.com> wrote:
> 
> I think you were initially in the "others" Romain, but not by the end of the conversation where you clearly understood the difference that I made between "start" and "self" links.
> 
> IMO the use case for an identifier is simple: we want to uniquely identify a WP. For instance if I add multiple WP in a UA, this is the identifier that the UA will rely on internally to associate various attributes and settings to a WP.
> 
> The URI of a primary resource can't uniquely identify a WP, since it can be present in multiple WP. That's not the case of a manifest, which is unique to a WP.
Received on Thursday, 27 July 2017 17:58:14 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:52:14 UTC