Re: Request for feedback on EPUB/A

Thanks Wendy,

while reading through the text, I have made a list of the restrictions to myself, but this may be useful for everyone. Compared to EPUB 3.3 these are the restrictions defined for EPUB/A:


- Use only core media types (section 3.2)
- Use of exempt resources is not encouraged (section 6.2)
- Use only UTF-8 (section 6.3)
- Publication resources shall be located in the EPUB container (section 7.3)
- EPUB container shall not be encrypted (section 7.4)
- Publications must not include multiple renditions until such time as the note becomes a stable W3C Recommendation or is replaced by another technology. (section 7.6)
- Publications require the following additional metadata (beyond those that are required by EPUB 3.3) (section 8.3):
 - Information about any compression methods or any reading systems for which the file is optimized
 - Creator
 - Creation Date or Start Date/End Date
 - Publisher/producer/distributor
 - A standard unique manifestation/work identifier (e.g. ISBN or ISSN)
 - An item or instance identifier, if available (e.g. a DOI)
 - Metadata format and its versions
 - Schema identifiers for metadata records (e.g. Dublin Core or PREMIS)
 - Administrative metadata (e.g. nature and formats of embedded media)
 - Technical metadata (e.g. file formats and versions, digital signatures and checksums)
 - Rights metadata 
 - Structural metadata
- Although the EPUB 3 specification requires a media type be specified for each resource, it does not require the correct media type be specified. For EPUB/A publications, each resource shall have the correct media type. (section 8.4)
- As EPUB/A publications do not allow remote hosting of resources, the `remote-resources` value shall not be used with this attribute (section 8.4)
- For collections (in the package document) only use collection types that are recognized as standard (none at this moment) (section 8.6)
- Scripts in EPUB content documents (section 9.3):
 - shall not include scripts that retrieve resources or information from outside the EPUB container (e.g., using JavaScript APIs such as XmlHttpRequest and Fetch).
 - shall not include HTML forms that submit data to external servers.
- Do not use features that are considered as deprecated in EPUB 3. (section 11)


I hope this helps.

Alicia, I hope I got them all.

Ivan


> On 27 Jun 2024, at 20:06, Reid, Wendy <wendy.reid@rakuten.com> wrote:
> 
> Hi all, 
>  
> I have been asked on behalf of the ISO/NISO group working on EPUB/A to share this call for feedback on the proposed draft of an ISO standard for the preservation of digital books.
>  
> https://clockss.org/new-draft-international-standard-for-the-preservation-of-ebooks-published-in-the-epub-format/
>  
> The draft of the document can be found at the link above, or here: https://clockss.org/wp-content/uploads/2024/06/EPUB-3-Archiving-for-Preservation.pdf
>  
> EPUB/A (EPUB archive) is based on EPUB 3, and does make reference to the latest W3C version of the standard (EPUB 3.3). The goal of EPUB/a is to provide a content conformance and packaging standard for long-term preservation of ebook content. Several of us from the W3C Publishing activity have participated in the development of this draft.
>  
> If you have any feedback on the document, please reach out to Alicia Wise from CLOCKSS, who has been leading this effort. She is CC’d on this message.
>  
> Thanks,
> Wendy
>  
> Wendy Reid
> Accessibility and Publishing Standards Lead, Rakuten Kobo
> Co-chair, W3C Advisory Board, Publishing Maintenance Working Group, Positive Work Environment Community Group


----
Ivan Herman, W3C 
Home: http://www.w3.org/People/Ivan/
mobile: +33 6 52 46 00 43