I notice that some on the TC react to this comment as an indication that the use of the Relax NG schema combine attribute is not permissible. I think it is more like "combine attribute considered harmful" because it means that the constituents of an element are not found locally. It is like using goto in programming, rather than a structured form where the interdependencies are more cohesive. On the other hand, it supported the integration of schema fragments in the narrative of the ODF 1.0/1.1 specifications and was rather creative in accomplishing that.

I'm not objecting to cleaning this up, since we are no longer integrating with the specification narrative and the narrative no longer has that structure in any case. But as much as "abuse" is used here, I don't think that is in reference to any normative provision of Relax NG.

I remain concerned that in changing the schema now we make it more difficult for folks to notice what changed and it bothers me a little that we will require tools to accomplish that for us.

See also OFFICE-2483

Marked as resolved, but "NEEDS-DISCUSSION" added.

Issue was discussed in the 05/03/2010 call. No objections for refactoring the schema was raised. I'm therefore resetting the NEEDS-DISCUSSION.

Correction appear in the OPpenDocument-v1.2-part1-cd04-rev01 schemas