SOAP Encoding / Data Model as a (REST?) stand-alone data format

Quick question(s):

Is it the intent of this WG that SOAP Encoding (and
associated datamodel) be deployable as a "stand alone" data format for
Web documents? (ie. deployed in the HTTP-GETable web alongside XHTML, SVG,
MathML, SMIL etc., as well as in protocol exchanges).

Could (for example) Google's indexer expect to stumble across a filetree
full of SOAP Encoding XML files? Would it be reasonable to anticipate
writing HTML or X-Link hyperlinks that points to HTTP GET'able URIs which
dereference to SOAP-Encoding? Might one create a Web site with data
exposed in Encoding, rendered to XHTML clientside using a browser's
built-in XSLT support?

I expect the answer is "people can use it for whatever they find it useful
for". From spending a little time looking at SOAP Encoding, my
expectation is that we _will_ see it used in these contexts, and that this
might address some of the concerns associated with the 'REST' slogan...

Dan


-- 
mailto:danbri@w3.org
http://www.w3.org/People/DanBri/

Received on Wednesday, 20 March 2002 13:34:55 UTC