Skip to content
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

make academic event series a subclass of academic event #146

Closed
StroemPhi opened this issue Jun 3, 2022 · 0 comments · Fixed by #147
Closed

make academic event series a subclass of academic event #146

StroemPhi opened this issue Jun 3, 2022 · 0 comments · Fixed by #147

Comments

@StroemPhi
Copy link
Contributor

In order to be able to inherit properties that are applicable to both single academic events as well as series of academic events it seems best to make academic event series a child of the academic event class. This is also in analogy to the ontology of the German National Library (GNDO)

StroemPhi added a commit that referenced this issue Jun 3, 2022
StroemPhi added a commit that referenced this issue Jun 3, 2022
StroemPhi added a commit that referenced this issue Aug 22, 2022
* deprecate unneeded contributor defined classes & roles already present in CRO, OMRSE, OBIB and OOSTT
* adding relevant event organizer roles
* improve labels & text definitions of AEON roles
* import committee from OOSTT
* deprecate unneeded "has participant" & "participates in" subproperties
* #146 was reversed by mistake in the ODK switch thus fixing this
* fix typos and add series plan spec
* fix wrong prefix of AEON classes
* improve EC axiom of event format spec
* add EC axiom on series format spec
* update import terms
* deprecate committee subclasess #144 (due to wrong IRI)
* removed some disjointedness of roles for the moment and some EC axioms
* delete unneeded interim aeon.ttl
* update example individuals
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant