ebu
Membership as a class
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.
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. However, in the current definition it cannot connect two Persons. @RendersKoen : Would that be sufficient anyway?
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.
Every member can have his own start and end time of the membership. That makes it neccessary to provide an affiliation per member.
However, I am not sure, whether we need to express affiliations between organisations and between persons as well? If you have a case for that, please let us know!
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!