Re: [foaf-dev] How to handle multiple cognitive characteristics on the same topic?

Hello again,

I came up with a probably appropriated solution of my addressed concern, 
to describe something by using a "shortcut relation" (a simple triple/ a 
statement) and if possible also as a detailed description of this 
relation, and to provide a semantic relation between these two modelling 
types.
It is an extension of the Property Reification Vocabulary proposal from 
[1], which can be found here[2].
It reflects in general an outsourcable (and hence optional evaluable) 
modelling approach, which was made by Toby Inkster (see [3]). This 
modelling approach was extended to loosen the mapping from a "shortcut 
relation" property to a specific reification class and hence enabling 
the opportunity to reuse one reification class for several property 
reification definitions. So it goes beyond modelling cases, which can 
also be addressed more or less by an owl:propertyChainAxiom.
As proof-of-concept-example I modelled appropriated property reification 
definitions for the Cognitive Characteristics Ontology (see [4]). 
Therefore, I needed also to introduce a new version of the Cognitive 
Characteristics Ontology[5] that includes a property 
(cco:characteristic) to address the applied cognitive characteristic in 
the cognitive characteristic description.

What do you think about this approach?

Cheers,


Bob

[1] http://esw.w3.org/PropertyReificationVocabulary
[2] http://smiy.sourceforge.net/prv/spec/propertyreification.html
[3] 
http://esw.w3.org/PropertyReificationVocabulary#Possible_Use_Case_-_Change_logs
[4] http://purl.org/ontology/prv/propertyreification.html#sec-cco-example
[5] http://smiy.sourceforge.net/cco/spec/cognitivecharacteristics.html

