OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ws-sx message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: Attachment element issue with applying i164


One note - you could argue this is backward compatible since any previous use of the Attachments element would have no content, compatible with the revision and the use of the default transform.

Thus this change should not break existing implementations but allow clarity going forward.

regards, Frederick

Frederick Hirsch
Nokia



On May 13, 2008, at 8:21 PM, ext Marc Goodner wrote:

I’ve been discussing the changes I made to the text for i164 with Frederick. The net is I may have made a bad decision in trying to avoid changes to the SP 1.2 spec and schema. We may have an additional errata on SP 1.2 to make the proper change here.
 
The proposal we accepted for i164 was to add two new elements underneath the Attachments element. The problem is that was defined as an empty element with no extensibility. The new elements adopted in i164 are not meaningful without the Attachments element, this is best reflected by nesting them. The text and the schema itself prevent that nesting. That is why in applying the proposal I placed the new elements in the SignedParts assertion that contains the Attachments element.
 
To place the elements the following changes would need to be made as errata to SP 1.2:
Change the description of Attachments as follows:
Original: <sp:Attachments />?
Proposed: <sp:Attachments> ... </sp:Attachments>?
 
/sp:SignedParts/sp:Attachments
Presence of this OPTIONAL empty element indicates that all SwA (SOAP Messages with Attachments) attachments [SwA] are to be integrity protected. When SOAP Message Security is used to accomplish this, all message parts other than the part containing the primary SOAP envelope are to be integrity protected as outlined in WSS: SOAP Message Security [WSS:SwAProfile1.1].
 
Change the schema as follows:
Original
<xs:element name="Attachments" type="tns:EmptyType" minOccurs="0" />
<xs:complexType name="EmptyType" />
 
Proposed
<xs:element name="Attachments" type="tns:AttachmentsType" minOccurs="0" />
<xs:complexType name="AttachmentsType"> 
 <xs:sequence>
  <xs:any minOccurs="0" maxOccurs="unbounded" namespace="##other" processContents="lax" />
 </xs:sequence>
</xs:complexType>
 



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]