EPUB Annotations 1.0: What Publishers Should Prepare for Now
W3C published a new EPUB Annotations 1.0 Working Draft on September 24, 2026. Publishers should preserve stable structure, identifiers, privacy expectations, and edition relationships before annotations become portable across reading systems.
Direct answer: W3C published a new Working Draft of EPUB Annotations 1.0 on September 24, 2026. The draft is not yet a final standard, but it points toward portable notes, highlights, and bookmarks that can be exported, imported, or embedded in EPUB publications. Publishers should prepare by protecting structural stability, edition identity, privacy, and change control.
Reader annotations have traditionally been trapped inside individual apps and devices. EPUB Annotations 1.0 is an attempt to define an interchange format so notes, highlights, and bookmarks can move more consistently between systems.
The September 24 Working Draft profiles the W3C Web Annotation Data Model and defines an EPUB-specific structure for annotations and annotation sets. It describes JSON-LD serialization, targets within EPUB resources, detached annotation packages, and annotations embedded in the EPUB package.
Because it is a Working Draft, publishers should not rebuild production systems around it yet. They should, however, examine what portable annotations require from the publication itself.
Annotations depend on stable targets
An annotation is useful only if the reading system can find the passage, image, or location it refers to. The draft defines target structures that point into EPUB resources. That makes structural stability important.
If a publisher silently replaces chapter files, radically restructures HTML, or changes an edition without documenting it, old annotations may no longer point to the intended content. The publishing lesson is familiar: corrections are allowed, but significant revisions need edition control.
The Publishing Standards rule: maintain an Annotation Readiness Record
| Field | Required record |
|---|---|
| Publication identifier | ISBN or other edition identifier tied to the exact EPUB. |
| EPUB version | Version of the publication format and production profile. |
| Content revision | Internal revision number or release date for the file. |
| Structural change log | Chapters, files, anchors, or content ranges changed after release. |
| Annotation policy | Whether annotations may be embedded, exported, imported, or supported by the publisher's own system. |
| Privacy owner | Person responsible for reviewing annotation data practices. |
| Compatibility notes | Known reading-system or edition limitations. |
Detached and embedded annotations create different responsibilities
The draft allows annotation sets to be shared as detached files or embedded within an EPUB package. Detached annotations can travel separately from the book. Embedded annotations remain with the package.
For publishers, that raises practical questions. Are embedded annotations editorial content, instructor notes, study material, or user data? Who created them? Are they part of the edition? Can they be redistributed? Does the publisher have permission to include them?
Those questions should be answered before annotations become another untracked asset inside the production ZIP.
Edition identity matters more when reader data can travel
The draft's AnnotationSet can include information about the associated publication such as title, publisher, creator, and publication date. That information helps connect detached annotations to the correct book, but publishers should not rely on title text alone.
A professional workflow should preserve edition-specific identifiers and clearly distinguish revised editions. A set of notes created against the first edition may not map cleanly to a substantially revised second edition even if the title remains unchanged.
Privacy cannot be an afterthought
Annotations can reveal what a reader highlighted, where they stopped, what they wrote, and potentially what they were studying or researching. The current Working Draft includes a privacy section that remains incomplete, which is itself a reason for caution.
Publishers building annotation services should minimize collection, document retention, avoid unnecessary profiling, and separate user identity from annotation content where possible. A technical ability to export reader notes is not automatic permission to analyze them.
Security matters when annotations come from outside the book
The draft warns implementers to treat imported annotation data as potentially malicious. It restricts textual bodies to plain text and discusses defensive processing against injection and malicious resource loading.
Publishers that later accept annotation files should validate them rather than treating them as trusted content. Any workflow that imports external annotation packages belongs inside the same security review used for other externally supplied files.
Do not market draft support as final conformance
EPUB Annotations 1.0 is still a Working Draft. A publisher or software vendor may experiment with it, but should not present draft implementation as conformance to a final W3C Recommendation that does not yet exist.
The correct language is specific: tested against the September 24, 2026 Working Draft, or compatible with a named experimental implementation. Versioned claims protect both the publisher and the reader when the specification changes.
What publishers can do now
- Keep EPUB structure stable within an edition.
- Assign clear edition identifiers and revision records.
- Document significant post-publication changes.
- Review privacy implications before collecting annotation data.
- Treat imported annotation files as untrusted input.
- Track W3C changes before making conformance claims.
FAQ
Is EPUB Annotations 1.0 a final standard?
No. The September 24, 2026 document is a W3C Working Draft and may change before becoming a Recommendation.
What kinds of reader activity does it address?
The draft covers annotations such as notes, highlights, and bookmarks and defines a model for grouping and sharing them.
Can annotations be separate from the EPUB?
Yes. The draft describes detached annotation packages as well as annotation data embedded within an EPUB package.
The standard begins with stable books
Portable annotations will work best when publishers maintain stable, well-identified editions and disciplined revision histories. The technology is new, but the operating principle is old: readers can rely on digital features only when the underlying publication is controlled.