Reviews:AldoGangemi about ConceptGroup

From Odp

Jump to: navigation, search

AldoGangemi about ConceptGroup (Revision ID: 5807)

Overall suggestion (score): 0 - needs major revision

Review Summary: The pattern tries to provide an OWL representation of a construct used to talk about groups of concepts or fragments of thesauri. I think the pattern is a valid contribution, but needs major revisions in documentation, axiomatization, and relation to other patterns.
Reviewer Confidence: High
Problems: The lack of a concrete example makes the pattern difficult to understand. From the technical viewpoint, there are some problems:

1) the object properties lack inverses: this is a bad practice; inGroup lacks an inverse at all, while BT is not made inverse of NT, and subGroup of superGroup 2) the reification of BT-NT, and subGroup-superGroup mught be due to the need of creating inverse object properties: in this case, this is a bad practice. If reifications are needed for other reasons, this is not clear

3) the structuringAssociationType object property seems used to link concept groups to the reification of BT-NT. Why is is needed? The use case behind this object property is unclear
Community Relevance: Fair
Relation to Best Practices: The pattern allows to represent groups of concepts, in that being a special case of the CollectionEntity pattern (Collection <- Group, Thing <- Concept, memberOf <- inGroup).

Moreover, it seems to encode also: a) a subgroup relation (could be kind of partof for collections) b) the BT relation (already existing in SKOS core, but could also be kind of specialization for concepts, see also Specialization and Classification patterns) c) a "membership restriction" class that is basically synonym to Group

I think this pattern can be represented in a simplier way (see Problems above)
Reusability: Good, if the problems are solved
Relations to Other Patterns: CollectionEntity can be specialized for the core part of this pattern.

Classification and Specialization are also related.

SKOS (potentially a content pattern has also overlaps).
Overall Understandability: Low
Clear Problem Description: Must be explained better
Clear Relevance and Consequences: Must be explained better
Clear Figures and Illustrations: Ok
Missing Information: Concrete example. I also suggest to load the annotations in the OWL file, not just on the portal.

Posted: 2009/9/12 Last modified: 2009/9/12

All reviews | Add a comment at the bottom of this page
Personal tools
Quality Committee
Content OP publishers