-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allowing role on dc:publisher #1583
Comments
For reference, this spec requirement was added in EPUBCheck after it was reported in w3c/epubcheck#1121 |
The issue was discussed in a meeting on 2021-03-26 List of resolutions:
View the transcript3. Extending "role" cardinality in contributor metadataSee github issue #1129, #1583. Dave Cramer: this came up early in epub 3.2 in CG Matt Garrish: part of the restriction is because we had the OPF role attribute role in epub Dave Cramer: more RS i'm aware of won't display this to end user at all Bill Kasdorf: allowing this might be good just for removing friction for publishers Hadrien Gardeur: from Readium perspective, we could support it Dan Fauxsmith: given that we are currently saying 0 to 1, but publishers are saying they have lots of ebooks where this is already >1, should we recommend that if there is more than 1 then it should be in priority order?
Gregorio Pellegrino: my Q is about ONIX Bill Kasdorf: this is really common in higher ed publishing Hadrien Gardeur: disagree that we should try to align with ONIX Dave Cramer: ONIX cardinality for contributor is that each can have multiple roles Ivan Herman: agree, but i think we should also make it clear that they should be in priority order Charles LaPierre: i just created book for diagram center that had multiple contributors, and there i had to add in all these roles for each contributor. Would have loved to have been able to do this in the epub as well. Brady Duga: for priority, i could seen some RS taking the first one, and some taking the last one Matt Garrish: can we also agree to 1583?
Wendy Reid: so we'll leave to mgarrish to draft amending language |
Thanks @iherman, good to know it's being considered. Looking at the transcript it's not clear to me if this would also allow roles on |
Yes, I asked that we resolve both right before we voted so they're both relaxed in #1591 I've also opened this in w3c/epubcheck#1230 to get epubcheck updated. |
Awesome, thanks! |
Tangentially related to #1129. With the release of epubcheck 4.2.5 the Standard Ebooks corpus is now throwing errors because we attach a
role
to<dc:publisher>
, and that appears to be no longer allowed.I would suggest including
<dc:publisher>
in the list of allowed elements that may have arole
attached. Many MARC roles apply to organizations, not just individuals, and it is often useful to include such metadata: for example, which organization is the Metadata Contact (mdc)? That might often be the publisher!For example, this is the standard boilerplate that has been included in all Standard Ebooks for years, which all of a sudden fails epubcheck:
This indicates that Standard Ebooks is the Book Designer (bkd), Markup Contact (mdc), and Publisher (pbl). One could argue that pbl is redundant but I think the rest are valid roles to attach to an organization.
The text was updated successfully, but these errors were encountered: