New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Publishing WG] CR Transition request for publication manifest and audiobooks #190
Comments
Transition approved. I encourage the following editorial fixes prior to publication: The citation in [bibo] times out; please check that URI and consider whether there is a better URI. In Manifest 4.2.5 there is a reference to a "note in the HTML5 spec", however the current HTML5 spec does not include that note. Fine to simply drop the sentence. In Manifest 4.8.1.1 there is a reference to WCAG 1.0 that looks it could just as well |
Thanks @swickr! I've opened a pull request with the changes you've noted (I think that entire note can go). I've also updated the specref database with the new bibo domain. |
one more nit: Update those links. Found 16 references in this category
|
To be clear: we would like those links to be directly to the WHAT HTML LS (per WHATWG/W3C MOU) |
Sure, no problem. I'll get those fixed asap. |
Published on 2019-12-05. Closing. |
Document title, URLs, estimated publication date
Abstract
Status
Link to the group's decision to request transition
Resolution at[1], based on a CfC by email, started at [2]
Changes
Major changes to Publication Manifest since FPWD include:
language
anddirection
keywords in the JSON-LD context for expressing the global language and direction of manifest text (also for local overrides) -inLanguage
now only identifies the language(s) of the content;alternate
property to provide alternative media representations of resources;conformsTo
property to identify the profile a manifest conforms to;A list of all changes to Publication Manifest since FPWD is available at: https://github.com/w3c/pub-manifest/commits/master
Requirements Satisfied
The Publication Manifest specification partially meets the original objective of defining Web Publications. Work on Web Publications was suspended due to a lack of interest at this time from publishers, plus significant differences of opinion in terms of how they are expected to function on the web and in browsers. The group generally agreed on the manifest format for expressing information about publications, however, so driving Publication Manifest forward puts a stake in the ground for returning to Web Publications while also enabling the creation of other formats for which there is more interest (audiobooks). Defining a common manifest format also aids in future interoperability, which was another goal of Web Publications. The Publication Manifest format is also largely translatable to and from the EPUB 3 Package Document, so this provides a potential future pathway for the next iteration of EPUB.
See also the use case review for how the Publication Manifest specification matches up to the original requirements for Web Publications.
Dependencies Met
JSON-LD 1.1 (on the
@direction
keyword usage). The latest JSON-LD 1.1 document (to be in CR soon) introduces this feature and the Publication Manifest depends on it.Wide Review
Practically all the work happened on GitHub, see the separate section on issues below. This included comments from outside of the Working Group.
Horizontal Reviews
Issues Addressed
Publication Manifest:
Note: the Publication Manifest document was originally developed within a larger framework called "Web Publications". That line of work has been paused, but the manifest part of the document was re-used as the starting basis for Publication Manifest. The issues for Web Publications listed below are only for completeness, because they (partially) contributed to the development of the Publication Manifest (the relevant open issues were transferred to the pub-manifest repository):
Audiobooks:
Formal Objections
None.
Implementation
Testing Strategy for Publication Manifest and Audiobooks
Interested implementers for Publication Manifest and Audiobooks will be provided with a test suite using the Web Platform tests model. These specifications will be testing all MUST and SHOULD statements, and for Audiobooks, there will be additional manual User Agent Behavior tests. The Working Group will provide details for implementers on how to run the tests and assistance with any issues encountered. Implementers should log issues against the Github projects for visibility.
As Publication Manifest is largely a vocabulary of terms, a comparison of the vocabulary to the structures and metadata of the EPUB 3 Package Document will also be carried out. This comparison is intended to show that there is already real-world precedent in publishing for the information included in the manifest, and a pathway for translating EPUB content (and vice versa).
Additionally, implementations will need to show that they are capable of ingesting and transforming a manifest into an internal representation using the algorithm defined in the Publication Manifest document. These transforms ensure that any authoring conveniences used in the authored manifest are normalized and sanitized, and result in a predictable data structure.
Exit Criteria
Publication Manifest and Audiobooks must have at least 2 passing tests for each feature in the specifications. For the Audiobooks User Agent Behaviors tests, all implementations should meet all of the behavior requirements that are applicable to them.
Potential Implementations
The following institutions have already expressed their interest in implementing an audiobook reader: Colibrio, EDRLab, Rakuten/Kobo, Google, Blackstone Publishing. Two out of those (Colibrio and EDRLab) already have a running prototype.
There are also two experimental implementations (one in javascript and the other in typescript) that have been used to "test" the specification.
Patent Disclosures
See https://www.w3.org/2004/01/pp-impl/100074/status
Cc @GarthConboy @mattgarrish @TzviyaSiegman @wareid
The text was updated successfully, but these errors were encountered: