07-25-2017, 10:07 AM | #1 |
Zealot
Posts: 100
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> Code:
<dc:identifier id="amazon-id">urn:AMAZON:BXXXXXXXXX</dc:identifier> <meta refines="#amazon-id" property="identifier-type" scheme="xsd:string">AMAZON</meta> (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> 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. |
07-25-2017, 11:14 AM | #2 |
Sigil Developer
Posts: 7,644
Karma: 5433388
Join Date: Nov 2009
Device: many
|
My 2 cents here:
All of these seem correct. But since refines go away under epub 3.1 metadata rules, and because the official rules of Universe Resource Name (urn:) are quite vague and do not require use of an "identifier-type", I would stick with the simplest approach for epub 3.0, using <dc:identifier id="amazon-id">urn:AMAZON:BXXXXXXXXX</dc:identifier> with no extra refines as parsing that urn provides all of the information needed to fully understand the identifier. Last edited by KevinH; 07-25-2017 at 01:21 PM. |
Advert | |
|
07-25-2017, 11:15 AM | #3 |
Grand Sorcerer
Posts: 27,549
Karma: 193191846
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
I honestly don't think the extra meta refines entry would be necessary. But if you do add it, I don't think your initial example would violate epub spec. I'm not the go-to spec expert, though.
EDIT: seems KevinH beat me with similar info. Last edited by DiapDealer; 07-25-2017 at 02:12 PM. |
07-25-2017, 01:09 PM | #4 |
Zealot
Posts: 100
Karma: 1204
Join Date: Jun 2012
Device: Bookari (née Mantano Reader) on Android; Kindle Fire HD
|
Thanks, both of you.
(Is it always like this when diving into the spec? It seems in some ways vastly over-specified and in other ways astoundingly under-defined.) |
07-29-2017, 07:12 PM | #5 |
Grand Sorcerer
Posts: 5,278
Karma: 98804578
Join Date: Apr 2011
Device: pb360
|
|
Advert | |
|
07-30-2017, 03:15 AM | #6 |
Wizard
Posts: 4,520
Karma: 121692313
Join Date: Oct 2009
Location: Heemskerk, NL
Device: PRS-T1, Kobo Touch, Kobo Aura
|
Yup. And don't forget my favorite: giving room to wiggle by using words like 'should', 'might', 'could'. A standard/specifications should not use those words if it can be avoided for at least the core. This is a short way of ensuring different interpretations and executions of the standard.
|
07-30-2017, 06:27 AM | #7 |
The Grand Mouse 高貴的老鼠
Posts: 71,506
Karma: 306214458
Join Date: Jul 2007
Location: Norfolk, England
Device: Kindle Voyage
|
The ePub spec has been a great disappointment to me, concentrating on extraneous stuff like video and sounds, and ignoring things like specifying minimal rendering standards so that it was possible to do things like drop caps, or even simple superscripts, without having to be concerned about how it will render.
|
07-30-2017, 06:51 AM | #8 |
eBook Enthusiast
Posts: 85,544
Karma: 93383043
Join Date: Nov 2006
Location: UK
Device: Kindle Oasis 2, iPad Pro 10.5", iPhone 6
|
Agreed. ePub 3 is in many ways a step backwards from ePub 2, to my mind.
|
07-30-2017, 04:37 PM | #9 | |
Resident Curmudgeon
Posts: 73,974
Karma: 128903378
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
Quote:
Support for multiple authors, series, covers without needing an html file to display it, support for non-ToC lines in the NCX ToC for display so there would be 100% no need for the HTML ToC and even support for multiple NCX as in an omnibus, and I bet there are other things I've not thought of. |
|
07-31-2017, 05:32 PM | #10 | |
Wizard
Posts: 4,520
Karma: 121692313
Join Date: Oct 2009
Location: Heemskerk, NL
Device: PRS-T1, Kobo Touch, Kobo Aura
|
Quote:
|
|
08-01-2017, 03:39 AM | #11 |
The Grand Mouse 高貴的老鼠
Posts: 71,506
Karma: 306214458
Join Date: Jul 2007
Location: Norfolk, England
Device: Kindle Voyage
|
Proper drop cap support (i.e. specify a drop cap for three lines, require the renderer to make the drop cap fit three lines, even if the line spacing gets changed, and taking into account the cap height of the selected font. Not really hard for a renderer to do, but impossible currently.)
Proper subscript/superscript support. Require that adding subscript/superscript doesn't change line spacing for the line the superscript is on. Poetry formatting. So that wrapped lines are right aligned. As was available in the Mobipocket format! |
08-01-2017, 04:28 AM | #12 |
eBook Enthusiast
Posts: 85,544
Karma: 93383043
Join Date: Nov 2006
Location: UK
Device: Kindle Oasis 2, iPad Pro 10.5", iPhone 6
|
|
08-01-2017, 06:16 AM | #13 |
Resident Curmudgeon
Posts: 73,974
Karma: 128903378
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
|
08-01-2017, 06:21 AM | #14 | |
Resident Curmudgeon
Posts: 73,974
Karma: 128903378
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
Quote:
It's like a larger first letter on a Kindle with KF8. That first line is going to have the line-height different from the rest of the lines and nothing can be done about it. |
|
08-01-2017, 12:54 PM | #15 | |
A Hairy Wizard
Posts: 3,094
Karma: 18727053
Join Date: Dec 2012
Location: Charleston, SC today
Device: iPhone 11/X/6/iPad 1,2,Air & Air Pro/Surface Pro/Kindle PW & Fire
|
Quote:
|
|
Tags |
asin, epub 3, metadata, onix |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Metadata for PDF magazines - ASIN? other id? | dhdurgee | Library Management | 5 | 02-12-2016 04:21 PM |
Download options for Identifier (isbn, asin, etc.) metadata | digital_carver | Library Management | 14 | 09-06-2015 08:35 PM |
Download metadata from ASIN | CaitlinShaw | Library Management | 3 | 06-17-2015 12:56 AM |
Mobi-asin and metadata | desertblues | Calibre | 6 | 01-20-2013 09:43 AM |
Downloading ASIN from Amazon | nynaevelan | Library Management | 6 | 02-02-2012 09:53 PM |