Re: addressable identifier?

Just chiming in to let you know I'm still reading.  Don't disagree enough
with much of the proceeding to proffer a substantive reply.  :-)

Best,
   Garth


On Thu, Jul 27, 2017 at 11:11 AM, Romain <rdeltour@gmail.com> wrote:

>
> On 27 Jul 2017, at 19:44, laurent.lemeur@edrlab.org wrote:
>
> Imho the identifier of a WP is not required to be addressable. Any global
> identification scheme could be use in fact (e.g doi). But Urls are easy to
> mint and avoid centralization issues; they are the de facto identification
> scheme on the web. As the manifest is the only resource specific to a WP,
> its address is a logical choice.
>
>
> OK, makes sense.
> But then, the URL to a manifest may change, or two different URLs can
> point to the same manifest:
>
> https://resilientwebdesign.com/manifest.json
> https://resilientwebdesign.com/books/../manifest.json
>
> (dumb case, but you see the point).
>
> All I'm saying is I understand the manifest _can_ be used as an identifier
> in a given context (e.g. a UA), but there's nothing to say about that in
> the spec, right? There's a URL, people can use that as an identifier or not.
>
> As far as I can tell, there's no such concept in web sites and apps, and I
> don't see that publications need anything other than a loosely specified
> "dc:identifier" property in metadata. (Maybe I'm wrong, I'm just not
> convinced yet :-)
>
> Pls refrain using other arguments like "it's not what users want to share"
> : users will share the "start" URL which will be different.
>
>
> +1.
>
>
> Cordialement, Laurent
>
> Le 27 juil. 2017 à 18:36, Hadrien Gardeur <hadrien.gardeur@feedbooks.com>
> a écrit :
>
> 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.
>
>
>