I am trying to model the following statement in Description Logic.
A co-teaching faculty member is any person who is an academic staff and teaches at least one course that is taught by others
The representation that I have thought of is:
CoTeachingFaculty EQUIV Person INTERSECTION AcademicStaff EXISTS teaches.(Course INTERSECTION EXISTS isTaughtBy.TOP)
I have a feeling that this is an incorrect representation as EXISTS isTaughtBy.TOP will connect an individual with itself via the chain x--teaches-->c--isTaughtBy-->x. Thus even if a faculty does not share a course with others, she will belong to the class CoTeachingFaculty.
Thus it is required to establish a chain x--teaches-->c--isTaughtBy-->y where x and y are different. Will it be possible to model this kind of situation in the Description Logic framework?
Yes, you are quite correct that your representation will not have the desired effect.
There are possibly 2 ways that I can think of that will achieve more-or-less what you want:
(1) Introduce a
coTeachesWithrole which is irreflexive and defineteachesasteaches \sqsubseteq coTeachesWith o teaches. In this way you can state that a lecturer co-teaches with another lecturer and from that you can infer that teach the same courses. The downside is that it will infer that all classes taught by this lecturer are also taught by the co-teaching lecturer - which is likely not what you want.(2) Another way is to use SWRL rules. With that you can provide a rule as follows:
teaches(?x, ?c) ^ teaches(?y, ?c) ^ differentFrom(?x, ?y) ->CoTeachingFaculty(?x) ^ CoTeachingFaculty(?y)Below I provide the OWL Manchester syntax for the ontology applying these 2 options:
Prefix: : http://www.henrietteharmse.com/turtorial/ontologies/DistinctIndividual# Prefix: owl: http://www.w3.org/2002/07/owl# Prefix: rdf: http://www.w3.org/1999/02/22-rdf-syntax-ns# Prefix: rdfs: http://www.w3.org/2000/01/rdf-schema# Prefix: xml: http://www.w3.org/XML/1998/namespace Prefix: xsd: http://www.w3.org/2001/XMLSchema#
PS. I did not set
teachesto be the inverse oftaughtBybecause thenteachesis no longer a simple role and then cannot be used in a role chain. For details see paper on SROIQ.