Cart
[Home] [By Thread] [By Date] [Recent Entries]
Very well said, Len: > That said, at the bottom of it, the bigger problem > is still the emergence and acceptance of common > vocabularies, same as it ever was. Regardless of > what we wrap them in, we still have to build those > and that is 90% a political/sales job. It always comes down to this classic problem. Communication. Not across a wire...but of requirements and vocabularies. Since that is still very much a "human" issue (despite the efforts of such technologies as UDDI), it will likely be the limiting factor in global adoption of web services. This is compounded by the fact that it becomes exponentially more difficult as the number of participants increases. (This list is sometimes a good example of that syndrome ;-) ). I don't really see much difference between REST and SOAP (RPC derivations)....one can usually be modelled with the other (and vice versa) without much difficulty if the need is there. It's defining the semantics of the interaction and the vocabularity that encapsulates those semantics that is the problematic issue. Andrzej Jan Taramina Chaeron Corporation: Enterprise System Solutions http://www.chaeron.com
|
