http://ontologydesignpatterns.org/index.php?action=history&feed=atom&title=Reviews%3AVojtechSvatek_about_SimpleOrAggregated 2026-04-25T10:42:12Z Revision history for this page on the wiki MediaWiki 1.25.6 http://ontologydesignpatterns.org/index.php?title=Reviews:VojtechSvatek_about_SimpleOrAggregated&diff=10120&oldid=prev 2010-09-16T21:29:55Z

<p>New page: {{Content OP Proposal Review Template |CreationDate=2010/9/16 |SubmittedBy=VojtechSvatek |ContentOPUnderReview=SimpleOrAggregated |RevisionID=10097 |Score=1 - needs minor revision |ReviewS...</p> <p><b>New page</b></p><div>{{Content OP Proposal Review Template<br /> |CreationDate=2010/9/16<br /> |SubmittedBy=VojtechSvatek<br /> |ContentOPUnderReview=SimpleOrAggregated<br /> |RevisionID=10097<br /> |Score=1 - needs minor revision<br /> |ReviewSummary=A reasonable pattern with somewhat imprecise description.<br /> |ReviewConfidence=The pattern is quite generic and I feel confident to judge it.<br /> |ReviewProblems=There is at least one inadequacy in the pattern description. The author claims to model that an aggregated individual is &quot;made up of several individuals of the same concept&quot;. This is however clearly not (necessarily) the case, as there is no guarantee that the individuals gathered in an aggregated object are of the same class within themselves and/or wrt. the aggregated object!<br /> For each specialization of this pattern, such a requirement would have to be stated explicitly, i.e. not inherited from the pattern itself.<br /> <br /> There is a typo: instanciate. I also wonder if Spanish translations within the Elements descriptions are not a bit distracting.<br /> <br /> |ReviewRelevance=The pattern is relevant.<br /> |ReviewBestPractice=Could be seen as best practice.<br /> |ReviewReusability=Medium.<br /> |ReviewRelations=I would expect a reference to http://www.w3.org/2001/sw/BestPractices/OEP/SimplePartWhole/.<br /> <br /> Importantly, the submitted pattern is based upon a more generic pattern that I have not come across yet: using different mutually equivalent classes to model different partitions (here, the distinction between 'simple' and 'aggregated') of the given class. This pattern should be either explicitly references (if already published) or submitted separately. Interestingly, this pattern may be used for a similar purpose as another submitted pattern, called Normalization: both can be used to dismantle a complex (possibly, multi-)hierarchy.<br /> <br /> I also wonder if the Object class can be considered similar as the Object class e.g. in the ObjectRole pattern.<br /> |ReviewUnderstandability=OK<br /> |ReviewClearProblem=OK<br /> |ReviewClearRelevance=Consequences not particularly analysed.<br /> |ReviewFigures=OK<br /> |ReviewMissing=As above<br /> }}</div>

VojtechSvatek