Re: definition of Web Publication

Looking at the full definition, I have a few comments to make.

[...] which must be “manifested” (in the FRBR [frbr] sense) by having the
> resources available on a Web server


This feels a little confusing, I don't think we should reference FRBR in
such definitions...

Thus the publisher provides an origin for the WP, and a URL that can
> uniquely identify that manifestation.


What's the definition of origin in that context? If by "origin" we mean a
domain or a scope, then I don't think this should be in our definition at
all.

A Web Publication must provide a default ordering of the primary
> constituent resources, although that order may be changed by user
> interaction or scripting.
>

Do we really need to say anything more than "must provide a default
ordering of the primary constituent resources"?

 The act of packaging must be reversible; one must be able to recover the
> original structure and organization.


Structure and organization are confusing terms in this context. IMO, each
resource in a PWP should have a reference to its original location (URI)
but nothing more.

I also strongly disagree that packaging should be "reversible". We're not
designing a package to transport files between servers or a backup system.

We consider the unpackaged state of a web publication to be canonical.


Not sure what that means.


> Packaging provides a convenient way to to transmit and store a
> publication, but user agents are not required to display, annotate, or
> reference such content in packaged form.


I don't think this belongs in a definition.

A Web Publication may be portable and be hosted at some other origin. But
> the PWP must preserve information about its original origin and identity,
> so that references to a portable copy can be reconciled with the original
> publication.
>

Not sure exactly what this means either. Do we expect the PWP to link to
the original WP (whatever we link to)? Are we talking about the resources
of the PWP? Still confused by the use and presence of origin.

A Web Publication must be available and functional while the user is
> offline. A user should, as much as possible, have a seamless experience of
> interacting with a Web Publication regardless of their network connection.
> We make no distinction between online and offline when defining Web
> Publications


Feels like a use case rather than part of a definition. This will be
entirely tied to the UA.


> [...] The metadata and manifest will also incorporate information about
> the sequence and presentation of the content.


"will also"? Do we expect the sequence to be expressed in metadata really?
Do we expect to have it elsewhere than a manifest?

Hadrien