This specification defines a packaging format for combining the resources of a Web Publication [[?wpub]] into a single portable file.

At this point, this is just a skeleton for the specification-to-be. At the moment, the focus of the Working Group is on the Web Publications document.

Due to the lack of practical business cases for Web Publications, and the consequent lack of commitment to implement the technology, the Publishing Working Group has chosen to discontinue the work on Web Publications, archive the work in the form of a Working Group Note, and focus on other areas of interest. As a consequence, the present document has also been discontinued and is being published as a Working Group Note. The public record of the group's discussions is available in group's archive of meeting minutes.

The separate Lightweight Packaging Format (LPF) Working Group Note fulfills a similar role, albeit with different requirements and goals.


The editors request community comments on especially on Sections 2-4 via the group’s primary mailing list. The archives are publicly visible, and anyone can post a mail.

A key decision on this specification will be the choice of packaging mechanism (section 5). The working group has decided to evaluate Web Packaging (see the Web Packaging Format Explainer) and to wait for its maturation before proceeding. This has been a major cause of the publication of this specification as a First Public Working Draft in such skeletal form.

General Conformance

A document is a Packaged Web Publication if it:

Additionally, a document that is a Packaged Web Publication MAY contain:

Conformance Classes

This specification defines two conformance classes: one for Self-Packaged Web Publications and one for Standard-Packaged Web Publications.

A document is a Self-Packaged Web Publication if it meets the following criteria:

A document is a Standard-Packaged Web Publications if it meets the following criteria:


Packaged Web Publication

A Web Publication [[?wpub]] that has been packaged into a single information resource, enabling it to be transported and stored independent of any specific address or protocol. A Packaged Web Publication does not have to originate on the Web (i.e., have a specific URL that is accessible via HTTP); the only requirement is that it conform to Web Publications. Similarly, it is possible to unpack a Packaged Web Publication to create a Web Publication, but there are practical limitations to doing so (e.g., re-publishing cross-domain resources will require that a client be able to access all domains used).

Self-Packaged Web Publication

A Packaged Web Publication [PWPUB] that defines its own package format.

Standard-Packaged Web Publication

A Packaged Web Publication [PWPUB] that is packaged using the packaging format defined in .

Descriptive Properties

A Web Publication is anticipated to have some Descriptive Properties, or WP-specific metadata. What PWP-specific metadata should a PWP contain, if any?


PWP will require the selection of some sort of packaging format in order to be a Packaged Web Publication.

Some options currently under consideration include, but are not limited to:

All of these have pros and cons. For example, Web Packaging is not finalized, the CBOR specification precludes inclusion of a general compression scheme (although one could add one on top of CBOR), and SQLite is not a standard of a recognized body.

What packaging format or style should a PWP use?


The editors realize that the concept of profiles of implementation is probably contentious. Much discussion is anticipated before this section is likely to be brought to conclusion.


Placeholder for security issues.


Placeholder for privacy issues.