![]() This requirement is dropped in EPUB 3.1 (although it would still be possible to use EPUBCFI for annotations and bookmarks). Until EPUB 3.0.1, Reading Systems were required to support EPUBCFI for hyperlinking within and between documents. The EPUB Canonical Fragment Identifier ( EPUBCFI) “defines a standardized method for referencing arbitrary content within an EPUB Publication”. These observations are all based on the 30 January 2016 draft of the changes document. This blog post is an attempt to identify the main implications of the current draft for libraries and archives: to what degree would the proposed changes affect (long-term) accessibility? Since the current draft is particularly notable for its aggressive removal of various existing EPUB features, I will focus on these. The authors of the draft also mention that they expect it “will provoke strong reactions both for and against”, and that changes that raise “strong negative reactions” from the community “will be reviewed for future drafts”. The EPUB working group has opted for a radical change approach to the addition and deletion of features in the 3.1 revision to move the standard aggressively forward with the overarching goals of alignment with the Open Web Platform and simplification of the core specifications.Īs Gary McGath pointed out earlier, this is a pretty bold statement for what is essentially a minor version. A note at the top states (emphasis added by me): The proposed changes relative to EPUB 3.0.1 are summarised in this document. IDPC has set up a community review, which allows interested parties to comment on the draft. ![]() This is meant to be the successor of the current 3.0.1 version. About a month ago the International Digital Publishing Forum, the standards body behind the EPUB format, published anĮditor’s Draft of EPUB 3.1.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |