|
Hi,
Nice list ...
Two things. The DC namespace is what the main epub spec is built on and both DCTERMS. and DC. and refinements are already supported where they overlap with the epub spec so your first list of valid metadata recognized now is still the main one.
So all we need think about is what to **add** to the epub spec and it looks like you agree with me that using DCTERMs. as the main source of these additions is the way to go.
2. So if we just look at the additions to what is already covered by Sigil/ and the epub spec you are suggesting the following, is that correct?
Series Name
<meta name="DCTERMS.isPartOf" content="SERIES NAME" />
Series Number
<meta name="DCTERMS.hasPart" content="SERIES NUMBER" />
Copyright Date
<meta name="DCTERMS.dateCopyrighted" contents="YYYY(-MM(-DD))" />
Copyright Holder
<meta name="DCTERMS.rightsHolder" contents="NAME/ORG." />
Copyright Status
<meta name="DCTERMS.license" contents="LICENSE/STATUS" />
and then from non-dc / non-dcterms you are suggesting we add the following:
File Name
-- The original name of the eBook file.
File Version
-- Using a defined versioning scheme. It's also a bit like a "#th Printing" statement.
File Comment
-- Information about how/why the ebook file was created.
File-As
-- Part of the ePub spec, but generally useful to define document sorting.
Sub-title
-- Lots of books have these.
Publication City
-- Commonly used. Might be growing less relevant in the digital age.
Is that correct?
If so, I think that is a good list. Perhaps we could encourage others to add their two cents and see what they think.
I wish there was a way to "advertise" this topic to all people interested in book metadata on this forum to get more input.
Thanks,
Kevin
|