Publishing WG Telco, 2019-12-02: Testing

See minutes online for a more detailed record of the discussions.

CR publication

The CR, as well as the LPF Note, is planned to be published on Thursday, 2nd of December. Everything has been approved and set up


  • There is an initial systematic (though not necessarily complete) test suite for the API (i.e., the transformation of the manifest into an internal representation, with a number of checks on the fly), including a report page
  • It was agreed to create a separate testing repository to collect all these, as well as other possible test suites, in one place
  • Other test suites considered are: TOC extraction tests (although that is not a required mechanism), JSON Schema-based tests, behavioral tests.

The next step is to populate these test suites, to have implementers self-report on those.

Meeting schedule for the rest of the year

The last meeting this year will be on the 16th of December.

Publishing WG Telco, 2019-11-18: CR approval, testing

See minutes online for a more detailed record of the discussions.

CR Approval

There was a Call for Consensus by email on two issues:

  • FPWD publication of the Lightweight Packaging Format (LPF)
  • Request to advance Audiobooks and the Publication Manifest to CR

Both proposals were accepted and the meeting recorded the positive resolution. The official request for CR should go out to the Director this week.

The rest of the meeting was going into the weeds of how testing will be done, what tests to use and how, how to report, etc.

Publishing WG Telco, 2019-11-11: Road to CR

See minutes online for a more detailed record of the discussions.

Road to CR

The main topic was the last steps to do for going to CR. There is a temporary request that has to be completed, primarily in terms of testing plans. To main issues forward:

  • WG members should read the document (and the aforementioned page) to prepare for a CR transition request vote in a week
  • The LPF document is almost ready to go, there will be an email request to agree on publishing that document in conjunction with the the CR publications

Publishing WG Telco, 2019-11-04: Final issues closing

See minutes online for a more detailed record of the discussions.

Open issues

The group handled some open issues:

  • Usage of fragment IDs and repeated URLs: the group agreed that
    1. Fragment identifiers can be used without further ado in the manifest (it was, formerly, disallowed)
    2. While it is recommended not to repeat URL-s for resources in readingOrder or resources, it is not explicitly disallowed any more
  • Choosing alternatives: at the moment the document is silent on how the User Agent should choose among several alternatives for a linked resource, if available. It was agreed that this should remain the case for now, future releases, as well as specific documents (including profiles) may add their own rules (e.g., for synchronized media). Future versions of the spec may have a more general mechanism
  • Resolving URL prefixes in the manifest: it is possible, in JSON-LD, to add prefixes to the context, and uses that in the form of a CURIE for terms. This is one of the extension mechanism in the publication manifest. The question was whether the simple handling of the manifest (i.e., without a JSON-LD processor) should resolve such prefixes and, as an additional issue, whether the context should include a number of predefined prefixes. The group agreed not to do any of these.
  • Cover description: is it always recommended?: this discussion touched upon the role of the description value, with its relationship to an alternate description of an image in HTML. It was agreed that this issue is way too complex for this group as it touches upon the interpretation of WCAG and possibly adding a technique to it. It is not a rule that can be added normatively in the document.

With these handled, it looks like the document is getting to a closure, and will be ready for CR. The group also discussed actions needed towards a Candidate Recommendation transition.

Publishing WG Telco, 2019-10-21: Closing some open issues

See minutes online for a more detailed record of the discussions.

Open issues

