That shows a non-existent dc-metadata tag and the x-metadata tag as a child of the metadata tag.
Where on earth is the dc-metadata needed? Certainly not in opf for epub2 or epub3. It is handled by namespaces.
Edit: I just checked and dc-metadata and x-metadata were both deprecated even BEFORE The epub 2.0 spec.
Quote:
From the epub 2.0 spec ...
The required metadata element is used to provide information about the publication as a whole. It may contain Dublin Core metadata elements directly or within a (now deprecated) dc-metadata sub-element. Supplemental metadata can also be specified directly or within a (now deprecated) x-metadata sub-element.
Reading Systems must allow the specification of the deprecated dc-metadata and x-metadata elements.
Newly created OPS 2.0 packages should not create dc-metadata or x-metadata elements.
If the dc-metadata element is used, all dc elements must go in dc-metadata and all other metadata elements, if any, must go into x-metadata. If the dc-metadata element is not used, all metadata elements must go directly in the metadata element.
|
My question is the docs show x-metadata tags after the metadata tag closes, not a child. Where exactly does the kindle software look for it. Can it not be nested?
Where is the package version attribute?