The class author should get properties:
I am aware that
@akleinau This comes from the factsheets, too, right? So I add the 1.1 milestone
not every author needs to have an institution, right? So I wouldn't state this in the ontology but when it's needed everything exists to relate an author to an institution (_author_individual_ 'has institution' value _institution_individual_).
@stap-m, @l-emele which working fields are needed or is a generic working field class enough?
active time period can be implemented by a "has active time period" relation with a one-dimensional temporal region as range.
I am not sure if _has institution_ can relate an author to an institution. According to the definition of _has institution_ it can only relate publications to institutions and according to the definition of its superproperty _has participant_ it can only relate processes and continuants (which is weird because publications are not processes). So we probably need to change both definitions to include authors as well. Another option would be to create a new object property like _member of_.
member of is more generic, so I would propose to just delete has institution and create member of as a property independent of has participant
ok I was too fast, has institution is still needed to relate a publication to an institution. But member of is still helpful, as well as it's inverse has member.
So:
has member, member of: "a relation between a person and an organisation in which the person is a member of the organisation" (adapted a bit of course depending on the relation)has institution and the other not fitting relations away from has participantactive time period can be implemented by a "
has active time period" relation with aone-dimensional temporal regionas range.
For active time period, maybe we could use time step, see #538
Where do we put working fields? Could they be sectors?
For which purpose do we need active time period and working field? Do we intend to store such information on the OEP?
For which purpose do we need active time period and working field? Do we intend to store such information on the OEP?
I don't think so. Also, these attributes are (constantly) changing. I'd propose to leave them out.
Then it's basically the implementation of _member of/ has mamber_.
All right. I'll do that.
Most helpful comment
ok I was too fast, has institution is still needed to relate a publication to an institution. But member of is still helpful, as well as it's inverse has member.
So:
has member,member of: "a relation between a person and an organisation in which the person is a member of the organisation" (adapted a bit of course depending on the relation)has institutionand the other not fitting relations away fromhas participant