- From: Jean-Jacques Moreau <moreau@crf.canon.fr>
- Date: Thu, 14 Nov 2002 15:56:03 +0100
- To: Rich Salz <rsalz@datapower.com>
- CC: Marc Hadley <marc.hadley@sun.com>, XMLP Public <xml-dist-app@w3.org>, WSD Public <www-ws-desc@w3.org>
No, it's not the intent of the XMLP WG, SOAP modules are identified by URIs, users are in control, not any one else. The question is, when you define your own header, should you also define the corresponding module (knowing you've done half the job when you've created the header in the first place) and associated URI? Jean-Jacques. Rich Salz wrote: >>Interesting question. I think its probably clear that there's nothing >>we can do to prevent a SOAP node from receiving a message containing an >>unknown header block (irrespective of whether a module specification >>for the header block exists or not). > > > Of COURSE this is going to happen. It's going to happen most of the time. > That's the whole purpose of distributed names (URI's) and mustUnderstand, > isn't it? It's not really the intent of this WG to set up IANA-style > registrations for SOAP modules, is it?
Received on Thursday, 14 November 2002 09:56:44 UTC