OPS URI Question
| Project: | EPUB Maintenance |
| Component: | Open Publication Structure (OPS) |
| Category: | task |
| Priority: | normal |
| Assigned: | GConboy |
| Status: | dismissed |
Jump to:
From epub-community:
Posted by: "Bill Janssen" janssen@parc.com JalopyUser
Thu Feb 11, 2010 5:17 am (PST)
Yesterday I put together an EPUB publisher extension for UpLib
(http://uplib.parc.com). I was playing around with it today, and found
that epubcheck doesn't like it when I include a URI of the form
"data:image/png;base64,...". Various readers seem to support it, but
the EPUB spec seems unclear on the subject:
``The required URI attribute, src, is used to reference the image
resource, which must be listed in the Manifest.''
So, should I just include the data: URI twice, once in the content, and
once in the OPF file? Or was the intent of the OPS spec to prohibit use
of the data: URI scheme altogether?
Description
Issue Id:
41
Resolution:
To be "dismissed." Not really an OPS/OPF issue. URI's of type "data:" may be supported by Reading Systems. The fact that epubcheck reports an error should be logged there as a "bug report" or "feature request" -- it seems as though epubcheck should let this slide as the data is inline, and thus shouldn't need to be in the manifest.
Comments
#1
Resolution field filled in. To be "dismissed."
#2