Re: addressable identifier?

>
> 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
> <https://resilientwebdesign.com/manifest.json>
>

That's why using a canonical location is also useful and makes sense for
the WP identifier.


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

It's entirely up to us to decide that.



> 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 :-)
>

We're trying to figure out how we're different from plain websites. We
agreed that the difference is mostly the manifest, having a canonical
location for the manifest and using it as an identifier could further prove
that point.

Also, rel="canonical" is widely used on the Web today.