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: [ws-sx] i128: Example 2.2.1


Issue i128

 

From: Anthony Nadalin [mailto:drsecure@us.ibm.com]
Sent: Tuesday, May 01, 2007 2:56 PM
To: ws-sx@lists.oasis-open.org
Subject: [ws-sx] NEW ISSUE: ws-sp-usecases-examples-draft

 

PLEASE DO NOT REPLY TO THIS EMAIL OR START A DISCUSSISON THREAD UNTIL THE ISSUE IS ASSIGNED A NUMBER.
The issues coordinators will notify the list when that has occurred.
Protocol: ws-sp-usecases-examples-draft

http://docs.oasis-open.org/ws-sx/ws-sp-usecases-examples-draft-9-01a.doc

Artifact: spec / schema
Type: design
Title: Example 2.2.1
Description:
Example 2.2.1
==============
In example 2.2.1, AlwaysToRecpt should be changed to be http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200512/IncludeToken/AlwaysToRecipient.
In example 2.2.1, Never should be changed to be http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200512/IncludeToken/Never.
In example 2.2.1, Id="WSS10Anonymous with Certificates_input_policy" should be changed to Id="WSS10Anonymous_with_Certificates_input_policy"
In example 2.2.1, Id="WSS10anonymous with certs_output_policy" should be changed to Id="WSS10anonymous_with_certs_output_policy"
The XML sample is missing the EncryptedKey element, which implies that the soap:Body content was encrypted with one of the asymmetric keys, which would be incorrect. Once this EncryptedKey element is added, the description will need to refer to it.





Related issues:
None.
Proposed Resolution:
Modify as follows.

(See attached file: Test221OutputFormatted.xml)


Anthony Nadalin | Work 512.838.0085 | Cell 512.289.4122



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