Business Ecology Initiative & Service-Oriented Solution

Michael Poulin

Three SOA Standards Bodies light navigation between them

user-pic
Vote 0 Votes

For last several months, OASIS, OMG and The Open Group worked together on 'SOA Harmonization' white paper. This document describes

• the types of the Standards in SOA arena from Each Standard Body
• Overview of and Guidance on Standards
• Inter-positioning of the Standards
• SOA and SOA Governance Core concepts

There are several goals of this collective effort that include, among others,
• Conveying "the same fundamental concept of SOA regardless of starting point"
• Helping navigate through overlapping standards
• Differentiate and select specification to particular needs
• "Outline the agreement on core SOA and SOA Governance concepts"
• "Establish collaboration between the Standards Bodies"
• "Encourage consistency across the standards addressing the various aspects of SOA"

I specially would like to notice that getting an agreement between the Standards Bodies, they had to come up with four categories of Reference Architecture (RA), in particular:
• Conceptual SOA RA
• Generic SOA RA
• Industry SOA RA
• SOA Enterprise RA
Since none of the participants had filled the 'SOA Enterprise RA' niche, it has become one of the target of the future collaborative efforts.

Another interesting fact is that the participants have positioned majority of their products (standards) in the area of "partial RA covering specific subsystems such as presentation, integration or security" or in the "technical RA covering only IT aspects". Nobody claimed any coverage of the business and IT aspects of SOA solutions, which a bit surprised me.

Anyway, I see this effort as a tremendously important and significant move in the Industry that gives us a hope on the 'end of standard wars and madness' and a chance to communicate about SOA in 'common' language.

Reference Lable.JPG

9 Comments

| Leave a comment

One additional piece of information: I have counted up to 17 different standards (across all three Standards Bodies) related to SOA. However, none of them mentioned Web Services (WS*-) or REST related standards.

I can read this as a message - SOA is about architecture while Web Services (WS*-) and REST are about technology; we should not mix apples and oranges (unless we want to make a 'shake').

One additional piece of information: I have counted up to 17 different standards (across all three Standards Bodies) related to SOA. However, none of them mentioned Web Services (WS*-) or REST related standards.

I can read this as a message - SOA is about architecture while Web Services (WS*-) and REST are about technology; we should not mix apples and oranges (unless we want to make a 'shake').

One additional piece of information: I have counted up to 17 different standards (across all three Standards Bodies) related to SOA. However, none of them mentioned Web Services (WS*-) or REST related standards.

I can read this as a message - SOA is about architecture while Web Services (WS*-) and REST are about technology; we should not mix apples and oranges (unless we want to make a 'shake').

One additional piece of information: I have counted up to 17 different standards (across all three Standards Bodies) related to SOA. However, none of them mentioned Web Services (WS*-) or REST related standards.

I can read this as a message - SOA is about architecture while Web Services (WS*-) and REST are about technology; we should not mix apples and oranges (unless we want to make a 'shake').

I like that because I think this is something they had to do some years ago, because OASIS, OMG and The Open Group work together is perfect, and also is amazing finding the list of goals in here.

I would be interested in learning more about " 17 different standards (across all three Standards Bodies) related to SOA"... See me on LinkedIn

Leave a comment

In this blog, Michael Poulin writes about business and technology ideas, concepts, methodologies and solutions leading to service-oriented enterprise, the primary instrument for obtaining business objectives in fast-changing environments.

Michael Poulin

Michael Poulin is an enterprise-level solution architect working in the financial industry in the U.K. and the United States.

He specializes in building bridges between business needs and technology capabilities with emphasis on business and technical efficiency, scalability, robustness and manageability. He writes about service orientation, application security and use of modern technologies for solving business problems. He contributes to OASIS SOA standards as an independent member and is listed in the the international "Who's Who of Information Technology" for 2001. View more

Subscribe

 Subscribe in a reader

Recently Commented On

Categories

Tag Cloud

