Property:HasClearRelevanceDescription

From Odp

Jump to: navigation, search

This is a property of type Text.


(previous 25) (next 25)

Pages using the property "HasClearRelevanceDescription"

Showing 25 pages using this property.

K

KarlHammar about LicenseLinkedDataResources +Relevance of the problem can partly be inferred from reading the bullet points under "Solution description", but this can be expanded upon and exemplified.

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
MariaPoveda about TransportPattern +Fair
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).

O

OlafNoppens about Literal Reification +good

R

RinkeHoekstra about OOPMetrics +Relevance is clear for OOP metrics, but not as a pattern.
RinkeHoekstra about Object with states +Consequences are not really made clear in the description. For instance, the assumption that states are distinct individuals is not sufficiently motivated nor discussed.
RinkeHoekstra about PeriodicInterval +Ok

S

StefanoDavid about NegativePropertyAssertions +They are not clearly stated, but intuitively understandable
StefanoDavid about OnlynessIsLoneliness (OIL) +yes

T

TimLebo about LicenseLinkedDataResources +8) Use of reasoning Despite being a submi 8) Use of reasoning Despite being a submission to the Ontology Patterns community, the LLDR proposal does not use any "useful" inference. The only inferences that are used define the structure that should be followed for assertion (and even that is incomplete and not usable). OWL allows us to share domain knowledge by exchanging domain-independent axioms that permit a non expert to determine what inferences can and should be applied to understand the domain. This is not the case for LLDR. The proposal provides merely terms and does not leverage any OWL reasoning to facilitate the understanding of the domain it is modeling. For example, "can not be used" is expressed in OWL using a restriction such as "max 0 on prov:used" and "obligated" is an inference in the form "If one does X, Y must also occur". This can be modeled in OWL, but I'm not going to provide the solution in this review. A satisfying solution for modeling the License of Linked Data Resources would be to provide axioms over the PROV notions of Agents, the kinds of Activities they perform (such as Distributing), and their use and generation of Entities (Works, Licenses, etc). See comment "Approachability for a licensing novice" below. oachability for a licensing novice" below.

V

ValentinaPresutti about Context Slices +It could be improved: see above
ValentinaPresutti about NegativePropertyAssertions +poor
VioletaDamjanovic about Classification scheme - path enumeration model - to Taxonomy +It is clear.
VojtechSvatek about Classification scheme - adjacency list model - to Taxonomy +Not much.
VojtechSvatek about ConceptTerms +Not much information about consequences.
VojtechSvatek about Context Slices +Yes, but the consequences could still be elaboreted a bit more.
VojtechSvatek about EventProcessing +The pattern is relatively simple, and its use doesn't seem to have dramatic consequences.
VojtechSvatek about Faceted Classification Scheme +Pretty relevant; the consequences are sketched but could be elaborated more.
VojtechSvatek about PeriodicInterval +Not quite clear consequences at the moment; alternative solutions should be explored.
VojtechSvatek about Reactor pattern +The consequences of pattern use are not properly discussed, as no modelling alternatives are compared.
VojtechSvatek about SimpleOrAggregated +Consequences not particularly analysed.
(previous 25) (next 25)
Personal tools
Quality Committee
Content OP publishers