I have two questions about the model below (picture and code block)
Content-wise:
We would like to indicate that a Person could fulfill a Organizational Role, but would not explicitly model all possible instances of Organizational Role as subclasses of Person.
The advantage of this is that we leave unspecified which subclasses can end up being added. We only model the fact that there are different subclasses of Position following from the Role that Position has.
Is this a 'correct' way to use gUFO?
Visually:
The property gufo:categorizes consideres Person and OrganizationalRole as instances of respectively gufo:Kind and gufo:Type.
The property :fulfillsTheRoleOf consideres Person and OrganizationalRole as classes.
How can we visualize efficiently the categorizes-relation between both classes without suggesting that instances of OrganizationalRole categorize instances of Person?
Model
:Person a gufo:Kind ;
rdfs:subClassOf gufo:FunctionalComplex .
:OrganizationalRole a gufo:Type ;
rdfs:subClassOf gufo:Role .
:OrganizationalRole gufo:categorizes :Person .
:fulfillsTheRoleOf a owl:ObjectProperty ;
rdfs:domain ex:Person ;
rdfs:range ex:OrganizationalRole .
:ProgramManager a :OrganizationalRole .
:John a :Person ;
:fulfillsTheRoleOf :ProgramManager .
I have two questions about the model below (picture and code block)
Content-wise: We would like to indicate that a Person could fulfill a Organizational Role, but would not explicitly model all possible instances of Organizational Role as subclasses of Person. The advantage of this is that we leave unspecified which subclasses can end up being added. We only model the fact that there are different subclasses of Position following from the Role that Position has. Is this a 'correct' way to use gUFO?
Visually: The property gufo:categorizes consideres Person and OrganizationalRole as instances of respectively gufo:Kind and gufo:Type. The property :fulfillsTheRoleOf consideres Person and OrganizationalRole as classes. How can we visualize efficiently the categorizes-relation between both classes without suggesting that instances of OrganizationalRole categorize instances of Person?
Model