Quote:
Originally Posted by KevinH
Hi,
I edited the list above to include the DCTERMS. namespace where it overlaps with the epub spec as well as use of refinements to hold schemes for identifiers.
As it stands now, EISBN is mapped to ISBN internally so using both at the same time would probably not be a good idea.
Hope this helps,
Kevin
|
Cool, that's great. Is there anything else that's currently possible, but not listed?
From your comment, I went and looked again at the DCTERMS list.
In my original list of custom metadata terms there were the following that didn't map to the DC list:
Code:
<meta name="FileName" content="FILENAME.EXT" />
<meta name="FileVersion" content="VERSION NUMBER/NAME" />
<meta name="FileScanner" content="NAME" />
<meta name="FileComment" content="COMMENT" />
<meta name="SubTitle" content="SUBTITLE" />
<meta name="Series" content="SERIES NAME" />
<meta name="SeriesNumber" content="SERIES SEQUENCE NUMBER" />
<meta name="PublicationCity" content="CITY NAME" />
<meta name="CopyrightHolder" content="NAME" />
And this one didn't map to the ePub spec:
Code:
<meta name="DC.date.copyrighted" content="YYYY(-MM(-DD))" />
What do you think of the following?
Code:
<meta name="DCTERMS.alternative" content="SUBTITLE" />
<meta name="DCTERMS.isPartOf" content="SERIES NAME" />
<meta name="DCTERMS.rightsHolder" content="NAME" />
<meta name="DCTERMS.dateCopyrighted" content="YYYY(-MM(-DD))" />
And maybe changing
Code:
<meta name="DC.rights" content="LICENSE" />
to
Code:
<meta name="DCTERMS.license" content="LICENSE" />
?
Still leaves me out in the cold with the following though:
Code:
<meta name="FileName" content="FILENAME.EXT" />
<meta name="FileVersion" content="VERSION NUMBER/NAME" />
<meta name="FileScanner" content="NAME" />
<meta name="FileComment" content="COMMENT" />
<meta name="SeriesNumber" content="SERIES SEQUENCE NUMBER" />
<meta name="PublicationCity" content="CITY NAME" />
m a r