Packages vs WP Address

[llemeurfr]

WP address are defined in https://w3c.github.io/wpub/#address.
Most packages created by publishers will have no address until they are "exposed" on the web.

The difficulty is that the WP address is required in a WP Manifest, the WP address references the PEP, but a, index.html (i.e. PEP file) is not mandatory in a Package.

A pragmatic solution is to require that the address value MUST be "index.html" inside the manifest even if the corresponding file is not present in the Package. The URL will be updated to the final WP address by a processor which transforms the Package to a Web Publication.

[llemeurfr]

Better proposal I think: specify a relative path to the PEP (usually "url":"index.html") if the PEP is present in the Package, and a null WP address ("url":"") if the PEP is not present in the Package. The URL will be updated to the final WP address by a processor which transforms the Package to a Web Publication.

[iherman]

I think what this shows that there may be a need to describe, explicitly, the steps taken by a processor when the content of a package is turned into a Web Publication (see also the discussions about w3c/wpub#456).

[llemeurfr]

The discussion on w3c/wpub#456 lead to a definition of a Publication Manifest where no Address is defined (the Address is defined at the level of the Web Publication, as "its value is conceptually finalized when things are put on the Web". I like this, as it solve the current issue.