Business Ecology Initiative & Service-Oriented Solution

Michael Poulin

Evidence of collaboration between SOA Standard Bodies

By Michael Poulin on November 1, 2009 8:13 AM 0

A few days ago, the OASIS SOA Reference Architecture Technical Committee announced that it changes its name to 'Reference Architecture Foundation for SOA'. As newly elected TC Chair Dr. Ken Laskey said "For those of you who have not been following the details of the RA work, you will note a slight change with the addition of "Foundation" to the title of the spec as a result of our discussions with OMG and The Open Group."

This slight change in the title outlines the recognition of the fundamental content and role the OASIS SOA Reference Architecture has established. We can expect several SOA Reference Architecture standards to emerge based on the OASIS' Reference Architecture Foundation in coming years. As a result, as I said before in the post "SOA Manifesto has been Released", we will witness clearer separation of concerns and roles in the collaboration within creation of service-oriented solutions.

Leave a comment

Recent posts from our Blogs

Defining BPM by Scott Cleveland in BPM from a Business Point of View
BPM and the CIO's Dilemma by Joe McKendrick in Business Transformation in Action
Why is social BI just as important as regular BI? by Nari Kannan in New Frontiers in Business Intelligence
Summer reading and sharing your opinions by Anne Stuart in Anne Stuart’s BPM in Action
BPM & Customer Expectations by Scott Cleveland in BPM from a Business Point of View
Fixing the Fifth Root Cause of Bad Data Quality - Errors in the BI Reporting Logic by Nari Kannan in New Frontiers in Business Intelligence
Can BPM optimize enterprise content management? Talking with Steve Weissman by ebizQ in ebizQ's Business Agility Watch
BPM and SOA Roundup: Cloudy BPM, Social Business, Single-Purpose Apps by Joe McKendrick in Business Transformation in Action
Driving a Stake Through the Heart of Single-Purpose Apps by Scott Menter in Ground-Floor BPM
Risk Managers: What should you report to the Board? by Steven Minsky in Manage Tomorrow's Surprises Today

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

Coupling in SOA (2)
Dr. Alexander Samarin wrote: I use the following definition of s... [more]
Trying the Next Step When Doing an Adaptable Case Management (4)
Tek Link Film İndir wrote: Free P... [more]
Why business process is always structured? (35)
Johnker wrote: Certainly, Adaptive Case Management... [more]
People ask: Why has social BPM failed to take off at the corporate level? (2)
Michael Poulin wrote: I do like "professional" BPM expres... [more]
Service-Oriented Enterprise coveted (1)
Web Design Company wrote: Thanks for the great article here. ... [more]

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,

Blogs

ADVERTISEMENT