View Single Post
Old 12-26-2009, 09:07 PM   #6
KevinH
Guru
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: 659
Karma: 230878
Join Date: Nov 2009
Device: many
more on dc

Quote:
Originally Posted by rogue_ronin View Post
Kevin --

> Beyond the DC, you seem to be supporting basic tags that you can assume folks might have: Publisher, Author, Editor, etc. Is that right?

Actually, I only support a few of the most basic, and these must map to the epub standard that Sigil uses internally.

The free-form ones I handle are:

"Title"
"Author"
"Subject"
"Description"
"Publisher"
"Date of publication"
"Date of creation"
"Date of modification"
"Type"
"Format"
"Relation"
"Coverage"
"Rights"
"Copyright"
"EISBN"
"ISSN"
"ISBN"
"CustomID"
"DOI"


The only reason these are supported and not others is that they map to the epub standard directly.

Your example has a much larger set, most of which would be ignored as things currently stands.



> Now, even if you catch some of it, I don't expect to be able to use it as is. > I've already explored some changes:

<meta name="DC.date.created" content="2009-12-09" />
<meta name="DC.date.modified" content="2009-12-09" />
<meta name="DC.contributor.pfr" content="FoundText" />
<meta name="DC.title" content="Book Title" />
<meta name="DC.creator.aut" content="First·Middle·LastName·" />
<meta name="DC.contributor.ill" content="First·Middle·LastName·" />
<meta name="DC.contributor.edt" content="First·Middle·LastName·" />
<meta name="DC.contributor.cov" content="Name" />

<meta name="DC.type" content="Howto" />
<meta name="DC.identifier" scheme="ISBN" content="123456789X" />
<meta name="DC.language" content="en" />
<meta name="DC.description" content="An example document for discussing metadata." />
<meta name="DC.subject" content="metadata,example" />

<meta name="DC.publisher" content="FoundText" />
<meta name="DC.rights" content="Public Domain" />

Are the ones in your second example that work now (actually the "published" one would work too given Valloric's change.

> How do you support the "file-as" attribute of the ePub spec?

It is simply used to replace the person's name in the epub spec if it is present. It is not supported in the html dc set since it is not part of the dc spec.

> What do you think about this

Code:
<meta name="DC.relation.series" content="Examples" />
<meta name="DC.relation.series.number" content="16" />
or

Code:
<meta name="DC.title.sub" content="Subtitle" />
?


I only handle single level refinements right now. Multiple layers of refinements are not part of the spec as far as I could determine.

> The two DC terms that you don't say you support are: Language, and Source. Would you consider them? Or are they unnecessary?

dc.language is supported, it is basic and handled in a pull down in Sigil.

> What is CustomID? Would my scheme="xBook" be okay?

I think those are actually ignored in the final run but Valloric would be the best one to ask that.

> And finally, the namespace can be either DC or DCTERMS, correct?

Yes where they overlap, but if it is something specific to the DCTERMS namespace it is better to prefix it with DCTERMS (for example - dcterms.modified for the date of modification.


m a r
You have a long list and many of the items you have would be interesting extensions. Right now, I have only focused on handling the epub spec.

The epub spec does allow for non dc to be passed through but handling that would be completely up to Valloric to decide if and how he wants it.

If he says "yes" I would be happy to take a shot at working with you to come up with a reasonable list of non-dc and extended dc terms to handle.

Take care,

KevinH
KevinH is offline   Reply With Quote