-
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
Membership as a class #374
Comments
EditorialCommittee: A good idea. We support this and will integrate a class "Membership", with properties about the start and end time and a classification of the type of membership ("hasObjectType skos:concept"). |
I just came across the class Affiliation. It connects a Person and an Organisation, allows to classifiy the affiliation with a skos:concept and lets you set a start time and an end time. |
Hi Juergen, yes that's pretty much what it is I think. I don't think it is necesary to connect more than one agent, since I think a membership should be a distinct class that connects one person (or one organisation) to one organisation. So a group consisting of four members will have 4 "affiliations" connected to it? Correct me if I'm misunderstanding something... |
Right. |
Hi Juergen, Between persons and persons, no. But organisations can be member of other organisations. (f.e. a daughther company or a subteam, a subrecordlabel...) ... and that membership can also be limited in time. In that respect I think the word affiliation is not hierachical enough? In case of persons and organisations the relationship is always clear, but in case of organisations it needs to be made explicit which is the "bigger" part... Just my two cents ofcourse! |
Wondering if there are plans to create a Membership class to be able to attach properties to the link between agents? Or is there another way to express this in the current version?
There you can express the start en especially the end Date of a Membership for example.
The text was updated successfully, but these errors were encountered: