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

Expand definition of software, uses software, and used by #19

Open
gneissone opened this issue Sep 16, 2015 · 5 comments
Open

Expand definition of software, uses software, and used by #19

gneissone opened this issue Sep 16, 2015 · 5 comments

Comments

@gneissone
Copy link

The domain and range of software, uses software, and used by is currently very narrow.

For example, software/databases/protocols "used by" currently has a range of foaf:Organization. But we want to model people who use software. Can the range be broadened up to foaf:Agent or beyond?

Similarly, "uses software" has a domain of service, which precludes people using software without performing a service. Incidentally, this property has a note "# deprecated" on line 5423 of initialTBoxAnnotations.n3 in the VIVO application distribution, which appears to date back to this commit: vivo-project/VIVO@f786366.

@gneissone
Copy link
Author

Okay, I see now that the # deprecated note is there because it is, in fact, a sub-property of deprecatedproperty. So switch that last paragraph to 'uses' and a domain of organization.

@arademaker
Copy link
Member

What is the concrete suggestion here? Maybe this issue can be followed by a PR with suggestions of changes in the ontology?

@gneissone
Copy link
Author

I'm not sure where the domain and range assertions are being made in the vivo-isf-ontology repo?
We want "uses" (http://purl.obolibrary.org/obo/ERO_0000031) to have a domain that includes foaf:Person and "used by" (http://purl.obolibrary.org/obo/ERO_0000070) to have a range that includes foaf:Person.

@arademaker
Copy link
Member

Both properties are not from VIVO-ISF ontology, they are OBO properties (given the IRIs) and I don't think we can change their definitions. We may start replacing OBO with other upper level ontology or creating our own properties and classes with less reuse of others definitions.

@gneissone
Copy link
Author

ERO is the eagle-i prefix, which was merged into VIVO. So I think this group is responsible for it? The eagle-i wiki leads back here. Not sure if the process is different with the OBO registered terms or not.

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

No branches or pull requests

2 participants