Estandares Oasis

The Use of Standards in SOA
Peter Roden Director of Technology Development The 2nd Service Oriented Architecture (SOA) and Web Services Best Practices
Chicago, IL Oct. 18, 2005

OPEN STANDARDS

What is an Open Standard?
s

An open standard is:
q q

q

q

publicly available in stable, persistent versions developed and approved under a published, transparent process open to publicinput: public comments, public archives, no Non-Disclosure Agreements (NDA) subject to explicit, disclosed (Intellectual Property Rights) IPR terms That's not a pejorative, it's a description Using a single company's method, or joint work from several companies, may be fine: but it has a different set of risks and qualities than the official output from a genuine open standards process
3

sAnything else is proprietary
q q

© OASIS, 2005

Standards ROI
s

s

s

Normalizing data, processes and users costs time and money ROI can come from operational savings and outweigh the costs, if those savings are stable and persistent This requires:
q q

q q

Established versioning Reliable, fixed terms of availability (some protection against withdrawal or “embrace-andextend”) INTEROPERABLE standards CONVERGING standards
4

© OASIS, 2005

Regulatory case for Open Standards
s

Increasingly, it matters to government regulators and implementers whether standards are developed under an open, fair, vendor-neutral process.
q

WTO Technical Barriers to Trade Agreement
s

http://www.wto.org/english/docs_e/ legal_e/final_e.htmhttp://www.whitehouse.gov/omb/circulars/a119/ a119.html)

q

United States criteria
s

s

Industry users care about the same issues

© OASIS, 2005

5

Interoperating with the world
s

Cooperation, liaison and harmonization with other standards organizations is a strategic OASIS priority
q

q

Working to reduce duplication and promote interoperability Gaining sanction/authority & adoption for OASIS StandardsISO, IEC, ITU, UN-ECE MoU for E-Business ISO/IEC JTC1 SC34, ISO TC154 (Cat. A Liaison) ITU-T A.4 and A.5 Recognition IPTC, LISA, SWIFT, UPU ABA, ACORD, AIAG, HL7, HR-XML, ISM, MBAA, NASPO, European ICTSB, CEN/ISSS, EC SEEM, PISCES, LRC Asia PKI, CNNIC, EA-ECA, ECIF, KIEC, PSLX, Standards-AU BPMI, CommerceNet, GGF, IDEAlliance, OAGi, OGC, OMA, OMG, RosettaNet/UCC, W3C, WfMC, WSCC, WS-I, ANSI
6

sFormal working relationships with:
q q q q q

q q

© OASIS, 2005

Standards Adoption
s s

To be successful, a standard must be used Adoption is most likely when the standard is
q q q q q q

Freely accessible Meets the needs of a large number of adopters Flexible enough to change as needs change Produces consistent results Checkable for conformance, compatibility Implemented andthus practically available

s

Sanction and traction both matter

© OASIS, 2005

7

Standards: Traction vs. Sanction
TRACTION
XML W3C

Market Adoption

SOAP v1.1

SOAP v1.2 W3C WSDL v1.2 W3C WS-S OASIS UDDI v2,3 UDDI.org UDDI v2,3 OASIS WS-BPEL OASIS SGML ISO

WSDL v1.1

ebXML(x4) OASIS

ISO 15000

WS-Security

BPEL4WS

PROPRIETARY

JOINT COMMERICAL VENTURECONSORTIA

STANDARDS DEVELOPMENT ORGANIZATION

Open Standardization
© OASIS, 2005

SANCTION

8

INTEROPERABILTY

What is interoperability?
s s

The harmonization of e-business standards Sometimes there is more than one way to fulfill a need:

© OASIS, 2005

10

Multiple Standards may co-exist
s

Different legacy systems or business requirements may require different methodsCOMPLEX
Heavyweight code, more functionality Highly scalable Bigger tools, higher cost More exclusive

SIMPLE
Lightweight code Limited Use Case Easier to build, deploy Loose Coupling

© OASIS, 2005

11

Interoperability & Convergence s Multiple filters make it happen

1

2

3

6. 7.

8.

Open standards process Proximity breeds comparison & convergence … and users drive...