Property:HasUnderstandability
From Odp
This is a property of type Text.
(previous 25) (next 25)
Pages using the property "HasUnderstandability"
Showing 25 pages using this property.
G | |
|---|---|
| GerdGroener about DisjointnessOfComplement (DOC) + | medium |
| GerdGroener about Inverse n-ary relationship + | Could be improved: Firstly, I would use the same type of diagram as on the W3C page. Secondly, I suggest to give an example with a diagram for your pattern. Moreover, I would use one of the examples that are given on the W3C page. |
| GerdGroener about SimpleOrAggregated + | See the comment above (Problems) |
| GerdGroener about Standard Enforcer Pattern + | The graphical representation (Figure 1) and the textual explanation of the pattern could be improved. |
| GerdGroener about SynonymOrEquivalence (SOE) + | The motivation of the pattern is well written. Unfortunately there is a breakup in the text. The overall description of the pattern is well understandable. |
H | |
| HenrikEriksson about Partition + | Fundamentally, the pattern is easy to understand. However, the current description is unclear which makes the pattern more difficult to understand. |
J | |
| JoseEmilioLabraGayo about LicenseLinkedDataResources + | The pattern lacks some fields in the description that could improve its understandability. A good set of examples and use scenarios could help its adoption. |
K | |
| KarlHammar about LicenseLinkedDataResources + | Due to the lack of many fields, the pattern is difficult to understand as here posted (i.e. without access to the WOP 2013 pattern summary paper). I would strongly urge the authors to spend some time on developing this pattern page. |
L | |
| LuigiIannone about OnlynessIsLoneliness (OIL) + | Rewording the Aim section will avoid confusion between the anti-pattern and the proposed solution. Commenting the problem example with more text in addition to the OWL could certainly improve the understandability of the pattern. |
M | |
| MariCarmenSuarezFigueroa about Literal Reification + | In general the pattern is well understood; however, I would recommend to include some known uses of this kind of solution as well as some examples in which this pattern should be used. |
| MariCarmenSuarezFigueroa about Normalization + | In general the pattern is well explained. |
| MariaPoveda about OOPMetrics + | Even though the understandability is good, it would be advisable to explain in more detail the solution description. |
| MariaPoveda about Template Instance + | Medium |
| MariaPoveda about TransportPattern + | The pattern is not described in detail in the wiki page, it is difficult to understand it without the corresponding paper. |
| MartaSabou about SynonymOrEquivalence (SOE) + | Good. |
| MartaSabou about Term-based thesaurus to lightweight ontology – record-based model + | Good. |
| MathieuDAquin about ConceptGroup + | Low |
| MathieuDAquin about DisjointnessOfComplement (DOC) + | OK, except that most of the necessary is missing. |
| MathieuDAquin about Xsd:sequence embedding + | There is a lot of description, but it doesn't help a lot in understanding how the pattern can be used. |
O | |
| OlafNoppens about Literal Reification + | good |
P | |
| PierluigiMiraglia about Term-based thesaurus to lightweight ontology – record-based model + | Excellent |
R | |
| RimDJEDIDI about Classification scheme - adjacency list model - to Taxonomy + | The pattern description is understandable. … The pattern description is understandable. May be for documentation purpose and to facilitate its reuse particularly for novice or learner users, it would be more clear to add a definition for the different parameters used in the process at the beginning of its description. ocess at the beginning of its description. |
| RimDJEDIDI about Faceted Classification Scheme + | Easy to understand with clear details. |
| RinkeHoekstra about OOPMetrics + | Ok |
| RinkeHoekstra about Object with states + | The pattern is understandable (the problem it tries to solve is clear), but it is formally underspecified. |
