© OASIS 2003 The future of standards in web services and service oriented architecture OASIS and W3C Town Hall XML 2003 Philadelphia

© OASIS 2003 Why talk about standards? A standard is:  publicly available in stable, persistent versions  developed and approved under a published process  open to public input:  public comments, public archives, no NDAs  subject to explicit, disclosed IPR terms Anything else is proprietary:  This is a policy distinction not a pejorative  See the US, EU, WTO governmental & treaty definitions of “standards”

© OASIS 2003 Standards affect the cost of e-commerce  Data conversion, process analysis and personnel training can be large expenses when adopting an e-commerce system  These costs can be balanced against tremendous operational savings -- but only if the user can employ the system for a sufficient period of time to enjoy them  Instability can thwart that recovery:  Insufficient breadth, obsolescence, competitive “embrace and extend” changes, IPR restrictions, over- versioning, sudden withdrawal

© OASIS 2003 Coordination of standards at OASIS  W3C and OASIS management regularly confer  Many dependencies across standards  Elements from OASIS standards are submitted to other SDOs, e.g.,  IETF, ISO, etc.  OASIS participates in many other standards and industry coordination efforts, e.g.,  ISO/IEC/ITU global coordination MoU  RosettaNet, OMA, etc.  AIAG, WS-I, GGF, etc.

© OASIS 2003 OASIS Conceptual Model for eBusiness standards Q u a l I t y o f S e r v I c e sM a n a g e m e n t S e c u r i t y Network Transport Generalized Processes Specialized Processes Generalized Content Specialized Content Transaction Patterns Transaction Instance XML Syntax Messaging Service Description Language Presentation Description Repository Registry / Directory Process Description Language Content Definition Language Conformance and Interoperabilit y

© OASIS 2003 OASIS Conceptual Model: populated Q u a l I t y o f S e r v I c e sM a n a g e m e n t S e c u r i t y Network Transport Generalized Processes Specialized Processes Generalized Content Specialized Content Transaction Patterns Transaction Instance XML Syntax Messaging Service Description Language Presentation Description Repository Registry / Directory Process Description Language Content Definition Language Conformance and Interoperabilit y Auto-Repair, C-Trade, Education, eGovernment, ElectionML, eProcurement, Emergency, LegalXML(8), MaterialsML, PLCS, ProdPS, TaxXML 19 ASAP, BCM, BTP, CAM, ebXML-BP, FWSI, TransWS, WSBPEL 8 XACML, AVDL, XCBF, DSS, DSML, XRI, PKI, RLTC, SAML, SPML, WAS, WSDM, WSS 13 Entity-Resolution, RELAX-NG, Topic Maps (3) 5 UIML, WSRP, HumanML 3 DSS, ebXML- RegRep, UDDI 3 ebXML- CPPA 1 ebXML-MSG, WSRM 2 Conformance, ebXML-IIC, XSLT- Conformance 3 CIQ, UBL, Doc- Book, XLIFF, OpenOffice 5

© OASIS 2003 OASIS Conceptual Model: populated Q u a l I t y o f S e r v I c e sM a n a g e m e n t S e c u r i t y Network Transport Generalized Processes Specialized Processes Generalized Content Specialized Content Transaction Patterns Transaction Instance XML Syntax Messaging Service Description Language Presentation Description Repository Registry / Directory Process Description Language Content Definition Language Conformance and Interoperabilit y Auto-Repair, C-Trade, Education, eGovernment, ElectionML, eProcurement, Emergency, LegalXML(8), MaterialsML, PLCS, ProdPS, TaxXML 19 ASAP, BCM, BTP, CAM, ebXML-BP, FWSI, TransWS, WSBPEL 8 XACML, AVDL, XCBF, DSS, DSML, XRI, PKI, RLTC, SAML, SPML, WAS, WSDM, WSS 13 UIML, WSRP, HumanML 3 DSS, ebXML- RegRep, UDDI 3 ebXML- CPPA 1 ebXML-MSG, WSRM 2 CIQ, UBL, Doc- Book, XLIFF, OpenOffice 5 Entity-Resolution, RELAX-NG, Topic Maps (3) 5 Conformance, ebXML-IIC, XSLT- Conformance 3 Final approval (as of Dec 2003) Preliminary approval

© OASIS 2003 Common transport (HTTP, etc.) Common language (XML) Viewing web services as a related set of functions Service Discovery Service Description Orchestration & Management Security & Access Messaging Data Content

© OASIS 2003 Common transport (HTTP, etc.) Common language (XML) Chords: Implementations usually combine functions Service Discovery Service Description Orchestration & Management Security & Access Messaging Data Content Example: The OASIS Disease Control Interoperability Demo at XML 2003 UBL XForms ebXML BP ebXML Registry ebXML MSG ebXML CPP/A XACML

© OASIS 2003 Common transport (HTTP, etc.) Common language (XML) What’s the short-term weather report for WS/SOA? Service Discovery Service Description Orchestration & Management Security & Access Messaging Data Content

© OASIS 2003 Common transport (HTTP, etc.) Common language (XML) Service Discovery Service Description Orchestration & Management Security & Access Messaging Data Content

© OASIS 2003 Let’s talk  Do you agree with the weather report?  Should users implement web services with proprietary products or wait for the standards?  Is conformance and interoperability part of the lifecycle of a standard?  How can we move from (inside) enterprise services to (B2B) web services? OASIS and W3C Town Hall XML 2003 Philadelphia

© OASIS 2003 The future of standards in web services and service oriented architecture OASIS and W3C Town Hall XML 2003 Philadelphia