talk to Tess on the audio explainer issues (Wendy Reid) (see details)

Cc: @wareid

ask PinG if someone can walk us through the questionnaire because we are without an expert (Ralph Swick) (see details)

Cc: @swickr

(This issue was originally raised by @BigBlueHat on the wpub issue list, but moved to this repository as part of the more "general" issues.)

AMP is the progenitor of the Web Packaging spec we are being encouraged to consider for PWP. It is also the source of several other specifications that may be of value to our work, and (consequently) we should be involved in these discussions if possible:
https://github.com/ampproject/amphtml/blob/master/contributing/web-standards-related-to-amp.md#overview-of-web-standards-and-features-related-to-amp

Our White Paper talks about the need for an interface and API for a collection of web resources. So really all we have to do is figure this out:

interface Collection: Node {
[SameObject] readonly attribute DOMImplementation implementation;
  readonly attribute USVString URL;
  readonly attribute USVString collectionURI;
  readonly attribute USVString origin;
  readonly attribute DOMString compatMode;
  readonly attribute DOMString characterSet;
  …a few missing details :)
};

Perhaps something like this, more than anything else we are discussing, is what it means for publications to be a first-class citizen of the web.

write a proposal to the WPUB on changes (Jeremy Morse) (see details)

Cc: @undefined

(This issue was originally raised by @BigBlueHat on the wpub issue list, but moved to this repository as part of the more "general" issues.)

Review has been requested of the TAG for an API to allow Web apps to provide custom UX in place of the browsers text finding functionality: w3ctag/design-reviews#236

It proposes some events as well as an "extended" set of possible features including loading additional custom results and/or pre-loading not-yet-displayed data so that it can be found by the browsers text finding code.

This differs from the FindText API Working Group Note which focuses on enabling JavaScript-based text searching and Range finding.

WICG discussion that turned into this proposal:
https://discourse.wicg.io/t/allowing-browser-find-in-page-to-find-non-dom-text/1205

The "Requirements and design options for synchronized multimedia" doc discusses synchronizing multimedia with "content" but then mentions "book" in the next phrase. Later on it describes a requirement as pertaining to "WP/PWP".

I believe that the ideal scope of synchronized multimedia with overall content (aka text) rendering is all OWP content not just publications. I.e. if we are going to redo and generalize EPUB 3 Media Overlays it should be applicable to web pages not just web publications. So to me the scope of this doc should be clarified as being that general. Of course we could always back off and do something for WP/PWP only but that would seem at odds with the goal of expanding the overall OWP for Publishing. But at a minimum it seems this document should clearly state its scope as that is unclear at the moment.

set up discussions with Karen, Jeremy, Maurice on an archival CG (Ivan Herman) (see details)

Cc: @iherman

talk to david about WebIDL (Ivan Herman) (see details)

Cc: @iherman

create PR for bespoke previews in WP (Garth Conboy) (see details)

Cc: @GarthConboy

add note to audiobooks (Wendy Reid) (see details)

Cc: @wareid

edit explainer about WAM (Tzviya Siegman) (see details)

Cc: @TzviyaSiegman

talk to david about Localizable strings (Ivan Herman) (see details)

Cc: @iherman

better explain the packaging options we rejected and why (Wendy Reid) (see details)

Cc: @wareid

Readers need to easily navigate through web publications. Such navigation could be complicated by the reality that many web publications consist of many resources, likely in a defined order. EPUB reading systems typically provide UI to access a (required) table of contents from anywhere in the publication, and further provide simple UI gestures to move from document to document.

Should web publications require a comprehensive navigation document? How can we make it easy for users to get from document to document?

edit Audiobooks standard to remove line about the origin. (Wendy Reid) (see details)

Cc: @wareid

complete the drafts of explainers and specs (Marisa DeMeglio) (see details)

Cc: @marisademeglio

There is certain level of confusion in the terminology. IRI (ie, rfc3987[1]) is the most general form that encompasses all internationalization requests in IETF land. It is also the reference used in the newest RDF or the Annotation recommendations.

On the other hand, at least for locators, the Web community has always ignored, in practice, the term IRI or URI, and they use URL. See for example, the note to the URL-s in the HTML5 standard[2] that does refer to[1] noting

For the purpose of producing strict URLs one may wish to consider [RFC3986] [RFC3987].

There is also an active work at WhatWG defining URL processing[3] which aims to be interoperable with IRI-s, ie, with RFC3987.

My proposal would be to use URL-s in our terminology, to be also in line with the Web Developer world, but making it clear in the general recommendations that we mean here RFC3987 compatible entities, the same way as HTML5 & Co. do.

1. https://tools.ietf.org/html/rfc3987
2. https://www.w3.org/TR/html5/references.html#refsURL
3. https://url.spec.whatwg.org

report back to dbaron that link rel value issue is resolved (Matt Garrish) (see details)

Cc: @mattgarrish

find a home for the Synchronized Narration spec (Wendy Reid) (see details)

Cc: @wareid

file issue about publication addresses being required to end in / (Benjamin Young) (see details)

Cc: @BigBlueHat

What information is required for an abstract manifest? [edited to add items from comments]

1. An identifier for the web publication, which should be a URL
2. Some way of saying that this URL represents a web publication.
3. Some way of identifying the constituent resources of the web publication.
4. Some way of providing a preferred order of (some of) the constituent resources in case there is more than one
5. Some way of being able to add more complex metadata to a publication. (Not clear to my mind whether we would define a minimally required set of metadata, but the slot should be there.)
6. Locating table of contents or other navigation structure

What else? I think we should distinguish required information from "nice to have" information.

The web is a free-for-all, with design and interaction nearly entirely controlled by the site author.

But ebook reading systems typically control how the user interacts with a publication, and sometimes even change the appearance of publication content.

Will web publications need to provide their own user interface? Will they need to be designed to support both paradigms? What might this mean?

obtain manifest integrating with CORS explanation - there is an open issue for resolution as well (Dave Cramer) (see details)

Cc: @dauwhe

produce a gap analysis of the ucr items vs. existing web concepts (Franco Alvarado) (see details)

Cc: @francofaa

A Web Publication (WP) is a collection of one or more constituent resources, organized together in a uniquely identifiable grouping that may be presented using standard Open Web Platform technologies. A Web Publication is not just a collection of links— the act of publishing involves obtaining resources and organizing them into a publication, which must be “manifested” (in the FRBR sense) by having the resources available on a Web server. Thus the publisher provides an origin for the WP, and a URL that can uniquely identify that manifestation.

Perhaps the simplest possible answer to these questions is just a URL: https://www.example.com/MobyDick/ would both identify the publication and mean that everything whose URL starts with this is part of the publication.

So I guess that I’m looking for reasons to make this more complicated :)

create a separate LPF repository (Ivan Herman) (see details)

Cc: @iherman

review "AudioObject" schema and explore what feedback is required for schema (Wendy Reid) (see details)

Cc: @wareid

add an informational text on using dcterms (Matt Garrish) (see details)

Cc: @mattgarrish

set up a repository for pub-manifest (Ivan Herman) (see details)

Cc: @iherman