Skip to content
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

Assign multiple roles to one person #1782

Closed
spajak opened this issue Aug 25, 2021 · 5 comments
Closed

Assign multiple roles to one person #1782

spajak opened this issue Aug 25, 2021 · 5 comments
Labels
Spec-EPUB3 The issue affects the core EPUB 3.3 Recommendation Status-Declined The issue has been reviewed and not accepted by the working group for inclusion Topic-PackageDoc The issue affects package documents

Comments

@spajak
Copy link

spajak commented Aug 25, 2021

Sometimes the same person has more than one role.

I would like to write it just like this, using comma:

<dc:contributor id="producer">Sebastian Pająk</dc:contributor>
    <meta refines="#producer" property="role" scheme="marc:relators">role-1, role-2, role-3</meta>

But I guess the above is not valid; one has to repeat the same contributor for every role. It would be nice to simplify this to just one contributor+meta(s) tags.

@mattgarrish mattgarrish added the Topic-PackageDoc The issue affects package documents label Aug 25, 2021
@dauwhe
Copy link
Contributor

dauwhe commented Aug 25, 2021

See also #1583 and #1129 for related discussions

@iherman
Copy link
Member

iherman commented Aug 25, 2021

What this means is that, I believe, the following is fine:

<dc:contributor id="producer">Sebastian Pająk</dc:contributor>
    <meta refines="#producer" property="role" scheme="marc:relators">role-1</meta>
    <meta refines="#producer" property="role" scheme="marc:relators">role-2</meta>
    <meta refines="#producer" property="role" scheme="marc:relators">role-3</meta>

ie, if I understand the remark "one has to repeat the same contributor for every role" then this isn't correct.

Using the comma separated list syntax would mean to formally specify a micro-syntax in the spec which, though not complicated, is an unnecessary extra complexity on the spec (which is already complex enough).

@mattgarrish
Copy link
Member

mattgarrish commented Aug 25, 2021

"one has to repeat the same contributor for every role" then this isn't correct

Not after this revision, no. We updated the rules in the earlier issues @dauwhe has pointed to.

Using the comma separated list syntax would mean to formally specify a micro-syntax in the spec

Right, this is why we avoided this approach. We can specify a syntax, but then people just do what they want anyway, which leaves it to reading systems to have to make sense of the input.

@dauwhe
Copy link
Contributor

dauwhe commented Sep 1, 2021

Are there reading systems that display contributor roles?

@wareid wareid closed this as completed Sep 17, 2021
@iherman
Copy link
Member

iherman commented Sep 17, 2021

The issue was discussed in a meeting on 2021-09-16

List of resolutions:

View the transcript

3. Multiple Roles

See github issue #1782.

Dave Cramer: about package metadata. someone proposed that we be able to assign multiple roles to a person using a comma separate string of different roles
… but we don't think we want to get involved in parsing
… but you can already assign multiple roles to a person in the current spec
… and i'm not aware of many RS that even present this information to user
… so i would close this issue

Proposed resolution: Close issue 1782 as won't fix. we (Wendy Reid)

Matt Garrish: agreed. If we come up with a micro-syntax for the meta tag that could open up a bunch of issues. The one property per tag is a simple system that works.

Proposed resolution: Close issue 1782 with maximum prejudice (won't fix) (Wendy Reid)

Dave Cramer: +1

Brady Duga: +1

Shinya Takami (高見真也): +1

Matt Garrish: +1

Matthew Chan: +1

Toshiaki Koike: +1

Wendy Reid: +1

Resolution #2: Close issue 1782 with maximum prejudice (won't fix)

@mattgarrish mattgarrish added the Status-Declined The issue has been reviewed and not accepted by the working group for inclusion label Sep 29, 2021
@mattgarrish mattgarrish added the Spec-EPUB3 The issue affects the core EPUB 3.3 Recommendation label Sep 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Spec-EPUB3 The issue affects the core EPUB 3.3 Recommendation Status-Declined The issue has been reviewed and not accepted by the working group for inclusion Topic-PackageDoc The issue affects package documents
Projects
None yet
Development

No branches or pull requests

5 participants