- From: MURATA Makoto (FAMILY Given) <eb2m-mrt@asahi-net.or.jp>
- Date: Tue, 26 Jan 2010 00:52:37 +0900
- To: "'XMLSec WG Public List'" <public-xmlsec@w3.org>
- Cc: Murata <eb2m-mrt@asahi-net.or.jp>
Why isn't processContents="lax" specified for <xsd:any>
within the dcl of CanonicalizationMethodType and that of SignatureMethodType?
Why
<sequence>
<element name="HMACOutputLength" minOccurs="0" type="ds:HMACOutputLengthType"/>
<any namespace="##other" minOccurs="0" maxOccurs="unbounded"/>
<!-- (0,unbounded) elements from (1,1) external namespace -->
</sequence>
rather than
<choice>
<element name="HMACOutputLength" minOccurs="0" type="ds:HMACOutputLengthType"/>
<any namespace="##other" minOccurs="0" maxOccurs="unbounded"/>
<!-- (0,unbounded) elements from (1,1) external namespace -->
</choice>
in the definition of SignatureMethodType? Even when
Algorithm = "http://www.w3.org/2000/09/xmldsig#hmac-sha1",
are foreign elements intentionally allowed to follow
the HMACOutputLength element? Or, as in the other cases,
the prose wins here and the <any> is ignored when
Algorithm = "http://www.w3.org/2000/09/xmldsig#hmac-sha1"?
Even when @Algorithm != "http://www.w3.org/2000/09/xmldsig#hmac-sha1",
can a SignatureMethod element have an HMACOutputLength element
as a child?
Cheers,
Makoto
Received on Monday, 25 January 2010 15:53:10 UTC