Skip to content

RDF metada <rdf:RDF> in SVG #173

@rdeltour

Description

@rdeltour

From j...@magusdigital.com on April 29, 2012 14:26:31

PROBLEM: I have been using SVG inserts to scale elements in ePUB documents. The files validate cleanly in every detail, except that ePUBcheck flags up <rdf:RDF> as invalid. Looking at the W3C website I don't think this is correct. It is valid. The files work perfectly, so perhaps this is a bug in ePUBcheck? This was with version 3.0b4.

METHOD: What steps will reproduce the problem?

  1. include an SVG image in the flow of the document, correctly inside a <div> tag.
  2. Make sure there are no errors at all in the ePUB, then make sure that the plain SVG contains <rdf:RDF> metadata, which typically it will.
  3. run the file through ePUBcheck version 3.0b4.

RESULT: ePUBcheck correctly identifies that the file is in fact ePUB 2.01. Everything passes validation, except for each SVG file the <rdf:RDF> element is said to be invalid.

EXPECTED: As far as I can see it isn't invalid, so I would expect a complete 'No errors' result.

PLATFORM: This was with version 3.0b4. I stopped using version 1.2 because that said there was a font type specification error in the .opf file that also didn't seem to be correct and because I am beginging to develop for ePUB 3. Version 3.0b4 does not report the font error, so presumably that has been fixed.

I am using Windows 7 64 bit

ADDITIONAL INFO: My objective is to create beautiful eBooks as eBooks, not as fallout from print, so I am probably pushing the boundaries of what may be done with ePUB 2.01; however, everything I do is validated by other checks and the files work well in all the major e-readers on the market, in desktop testing and on the iPad.

I haven't tried version 3.0b5 yet. This doesn't seem to be amont the fixes listed though.

Original issue: http://code.google.com/p/epubcheck/issues/detail?id=173

Metadata

Metadata

Assignees

No one assigned

    Labels

    status: completedWork completed, can be closedtype: false-positiveThis issue is about valid content being incorrectly rejected

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions