RE: Issues 12 & 192 (long)

Yes, I do see HTTP as being purely transport.  I think that if it is
anything more, then it runs the risk of converging with SOAP, and we'll end
up with A.N.Other protocol that's a kinda hybrid of the two.  Whilst there
are merits for this, personally I regard an approach using independent
layers as better than one which is effectively an <xsd:extension base="HTTP"
/>.

Whilst I agree that you can build a purchasing agent using HTTP headers or
RDF, I query whether that is something that /should/ be done in conjunction
with SOAP; surely the whole point of SOAP is to supply the application's
semantic meaning, not to be an adjunct to another mechanism.  If the
application were built using HTTP with some custom headers, then use a
custom HTTP proxy - but if it's built using SOAP, then use a SOAP
intermediary.

Pete Appleton
Information Systems Controller, Bemis Packaging Limited
pmappleton@bemis.com

> -----Original Message-----
> From: Mark Baker [mailto:distobj@acm.org]
> Sent: 28 March 2002 15:49
> To: highland.m.mountain@intel.com
> Cc: PMAppleton@bemis.com; highland.m.mountain@intel.com;
> xml-dist-app@w3.org
> Subject: Re: Issues 12 & 192 (long)
> 
> 
> Pete wrote;
> 
> > Pete Appleton wrote:
> > 
> > How can an HTTP proxy track your purchasing habits?  
> Shouldn't this be a
> > SOAP intermediary?  If an HTTP proxy is tracking, this 
> implies that the
> > message contents have semantic meaning to it (the HTTP 
> proxy), which implies
> > that it is more than just an HTTP proxy.
> 
> Nope.  A purchasing agent can be built with just HTTP and a handful
> of assertions, either in RDF or with HTTP headers.
> 
> You're still seeing HTTP as a transport protocol.  It isn't.
> 
> 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, 28 March 2002 11:40:07 UTC