Dig Sig should carefully specify how canonicalization processes relationships that are missing optional attributes.

For relationships that are missing optional attributes,.add the following text after Step 3 in the Relationship Transform Algorithm section:
4. The package implementer shall add TargetMode attribute with default value, if the optional attribute is missing for the Relationship element.

Part 2, 12.2.4.26

te

Proposed Disposition of DIS 29500 Comment ECMA-0070 (Modified: 2007-12-07) Agreed; the following change will be made to Part 2, §3.17.7.96, page 58, after line 7: Step 3: Prepare for canonicalization 1. The package implementer shall remove all characters between the Relationships start tag and the first Relationship start tag. 2. The package implementer shall remove any contents of the Relationship element. 3. The package implementer shall remove all characters between the last Relationship end tag and the Relationships end tag. 4. If there are no Relationship elements, the package implementer shall remove all characters between the Relationships start tag and the Relationships end tag. 5. The package implementer shall remove comments from the Relationships xml content 6. The package implementer shall add TargetMode attribute with default value, if the optional attribute is missing for the Relationship element. 7. The package implementer can generate <Relationship> elements as start-tag, end-tag pairs with empty content, or as EMPTY elements. A canonicalization transform, applied immediately after Relationships Transform, converts all xml elements into start-tag/end-tag pairs. Similar Comments: ECMA-0052 ,