bell notificationshomepageloginedit profileclubsdmBox

10.02% popularity   0 Reactions

couple questions about metadata in epub3:

is the namespaced opf attribute (opf:file-as="", for example) deprecated?
if so, does anyone know why?
given that it this format is deprecated, what is the correct format for including attributes in the opf namespace?

Oreilly's epub3 best practices declares the following as the correct way to use the property attribute:

<meta refines="#creator" property="file-as">Murakami, Haruki</meta>

but, the namespace is not declared as they suggest in the following paragraph:

You can also use property values, which must include the proper prefix, from any of the reserved vocabularies or any vocabulary for which you’ve declared the prefix:
<meta property="dcterms:dateCopyrighted">2012</meta>

wouldn't this mean that the following should be the correct implementation?:

<metadata
xmlns:opf='http://www.idpf.org/2007/opf'
... >

<meta refines="#creator" property="opf:file-as">Murakami, Haruki</meta>

is there a comprehensive list of values allowed for the property attribute (role, meta-auth, etc)?

thanks in advance!

Free books android app tbrJar TBR JAR Read Free books online gutenberg

Load Full (1)

Login to follow story

More posts by @Nanci

Login to post a comment!

1 Comments

Sorted by latest first Latest Oldest Best

 

@Kevin

10% popularity   0 Reactions

The difference between the suggestions from the source you pointed at is how you define the target element. You should be aware that a lot of the metadata options available in an EPUB 3 can have multiple occurrences.
E.g. 1
<metadata ...>
...
<dc:creator id="author">John Doe</dc:creator>
<dc:creator id="author1">Jane Doe</dc:creator>
<meta property="dccreator:file-as">Something</meta>
...
</metadata>

The above example is problematic because the meta element is trying to work on the dc:creator element, except there are two of them. Which one does it go for?
E.g 1 - Solution
<metadata ...>
...
<dc:creator id="author">John Doe</dc:creator>
<dc:creator id="author1">Jane Doe</dc:creator>
<meta refines="#author" property="file-as">Doe, John</meta>
<meta refines="#author1" property="file-as">Doe, Jane</meta>
...
</metadata>

You should use the refines attribute and the simplified version of the property attribute (e.g. 'file-as') when there is more than one occurrence of the target metadata element. The refines attribute allows you to specify by the id attribute of the target element (which according to specs must be unique).
If you do not specify a refines attribute, and the property attribute doesn't refer specifically to a reserved list of EPUB 3 spec metadata (Dublin Core), then the meta element is deemed to be working on the publication as a whole.
Other Examples
// We only have a single dc:title in our metadata so we can use the extended property attribute in the meta element
<metadata ...>
...
<dc:title id="title">My Book</dc:title>
<meta property="dctitle:file-as">Book, My</meta>
...
</metadata>

// This is only hypothetical, as I'm not sure whether the publication itself would require a 'Metadata Authority' definition.
<metadata ...>
...
<dc:title id="title">My Book</dc:title>
<meta property="meta-auth">Awesome EPUB Organization</meta>
...
</metadata>

EDIT: In regard to what meta::property values are allowed have a look here: Archived from the original on epubzone.org here
Also, the latest official IDPF specifications for EPUB Open Container Format may be found here: www.w3.org/publishing/epub3/epub-spec.html#sec-core-media-types

Free books android app tbrJar TBR JAR Read Free books online gutenberg

Load Full (0)

Trending!

 

Back to top