Closing issue X

Greetings,

I raised an issue[1] about the time the architecture document draft was
published, about REST's "uniform interface" constraint.  It hasn't yet
made it onto the issues list, so I'll refer to it as "Issue X".  Seems
appropriate. 8-)

In the interest of closing this issue so we can all get on with our
lives, I'm going to take a stab at providing some closing text based
on my best understanding of why Web services proponents believe that
REST's uniform interface constraint isn't important to the problems
they're trying to solve.  This is not flame bait, as I hope(!) you'll
be able to tell from the prose.  It is done with a sincere desire to
simply document the reasons why it is felt that GET/PUT/POST is not
sufficient.

==snip==

The Web Services Architecture WG believes that the Web is currently
well suited to browser-centric tasks where a human is present to
interpret the information displayed in a hypertext document.  Web
services are a machine-to-machine integration technology where a
human may or may not be present, so we feel that interfaces richer than
GET/PUT/POST/etc.. are necessary.  Web services extend Web architecture
with this capability.

==snip==

How's that?

 [1] http://lists.w3.org/Archives/Public/www-wsa-comments/2002Nov/0001

MB
-- 
Mark Baker.   Ottawa, Ontario, CANADA.        http://www.markbaker.ca
Web architecture consulting, technical reports, evaluation & analysis

Received on Thursday, 12 December 2002 13:39:22 UTC