FWIW,
I have been reading up on the epub3.1 metadata
In epub3.1 only one opf:role attribute will be allowed on a dc:creator or dc:contributor element and from what I have been able to find it may only hold a single 3 letter value - not a list of space separated values.
See
http://www.idpf.org/epub/31/spec/epu...-dccontributor
Quote:
|
As attributes cannot be repeated, only a single alternative representation can be declared for any element.
|
Quote:
opf:role
Identifies the role of a creator or contributor. The value must be a three-letter lowercase code from [MARC Relators].
|
So the only way for "Evil Overlord" to be both "edt" and "edc" under epub3.1 would be as follows:
Code:
<dc:contributor opf:role="edt">Evil Overlord</dc:contributor>
<dc:contributor opf:role="edc">Evil Overlord</dc:contributor>
Effectively like giving the same person credits as both actor and director in movie credits as his/her name would then appear twice.
So the safest way to handle this under epub 3.0 might be as follows:
Code:
<dc:contributor id="contrib1">Evil Overlord</dc:contributor>
<dc:contributor id="contrib2">Evil Overlord</dc:contributor>
<meta refines="#contrib1" scheme="marc:relators" property="role">edt</meta>
<meta refines="#contrib2" scheme="marc:relators" property="role">edc</meta>
That may seem strange but as far as I can tell from the epub 3.0 specs is perfectly legal and it would then be mappable back into both older epub2 metadata and future epub3.1 metadata.
So instead of using multiple refines pointing at the same dc:contributor, you may want to use multiple dc:contributor elements each with its own single role related refine.
My 2 cents ...
KevinH
ps. FWIW: Sigil's epub3 metadata editor should already properly handle things things this way