Property:HasClearRelevanceDescription
From Odp
This is a property of type Text.
(previous 25) (next 25)
Pages using the property "HasClearRelevanceDescription"
Showing 25 pages using this property.
A | |
|---|---|
| AldoGangemi about ConceptGroup + | Must be explained better |
| AlessandroAdamou about DisjointnessOfComplement (DOC) + | As per problem description, the authors should display how such bizarre phenomena should not occur if disjointness is used instead. |
| AlessandroAdamou about Inverse n-ary relationship + | Clear if we don't take into account that the "bridge" property pair does not show a connection to those between the main participants and the n-ary relationship class. |
| AlessandroAdamou about OnlynessIsLoneliness (OIL) + | Perhaps ontology developers should be help … Perhaps ontology developers should be helped a little more in finding out when this patterns applies to their case. The authors suggest to replace two or more anonymous classes with a single one "if it makes sense", but not everyone might have a clue as to when it makes sense and when it doesn't. If the statements can be considered equivalent (which is my impression), then this should be made clear, otherwise an example, describing how different facts can be inferred from using different methods, is needed. d from using different methods, is needed. |
| AlessandroAdamou about Reactor pattern + | Clear. Thers's one extra newline in the "Consequences" field. |
| AlessandroAdamou about Symmetric n-ary relationship + | As stated earlier, this proposal seems to be generating side effects with rspect to redundancy. If the authors can rule out these side effects, they should make a clearer statement about them. |
| AndreaNuzzolese about Faceted Classification Scheme + | High. |
B | |
| 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 Xsd:sequence embedding + | Not clear |
C | |
| CatherineRoussey about SimpleOrAggregated + | The consequence on individual are not well … The consequence on individual are not well described. If a whole is composed of two aggregatedMembers which are fixed as equivalent, the whole is still classified as a aggregatedObject. Is it what do you expect from the reasoner? Moreover if the whole is classified as a simple Object and is composed of two objects that are equivalent to each other there are an unconsistency... So I do no think that the reasoning about number of parts is possible with this pattern... of parts is possible with this pattern... |
E | |
| EnricoDaga about Xsd:sequence embedding + | Not clear at the moment. |
F | |
| FrancoisScharffe about Classification scheme - adjacency list model - to Taxonomy + | Not clear. Please state this pattern is only valid if the adjacency list supposes a subsumption between the entities. |
| FrancoisScharffe about ConceptGroup + | Here it misses a statement about the pattern usage together with SKOS |
| FrancoisScharffe about Enlarge Class Definition for Resolving Disjointness due to Subsomption + | Relevance is clear. However logical consequences of enlarging definition is a bit obscure. |
G | |
| GerdGroener about Classification scheme - path enumeration model - to Taxonomy + | medium |
| GerdGroener about DisjointnessOfComplement (DOC) + | medium |
| GerdGroener about SynonymOrEquivalence (SOE) + | The relevance of the pattern and its benefits are given. |
H | |
| HenrikEriksson about Partition + | No. |
L | |
| LuigiIannone about OnlynessIsLoneliness (OIL) + | Something more could be said in the motivation about the consequences that using the wrong solution (anti-pattern) could have in terms of consistency of the ontology and satisfiability of its classes |
M | |
| MariaPoveda about OOPMetrics + | Good |
| MartaSabou about Partition + | Not specified. |
| MathieuDAquin about ConceptGroup + | Not really. |
| MathieuDAquin about DisjointnessOfComplement (DOC) + | Not really, as it is not explained how to … Not really, as it is not explained how to detect where this anti-pattern applies (when it is used incorrectly). Not appropriate explanation of the consequences of using this one instead of the solution (can be easily understood for users familiar with DLs, but probably not by others). iar with DLs, but probably not by others). |
