RE: [xml-dev] Re: Major Historical SOA Milestone Today

["Bullard, Claude L \(Len\)" <len.bullard@intergraph.com>]

To milk a comment from another list, when defining concepts (terms) it is just as important to define the relationships among the terms.  In this case, it is very necessary to know if SOA in one domain means the same thing in another domain.  It helps if the relationships are named and typed.

SOA isn't meaningless.  It is more or less meaningful depending on the locale in which it is found and its proximity to other locales (so-called, semantic distance given the proximity of situations).   One doesn't try to explain that to the customers.

Yes, so it goes.  And if we want to maintain our freedom to innovate, it must go that way.   To mix two quotes, rationale squeezes out innovation but empowerment is not abandonment.

len


From: Andrzej Jan Taramina [mailto:andrzej@chaeron.com] 

Joseph said:

> Though the call began with the context of harmonizing our definitions of SOA
> to have a single, shared definition, in discussion we realized that that would
> not be possible given the differences between the consortiums, the areas that
> we each focus on, and the role we each play in industry

Great...3 different definitions of SOA...with a 4th coming when W3C gets 
involved, and many more (ie. IBM, Sun, etc. variants).

And people wonder why organizations are confused as to what SOA is or should 
be and thus are sceptical and have a gut feeling that SOA is yet another 
meaningless IT marketing buzzword.

Sad, but so it goes.




Andrzej Jan Taramina
Chaeron Corporation: Enterprise System Solutions
http://www.chaeron.com


-----------------------------------------------------------------
The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
initiative of OASIS <http://www.oasis-open.org>

The list archives are at http://lists.xml.org/archives/xml-dev/

To subscribe or unsubscribe from this list use the subscription
manager: <http://www.oasis-open.org/mlmanage/index.php>