-
Notifications
You must be signed in to change notification settings - Fork 20
[Publishing WG] CR Transition for pub manifest and audiobooks
- Publication Manifest
- Editor's draft: https://w3c.github.io/pub-manifest/
- Expected publication date: @@@@
- Audiobooks
- Editor's draft: https://w3c.github.io/audiobooks/
- Expected publication date: @@@@
- Publication Manifest: https://w3c.github.io/pub-manifest/#abstract
- Audiobooks: https://w3c.github.io/audiobooks/#abstract
- Publication Manifest: https://w3c.github.io/pub-manifest/#sotd
- Audiobooks: https://w3c.github.io/audiobooks/#sotd
[TODO: eg minutes, CfC in GitHub, email]
[TODO: focus on substantive changes]
[TODO: references to requirements]
JSON-LD 1.1 (on the @direction keyword usage)
Practically all the work happened on GitHub, see the separate section on issues below. This included comments from outside of the Working Group.
- TAG Review
- @@@@@
- I18N Horizontal review
- A11y Horizontal review
-
Publication Manifest:
- Open issues minus editorial or postponed: https://tinyurl.com/y38cxuhv
- Same as above, but including closed issues: https://tinyurl.com/y378byy6
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):
- Open issues minus editorial or postponed: https://tinyurl.com/yygspsdm
- Same as above, but including closed issues: https://tinyurl.com/y2ohwaqm
-
Audiobooks:
- Open issues minus editorial, deferred, or transferred to best practices: https://tinyurl.com/y67bemer
- Same as above, but including closed issues: https://tinyurl.com/yxfp7yz3
None.
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 Behaviour 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.
Publication Manifest and Audiobooks must have at least 2 passing tests for each feature in the specifications. For the Audiobooks User Agent Behaviours tests, all implementations should meet all of the behaviour requirements that are applicable to them.