OASIS SOA Reference Model Goes to Vote

by Miko Matsumura on Sep 20, 2006 |

The The OASIS Reference Model for Service Oriented Architecture v1.0 has been submitted for standardization by OASIS.

A reference model is an abstract framework for understanding significant relationships among the entities of some environment, and for the development of consistent standards or specifications supporting that environment. A reference model is based on a small number of unifying concepts and may be used as a basis for education and explaining standards to a non-specialist. [1] A reference model is not directly tied to any standards, technologies or other concrete implementation details, but it does seek to provide a common semantics that can be used unambiguously across and between different implementations.

A Reference Model is used by architects as a template for composing architectures. Much the same way as the auto industry agrees on the logical divisions in components of a car, the software industry uses reference models to make logical divisions and groupings within architectures. Doing so makes it easier for vendor products to be aligned to meet the requirements of the architecture and allows users to understand where their products fit into their corporate architecture. It works much the same way as when a tire manufacturer knows that an auto manufacturer understands implicitly that a "wheel" is a round component that bolts to a " hub" and accepts a " tire" into its rim. Unlike specific architectures, however, the reference model does not specify what size the wheel is or what bolt pattern it must use, only that it has those attributes. Individual instance of wheel and rim may vary in size, shape, and composition.

As such, this OASIS work provides an abstract template for definiing SOA projects. The document describes SOA as a paradigm for organizing and utilizing distributed capabilities that may be under the control of different ownership domains.

You can read the full committee draft of the specification here (31 page PDF file).

Related Editorial

Application Performance Management Buyer's Guide

Enterprise-class API Patterns for Cloud & Mobile

APM Survival Guide from a Veteran Performance Geek

Speed Matters: See why Nike, Groupon, and Comcast are using New Relic

A Unified Mobile Architecture for the Modern Data Center

Hello stranger!

You need to Register an InfoQ account or to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Community comments

mapping to WS-* by Gerald Loeffler Posted

Re: mapping to WS-* by John Harby Posted

mapping to WS-* by Gerald Loeffler

while i agree that precise definition of concepts and their relationships (which is what this reference model provides, IMHO) is important, i really think that a mapping of these concepts to real technologies would very much clarify the discussion and also make it more useful to the practitioner. What's more, this reference architecture has been written by people who presumably had very concrete technologies in the back of their minds, and to drop that reference to technologies is neither very honest (as it falsely suggests a top-down process) nor very useful.

So: does anybody know of a document that provides the missing link between the SOA reference model and concrete webservice standards (WS-*)? Not that this link isn't obvious in some cases (say "service interface" and "policy")...

thank you,
gerald

www.gerald-loeffler.net

Re: mapping to WS-* by John Harby

I did actually work on this TC for awhile. I know they were also planning on publishing a "Reference Architecture". This document may address the issues you raise. I'm not sure when it is targeted for completion, I was getting a bit overextended so I left the TC. Here is a link to the RA subcommittee page: wiki.oasis-open.org/soa-rm/ReferenceArchitecture