Mark, I don't understand your answer. How does defining the operations in "a document" make it any easier to deploy the application? One has to agree on the semantics of the document to understand the data and the operations. This is basically equivalent to a UML model that must be sent over the single interface. (data + methods = objects). What semantics are used to express this? Greg's point is that one has to do the same work in either case. The debate then over which is an easier way to express the semantics (and then to implement them).
Dave Mark Baker wrote: > > On 7/10/06, Steve Jones <[EMAIL PROTECTED] > <mailto:jones.steveg%40gmail.com>> wrote: > > > That's difficult to quantify, of course. It depends a lot on the data > > > itself. As a low watermark though, we know; > > > > > > work(Web services) = work( solving interface problem) + work ( solving > > > data problem ) > > > work(Web) = work( solving data problem ) > > > > Do we? I certainly don't. You still have to define the operational > > interface, even though it is a document post rather than a defined > > interface document. If you don't define the operations available to > > consumers then THEY WON'T KNOW ABOUT THEM. > > Steve - it is *axiomatic* in REST that all services expose the same > "operational interface", so yes, we do know that. > > http://roy.gbiv.com/pubs/dissertation/rest_arch_style.htm#sec_5_1_5 > <http://roy.gbiv.com/pubs/dissertation/rest_arch_style.htm#sec_5_1_5> > > Mark. > > _Mark ------------------------ Yahoo! Groups Sponsor --------------------~--> Great things are happening at Yahoo! Groups. See the new email design. http://us.click.yahoo.com/TISQkA/hOaOAA/yQLSAA/NhFolB/TM --------------------------------------------------------------------~-> Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/service-orientated-architecture/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
