Modelling Postures (was: Property individuals used differently)
Property individuals used differently See also the slideset on the sharepoint
There is an inconsistency in what the individuals of saref:Property actually mean. In issue #x we saw that two modelling paradigms are used, but within the paradigm of using individuals differences exist. A comparison between LightProperty from saref4envi and Posture from saref4ehaw can exemplify.
- s4envi:LightProperty (abbreviated example)
:LightProperty rdf:type owl:Class ;
rdfs:subClassOf saref:Property ;
rdfs:comment "An aspect of light that can be observable by a sensor."@en ;
rdfs:label "Light property"@en .
:Luminiscence rdf:type owl:NamedIndividual, :LightProperty .
:Phosphorescence rdf:type owl:NamedIndividual, :LightProperty .
:ReflectionOfLight rdf:type owl:NamedIndividual, :LightProperty .
:ScatteringOfLight rdf:type owl:NamedIndividual, :LightProperty .
- s4ehaw:Posture (abbreviated example)
s4ehaw:Posture rdf:type owl:Class ;
rdfs:subClassOf saref:Property ;
rdfs:comment "The posture of a health actor (mainly a patient or a user), e.g. exercising, lying, running, sitting, walking..."@en ;
.
s4ehaw:Exercising rdf:type owl:NamedIndividual, s4ehaw:Posture .
s4ehaw:Lying rdf:type owl:NamedIndividual, s4ehaw:Posture .
s4ehaw:Running rdf:type owl:NamedIndividual, s4ehaw:Posture .
s4ehaw:Sitting rdf:type owl:NamedIndividual, s4ehaw:Posture .
s4ehaw:Walking rdf:type owl:NamedIndividual, s4ehaw:Posture .
The difference is that saref4envi interprets the Property individuals as more specific types of properties concerning light, whereas s4ehaw seems to interpret the Property individuals as codelist elements covering the values of the property.
The s4ehaw:Posture is the odd-one-out in this case. All other extensions interpret subclasses/individuals also as more specific types of the property.
Result: This issue can be closed with a decision on which modelling choice is appropriate.