Am 22.09.2010 15:22, schrieb Bob Ferris:
> Hi,
>
> I experimented a bit more with the quadrupel approach (Named Graph /
> N-Quad). I remodeled the Named Graph proposal[1], so that the detailed
> description of the "shortcut relation" is now outsourced into the Named
> Graph instance description[2].
> I also tried to apply N-Quads[3] here, which may result in the semantics
> as the new Named Graph proposal.
> Furthermore, I would tend to use the N-Quads approach here, because it
> states, from my point of view, a bit more the context relation, where
> the Named Graph approach is more intended to represent further
> provenance descriptions. One can also see the detail descriptions of a
> cognitive characteristic as provenance information of the "shortcut
> relation", but maybe we should differ somehow between this type of
> provenance information and "common" provenance information, e.g.
> modification date, author, information service etc.
> This let me also think about the quintuple approach again. That means,
> to be more concrete: a combination of the Named Graph and the N-Quads
> approach, where the context of the N-Quad represents the reification of
> the relation represented by the related triple and the surrounding Named
> Graph represents the "common" provenance information. Would you agree
> with that modelling?
>
> Cheers,
>
>
> Bob
>
> [1] http://smiy.sourceforge.net/cco/examples/N3/cco_-_football_example.trig
> [2]
> http://smiy.sourceforge.net/cco/examples/N3/cco_-_football_example_02.trig
> [3] http://smiy.sourceforge.net/cco/examples/N3/cco_-_football_example.nq
>
> Am 22.09.2010 12:50, schrieb Bob Ferris:
>> Hi,
>>
>> until yesterday, I thought that the expressiveness of the Cognitive
>> Characteristics Ontology[1] would also include the use case of handling
>> multiple cognitive characteristics on the same topic. However, today I
>> noticed a problem with that modelling. Now, I'm looking forward for an
>> elegant solution.
>> The problem can be illustrated in the following example (see also [2]):
>>
>> ex:APerson
>> 	a foaf:Person , cv:Person ;
>> 	foaf:name "John Wayne" ;
>> 	cco:skill<http://dbpedia.org/resource/Football_(soccer)>   ;
>> 	cco:expertise<http://dbpedia.org/resource/Football_(soccer)>   ;
>> 	cco:interest<http://dbpedia.org/resource/Football_(soccer)>   ;
>> 	cco:habit [
>> 		a cco:CognitiveCharacteristic ;
>> 		cco:topic<http://dbpedia.org/resource/Football_(soccer)>   ;
>> 		wo:weight [
>> 			a wo:Weight ;
>>          		wo:weight_value 6.0 ;
>>          		wo:scale ex:AScale
>>          		] ;
>>          	cco:activity
>> <http://sw.opencyc.org/concept/Mx4rwJRiEpwpEbGdrcN5Y29ycA>
>> 		] ;
>> 	cco:habit [
>> 		a cco:CognitiveCharacteristic ;
>> 		cco:topic<http://dbpedia.org/resource/Football_(soccer)>   ;
>> 		wo:weight [
>> 			a wo:Weight ;
>>          		wo:weight_value 7.0 ;
>>          		wo:scale ex:AScale
>>          		] ;
>> 		] ;
>> 	cco:habit [
>> 		a cco:CognitiveCharacteristic ;
>> 		cco:topic<http://dbpedia.org/resource/Football_(soccer)>   ;
>> 		wo:weight [
>> 			a wo:Weight ;
>>          		wo:weight_value 5.0 ;
>>          		wo:scale ex:AScale
>>          		] ;
>>          	cco:activity
>> <http://sw.opencyc.org/concept/Mx4rwO0J55wpEbGdrcN5Y29ycA>   .
>> 		] .
>>
>> A person, who has 3 cognitive patterns with the topic soccer - a skill,
>> an expertise and an interest. However, the activity vary re. these
>> cognitive patterns. The activity
>>
>> - re. the skill should be playing
>> (http://sw.opencyc.org/concept/Mx4rwJRiEpwpEbGdrcN5Y29ycA) ->   hence
>> "soccer playing"
>> - re. the expertise is not set, it should simple express that the person
>> has some "knowledge of soccer" (e.g. soccer rules)
>> - re. the interest should be watching
>> (http://sw.opencyc.org/concept/Mx4rwO0J55wpEbGdrcN5Y29ycA) ->   hence,
>> "soccer watching"
>>
>> So I tried to apply Named Graphs (again). That means, I separated each
>> "shortcut relation" with its detail description (see also [3]):
>>
>> ex:APerson
>> 	a foaf:Person ;
>> 	foaf:name "John Wayne" .
>> 	
>> ex:NG1 {
>> 	ex:APerson 	
>> 		cco:skill<http://dbpedia.org/resource/Football_(soccer)>   ;
>> 		cco:habit [
>> 			a cco:CognitiveCharacteristic ;
>> 			cco:topic<http://dbpedia.org/resource/Football_(soccer)>   ;
>> 			wo:weight [
>> 				a wo:Weight ;
>>          			wo:weight_value 6.0 ;
>>          			wo:scale ex:AScale
>>          			] ;
>>          		cco:activity
>> <http://sw.opencyc.org/concept/Mx4rwJRiEpwpEbGdrcN5Y29ycA>
>> 			] .
>> 		}
>> 		
>> ex:NG2 {
>> 	ex:APerson		
>> 		cco:expertise<http://dbpedia.org/resource/Football_(soccer)>   ;
>> 		cco:habit [
>> 			a cco:CognitiveCharacteristic ;
>> 			cco:topic<http://dbpedia.org/resource/Football_(soccer)>   ;
>> 			wo:weight [
>> 				a wo:Weight ;
>>          			wo:weight_value 7.0 ;
>>          			wo:scale ex:AScale
>>          			] ;
>> 			] .
>> 		}
>> 		
>> ex:NG3 {
>> 	ex:APerson		
>> 		cco:interest<http://dbpedia.org/resource/Football_(soccer)>   ;
>> 		cco:habit [
>> 			a cco:CognitiveCharacteristic ;
>> 			cco:topic<http://dbpedia.org/resource/Football_(soccer)>   ;
>> 			wo:weight [
>> 				a wo:Weight ;
>>          			wo:weight_value 5.0 ;
>>          			wo:scale ex:AScale
>>          			] ;
>>          		cco:activity
>> <http://sw.opencyc.org/concept/Mx4rwO0J55wpEbGdrcN5Y29ycA>
>> 			] .
>> 	}
>>
>> Further proposals are:
>>
>> - entail only the "shortcut relation" into a named graph and related the
>> detail description directly to the named graph, e.g. ex:NG1 cco:habit [
>> ... ]
>> - introduce a further property with a domain of
>> cco:CognitiveCharacteristic, which directs to the applied cognitive
>> characteristic, e.g. ex:CC1 cco:applied_cognitive_characteristic cco:skill
>> 	->   then we might somehow fall back to the "standard" 		
>> 	reification approach (subject relation ->   cco:agent/cco:habit; 	
>> 	predicate relation ->   cco:applied_cognitive_characteristic;
>> 	object relation ->   cco:topic)
>> - we can introduce further sub classes of cco:CognitiveCharacteristic,
>> which reflect the specific cognitive characteristics, e.g. cco:Skill for
>> cco:skill, and define further specific property chain axioms for them
>> 	->   this would end up in a parallel hierarchy, which is, as far 	
>> 	as I know, not a good design
>>
>> I have the feeling, that we need some proper Named Graph / Quad
>> semantics, or?
>>
>> Cheers,
>>
>>
>> Bob
>>
>>
>> [1] http://smiy.sourceforge.net/cco/spec/cognitivecharacteristics.html
>> [2] http://smiy.sourceforge.net/cco/examples/N3/cco_-_football_example.n3
>> [3]
>> http://smiy.sourceforge.net/cco/examples/N3/cco_-_football_example_-_w_named_graphs.n3