IAWG

Version 3 deliverables

1. What are we refactoring

• Authentication
• Addressing, Routing
• Message Identifiers
• Transaction Names
• Encryption

1. XML examples https://sharepoint.mismo.org/enveloping/Shared%20Documents/soapV3examples040307.zip

1. The XML Encryption Syntax and Processing <http://www.w3.org/TR/2002/REC-xmlenc-core-20021210/Overview.html>

Strategic Questions

• Should Enveloping use the above Roles as the replacement for ’*Party’

• • either we drop the connection between the envelope role and the business detailed data (like contact detail)
  • or we use the roles above to connect the envelope to the information within the payload

Version 2 deliverables

<RS> SOAP ↔ mismo v2.x Applying SOAP to MISMO, and MISMO‘s WS* Profile

• done: what is left (we’ve got to rearrange to present upfront recommendation)
• done: remove OR‘s and non-discrete recommendations in replacement
• waiting for Security (same security as 3.x)

<RJ>

• done: include SOAP security chapter from ISWG
• done: encryption (valid for node-level encryption)
• done: security (pending Hal‘s comments)
• implement XML changes from Hal (clean up XML)

<DD> namespaces approval from Core Structures

• how do we use the mismo.org namespace (is it in a 2.x MEG?)
• v3 has namespaces defined but 2.x does not
• complex scenario (E & F) XML samples for security
• <done> review of https://sharepoint.mismo.org/enveloping/Shared%20Documents/Discussion%20Document%20MISMO%20and%20WS%20Security%2004032007.doc with Hal from W3C

<PKJ> addressing roles approval from Core Data

• reuse the role specification from Architecture / D3; AWGRoles

• XML examples similar to

• Primer https://sharepoint.mismo.org/enveloping/Shared%20Documents/mismo%20soap%20ws%20primer-20060623.pdf

• Design consideration https://sharepoint.mismo.org/enveloping/Shared%20Documents/MISMO%20SOAP%20Design%20Consideration.doc

• Discussions https://sharepoint.mismo.org/enveloping/Shared%20Documents/MISMO%20SOAP%20Discussions%20History.doc