From Odp

Jump to: navigation, search

This is a property of type Text.

(previous 25) (next 25)

Pages using the property "HasMissingInformation"

Showing 20 pages using this property.


MathieuDAquin about DisjointnessOfComplement (DOC) +It is not clear where this pattern comes from, what makes the authors think it is common, etc. See also "Clear Relevance and Consequences"


OlafNoppens about Inverse n-ary relationship +Example in OWL
OlafNoppens about Symmetric n-ary relationship +As the pattern is related to the W3C n-ary relationship I suggest to use the same type of diagram and/or examples. Moreover, an example in OWL and/or OWL building blocks are missing.


RinkeHoekstra about Object with states +A discussion of design decisions with reference to the literature would really help engineers in choosing this pattern.


StefanoDavid about NegativePropertyAssertions +Overall documentation
StefanoDavid about OnlynessIsLoneliness (OIL) +ER/UML diagram


TimLebo about LicenseLinkedDataResources +1) Compared to related RELs The paper cla 1) Compared to related RELs The paper claims that the proposed pattern is conceived by extracting commonalities among the well-known Rights Expression Languages, but does not provide even a sketch of the mapping between the proposed pattern and the essential concepts in each of these other languages. In addition, the paper does not indicate the shortcomings of the well-known RELs or the advantages that the LLDR pattern provides. Why not just use the existing and well-known languages? 5) Relationship to Planning The research topic of AI planning centers around conditions and consequences, and seems to be extremely relevant to your concepts and requirements. The LLDR ontology should be compared and contrasted with this body or related work. 11) No concrete examples There should be concrete RDF/OWL examples available to illustrate *each* term proposed in the ontology. There are no examples provided. Beyond examples for illustration, where are the real examples of this pattern being used in the wild? In Linked Data, that should be easy to fulfill, since it can just be done and one can point to them. If there hasn't been a need compelling enough to actually solve a real problem, then is the pattern truly simple, useful, and worthwhile enough for others to adopt? and worthwhile enough for others to adopt?


ValentinaPresutti about Context Slices +Nothing to add with respect to the above comments.
ValentinaPresutti about NegativePropertyAssertions +figures, illustration, use cases, scenarios, consequences, proof.
VioletaDamjanovic about Classification scheme - path enumeration model - to Taxonomy +Parhaps some real usage of the proposed pattern can be found.
VojtechSvatek about ConceptTerms +Especially information (and examples) on compound non-preferred terms.
VojtechSvatek about Context Slices +As above.
VojtechSvatek about EventProcessing +Two missing classes in the diagram.
VojtechSvatek about Faceted Classification Scheme +Especially that on possible functionality of the object properties, see above.
VojtechSvatek about PeriodicInterval +See above.
VojtechSvatek about Reactor pattern +None aside what mentioned above.
VojtechSvatek about SimpleOrAggregated +As above


WimPeters about ConceptTerms +A scenario should be added, in which ideal A scenario should be added, in which ideally all classes come into play, in order to show why this particular constellation of simple/compound (non)prefered terms is necessary versus a more straightforward list of components model from LMF (see and The authors should be more specific about the way in which the re-engineering of this particular BS8723-2 fragment is incomplete. It omits the Equivalence relation between SimpleNonPreferredTerm and PreferredTerm. Also, the CompoundEquivalence relation between PreferredTerm and CompoundNonPreferredTerm is lacking. The model is available from from
WimPeters about Define Hybrid Class Resolving Disjointness due to Subsomption +There is no owl version of the pattern. Also, there is no scenario description.
WimPeters about Enlarge Class Definition for Resolving Disjointness due to Subsomption +there is no owl ontology, nor a scenario description
(previous 25) (next 25)
Personal tools
Quality Committee
Content OP publishers