EpubCCEPUBCheck OPF-085: invalid UUID identifier
Updated:
EPUBCheck OPF-085 is a warning message: “"dc:identifier" value "…" is marked as a UUID, but is an invalid UUID.” A dc:identifier says it is a UUID (urn:uuid:) but the value is not a valid UUID. Reading apps and stores may use the identifier to recognise the book, so a malformed one is reported.
The official message
"dc:identifier" value "%1$s" is marked as a UUID, but is an invalid UUID.
- Default severity
- Warning. The EPUB is still valid, but something is likely to cause problems in some reading apps. EPUBCheck exits with 0 unless you pass --failonwarnings.
- EPUBCheck version
- 5.4.0
%1$s, %2$s… are filled in with the file, value or element EPUBCheck found.
Typical causes
- A shortened or mistyped value after urn:uuid:.
- An invented value, such as urn:uuid:my-book-1.
- An ISBN or another identifier written after the urn:uuid: prefix.
How to fix it
- Read the value EPUBCheck quotes.
- Replace it with a real UUID in the form 8-4-4-4-12 hexadecimal digits (any UUID generator makes one).
- If the identifier is not a UUID, drop the urn:uuid: prefix and write it in its own form, such as urn:isbn:…
When it's not this
If the package's unique-identifier does not match any dc:identifier, that is OPF-030.
Terms used here
Other OPF messages
OPF-086Property "…" is deprecated. Consider using … instead.OPF-086bepub:type value "…" is deprecated. Consider using … instead.OPF-086cthe "…" reserved prefix is deprecated.OPF-088Unrecognized epub:type value "…".OPF-089The "alternate" link rel keyword cannot be paired with other keywords.OPF-090It is encouraged to use MIME media type "…" instead of "…".
Sources
Message text and severity from EPUBCheck 5.4.0 (W3C, BSD-3-Clause). Explanation by EpubCC.