Ordering of activities in finalize is not defined

Hi

Referring back to an issue that Tony previously raised, regarding whether we needed to include in the document a default ordering statement for cases where it was not explicit, this issue was closed because it was felt that all structural activities did explicitly define their semantics.

However, I believe the 'finalize' activity is the except to the rule. It does not explicitly state that each of the finalizeReferences should be performed in sequence.

Therefore if we are going to fix this inconsistency, I think there are three possibilities:

1) We add a default ordering rule, although all other cases are explicitly covered
2) We add a new rule in the finalize activity to state that the finalizeReferences will be handled in sequence
3) I don't believe that the finalize element is adding any value - it is simply acting as a sequence. Therefore we could do any with this unnecessary grouping construct and move all of the attributes from the finalizeReference onto the finalize activity (and remove the finalizeReference).

Although technically no more proposals are being accepted, this was a last call issue that Tony raised, and therefore it appears as if it was prematurely closed.

Regards
Gary