View source

{{Content OP Proposal Review Template
|SubmittedBy=CatherineRoussey
|ContentOPUnderReview=SimpleOrAggregated
|RevisionID=10064
|CreationDate=2010/9/10
|Score=0 - needs major revision
|ReviewSummary=I do not understand exactly what will be the purpose of this pattern and Which behavior the author expect from the reasoner. So I need more information to give a review.  

The main problem is the semantic of the aggregation property. There exist different partOf relationship and I need to know the relationship between the aggregation property and the partOf one...
|ReviewConfidence=I know the design pattern composite in software engineering...and the DUL ontology. The hasPart and isPartOf property has to be associated to this pattern.
|ReviewProblems=No information is given on the meaning of the aggregation property: 
is it a hasMember, hasPart, hasComponent property?
maybe the aggregation can be replace by any of them...
and does this property transitive or not?

Why do you thing that all the objects can be classified as a simple one or an aggregated one?
First I would rather fixe a subClassOf relationship between ObjectByCardinality and Object... Depend of the point of view (the scale) an object can be classified as simple or not...
An organ is a simple object or not? Organ is composed of cells and cell is composed of...

if an individual O has two aggregated Members O1 and O2 asserted in the ontology... Moreover if O1 is fixed as same as O2... what do you expect from the reasoner? What's happen if instead 02 is also an aggregatedMember of O1?
|ReviewClearProblem=This pattern is only applicable in certains conditions which are not well described ...
|ReviewClearRelevance=The consequence on individual are not well described.
If a whole is composed of  two aggregatedMembers which are fixed as equivalent, the whole is still classified as a aggregatedObject.
Is it what do you expect from the reasoner?

Moreover if the whole is classified as a simple Object and is composed of two objects that are equivalent to each other there are an unconsistency...
So I do no think that the reasoning about number of parts is possible with this pattern...
|ReviewMissing=the semantic of the aggregation property: hasAggregatedMember...
}}