This standard was last reviewed and confirmed in 2018. Therefore this version remains current.
This specification, EPUB Canonical Fragment Identifier (epubcfi), defines a standardized method for
referencing arbitrary content within an EPUB® Publication through the use of fragment identifiers.
The Web has proven that the concept of hyperlinking is tremendously powerful, but EPUB Publications
have been denied much of the benefit that hyperlinking makes possible because of the lack of a
standardized scheme to link into them. Although proprietary schemes have been developed and
implemented for individual Reading Systems, without a commonly-understood syntax there has been no
way to achieve cross-platform interoperability. The functionality that can see significant benefit from
breaking down this barrier, however, is varied: from reading location maintenance to annotation
attachment to navigation, the ability to point into any Publication opens a whole new dimension not
previously available to developers and Authors.
This specification attempts to rectify this situation by defining an arbitrary structural reference that can
uniquely identify any location, or simple range of locations, in a Publication: the EPUB CFI. The following
considerations have strongly influenced the design and scope of this scheme:
· The mechanism used to reference content should be interoperable: references to a reading
position created by one Reading System should be usable by another.
· Document references to EPUB content should be enabled in the same way that existing
hyperlinks enable references throughout the Web.
· Each location in an EPUB file should be able to be identified without the need to modify the
· All fragment identifiers that reference the same logical location should be equal when compared.
· Comparison operations, including tests for sorting and comparison, should be able to be
performed without accessing the referenced files.
· Simple manipulations should be possible without access to the original files (e.g., given a
reference deep in a file, it should be possible to generate a reference to the start of the file).
· Identifier resolution should be reasonably efficient (e.g., processing of the first chapter is not
required to resolve a fragment identifier that points to the last chapter).
· References should be able to recover their target locations through parser variations and document
· Expression of simple, contiguous ranges should be supported.
· An extensible mechanism to accommodate future reference recovery heuristics should be
Status : PublishedPublication date : 2014-11
Edition : 1Number of pages : 15
Technical Committee:Document description and processing languages
Buy this standard