> > IMO, that's not "subversion." It's just another level at which SO > principles can be applied. Ideal? Depends on one's goals. > > There are a couple of approaches to resolving the "issue." Continue > to debate to arrive at a single detail definition. Or accept that > many definitions exist and that all are okay, with pros and cons at > each level. > > -Rob
Rob, If granularity is important in the case of SO(A), then it should be equally important in the definition of SO(A). If there's an aspect of SO that deals specifically with technology, then it should be named accordingly. I warmed to the term SODA, because it said "applying SOA to application design", unfortunately, people overloaded this term and I've seen the 'D' be used for design and development, which ended up making the term useless once again. But, it was on the right track there for a moment. I covered this in my blog posting here: http://www.avorcor.com/morgenthal/index.php?entry=entry060311-084440 If you look at the comments someone raised the variance on the use of the 'D' word. JP > >
