From Odp

Jump to: navigation, search

This is a property of type Text.

(previous 25) (next 25)

Pages using the property "HasUnderstandability"

Showing 25 pages using this property.


AldoGangemi about ConceptGroup +Low
AlessandroAdamou about DisjointnessOfComplement (DOC) +Immediate for the knowledgeable ontology d 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. ution example in English should be posted.
AlessandroAdamou about Inverse n-ary relationship +Flawed. Could raise the score by one entire point if properly reformulated (see below).<br /> Watch out for a few typos : "patter" and "exits" in the motivation, "querys" in the problem example, "taht" in the consequences...
AlessandroAdamou about Object with states +The ontology and its members are annotated appropriately.
AlessandroAdamou about OnlynessIsLoneliness (OIL) +While the motivation, aim etc. should be q While the motivation, aim etc. should be quite clear to the seasoned knowledge engineer (who is less likely to incur in antipatterns, though), maybe the narrative should be thought of from the angle of the less experienced. The name of this proposal is very poetic and that's appreciated, but this can a double-edged sword. As an ontology engineer in training, it would never come to my mind that I could make use of this pattern in my everyday modelling activities. Also, we have an OIL acronym in the discipline of Web Ontologies since 2001, and I think such clashes should be avoided at least in the same research field. The motivation is clear enough, though maybe it should be a little more targeted at the naive ontology developer coming to the ODP portal to seek help. This holds for the DOC pattern as well. p. This holds for the DOC pattern as well.
AlessandroAdamou about Reactor pattern +The intent and implementation are very clear, sans the issues described in other fields.
AlessandroAdamou about Symmetric n-ary relationship +Fairly comprehensible, though it could use a less misleading name.
AndreaNuzzolese about Faceted Classification Scheme +Good
AndreaNuzzolese about Normalization +The example figure is not so clear and self-explained. I suggest to add some lines to explain how and where restrictions and disjointess clauses are added.


BenedictoRodriguezCastro about Object with states 2 +The understandability of the pattern is acceptable but it can be highly improved as per comments in sections: - "Relation to Other Patterns", - "Clear Relevance and Consequences", - "Clear Figures and Illustrations", and - "Missing information".
BenedictoRodriguezCastro about Template Instance +There is opportunity to improve the understandability by providing a concrete example of the pattern in addition to the abstract one.
BenedictoRodriguezCastro about TransportPattern +See section "Review Summary".
BorisVillazón-Terrazas about Define Hybrid Class Resolving Disjointness due to Subsomption +Medium
BorisVillazón-Terrazas about Faceted Classification Scheme +Good
BorisVillazón-Terrazas about Normalization +Good presentation, but it can be improved, according to the suggestion given in the review summary.
BorisVillazón-Terrazas about Standard Enforcer Pattern +The pattern needs to be explained in a better way. Also the author needs to improve the description of the uses cases.
BorisVillazón-Terrazas about TransportPattern +Good
BorisVillazón-Terrazas about Xsd:sequence embedding +Low


EnricoDaga about Xsd:sequence embedding +Actually the aim is not clear.
EnricoMotta about Context Slices +The description of the pattern says: “In The description of the pattern says: “In RDF and other binary relation languages (like object oriented languages and description logics), one typical way to represent that a binary relation holds in some context is to "reify" the relation-holding (sometimes called obtainment) in the context as an object with a binary relation between the obtainment and each the two relation arguments and a third binary relation between the obtainment and an object representing the context itself. The downside to this approach is the expressive ability of the language to describe the binary relation, especially in the case of description logics, is lost.” Actually, this is not completely clear. The standard way to do reification in RDF is simply to reformulate a triple using the built-in RDF support. This allows then one to make statements about a triple, such as <triple1, holds, context1>. However, reifying a triple is an additional operation to representing the original statement, e.g., <Sam, ceoOf, IBM>, hence it is not clear why the proposed pattern is an improvement in this respect, given that also a reification-based solution permits to model the original domain-level relation – in this case, ceoOf. Another thing that hampers understanding is that the term 'obtainment' does not seem to be a standard one in the literature. I could not find any use of it and indeed, even the referenced paper by Welty and Fikes does not use this term!!! Hence, it is difficult for the reader to completely understand the obtainment-based alternative and I suggest that this part is clarified. It is also not clear whether having two IBMs and two Sams in the model causes potential problems. Can one say <sam@c1 sameAs sam>? Probably not. But then how do I retrieve all properties of Sam? Related to the above point, it is also unclear what is the semantics of projectionOf. ear what is the semantics of projectionOf.
EnricoMotta about Literal Reification +The pattern is reasonably easy to understand although the description, context and motivation are rather minimalist


FrancoisScharffe about Classification scheme - adjacency list model - to Taxonomy +Overall very understandable.
FrancoisScharffe about ConceptGroup +Okay
FrancoisScharffe about Enlarge Class Definition for Resolving Disjointness due to Subsomption +High for problem description, medium for solution


GerdGroener about Classification scheme - path enumeration model - to Taxonomy +good
(previous 25) (next 25)
Personal tools
Quality Committee
Content OP publishers