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

Handling roles for creators #167

Closed
HadrienGardeur opened this issue Mar 15, 2018 · 2 comments
Closed

Handling roles for creators #167

HadrienGardeur opened this issue Mar 15, 2018 · 2 comments

Comments

@HadrienGardeur
Copy link
Member

This is a follow-up to #151 and the recent #161 pull request.

Now that our WebIDL can support multiple creators and canonical identifiers for them, we need to continue discussing how roles will be handled.

I think there are essentially two different solutions:

  • using a generic element with a specialized vocabulary for roles (like in EPUB 2/3 where we use dc:creatorand dc:contributor + MARC relators)
  • using specialized elements per role (for instance, roles extracted from schema.org)

RWPM is a mix of both with the following dedicated roles that are mapped to schema.org: author, translator, editor, artist, illustrator, letterer, penciler, colorist, inker and narrator.

As a fallback option, RWPM also has a contributor element (also mapped to schema.org) with a role member that relies on MARC relators.

The exact scope of our infoset is vague, but my personal preference would be to align with schema.org and adopt at least a subset of the roles that are available.

@iherman
Copy link
Member

iherman commented Mar 15, 2018

I think in general aligning with schema.org is a good move. It is time publications are recognized by schema, and that their metadata end up in various knowledge graphs...

@HadrienGardeur
Copy link
Member Author

This is now covered by our draft: https://w3c.github.io/wpub/#wp-creator-manifest

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants