And the problem is, it still depends on a shared vocabulary.
HTML was successful because it took away that option.
I have to wonder if it will be harder to control drift
in an API or drift in agreements on large, non-semantic
data object descriptions. I also wonder which is faster
to setup and get running dependably.
Software components are what programmers know how to
do best. Documents are for tech writers. ;-)
len
From: Michael Kay [mailto:]
> I have created a tutorial on REST. I welcome all comments,
> suggestions, criticisms.
>
> HTML version: http://www.xfront.com/REST.html
>
I finally understand. REST is just a fancy marketing name for the stuff
we've all being doing these last n years. And there was me trying to put
off the day I had to learn about yet another new acronym.
