Property:HasClearProblemDescription
From Odp
This is a property of type Text.
(previous 25) (next 25)
Pages using the property "HasClearProblemDescription"
Showing 25 pages using this property.
A | |
|---|---|
| AldoGangemi about ConceptGroup + | Must be explained better |
| AlessandroAdamou about DisjointnessOfComplement (DOC) + | This aspect should be developed in more de … 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<br /> - Balkhash isA SaltLake<br /> - 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. enced ontology developers to get it right. |
| AlessandroAdamou about Inverse n-ary relationship + | The problem is better described in the exa … The problem is better described in the example than in the motivation. The three reasons for using this pattern are not very clear at all: what does it mean that a relationship "is really amongst" several things and that it "really needs" a further argument? Are these three conditions supposed to hold altogether? It looks like that.<br /> On the other hand, the aim to speed up frequent queries is comprehensible. eed up frequent queries is comprehensible. |
| AlessandroAdamou about Object with states + | Competency questions are not formulated according to standards, but the intent and solution description are reasonably clear. |
| AlessandroAdamou about OnlynessIsLoneliness (OIL) + | Again, a real-world example should be incl … Again, a real-world example should be included directly in the pattern description, and not entirely deferred to the example ontology (which, by the way, non-Spanish speakers may have some trouble interpreting). With that said, the abstract example is fine as it is. id, the abstract example is fine as it is. |
| AlessandroAdamou about Reactor pattern + | Clear, but it seems to tackle two problems, i.e. parametric processes and cause/effect relations. Content Patterns should be atomic solutions whenever possible. |
| AlessandroAdamou about Symmetric n-ary relationship + | From a purely OWL perspective, this proble … From a purely OWL perspective, this problem seems to come into play when datatype properties are involved, while for object properties it should suffice to set the symmetric flag. This distinction should be pointed out, otherwise an explanation why it is not pertinent to the datatype/object property pair should be given. type/object property pair should be given. |
| AndreaNuzzolese about Faceted Classification Scheme + | Good. |
B | |
| BenedictoRodriguezCastro about Object with states 2 + | The description of the problem is clear. |
| BenedictoRodriguezCastro about Template Instance + | The problem can be also better characterized by giving a clear real world example of the modelling problem addresed. |
| BenedictoRodriguezCastro about TransportPattern + | See section "Review Summary". |
| BorisVillazón-Terrazas about Define Hybrid Class Resolving Disjointness due to Subsomption + | Yes |
| BorisVillazón-Terrazas about Faceted Classification Scheme + | Good |
| BorisVillazón-Terrazas about Normalization + | Good |
| BorisVillazón-Terrazas about Standard Enforcer Pattern + | The problem is clearly described. |
| BorisVillazón-Terrazas about TransportPattern + | Good |
| BorisVillazón-Terrazas about Xsd:sequence embedding + | Not clear |
C | |
| CatherineRoussey about SimpleOrAggregated + | This pattern is only applicable in certains conditions which are not well described ... |
E | |
| EnricoDaga about Xsd:sequence embedding + | As above. |
| EnricoMotta about Context Slices + | The problem description is reasonably clea … The problem description is reasonably clear. However, because the example used is "Chris believes..." and the "Chris believes" bit is not actually represented, it would be useful to clarify explicitly whether this solution is adequate to model the different beliefs of different people, or whether "Chris believes" is simply considered as an atomic context and more machinery (i.e., more patterns) would be needed if we also want to add an entity called Chris to the model and relate this to his beliefs. the model and relate this to his beliefs. |
| EnricoMotta about Literal Reification + | I think the scenario could be made clearer and more meaningful by showing how to link tags to the owl entities denoting the same object as the tag |
F | |
| FrancoisScharffe about Classification scheme - adjacency list model - to Taxonomy + | yes |
| FrancoisScharffe about ConceptGroup + | Okay |
| FrancoisScharffe about Enlarge Class Definition for Resolving Disjointness due to Subsomption + | It is clearly described. |
G | |
| GerdGroener about Classification scheme - path enumeration model - to Taxonomy + | medium |
