(New page: {{Content OP Proposal Review Template |CreationDate=2009/9/8 |SubmittedBy=AlessandroAdamou |ContentOPUnderReview=DisjointnessOfComplement (DOC) |RevisionID=5597 |Score=0 - needs major revi...)
 
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
{{Content OP Proposal Review Template
 
{{Content OP Proposal Review Template
|CreationDate=2009/9/8
 
 
|SubmittedBy=AlessandroAdamou
 
|SubmittedBy=AlessandroAdamou
 
|ContentOPUnderReview=DisjointnessOfComplement (DOC)
 
|ContentOPUnderReview=DisjointnessOfComplement (DOC)
 
|RevisionID=5597
 
|RevisionID=5597
|Score=0 - needs major revision
+
|CreationDate=2009/9/8
 +
|Score=1 - needs minor revision
 
|ReviewSummary=The proposal looks sensible to me, but I do expect that other peers might believe it to be rather trivial, thus I would recommend it for discussion at WOP. It is however essential that this proposal is presented in such a way as to target naive developers.
 
|ReviewSummary=The proposal looks sensible to me, but I do expect that other peers might believe it to be rather trivial, thus I would recommend it for discussion at WOP. It is however essential that this proposal is presented in such a way as to target naive developers.
 
|ReviewConfidence=ODPs: medium/high
 
|ReviewConfidence=ODPs: medium/high
Line 11: Line 11:
 
|ReviewRelevance=This proposal could bring up some fruitful discussion during the workshop. I, for one, had never even thought about the very existence of such a pitfall in ontology engineering, and the first time I read it I was questioning the actual utility of such a pattern, though some more thorough analysis made me change my mind.
 
|ReviewRelevance=This proposal could bring up some fruitful discussion during the workshop. I, for one, had never even thought about the very existence of such a pitfall in ontology engineering, and the first time I read it I was questioning the actual utility of such a pattern, though some more thorough analysis made me change my mind.
 
|ReviewReusability=I'm reasonably sure it is unwittingly being used in many ontology design activities as I write. At least I hope so.
 
|ReviewReusability=I'm reasonably sure it is unwittingly being used in many ontology design activities as I write. At least I hope so.
|ReviewUnderstandability=Immediate for the knowledgeable ontology developer, but since the proposal is aimed at solving a trivial yet possibly frequent issue, maybe a step-by-step explanation "for dummies" on how to use it could help. See suggestions below.
+
|ReviewUnderstandability=Immediate for the knowledgeable ontology developer, but since the proposal is aimed at solving a trivial yet possibly frequent issue, maybe a step-by-step explanation "for dummies" on how to use it could help. See suggestions below.
 +
 
 +
In addition, at least one more ontology providing a solution example in English should be posted.
 
|ReviewClearProblem=This aspect should be developed in more detail. Please bear in mind that this description should be thorough enough to aid all ontology engineers, let alone the least experienced ones.
 
|ReviewClearProblem=This aspect should be developed in more detail. Please bear in mind that this description should be thorough enough to aid all ontology engineers, let alone the least experienced ones.
  
Since we are mentioning logical antipatterns, I think a couple of examples showing the bizarre consequences of a failure to apply such a pattern. Like, say, showing how statements such as :  
+
Since we are mentioning logical antipatterns, I think a couple of examples showing the bizarre consequences of a failure to apply such a pattern would help. Like, say, showing how statements such as :  
  
- SaltLake isEquivalentTo not FreshWaterLake
+
- SaltLake isEquivalentTo not FreshWaterLake<br>
- Balkhash isA SaltLake
+
- Balkhash isA SaltLake<br>
- SpiderMan isDifferentFrom Balkhash
+
- SpiderMan isDifferentFrom Balkhash<br>
  
 
then reasoning could infer that SpiderMan is a FreshWaterLake. Anyway, the more absurd and shocking the examples, the higher the chance for inexperienced ontology developers to get it right.
 
then reasoning could infer that SpiderMan is a FreshWaterLake. Anyway, the more absurd and shocking the examples, the higher the chance for inexperienced ontology developers to get it right.

Latest revision as of 22:32, 9 September 2009

{{#reviewabout:Submissions:DisjointnessOfComplement (DOC)|}}

Reviewer.png
Review Summary: The proposal looks sensible to me, but I do expect that other peers might believe it to be rather trivial, thus I would recommend it for discussion at WOP. It is however essential that this proposal is presented in such a way as to target naive developers.
Reviewer Confidence: ODPs: medium/high Description Logics: medium
Community Relevance: This proposal could bring up some fruitful discussion during the workshop. I, for one, had never even thought about the very existence of such a pitfall in ontology engineering, and the first time I read it I was questioning the actual utility of such a pattern, though some more thorough analysis made me change my mind.
Relation to Best Practices:
Relations to Other Patterns:
Overall Understandability: Immediate for the knowledgeable ontology developer, but since the proposal is aimed at solving a trivial yet possibly frequent issue, maybe a step-by-step explanation "for dummies" on how to use it could help. See suggestions below. In addition, at least one more ontology providing a solution example in English should be posted.
Clear Problem Description: This aspect should be developed in more detail. Please bear in mind that this description should be thorough enough to aid all ontology engineers, let alone the least experienced ones.

Since we are mentioning logical antipatterns, I think a couple of examples showing the bizarre consequences of a failure to apply such a pattern would help. Like, say, showing how statements such as :

- SaltLake isEquivalentTo not FreshWaterLake
- Balkhash isA SaltLake
- SpiderMan isDifferentFrom Balkhash

then reasoning could infer that SpiderMan is a FreshWaterLake. Anyway, the more absurd and shocking the examples, the higher the chance for inexperienced ontology developers to get it right.

Posted: 2009/9/8 Last modified: 2009/09/9

All reviews | Add a comment at the bottom of this page
The page [[Bootstrap:Footer]] was not found.