[Council] [VOTE] JEP-0072: SOAP over XMPP
stpeter at jabber.org
Tue Nov 1 17:33:16 CST 2005
Version 0.13 has been published:
The disposition of open issues is as follows...
Matthew A. Miller wrote:
> 1) Section 3.3 (Sending Attachments) needs to be subsectioned into the
> the (desirable/acceptable) methods for transfer.
> 2) Each subsection for 3.3 needs an XMPP-specific example.
Done (except for the section on multipart MIME, which is impossible in
> 3) "Example 10. Example of WSDL definition for a tranlation service that
> supports SOAP over XMPP" has a typo, I think. The following:
> <soap:binding style='rpc' transport='http://jabber.org/protocol/soap'>
> At least MUST be:
> <soap:binding style='rpc' transport='http://jabber.org/protocol/soap' />
> but probably SHOULD be:
> <soap:binding style='document' transport='http://jabber.org/protocol/soap'>
> To match with the preceding narrative.
> 4) I think it would be beneficial to define an application-specific
> error condition for when a SOAP fault occurs, which would explicitly
> differentiate itself from an XMPP-layer error. The current behavior is
> partly in opposition to RFC 3920, Section 9.3.1 (although I note that
> the RFC specifies SHOULD, not MUST), and I believe this would help
> alleviate that.
> 5) Although not necessary to address, I wonder if the "SOAP attachment
> using file transfer" would be an appropriate use of "JEP-0137:
> Publishing SI Requests". I'm a little concerned about senders
> potentially spamming a SOAP service, since there's no "go" button from
> the service to trigger the transfer.
Yes, that makes a lot of sense. I've updated JEP-0072 to use JEP-0137
(which didn't exist when JEP-0072 was first drafted).
Jabber Software Foundation
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 3641 bytes
Desc: S/MIME Cryptographic Signature
Url : http://mail.jabber.org/pipermail/council/attachments/20051101/5bcaf429/smime.bin
More information about the Council