The OCF Abstract Container defines a file system model for the contents of the OCF ZIP Container, as defined in OCF AbstractĪ software application that processes OCF ZIP Containers according to the requirements of this specification. Non-Codec refers to content types that benefit from compression due to the nature of their internal data structure, such as file formats based on character strings (for example, HTML, CSS, etc.). The name of any type of file within an OCF Abstract Container, whether a directory or a file within a directory. The Rendition listed in the first rootfile element in the container.xml file. In addition, the following terminology is defined for use in this specification: CodecĬodec refers to content that has intrinsic binary format qualities, such as video and audio media types which are already designed for optimum compression, or which provide optimized streaming capabilities. Only the first instance of a term in a section is linked to its definition. A complete list of these terms and definitions is provided in. Terms with meanings specific to EPUB 3.1 are capitalized in this document (e.g., "Author", "Reading System"). Refer to for more information on the differences between this specification and its predecessor. It is meant to be read and understood in concert with the other specifications that make up EPUB 3.1. This specification is one of a family of specifications that compose, an interchange and delivery format for digital publications based on XML and Web Standards. OCF also defines a standard method for obfuscating embedded resources, such as fonts, for those EPUB Publications that require this functionality. The rules for ZIP containers build upon the ZIP technologies used by.
#Epub metadata editor read only error archive#
This specification defines the rules for structuring the file collection in the abstract (the " abstract container") and the rules for the representation of this abstract container within a ZIP archive (the " ZIP container"). This specification, EPUB Open Container Format (OCF) 3.1, defines a file format and processing model for encapsulating the set of related resources that comprise an EPUB® Publication into a single-file container, the EPUB Container. Appendix C. The application/epub+zip Media Type
3.5.2.6 Digital Signatures File (signatures.xml).3.5.2.5 Rights Management File (rights.xml).3.5.2.2 Encryption File (encryption.xml).3.3 Relative IRIs for Referencing Other Components.Please consult the complete list of acknowledged W3C Member Submissions. Please consult the requirements associated with Member Submissions of section 3.3 of the W3C Patent Policy. Publication of acknowledged Member Submissions at the W3C site is one of the benefits of W3C Membership. A W3C Team Comment has been published in conjunction with this Member Submission. This document is not the product of a chartered W3C group, but is published as potential input to the W3C Process. Publication of this document by W3C indicates no endorsement of its content by W3C, nor that W3C has, is, or will be allocating any resources to the issues addressed by it. īy publishing this document, W3C acknowledges that the Submitting Members have made a formal Submission request to W3C for discussion. A list of current W3C publications can be found in the W3C technical reports index at. Other documents may supersede this document.
This section describes the status of this document at the time of its publication. This specification, EPUB Open Container Format (OCF) 3.1, defines a file format and processing model for encapsulating a set of related resources into a single-file container. Intellectual Rights Notice and Legal Disclaimers for additional EPUB Open Container Format (OCF) 3.1 W3C Member Submission 25 January 2017 This version: Latest published version: Editors: James Pritchett, Learning Ally Markus Gylling, International Digital Publishing Forum (IDPF)
0 kommentar(er)
