View Single Post
Old 07-25-2017, 11:14 AM   #2
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,851
Karma: 6120478
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.
KevinH is offline   Reply With Quote