W3C home > Mailing lists > Public > xml-dist-app@w3.org > August 2002

FW: XML Protocol Implementers Meeting Summary - 8/1

From: Thompson, Lynne R <Lynne.Thompson@unisys.com>
Date: Mon, 5 Aug 2002 23:02:07 -0500
Message-ID: <F87D090845D31F44B2D8DB6BFD3EDFEAF0D09F@USMV-EXCH3.na.uis.unisys.com>
To: xml-dist-app@w3.org



>  -----Original Message-----
> From: 	Thompson, Lynne R  
> Sent:	Monday, August 05, 2002 5:23 PM
> To:	'Yin-Leng.Husband@hp.com'; 'akarmark@oracle.com';
> 'alexdej@microsoft.com'; 'asirv@webmethods.com'; 'carine@w3.org';
> 'frystyk@microsoft.com'; 'gdaniels@macromedia.com'; 'jacek@idoox.com';
> 'johnko@microsoft.com'; Martin Gudgin (E-mail); 'Narendra.Goyal@hp.com';
> 'paulclinger@yahoo.com'; 'skw@hplb.hpl.hp.com'; 'ylafon@w3.org';
> 'rubys@us.ibm.com'; Thompson, Lynne R
> Cc:	fallside@us.ibm.com
> Subject:	XML Protocol Implementers Meeting Summary - 8/1
> 
> In attendance were:
> 
> 	Glen Daniels, Macromedia
> 	Alex DeJarnatt, Microsoft
> 	Narendra Goyal, HP/Compaq
> 	Yin Leng Husband, HP/Compaq
> 	Anish Karmarkar, Oracle
> 	John Koropchak, Microsoft
> 	Lynne Thompson, Unisys
> 	Asir Vedamuthu, WebMethods
> 
> Status of Implementation Features in Table 2 as agreed upon in today's
> telecon:
> 
> 1. Rewording of #9 approved. Structure of SOAP-ENV:Fault will be covered
> in the Fault
> Handling section
> 
> "Correctly constructs SOAP messages containing Envelope, optional Header
> and mandatory Body element information items with Infoset properties as
> described in Part 1 Section 5."
> 
> 2. Add a new implementation feature to cover both senders and receivers in
> the 
> Messaging Framework - Processing SOAP Messages section
> 
> "Accepts SOAP messages containing Envelope, optional Header and mandatory 
> Body element information items with Infoset properties as described in 
> Part 1 Section 5."
> 
> 3. With the rewording of #9, the following entries will be deleted.
> 
> #12, #15, #16, #20, #21
> 
> 4. Merge #13 and #14 to read:
> 
> "Supports SOAP encodingStyle Attribute"
> 
> 5. Delete #17 - duplicated by #2 and 7
> 
> 6. #19 remains unchanged.
> 
> 6. Delete #22 
> 
> 7. Delete #23 - Obsoleted by 29
> 
> 8. Rephrase #24 as:  "Supports SOAP encodings"
> 
> 9. #25 remains unchanged.
> 
> 10. Delete #26 (Deleted from SOAP 1.2 Part 1 specification)
> 
> 11. #29 remains unchanged.
> 
> 12. Delete #30
> 
> 13. Delete #35 (Duplicate of #31 and #32)
> 
> 14. #33 remains unchanged.
> 
> 15. Delete #37 (Not specified by SOAP)
> 
> 
> Other discussions:
> 
> *	The same question from 7/31 call was raised regarding the level of
> granularity for each feature category.  Would the level of granularity of
> the features specified in Table 2 demonstrate interoperability of at least
> two implementations?
> 
> *	#68, 69, and 70 - Need appropriate wording (Asir)
> 
> *	#18 - Verify that this is duplicated by #2 and/or #9 (Yin-Leng)
> 
> 
> References:
> 
> [1] SOAP 1.1 Implementation Feature Summary
> 	http://www.w3.org/2000/xp/Group/2/03/soap1.2implementation.html
> 
> [2] Implementation Feature Comments from Jacek Kopecky:
> 	http://lists.w3.org/Archives/Public/xml-dist-app/2002Jul/0163.html
> 
> [3] SOAP 1.2 Part 1 Feature List from Anish Karmarkar:
> 	
> http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0033.html
> 
> [4] Additional Implementation Feature Suggestion from Jacek Kopecky
> 	http://lists.w3.org/Archives/Public/xml-dist-app/2002Jul/0174.html
> 
> [5] SOAP Part 2, Sections 3, 7, and 4 - Features Missing in Test
> Collection from Asir Vedamuthu
> 	
> http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0117.html
> 	
> http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0119.html
> 	
> http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0154.html
> 
> [6] Response to SOAP 1.2 Part 1 Feature List from Jacek Kopecky
> 	http://lists.w3.org/Archives/Public/xml-dist-app/2002Jul/0151.html
> 
> 
Received on Tuesday, 6 August 2002 00:02:15 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:10 GMT