Publishing WG Telco, 2019-04-29: Lightweight packaging issues

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

The whole meeting was devoted to open issues around the lightweight packaging issue. Most of the issues were easy and handled right away: media type (application/lpf+zip), name of the PEP and the manifest file itself (index.html, resp. publication.json), or no signing components in the package.

The only issue discussion that turned out to be more complicated was related to the way URI/URL’s are described and referred to in the document. There was a general agreement that, instead of including a longer paragraph, a deep link to the relevant section in the WPUB document should be used. However, the issue raised some other potential issues that will need resolution:

  • What is the ‘origin’ to be used for relative URL-s, scripts, etc, for a packaged document?
  • The current manifest canonicalization algorithm turns all relative URL-s into absolute ones. This may be fine on the Web, but it is not clear for a package, in view of the previous issue.

These questions will be raised as separate issues to be discussed (maybe at the F2F next week).

Publishing WG Telco, 2019-04-15: Duration; integrity hash

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

Final issues on the duration values

While finalizing the move of duration values to the core WP documents, some specific technical questions came up. These were taken care of in the call:

  1. What is the value of a resource level “duration” value? The resolution is that it should be a number (meaning the number of seconds), and the term’s name is, for now, length.
  2. What is the value of the top-level “duration” value? The resolution is to stick to the schema.org definitions of duration.
  3. Is the duration term required? The resolution is that it is optional for a WP in general, and recommended for an audiobook.

The resolutions will be incorporated in the editors’ draft in the coming days.

File hash, a.k.a. “integrity”

It was agreed to add an optional integrity when defining a resource. The value, and its semantics, is defined by the Subresource Integrity Recommendation.

Publishing WG Telco, 2019-04-08: Supplemental Materials in Audiobooks, usage of duration

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

Should there be a TOC if supplemental materials are provided in an audio book?

This question has been raised in Issue #408. Having a clear place to find those materials is important (e.g., for accessibility purposes if they provide a textual transcript). The discussion was around whether supplemental materials (e.g., PDF booklet) in an audiobook should be added in a TOC or whether it should be part of the usual resources’ structure labeled with a particular rel value. There is no formal resolution yet.

Should duration be part of the general WPUB draft

The current audiobook uses the duration term from schema.org. It does it for an individual (audio) resource as well as for the whole book. However, there is nothing in that definition which would be audio specific; the same attribute could also be used for, e.g., video resource as well.

Another issue was what exactly the role is of the book level information. Current readers usually calculate that value; they do not trust the author/publisher data for accuracy. On the other hand, that value may have an important role in user-friendliness; e.g., it would inform the “reader” (i.e., listener) how long that book is.

Two outcomes of the discussion:

  • It was decided to move the duration term into the general WPUB draft as one of the generic terms for linked resources
  • An alternative for book level data could be the schema.org timeRequired term, that seems to be looser in its requirement, and may very well be enough for the purpose of that information. To be discussed further.
Posted in Activity News, Meeting reports | Comments Off on Publishing WG Telco, 2019-04-08: Supplemental Materials in Audiobooks, usage of duration

Publishing WG Telco, 2019-04-01: New WPUB document structure, audiobook profile draft

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

New WPUB Document Structure

The WPUB Draft has been restructured to fulfill a series of past resolutions.

  • Part I: the manifest, its structure, its lifecyle (canonicalization, final checkings, etc). The terms are now more precisely categorized, and the canonicalization is defined in terms of these categories, instead of referring to the terms explicitly. Profiles may add their own terms and provide extra processing steps if needed.
  • Part II: the Web Publication Profile, describing the PEP, the way to obtain a manifest, the possible extraction of some metadata items (i.e., title) from a the PEP.
  • Part III: how to define new profiles

The group has agreed to re-publish the official W3C Draft with this version.

Audiobook profile draft

The first Editor’s draft for the Audiobook profile is now available, and the group discussed some immediate issues (to be incorporated into the ED). The main features discussed:

  • The reading order of an audiobook MUST incude audio files only. Other possible resources (cover page, etc) may be present in the resources’ list, but not in the reading order.
  • There is now a duration property. There were discussions around this property:
    • There is a duration term for the book as a whole as well as for individual resources
    • There was no consensus whether the duration for the book as a whole should be REQUIRED or not; a new issue will be raised for that
    • The term may be useful for other media objects like video, ie, the property should probably be defined in general (ie, part of the WPUB document). However, usage of the terms for the book as a whole may be restricted to audio (or video) books.

Discussions will continue with the evolution of this new draft.

Posted in Activity News, Meeting reports | Comments Off on Publishing WG Telco, 2019-04-01: New WPUB document structure, audiobook profile draft

Publishing WG Telco, 2019-03-25: Some use cases

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

Implementations and UCR

