InfoQ

News

SOA Reference Model 1.0 Approved as OASIS Standard

Posted by Miko Matsumura on Oct 12, 2006 04:46 PM

Community
SOA
Topics
WS Standards
Tags
OASIS,
Standardization


According to the SOA Reference Model document itself, a reference model is an abstract framework for understanding significant relationships among the entities of some environment. It enables the development of specific reference or concrete architectures using consistent standards or specifications supporting that environment. A reference model consists of a minimal set of unifying concepts, axioms and relationships within a particular problem domain, and is independent of specific standards, technologies, implementations, or other concrete details.

The reference model defines SOA as:
Service Oriented Architecture (SOA) is a paradigm for organizing and utilizing distributed capabilities that may be under the control of different ownership domains.

Now SOA has a standardized reference model, thanks to the work of OASIS SOA-RM technical committee. According to an email sent to the OASIS Reference Model Technical Committee, Duane Nickull, chair of the TC notified the group's status on the standardization vote as follows:

The Ballot to advance the Reference Model for SOA to become a full OASIS Standard received 89 positive votes, the second highest number of positive votes anyone on the TC can recall being cast to support a standard.  The single no vote came from Avaya Inc.  The sole statement provided by a representative from that company was:

"Too vague and confusing, e.g. things which are not SOA can be mapped into this and claim they conform to this SOA model."

Despite this sole dissenting vote, the techical committee, after approaching Avaya with a formal letter and expressing an interest to resolve any issues with the spec, the Technical Committee decided to move ahead according to the OASIS rules and move to a standard with a final tally of 89 organizations supporting, one against.

The Reference Model can be downloaded here:
http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=soa-rm

4 comments

Reply

Smart Folks by Stefan Tilkov Posted Oct 13, 2006 4:39 AM
Re: Smart Folks by John Harby Posted Oct 13, 2006 9:06 AM
ownership domains definition by Floyd Marinescu Posted Oct 13, 2006 9:16 AM
Re: ownership domains definition by Jeevak Kasarkod Posted Oct 13, 2006 7:16 PM
  1. Back to top

    Smart Folks

    Oct 13, 2006 4:39 AM by Stefan Tilkov

    Those Avaya guys, they're smart. I honestly don't know what value, exactly, the RM provides ...

  2. Back to top

    Re: Smart Folks

    Oct 13, 2006 9:06 AM by John Harby

    Also notice noone from Microsoft, IBM or Oracle on the membership list. This lack of major vendor leadership or support always concerned me.

  3. Back to top

    ownership domains definition

    Oct 13, 2006 9:16 AM by Floyd Marinescu

    Service Oriented Architecture (SOA) is a paradigm for organizing and utilizing distributed capabilities that may be under the control of different ownership domains.
    I find this definition surprising as I've never heard SOA described in this manner anywhere else. No mention of loose coupling, no mention of standard protocols, etc. I'm curious why this definition is the way it is.

  4. Back to top

    Re: ownership domains definition

    Oct 13, 2006 7:16 PM by Jeevak Kasarkod

    It is so loosely defined that everything from CORBA to EAI and grid systems fit into this definition.Secondly, do the component services have to be distributed by definition? It should be easier to distribute the capabilities of a choreographed business process or a business service which follows the SOA principles. Any comments on that?

Exclusive Content

VMware Infrastructure 3 Book Excerpt and Author Interview

VMware Infrastructure 3: Advanced Technical Design Guide and Advanced Operations Guide provides a wealth of practical insights into setting up virtualization in todays corporate environments.

Architectures of extraordinarily large, self-sustaining systems

Can a system that is so large it cannot be comprehended be "designed" in a conventional sense? The foundations of computing are about to change. In this talk, Richard P. Gabriel explores why and how.

Using Ruby Fibers for Async I/O: NeverBlock and Revactor

Ruby 1.9's Fibers and non-blocking I/O are getting more attention - we talked to Mohammad A. Ali of the NeverBlock project and Tony Arcieri of the Revactor project.

Agile and Beyond - The Power of Aspirational Teams

Tim Mackinnon talks about the aspirations behind the Agile principles and practices, the desire to become efficient, to write quality code which does not end up being thrown away.

Concurrency: Past and Present

Brian Goetz discusses the difficulties of creating multithreaded programs correctly, incorrect synchronization, race conditions, deadlock, STM, concurrency, alternatives to threads, Erlang, Scala.

ActionScript 3 for Java Programmers

Often the hardest part of changing technologies is language syntax differences. This new article provides Java developers with a transition guide to Actionscript which forms the foundation of Flex.

Neal Ford On Programming Languages and Platforms

Neal Ford talks about having multiple languages running on one of the two major platforms: Java and .NET. He also presents the advantages offered by Ruby compared to static languages like Java or C#.

Future Directions for Agile

David Anderson talks about the history of Agile, the current status of it and his vision for the future. The role of Agile consists in finding ways to implement its principles.