With the purpose of looking up the stack to a higher level of abstraction and utility, I have just uploaded a paper by KH-B on processes, human interation et al. to the Articles-Whitepaper section of our Files folder. Apart from the fact that it is obviously written by a well educated man of thoughtful and original intellect, I would urge you to have a wee think about this as an example whereby an underlying SOA structure could lend some practical utility. What would it need to in its design to achieve these ends?
Gervas --- In [email protected], Keith Harrison-Broninski <[EMAIL PROTECTED]> wrote: > > +1. Steve shows that pursuing an accurate definition of "distributed > system" is going to lead us into technical depths irrelevant to most > system developers, let alone system users. Taking a user perspective > seems a very sensible approach. > > -- > > All the best > Keith > > http://keith.harrison-broninski.info > > Gervas Douglas (gmail) wrote: > > > So, let us look above a SOA infrastructure and examine how we are > > going to implement robust, scalable, agile systems with the minimum > > delay and cost. Let us look at Composite Apps, BPM et al. [Please > > suggest similar relevant factors based on your experience] May I > > suggest that keeping in mind these higher needs will help keep us > > fixed on what is relevant for SOA more usefully than worrying about > > definitions at this stage? > > > ------------------------ Yahoo! Groups Sponsor --------------------~--> Fair play? Video games influencing politics. Click and talk back! http://us.click.yahoo.com/T8sf5C/tzNLAA/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/
