Hi Robin, The discussion thread had inclined me towards layers (not to be confused with tiers, which run at 90 degrees). A layered architecture (or meta-architecture, if we are talking about standards for standards, as in the case of the ISO OSI 7 Layer Model for comms.) does two things:
Firstly Enables certain suggestions to be immediately seen as tunnelling, and thus deprecated. Tunnelling is always the result of expedience, and never of strategic design. Secondly Layering facilitates economic vertical disintegration amongst suppliers, which is a 'good thing'. In as much as I accept that we are not talking solely about a software deliverable here (there are also patterns to be fostered, and culture changes to be evangelised) then I agree with you whole heartedly. Also, I think there is always a 'layer view' of things, so in this case I guess you are answering my rhetorical question in it's own terms by saying "It doesn't live just there!". Well, I was open to that answer, as you might have detected from my tone. It leaves me at a bit of a loss, though. As a designer, I expect to proceed from knowing what it is people want to be able to do, but can't do now, to pieces of functionality that need to be provided. If one such requirement is semantic discovery, then doubts have already been expressed in this thread about whether that is possible even in principle. A service in which you can place orders for GPS guided missiles would no doubt allow you to specify a delivery address. Indeed such a service might be in every way the 'same shape' as one used for ordering missile STRIKES. Some very expensive mistakes could be made if you leave it to your stock control package. Nic --- In [email protected], "Robin" <[EMAIL PROTECTED]> wrote: > > Hi Nic, > I would not consider WS, SOA and applications as layers. Those are 3 > different topics but they have more complex relationships than just > being layers on top of each other. > > WS is a set of standards implemented by products that could help in > establishing a SOA, some of these standards and products might also > be used in other applications than just SOAs. > > SOA is at a more conceptual architecture level, while WS is at a more > concrete technical implementation level. > > Robin ------------------------ Yahoo! Groups Sponsor --------------------~--> Most low income households are not online. Help bridge the digital divide today! http://us.click.yahoo.com/cd_AJB/QnQLAA/TtwFAA/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/
