[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Attribute Requirements on wss11:SignatureConfirmation ( was [wss-comment] Public Comment )
Dear TC, Peter, This is my mistake. The normative spec text is correct. I got the attribute requirements the wrong way round in the XSD file. The complexType definition should read as follows; <xs:complexType name="SignatureConfirmationType"> <xs:attribute ref="wsu:Id" use="required" /> <xs:attribute name="Value" type="xs:base64Binary" use="optional" /> </xs:complexType> Apologies, Gudge -----Original Message----- From: comment-form@oasis-open.org [mailto:comment-form@oasis-open.org] Sent: 26 January 2006 09:11 To: wss-comment@lists.oasis-open.org Subject: [wss-comment] Public Comment Comment from: peter.hendry@capeclear.com Name: Peter Hendry Title: Principal Engineer Organization: Cape Clear Software Inc. Regarding Specification: http://www.oasis-open.org/committees/download.php/15251/oasis-wss-soap-m essage-security-1.1.pdf The specification states in section 8.5 "/wsse11:SignatureConfirmation/@Value This optional attribute contains the contents of a <ds:SignatureValue>" but in the schema the Value attribute is defined as "required". Second, in the same section "/wsse11:SignatureConfirmation/@wsu:Id ...This attribute MUST be present so that un-ambiguous references can be made to this <wsse11:SignatureConfirmation> element" The wsu:Id attribute is defined in the schema for SignatureConfirmation as "optional". I assume if this id is only to identify the signature confirmation it should be optional as there should be no need to make it required in the case there is no refefence to the element. --------------------------------------------------------------------- To unsubscribe, e-mail: wss-comment-unsubscribe@lists.oasis-open.org For additional commands, e-mail: wss-comment-help@lists.oasis-open.org
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]