View Single Post
Old 07-25-2017, 10:07 AM   #1
jcsalomon
Zealot
jcsalomon can extract oil from cheesejcsalomon can extract oil from cheesejcsalomon can extract oil from cheesejcsalomon can extract oil from cheesejcsalomon can extract oil from cheesejcsalomon can extract oil from cheesejcsalomon can extract oil from cheesejcsalomon can extract oil from cheesejcsalomon can extract oil from cheese
 
jcsalomon's Avatar
 
Posts: 98
Karma: 1204
Join Date: Jun 2012
Device: Bookari (née Mantano Reader) on Android; Kindle Fire HD
EPUB3-compatible Amazon ASIN metadata

In EPUB2 books, a metadata entry of the form
Code:
<dc:identifier opf:scheme="AMAZON">BXXXXXXXXX</dc:identifier>
(where “BXXXXXXXXX” is the ASIN) seems to be the correct way to add such information. But in EPUB3, “opf:scheme” is not allowed, so I’m wondering what the “correct” method should be. Seems something along the lines of
Code:
<dc:identifier id="amazon-id">urn:AMAZON:BXXXXXXXXX</dc:identifier>
<meta refines="#amazon-id" property="identifier-type" scheme="xsd:string">AMAZON</meta>
should work, but is this right? Is the “<meta refines>” even needed, or perhaps is the “urn:AMAZON:” not correct?

(Perhaps, following http://idpf.org/epub/30/spec/epub30-...f-dcidentifier and substituting “01” [Proprietary] for “06” [DOI], the second line should be something like
Code:
<meta refines="#amazon-id" property="identifier-type" scheme="onix:codelist5">01</meta>
but http://stison.com/onix/codelists/onix-codelist-5.htm says, “Note that <IDTypeName> is required with proprietary identifiers” and there is no obvious place to put such “IDTypeName” information.)

Note that I’m asking what the EPUB3 spec suggests. I know full well that the Kindle generating process ignores such metadata, and I know that the first line is a format Calibre will interpret and EpubCheck will pass.
jcsalomon is offline   Reply With Quote