address is canonical identifier?

[mattgarrish]

This sentence could probably use some clarifying:

The address of the primary entry page is also the canonical identifier (i.e., it serves as its unique identifier) for the audiobook when present.

Address here points to the address property in pub manifest, but wouldn't this be the actual location of the entry page (address is supposed to be other addresses that get you to the publication/pep).

But what if a canonical identifier is already specified in the manifest, is this sentence saying it has to be overridden when the pep has an address (when doesn't it?), or only added if an identifier isn't present? In either case, this would require extending the processing algorithm to add this info from the html since we don't harvest the url.

I'm not sure exactly how best to reformulate this, but a quick idea might be to say:

When a canonical identifier is not specified in the manifest, user agents MUST use the address of the primary entry page (i.e., the address serves as the unique identifier for the audiobook).

I just wonder about harvesting when the audiobook isn't web hosted (i.e., in a package). You get an absolute url resolved from some potentially inconsistent base.

[mattgarrish]

FYI: w3c/wpub#453

[mattgarrish]

Hm, what I wrote above isn't valid. I should have looked at the definition, but it contradicts the manifest statement that user agents not try to construct canonical identifiers when they aren't present. The address of the PEP could just be a local file:// address, or could change depending on where that gets processed.

I think with this statement we can just drop it entirely.

[mattgarrish]

I don't see this anymore, so closing.