- From: Mark Baker <distobj@acm.org>
- Date: Sun, 2 Dec 2001 21:10:02 -0500 (EST)
- To: henrikn@microsoft.com (Henrik Frystyk Nielsen)
- Cc: xml-dist-app@w3c.org (XML dist app)
> As we are now defining a new media type, we no longer have this > constraint. Therefore, I suggest we consider defining an OPTIONAL media > type attribute as part of our new media type that can contain this > information, something like this: > > application/soap+xml; action="http://www.example.org/foo" Right. I've been suggesting this for a while, though I've always named the parameter "namespace", because I always saw it as being the namespace of the immediate (assuming only one) child of the body element. But I suppose "action" is more neutral with respect to the RPC use of SOAP. I support this proposal. > If we go this way we can in fact GET RID OF SOAPAction HTTP header field > altogether and make the link between the media type explicit hence > avoiding some of the confusion. There's other issues that we'd have to resolve before removing SOAPAction. For example, do we want to also allow application/xml (as defined in RFC 3023) to be used? I think we do, so some thought has to go into that. MB -- Mark Baker, Chief Science Officer, Planetfred, Inc. Ottawa, Ontario, CANADA. mbaker@planetfred.com http://www.markbaker.ca http://www.planetfred.com
Received on Sunday, 2 December 2001 21:11:25 UTC