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.
G | |
|---|---|
| GerdGroener about DisjointnessOfComplement (DOC) + | medium |
| GerdGroener about Standard Enforcer Pattern + | The problem is clearly described. |
| GerdGroener about SynonymOrEquivalence (SOE) + | The problem is clearly described. |
H | |
| HenrikEriksson about Partition + | Currently, none at all. |
J | |
| JoseEmilioLabraGayo about LicenseLinkedDataResources + | The problem is clearly described. |
K | |
| KarlHammar about LicenseLinkedDataResources + | The problem that the pattern solves can be partly inferred from the intent field, but this could be expanded upon and exemplified. |
M | |
| MariCarmenSuarezFigueroa about ConceptTerms + | The problem is not clearly described, because author mention something about synonyms and translations, and this kind of features are not included in the paper. |
| MariCarmenSuarezFigueroa about Normalization + | The problem description is ok; however, I … The problem description is ok; however, I would like to comment that the problem example (with the figure) is not clear enough. I mean it is not clear the meaning of the first hierarchy and of the second; I assume 'classify' means to run a reasoner, but I think this should be explained in the pattern. k this should be explained in the pattern. |
| MariaPoveda about OOPMetrics + | Good |
| MariaPoveda about Template Instance + | Good |
| MariaPoveda about TransportPattern + | Good |
| MartaSabou about Partition + | Yes. |
| MartaSabou about SynonymOrEquivalence (SOE) + | Yes. |
| MartaSabou about Term-based thesaurus to lightweight ontology – record-based model + | Yes. |
| MathieuDAquin about ConceptGroup + | Not really. I don't in which scenario this helps. |
O | |
| OlafNoppens about Literal Reification + | good |
P | |
| PierluigiMiraglia about Term-based thesaurus to lightweight ontology – record-based model + | The problem should be described in more pr … The problem should be described in more practical terms, without prejudging the options. I think it would be better to formulate the problem faced by the "consumer" of the resulting resources, rather than state that the result must be a lightweight ontology. the result must be a lightweight ontology. |
R | |
| RimDJEDIDI about Classification scheme - adjacency list model - to Taxonomy + | In the "non-ontological resource descripti … In the "non-ontological resource description" property, it is stated that the considered classification is a rooted tree, so if this means that adjacency list cannot represent a graph, it should be mentioned explicitly to avoid ambiguity about cyclic relation. Besides, it should be made precise whether the re-engineering is specifically proposed to hierarchical classification adjacency list. In summary, it should be specified under what conditions the pattern is applicable. A proposition could be to add a property "Applicability" to pattern description template? cability" to pattern description template? |
| RinkeHoekstra about OOPMetrics + | Far to limited discussion |
| RinkeHoekstra about Object with states + | The problem is clear |
| RinkeHoekstra about PeriodicInterval + | Ok |
S | |
| StefanoDavid about NegativePropertyAssertions + | Yes |
| StefanoDavid about OnlynessIsLoneliness (OIL) + | No, it needs some rework. |
T | |
| TimLebo about LicenseLinkedDataResources + | The problem description was very broadly stated, and the "definition by examples" were insufficient to clearly show how they addressed each of objectives stated. |
V | |
| ValentinaPresutti about Context Slices + | It could be improved: see above |
