search

openminted / omtd-share-schema

OMTD-SHARE schema (versioned)
0 stars 0 forks source link

ActorInfo could have information about the role #7

Open reckart opened 7 years ago

reckart commented 7 years ago

ActorInfo could have information about the role(s), e.g. whether an actor is a contributor, developer, cheerleader, whatever.

pennyl67 commented 7 years ago

ActorInfo, personInfo, organizationInfo are the base modules used for persons and organizations (actor for the combination). Depending on where each of these is used, it's assigned a role indirectly, e.g. resourceCreator, contactPerson, evaluator, rightsHolder, annotator etc. We could add the role on the actor/person/organizationInfo, but we lose some info: X can be creator, annotator etc. and all of them assigned at the same place (i.e. role can be unbounded). But the important thing is that X is the creator, annotator, etc. of the resource Y. In OMTD-SHARE, the core entity is the resource and the actor/person/organization is dependent on it.

reckart commented 7 years ago

Ok. I see. Maven makes a distinction between developers and contributors. I am currently mapping both to resourceCreator. Should I continue doing that? Or only developers and not map contributors at all? Or map contributors somewhere else?

pennyl67 commented 7 years ago

I suppose contributor is considered a bit minor than developer? Assuming that resourceCreator should be used for citation and attribution purposes at some point, would you consider "contributors" important enough to be acknowledged at the same level as the developers? For moral reasons, I would tend to add them (better acknowledge than ignore them). Currently we have no "contributors" - of course, it could be added, if considered useful. But it will be just another role with no real semantics or action behind it. Should it be used only for resourceCreation? For instance, will we also have "contributors" in the evaluation or the annotation process? At the worst case, we could have it as a generic relation between resources and persons/organizations/groups without any explanation or action associated to it.

reckart commented 7 years ago

I guess, developers and contributors are both resource creators. I suppose that developers would also be contacts - even if they do not have provided any contact information, it would be the people one should try seeking out first.

I think if somebody goes as far as adding contributors in a machine-readable way go the POM, then it would be reasonable to expose that information also in the OMTD registry.

Even for non-Maven projects, I can imagine that people would like to give attribution to contributors of their resource and distinguish between "maintainers/developers" and contributors. Others might not want to make a distinction and yet others might choose not even to list contributors, e.g. if they made their contributions as part of a paid employment.