'Navigating the SOA Standards Landscape, 1471, abstraction, ACM, active service, Adaptive, ADM, adopt changes, aggregate service, AIA, Amazon, analysis, API, application, Application Integration Architecture, architect, Architect, architectural mission, architecture, Architecture, architercture, AWS failure, Azure, B-SOA, BAWG, BEI, Best Practice, bottom-up, BPEL, BPM, brokerage, Brokering, brokering, bus, Busienss, busienss case, business, Business, Business Architect, Business Architecture, business architecture, Business architecture, Business Architecture Working Group, business concerns, business data, Business Ecology, business efficiency, business model, business operational model, business organisation, Business Platform Division, business process, Business Process Designer, Business Requirements, business risk, business service, Business service, Business SOA, business value, business view, business-centric, Business-IT problem, BuTechCon, Canonical Schema, capability, Case, CBDI, CBM, Centralization, choreography, CIO, Cloud, cloud, Cloud Computing, Cloud of Clouds, COBA, Collaboration, collaboration, collaboreation, commodity, component, Composite Application, composition, concept, Conciliator, consumer, contract, COSMIC, cost, cost estimate, cost of ounership, cost of ownership, coupling, crisis, CRUD, culture, Cutter Consortium, data ownership, data service, data store, DDD, decision logic, decomposition, definition, demand, design, Design Pattern, development, discipline, distributed orchestration, Domain, domain, Domain Aggregate, Domain Events, Domain Service-Oriented Modelling, DOSOM, DOSOSM, driver, Dynamic Process Edition, EA, EC2, ecosystem, EDA, efficiency, end-to-end, enemy, enterprise, Enterprise, Enterprise Architect, Enterprise Architectural Framework, Enterprise Architecture, enterprise architecture, ERP, ESB, event, Event, execution context, Execution Context, expertise, explicit, failure, fake, feature, Flexibilit, flexibility, FPA, FSM, Full Functional Points, Functional Points, functionality, functionality model, future, Gartner, goal, Governance, governance, granularity, harmonization, Healthcare, how to, IBM, identiy credential, IEEE, IEEE 1471, IFPUG, implementation, implicit, intangible, intangible value, Integration-Oriented Architecture, intent, interface, interface orientation, Inventory, investment, IOA, IT, IT Architect, IT Operation Support, IT organisation, IT without the IT Department, ITIL, Java, Ladder to SOE, leasable Cloud, lease, Loose coupling, Lost in Translation, Malik, management, Management, Manifesto, market, MDA, Michrosoft, Microsoft, Mike Rosen, model, Model-Driven Approach, modelling, Navigating the SOA Standards Landscape Around Architecture, navigation, OASIS, OASIS SOA RA, OASIS SOA RAF, OASIS SOA Reference Architecture Foundation, OASIS SOA RM, ODBC, OMG, ONA, Ontology, OO, Open Group, Oracle, orchestration, organizational change, outsourcing, ownership, participant, pattern, patterns, people, planning, policy, principle, principle of separation of concerns, principles, Principles, priority, Private, Private Cloud, process, Process, process-oriented, process-orineted, process-service, project, Provisioning, Pub/Sub, Public, Public Cloud, Public Cloud Busienss Requirements, QCon, RA, RAF, re-composition, Real World Effect, Real World SOA, redundancy, Referemce Architecture, Reference Architecture, Reference Architecture Foundation for SOA, Reference Model, Registry, rent, rentable Cloud, Repository, reuse, RIA, risk, RM, ROI, RPC, rules engine, RWE, SCA, scalability, Schema, security, semantics, Service, service, Service Autonomy, Service Composability, service contract, Service Contract, service description, Service Description, Service Discoverability, Service Execution Context, service orientation, Service Orientation, Service Oriented Enterprise, Service Relative Autonomy, Service Reusability, service semantic, Service Separation of Concerns, Service State Management, Service Statelessness, service-oriented, service-oriented eco-system, Service-Oriented Enterprise, service-oriented enterprise, service-oriented environment, ServiceContract, seven properties that differentiate emergent architecture from the traditional approach to EA, shared interface, shared library, simple, situational, sizing, SLA, SO, SO environment, SO Principles, SOA, SOA Manifesto, SOA standard, SOA-RAF, SoaML, SOBA, social, social networking, SOE, SOEA, software, solution SOA, SOMA, Spring, stakeholder, standard, Standard, study, subject, Summit, supply, supply chain, support, system, T-SOA, tangible, tangible value, Technical, Technical Architect, Technical Architects, Technical Architecture, technical capabilities, Technical SOA, technology, Technology, tendency, The Open Group, TOGAF, TOGAF 9.0, top-down, transparency, UI, UI Mediator, unstructured, use, Value Chain, Value Network, Value Networks, view, view model, viewpoint, vision, VNA, VPEC-T, WCF/WF, Web, Web 2.0, Web Service, Web Services, WebSphere, WS-CDL, WSDL, ZapFlash, ZapThink,

Monthly Archives

Blogs

ADVERTISEMENT