Review Summary: This submission needs major revision. It is not clear if the aim is to model a partitive relation between embedded xml elements to the relative parent element in general or in particular for the xsd:sequence element. In the second case the partOf property defined in DOLCE is not enough, better use the
Submission:Sequence pattern. In the first case the pattern should be focused on the xsd:all element instead. Additionally, a reengineering pattern for partitive relation in XML-based documents is more general then the XSD case, and probably should be approached at that level, focusing on XSD case in the example section.
Reviewer Confidence: The submission should be revised for the meaning described above. Anyway the problem of reengineering XML-based structures to patterns should be faced in the near future by the community. Revised properly, this proposal could be a good starting point.
Problems: This pattern is named XSD:Sequence embedding. The 'sequence' indicator in XSD means not only a group of element into another (as xsd:all or rdf:Bag), but implies also the fact that those elements must be in a particular order, and this order cannot change, or if it changes, or it is lost in the reengeneering process, the result is a loss of information (see, for example
[1]).
The semantic of the 'partOf' ObjectProperty defines pure meronimy relation. It is probably the good solution for representing the containment of one or more XML elements into another (also rdf:Bag could be reengineered in an ontology in the same way). In the XSD case, it can be used to reengineer the 'All' order indicator instead of the 'sequence' one.
Additionally, the example refers to the case in wich the order of the embedded elements is not important.
There are two possibilities:
1) The pattern should be renamed, removing the relation to the 'sequence' and changing it into 'meronimy' or 'partitive' relation, taking the example as meaningful
2) The sequence is a crucial point of this pattern, and this should be better motivated in the example and description of the process.
Community Relevance: The problem of reengineering XML-based structures to patterns should be faced in the near future by the community. A revised version of this pattern could have a place in that scenario.
Relation to Best Practices: Actually no relation to best practices. Also this point should be take into account in future revisions of this submissions.
Reusability: Not evaluable at the moment.
Overall Understandability: Actually the aim is not clear.
Clear Problem Description: As above.
Clear Relevance and Consequences: Not clear at the moment.
Clear Figures and Illustrations: Not evaluable at the moment.
Missing Information: A clear report about the usage and meaning of the xs:sequence element in XSD could be added.