Some entries from the UCR document were discussed to see what type of implementation issues it would raise and how it would work with the current draft:

  • UC #86: is about page numbers and how they are displayed/located. There were several implementation scenarii, but the current pagelist feature in the draft is present and the author/implementation can use it. It becomes more complicated if that list is not present, and implementations may decide to search the content for special triggers (e.g., role=doc-pagebreak). An issue should be opened to describe the behavior in more details.
  • UC #93: adjusting the contrasts if, for example, one is reading in the sun. This is closely related to CSS issues and behavior, and touches upon operating system features as well; it should not be a solely WPUB discussion (although WPUB brings this requirement to the fore)
  • UC #40: reading order. This is a basic feature on current reading system, but not necessarily on the Web. A best practice and minimal behavior should be described for this.

Misc.

The group also closed a longstanding issue (Issue #376) which got to an agreement on the issue list itself.

There were also some F2F planning.

Publishing WG Telco, 2019-03-18: Issue management

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

A large number of leftover old issues were discussed and closed (see minutes for details). The only issue that had a longer discussion was:

Only allow embedded manifests

(Is issue 327.)

It was recognized that various security issues are better taken care of with embedded manifests, which is also the favored choice by schema.org processors. On the other hand, the audiobook discussion has already led to the resolution whereby they would need a separate manifest for audiobooks. The decision is to make the requirement of an embedded manifest a SHOULD (rather than a MUST).

Publishing WG Telco, 2019-03-11: Lightweight packaging format

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

TOC Format

The current draft is now at https://w3c.github.io/pwpub/spec/ocf-lite.html. The document is very short: refers to the ISO ZIP standard as for the packaging file format itself. The only WPUB-specific specification is the requirement on having an entry page in HTML and/or a manifest file (defined by wpub) at the root directory. The rest of the organization depends on the author and is described in the manifest.

There are some editorial issues; the only major non-editorial issue was whether this document should be proposed as a W3C Recommendation track document or not. There are pro-s and con-s, but the current decision of the Working Group is to publish this document, eventually, as a W3C WG Note, making it clear that the ideal solution would be to use some sort of a Web Packaging specification, but this is not available today.

Misc

The telco discussed horizontal reviewing issues as well as the agenda of the upcoming F2F meeting in Cambridge, MA.

Publishing WG Telco, 2019-03-04: Audio Issues, Implementation Discussion

Publishing WG Telco, 2019-03-04: Audio Issues, Implementation Discussion

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

Audio Issues

Wendy led the group through resolving several open audiobooks issues about using the type attribute in audiobooks, handling of external (non-audio) resources in audiobooks, and allowed formats for audiobooks.

Implementations

Franco and Josh led a discussion about real world implementations and expected behaviors of use cases and requirements. We began with a discussion of syncing location across platforms. After much discussion, most people agreed that the approach should revolve around the URL or fragment not adjusting the content in any way.

Posted in Activity News | Comments Off on Publishing WG Telco, 2019-03-04: Audio Issues, Implementation Discussion

Publishing WG Telco, 2019-02-25: TOC format in JSON, Auxiliary Media in Audiobooks

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

TOC Format

This is issue #376 on whether the current HTML based format for a TOC is the only format, or whether it is possible to simply add a TOC into the manifest directly. This discussion continued the one started on the 11th of February, but did not really conclude yet. It turned out that there may be some misunderstandings on what the current manifest format can or cannot already have, and what restrictions in an HTML based TOC it defines. It was agreed to set up a separate call to clarify these details to be able to make a more informed decision.

Auxiliary Media in Audiobooks

This is issue #322: what should happen with non-audio materials (e.g., attached PDF files) in terms of an audiobook content: can it or can’it be part of the reading order? The discussion started but not concluded yet…

Posted in Activity News, Meeting reports | Comments Off on Publishing WG Telco, 2019-02-25: TOC format in JSON, Auxiliary Media in Audiobooks

Publishing WG Telco-Asia, 2019-02-07

See minutes online for a more detailed discussion.

The Publishing WG convened a meeting at a (somewhat) Asia-friendly time. Asia is a big continent with many time zones. Most of the attendees from Asia are from Japan. The general sense from Japanese publishers is that EPUB 3 is stable, and there is a strong desire to keep it that way. There is not much interest from Japan in audio books or the manifest work happening in the Publishing WG. However, there is real interest in future work on merging the Web and Publishing platforms.

The consensus from members of the group joining from Asia was that toggling the meeting time is more difficult than joining late at night. The larger concern is the language barrier. One of the things that made this meeting successful was that we had several participants who were comfortable in multiple languages. One proposal was to arrange a pre-meeting in Japanese and choose a representative who is comfortable in Japanese and English to represent the Japanese-speaking members. The chairs are working on arranging this for future meetings. Other work will occur in the parallel BD Manga CG and may ultimately come to the Working Group.

Posted in Activity News | Comments Off on Publishing WG Telco-Asia, 2019-02-07