-
Notifications
You must be signed in to change notification settings - Fork 6
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
Involvement Type #376
Comments
Editorial Committee recommendation: Using a skos:conceptScheme is the right way. If you bring your own vocabulary, eg a role list, you can create a subclass of the skos:concept and use whatever list fits your use case. You may want to have a look at the EBU classification scheme as an example for creating a vocabulary. Link will follow. |
I think I found the link: or are there still some changes planned? |
Sorry, I forgot to post the link! You found it anyway :) |
Is there already something like an
Involvement type
concept subclass?Am I right to assume that this would be a skos list including things like Actor, Presenter, Interviewer, Interviewee?
Or maybe rather verbs like Acting, Presenting, Interviewing, Being Interviewed... dunno.
The text was updated successfully, but these errors were encountered: