RE: SOAP Proposal Documents

[David Fischer <david@drummondgroup.com>]

I thought one of our basic criteria was NOT to change SOAP but to completely
support the SOAP 1.1 & SWA specs -- problems and all.  If we can't do this
then we should not convert.  The investigation team thought we could support
SOAP without changes to the SOAP specs -- I was on that team and I agreed.

This does not, of course, preclude the enunciation of problems we may
encounter.

David Fischer
Drummond Group

-----Original Message-----
From: Dick Brooks [mailto:dick@8760.com]
Sent: Wednesday, February 21, 2001 7:46 AM
To: Krishna Sankar; Rik Drummond; ebXML Transport (E-mail)
Subject: RE: SOAP Proposal Documents


Krishna,

I'll be attending the W3C XML Protocol Activity f2f meeting in Boston next
week where SOAP issues will be discussed. If you have something in
particular you would like discussed please let me know.
The SOAP issues list is located at:
http://msdn.microsoft.com/xml/general/soapspec_issues.asp

Thanks,

Dick Brooks
http://www.8760.com/


-----Original Message-----
From: Krishna Sankar [mailto:ksankar@cisco.com]
Sent: Wednesday, February 21, 2001 7:13 AM
To: Rik Drummond; ebXML Transport (E-mail)
Subject: RE: SOAP Proposal Documents


List-Unsubscribe:
 <mailto:ebxml-transport-request@lists.ebxml.org?body=unsubscribe>
List-Archive: <http://lists.ebxml.org/archives/ebxml-transport>
List-Help: <http://lists.ebxml.org/doc/email-manage.html>,
 <mailto:ebxml-transport-request@lists.ebxml.org?body=help>

Rick,

	I am talking about issues related to the convergence not other SOAP issues.
The point is if there are somethings ebXML TRP requires from SOAP, let us
bring them up and make that interaction smooth. May be there is a
workaround, but for long term, we need to solve it.

cheers

|-----Original Message-----
|From: Rik Drummond [mailto:rvd2@worldnet.att.net]
|Sent: Wednesday, February 21, 2001 5:04 AM
|To: Krishna Sankar; ebXML Transport (E-mail)
|Subject: RE: SOAP Proposal Documents
|
|
|krishna, i believe you are correct. we knew that soap had a lot of
|outstanding issues. however, we are not here to resolve soap issues but to
|combine ebxml trp functionality with soap envelope... nothing more.... we
|don't have time to resolve any soap issues... just make it work and work
|well in ebxml trp...... hope that helps... rik
|
|-----Original Message-----
|From: Krishna Sankar [mailto:ksankar@cisco.com]
|Sent: Tuesday, February 20, 2001 10:48 PM
|To: david@drummondgroup.com; ebXML Transport (E-mail)
|Subject: RE: SOAP Proposal Documents
|
|
|Dave,
|
|	The W3C XMLP (a.k.a XP) group maintains a SOAP issues list.
|I think issues
|like 4.2 in the excel spreadsheet need to be resolved at that venue and not
|by Microsoft. I am sure the ebXML TRP would influence a few more changes to
|SOAP and I think we could resolve all of them thru the XMLP SOAP issues
|list.
|
|	On a related note, let us (as ebXML TRP) raise all changes
|we need in SOAP
|(instead of working around them) so that the SOAP also gets the benefit of
|the convergence.
|
|	just my 2c.
|
|cheers
|
||-----Original Message-----
||From: David Fischer [mailto:david@drummondgroup.com]
||Sent: Tuesday, February 20, 2001 2:31 PM
||To: ebXML Transport (E-mail)
||Subject: SOAP Proposal Documents
||
||
||Welcome home from Vancouver,
||
||These are the three SOAP related documents we used on the overhead in
||Vancouver.  It is my understanding there is some problem with the
||ebXML/SOAP
||press release scheduled for today.  It may not go out yet.  Please do not
||distribute these documents too far.
||
||On the PPT, the right picture is the old structure and the left is the new
||proposed SOAP structure.
||
||Also, Rik asked if any document contributor does not see their name on the
||0.93 version, please reply with name and company so we may correct that
||oversight.
||
||Regards,
||
||David Fischer
||Drummond Group
||817-371-8422
||
|
|
|------------------------------------------------------------------
|To unsubscribe from this elist send a message with the single word
|"unsubscribe" in the body to: ebxml-transport-request@lists.ebxml.org
|
|


------------------------------------------------------------------
To unsubscribe from this elist send a message with the single word
"unsubscribe" in the body to: ebxml-transport-request@lists.ebxml.org


------------------------------------------------------------------
To unsubscribe from this elist send a message with the single word
"unsubscribe" in the body to: ebxml-transport-request@lists.ebxml.org