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

is-about #7

Open
wceusters opened this issue Apr 13, 2021 · 2 comments
Open

is-about #7

wceusters opened this issue Apr 13, 2021 · 2 comments

Comments

@wceusters
Copy link

In the paper https://wellcomeopenresearch.org/articles/6-77/v1 I read " The relationship ‘is_about’ from the Information Artifact Ontology (Ceusters, 2012) was also used to represent one class presenting information about another (e.g Total number of people able to deliver intervention is_about Source)." I don't find this relational expressed in the BCIO version here, so perhaps it is not an issue. But note that if you intend to do so as in the paper, it wouldn't work under the BFO principles: since 'source' is defined in the paper as 'role played by a person', so you would be specifying how many distinct intervention roles one specific person has. Linking it to 'person' would also not work, as the total number of an instance of 'person' is 1. The range of the relation in your example would be an aggregate of persons.

@jannahastings
Copy link
Contributor

@wceusters, many apologies for the delay responding, for some reason I was not notified about this comment, thank you!

You are absolutely correct, the target of the 'is about' relation for an entity 'total number of people able to deliver intervention' should be an aggregate of persons, not an individual person nor a role. We will correct that in the next release.

@robertjwest
Copy link
Contributor

Good catch - thanks. To to it correctly then I think we need a defined class for a person who has the role of source, rather like in a previous comment we need a defined class for 'occupation holder' (though we may want to keep our 'occupational role' as the primary class for this rather than thinking of occupation as a process aggregate?

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

3 participants