- From: Christopher Ferris <chris.ferris@sun.com>
- Date: Thu, 06 Dec 2001 11:07:28 -0500
- To: Mark Baker <mbaker@planetfred.com>
- CC: xml-dist-app@w3.org, mnot@mnot.net
There was some discussion, I believe initiated by Henrik, that we could have SOAPAction replaced by a (OPTIONAL?) parameter on the application/soap(+xml) media type MIME header. If we intend to pursue the SOAPAction HTTP header registration, I would strongly recommend a separate ID as it has nothing to do with the media type registration and is only applicable to HTTP. My $0.02, Chris Mark Baker wrote: > Hi all, > > To close an action item that I took at the f2f, I want to bring the > group up to speed on the status concerning SOAP 1.2 IANA considerations. > > We have identified three items requiring registration with IANA; > > - SOAP media type > - SOAPAction header (*) > - SOAPAction-negotiation HTTP response code > > (*) there is currently no HTTP header registry at IANA, but we can > establish one > > Mark Nottingham has graciously(!!) offered to do much of this work on > his own time. I expect to be writing the bulk of the media type > registration section/draft (our current position is that all three items > would go in one internet draft), as well as be the WG prime (owning the > schedule, etc..). > > MB > > Mark Baker, Chief Science Officer, Planetfred, Inc. > Ottawa, Ontario, CANADA. mbaker@planetfred.com > http://www.markbaker.ca http://www.planetfred.com >
Received on Thursday, 6 December 2001 11:11:47 UTC