The group handled some open issues:

  • single localizable string: the group agreed that description and accessibilitySummary should allow for several string values (allowing, e.g., multilingual descriptions)
  • Presence of id and type should be a SHOULD?: the group agreed that the presence of these terms are RECOMMENDED (although not required
  • Bounds of an audiobook: the concept of “bounds” are present in the audiobook spec (normatively) and in the publication manifest spec (non-normatively). Also, although the concept of bounds is useful, it is not clear how to use the concept, there is no specific user behavior attached to it. The decision was to remove it from the audiobooks spec, with the right refeference changes.

The group also discussed actions needed towards a Candidate Recommendation transition.

Publishing WG Telco, 2019-10-14: PR handling, horizontal reviews

See minutes online for a more detailed record of the discussions.

PR handling

  • There is a new PR for the audiobooks which added some minimal audiobook reading system behavior. The agreement was to merge this PR and possibly discuss it further as an editor’s draft
  • There is also a new PR for the manifest which moves the WebIDL formalism into an informative annex, and reformulates the processing steps using the upcoming Infra standard. The PR is fairly large and it was agreed to merge this, too, with possibly further discussions.

Draconian handling of conformsTo values

The current editor’s draft requires the existence of a conformsTo and it is considered to be a fatal error not to have it in the manifest with a specific profile reference. This was raised as an issue (Issue #101). The rough consensus was that we should not have such a draconian approach, and the editors will come up with a somewhat “milder” proposal (maybe along the lines of a larger proposal in the issue discussion).

Horizontal reviews

  • i18n review is closed
  • a11y review is almost done, there was only one pending question on synchronized media (whether it can be put on recommendation track).
  • PING review answer is pending, although there are no open issues

Publishing WG Telco, 2019-10-07: Base direction, metadata usage, webidl

See minutes online for a more detailed record of the discussions.

Base direction

With the introduction of @direction into JSON-LD 1.1 it has become possible to properly add this i18n feature into the publication manifest. This was done via PR manifest#92. With some minor changes (related on how to communicate the dependency on JSON-LD 1.1) the WG accepted to merge this. With this, the i18n horizontal review has also been closed.


There was a discussion (see issue manifest#57) on what exactly the role and usage of metadata is, and how much of that should be visible in the publication manifest. The discussion was around how extensible the current structure is, how easy it is to either incorporate or refer to metadata vocabularies defined elsewhere. No change on the document is required but the WG should keep an eye on the way metadata registries may be handled in the new W3C process coming out in 2020.

Usage of WebIDL

(See also issue manifest#98.) There have been discussion elsewhere on whether WebIDL is the right approach to describe data structures for a spec like manifest. The Web App Manifest spec is moving away from this towards the usage of the “infra standard”, that unifies the language used for processing steps and related data structures (although that does not replace the overall view of the structure that WebIDL provides). Infra will be adopted in the document to describe the processing steps; whether to use WebIDL or not remains open for now.

Publishing WG Telco, 2019-09-30: TPAC reports, CR plans

See minutes online for a more detailed record of the discussions.

There was a short report on the TPAC F2F meeting (for a detailed account, see the minuges for the first day and the ones for the second day). At TPAC there were a number of discussions with other groups (DPUB-ARIA, PING, also expert on MathML); there were discussions on testing a CR progressions and plans. On separate discussions there were also advances to solve the base direction issue for texts (a PR is to be expected soon).

Most of the meeting was on planning the details and procedures on the CR testing phases.

Publishing WG Telco, 2019-09-09: Settling Issues, pre-TPAC publication

See minutes online for a more detailed record of the discussions.

The meeting concentrated on a number of issues that could be either closed or that should be discussed on the F2F meeting next week. In particular, issues 40, 22, 13, and 16 were all closed without further actions, whereas issues 12 (“What is null base URL”), 9 (“Should canonicalization include absolutization”), and 51 (“Values for readingProgression”) were postponed to the F2F meeting.

There was also a short update on the latest editorial draft changes since the last official output. The changes were mainly on the manifest document: removal of the concept for canonical manifests (with the emphasis of a “canonical” representation of the data structures encoded in WebIDL) and the strict separation of the language set for the publication (i.e., the content) and the literal texts in the manifest proper. Depening on external circumstances the new versions may be published before TPAC.

Publishing WG Telco, 2019-08-26: Horizontal reviews, issue handling

See minutes online for a more detailed record of the discussions.

Horizontal reviews

The group discussed the horizontal reviews; the I18N review is essentially done, the self-review test for security/privacy will be done by next week, and a meeting with the APA WG will take place at TPAC to finalize the accessibility review.


Some minor issues have been handled for audiobooks: some existing terms will be called out for publishers (adult content, abridged…) These will be the subject of an upcoming PR.

The were also some minor LPF issues; the document is essentially ready to go.

On internationalization, a somewhat more complex issue was to separate the language used for the textual content of the manifest from the (main) language of the publication itself. The solution, put forward in an issue comment will be adopted in an upcoming Pull Request.

No meeting next week

Next week Monday is holiday both in the USA and in Canada, so there will be no meeting.