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

VIVO-1652: Administrative unit as a new sub-class of foaf:Organization #3242

Closed
chenejac opened this issue Dec 5, 2018 · 2 comments
Closed

Comments

@chenejac
Copy link
Contributor

chenejac commented Dec 5, 2018

Mike Conlon (Migrated from VIVO-1652) said:

The list of organization types in VIVO could be extended with :AdministrativeUnit as a sub-class of foaf:Organization. There are already a couple of universities like http://scholars.library.tamu.edu/vivo/display/n78eb517b or https://vivo.ufl.edu/organizations#http://vivo.ufl.edu/ontology/vivo-ufl/AdministrativeUnit%20 which have this class in their local ontology and use it. We also have a similar class in our local ontology. Since there is a need for this class at several institutions, it would be good to have this class in VIVO Core.

This is also issue openrif/vivo-isf-ontology#756

 

@chenejac
Copy link
Contributor Author

chenejac commented Dec 5, 2018

Mike Conlon said:

AdministrativeUnit defined in vivo.owl.  Application annotations added to vitroAssertions.n3.

See #101

@VeljkoMaksimovic
Copy link

#101 Pull request where :AdministrativeUnit was added is still open, but the community and committers didn’t think that adding this subclass is a good idea. Entire discussion can be read on the PR page. It seems like the addition (or omission) of this subclass will be left to the individual organizations which use VIVO.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants