From Odp

Jump to: navigation, search

This is a property of type Text.

(previous 25) (next 25)

Pages using the property "HasMissingInformation"

Showing 25 pages using this property.


AldoGangemi about ConceptGroup +Concrete example. I also suggest to load the annotations in the OWL file, not just on the portal.
AlessandroAdamou about DisjointnessOfComplement (DOC) +Nothing I haven't pointed out already.
AlessandroAdamou about Object with states +The link to the example usage in Known Usage should appear in the field "Examples (OWL files)". Other than that, missing information is a consequence of the pattern not having been related to other ODPs.
AlessandroAdamou about OnlynessIsLoneliness (OIL) +Nothing that hasn't been mentioned already Nothing that hasn't been mentioned already. To sum it up: - A concrete example right in the pattern description, possibly accompanied with its ontology diagram<br /> - A reference to an example ontology in English (or at least with English RDFS annotations)<br /> - A clear statement on the consequences of adopting the pattern rather than the antipattern, if any. If there are no differences, that should be made explicit. differences, that should be made explicit.
AlessandroAdamou about Reactor pattern +- Labels and comments for most entities - - Labels and comments for most entities - There is a scenario annotation in the ontology - It would be good to add a more elaborate version of it to the "Scenarios" section of the pattern page (not just the field in the general description). - The OntoMDL implementation should be mentioned (with a link to the ontology) in the "Known Uses" field. - I personally would suggest that Content Patterns start to use OWL 2 version IRI, given that they are subject to refinement -> versioning. Please note that version IRIs should resolve to the specific version of the ontology, while the ontology IRI should resolve to the latest stable release. ould resolve to the latest stable release.


BenedictoRodriguezCastro about Object with states 2 +Firstly, see sections: - "Relation to Oth Firstly, see sections: - "Relation to Other Patterns", - "Overall Understandability", - "Clear Relevance and Consequences", - "Clear Figures and Illustrations", and And one more consideration. A known use case is provided in the form of an alm-istack.owl file. Please, consider providing a textual description to highlight the main aspects of this particular known use case with respect to the proposed pattern. At a glance, it seems that the pattern is instantiated several times in the .owl use case provided. Consider describing these different instantiations and how the main generic elements have been populated. main generic elements have been populated.
BenedictoRodriguezCastro about Template Instance +In addition to the various issues mentione In addition to the various issues mentioned throughout the review, the authors refer to the notion of "immutable" to mark the "template instance" via an annotation property. This is a very interesting aspect of the pattern and ideally it would be great if it could be discussed in greater detail, for example, how could this aspect of the pattern be conveyed to potential third-party consumer applications of the ontology? rty consumer applications of the ontology?
BenedictoRodriguezCastro about TransportPattern +See section "Review Summary".
BorisVillazón-Terrazas about Define Hybrid Class Resolving Disjointness due to Subsomption +Perhaps some "real" usage of the proposed pattern can be found.
BorisVillazón-Terrazas about Normalization +The owl file of the input ontology and the resultant ontology after applying the pattern. Also, it would be good to include in the example a disjoint relation.
BorisVillazón-Terrazas about Standard Enforcer Pattern +Use case/Scenario
BorisVillazón-Terrazas about Template Instance +The pattern is missing a real application example.
BorisVillazón-Terrazas about TransportPattern +You neeed to improve the use case scenario.


CatherineRoussey about SimpleOrAggregated +the semantic of the aggregation property: hasAggregatedMember...


EnricoDaga about Xsd:sequence embedding +A clear report about the usage and meaning of the xs:sequence element in XSD could be added.
EnricoMotta about Literal Reification +How do I link the tag :parisTag2 in your scenario to


FrancoisScharffe about Classification scheme - adjacency list model - to Taxonomy +Already mentioned
FrancoisScharffe about ConceptGroup +The pattern description misses an example instanciation.
FrancoisScharffe about Enlarge Class Definition for Resolving Disjointness due to Subsomption +relation to 'Define Hybrid Class Resolving relation to 'Define Hybrid Class Resolving Disjointness due to Subsumption' pattern, dicussion about logical and modelling consequences of this solution, argumentation wrt. the other solution ('Define Hybrid Class Resolving Disjointness due to Subsumption') to the same problem s due to Subsumption') to the same problem


GerdGroener about SynonymOrEquivalence (SOE) +Provide simple examples: ontology + description.


HenrikEriksson about Partition +Problem description, examples, figures.


JoseEmilioLabraGayo about LicenseLinkedDataResources +There is a lack of several fields in the description, specially the examples field.


KarlHammar about LicenseLinkedDataResources +Competency questions, consequences, scenarios, solution description..


MariaPoveda about TransportPattern +Diagram Scenarios Web references Examples Related CPs
MathieuDAquin about ConceptGroup +example of usage, clear description/definition of the entities.
(previous 25) (next 25)
Personal tools
Quality Committee
Content OP publishers