La version électronique de cette Norme internationale peut être téléchargée à partir du site Web du Groupe de travail ISO/CEI sur les technologies de l'information (ITTF)
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 an EPUB 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 document.
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 necessary 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 revisions.
Expression of simple, contiguous ranges should be supported.
An extensible mechanism to accommodate future reference recovery heuristics should be provided.
In the case of both Standard EPUB CFIs and Intra-Publication EPUB CFI, this specification conforms with the guidelines expressed by W3C in Section 6. Best Practices for Fragid Structures [FragIDBestPractices].
In other words, both standard CFI URIs (e.g., "book.epub#epubcfi(?)", referred media type "application/epub+zip") and intra-publication CFI URIs (e.g., "package.opf#epubcfi(?)", referred media type "application/oebps-package+xml") make use of a fragment identifier syntax that does not overlap with existing schemes in the context of the aforementioned media types' suffix registrations (i.e., "-xml" and "zip").
"Kama ilivyoelezwa katika toleo la kielektroniki la kanuni hii ya kimataifa, ""Kuhusu teknolojia ya habari"" (ITTF) ni kanuni ya kipekee ya utambulisho wa sehemu ya EPUB (epubcfi) ambayo inatoa njia ya kawaida ya kutaja maudhui ya hiari ndani ya chapisho la EPUB kwa kutumia vitambulisho vya sehemu." Web imethibitisha kuwa dhana ya hyperlinking ni nguvu sana, lakini EPUB Publications wamekuwa kukataliwa mengi ya faida kwamba hyperlinking hufanya inawezekana kwa sababu ya ukosefu wa mpango standardized kuunganisha ndani yao. Ingawa mipango ya wamiliki wamekuwa maendeleo na kutekelezwa kwa ajili ya binafsi Reading Systems, bila kawaida-kueleweka syntax kumekuwa hakuna njia ya kufikia msalaba-platform interoperability. Hata hivyo, utendaji ambao unaweza kuona faida kubwa kutoka kuvunja kizuizi hiki ni tofauti: kutoka kwa usimamizi wa eneo la kusoma hadi kiambatisho cha maelezo kwa urambazaji, uwezo wa kuelekeza kwenye Uchapishaji wowote unafungua mwelekeo mpya kabisa ambao haujawahi kupatikana kwa watengenezaji na waandishi. "Hii maalum inajaribu kurekebisha hali hii kwa kufafanua kumbukumbu arbitrary muundo kwamba inaweza kipekee kutambua eneo lolote, au mbalimbali rahisi ya maeneo, katika EPUB ""chapisho.""" Mawazo yafuatayo yameathiri sana muundo na wigo wa mpango huu: Utaratibu unaotumiwa kurejelea maudhui unapaswa kuwa na ushirikiano: marejeo ya nafasi ya kusoma iliyoundwa na Mfumo mmoja wa Kusoma inapaswa kutumika na mwingine. Hati marejeo ya maudhui EPUB inapaswa kuwezeshwa kwa njia ile ile ambayo viungo vya sasa hyperlinks kuwezesha marejeo katika mtandao wote. Kila eneo katika faili ya EPUB inapaswa kuwa na uwezo wa kutambuliwa bila haja ya kurekebisha hati. Vipimo vyote vya sehemu ambavyo vinarejelea eneo moja la mantiki vinapaswa kuwa sawa wakati wa kulinganishwa. Operesheni za kulinganisha, ikiwa ni pamoja na vipimo kwa ajili ya kuchagua na kulinganisha, inapaswa kuwa na uwezo wa kutekelezwa bila kupata faili zilizotajwa. Manipulations rahisi inapaswa kuwa inawezekana bila upatikanaji wa faili ya awali (kwa mfano, kutokana na rejea kina katika faili, inapaswa kuwa inawezekana kuzalisha rejea kwa mwanzo wa faili). Utambuzi wa kitambulisho inapaswa kuwa busara busara (kwa mfano, usindikaji wa sura ya kwanza si muhimu kwa kutatua kitambulisho kipande kwamba inaonyesha sura ya mwisho). Marejeo yanapaswa kuwa na uwezo wa kurejesha maeneo yao ya lengo kupitia tofauti za parser na marekebisho ya hati. Maonyesho ya rahisi, contiguous mbalimbali inapaswa kuungwa mkono. utaratibu extensible ili kukidhi baadaye rejea upatikanaji heuristics inapaswa kutolewa. Kwa mfano, kwa ajili ya CIFs za EPUB za kawaida na CIFs za EPUB za ndani ya kuchapishwa, vipimo hivi vinakubaliana na miongozo iliyoonyeshwa na W3C katika Sehemu ya 6. Mazoea bora kwa miundo dhaifu [FragIDBestPractices]. Kwa maneno mengine, wote kawaida CFI URI (kwa mfano, "kitabu.epub#epubcfi(? "Kama ilivyoelezwa hapo juu, ""kitu"" ni aina ya media inayojulikana kama ""application"" au ""epub"" na ""cpc"" ni aina ya media inayojulikana kama ""application"" au ""epub"" au ""epub"" au ""epub"" au ""epub"" au ""epub"" au ""epub"" au ""epub"" au ""epub"" au ""epub"" au ""epub"" au ""epub"" au ""epub"" au ""epub"" au ""epub"" au ""epub"" au ""epub""." "Kama ilivyoelezwa hapo juu, ""kitu"" cha ""kitu"" cha ""kitu"" cha ""kitu"" cha ""kitu"" cha ""kitu"" cha ""kitu"" cha ""kitu"" cha ""kitu"" cha ""kitu"" cha ""kitu"" cha ""kitu"" cha ""kitu"" cha ""kitu"" cha ""kitu"" cha ""kitu"" cha ""kitu"" cha ""kitu"" cha ""kitu"" cha ""kitu"" cha ""kitu"" cha ""kitu"" cha ""kitu"" cha ""kitu"" cha ""kitu"" cha ""kitu"" cha ""kitu"" cha ""kitu"" cha ""kitu"" cha ""kitu"" cha ""kitu"" cha ""kitu"" cha ""kitu"" cha ""kitu"" cha ""kitu"" cha ""kitu.""""