eb-SOA TC • Electronic Business Service Oriented Architecture (eb-SOA) • Purpose • To continue work on the ebXML Technical Architecture to bring it from v1.04 to a more current architecture that takes into account both subsequent releases of the ebXML specifications and other Web Services and service-oriented architecture works. • Current status • Date Formed: Mar-2004 • Active
eb-SOA – List Of Deliverables • An eBusiness Service Oriented Architecture Technical Specification - completion date in eighteen months from formation of this TC, with incremental drafts published on a regular basis in advance of completion. • A Service Oriented Architecture (including ebXML and Web Services) Best Practices Document (first version) - a non prescriptive (illustrative) guide to help implement a modern SOA. Completion date is twelve months after the completion of the architecture above.
eb-SOA - Major Players • Companies • Adobe Systems • Booz Allen Hamilton • CommerceOne • Cyclone Commerce • Enigmatec Corporation Ltd • General Services Administration • Logistics Management Institute • Singapore Institute of Manufacturing Technology • Sterling Commerce • The Boeing Company • Seeburger, AG • Lockheed Martin • Chairs • Duane Nickull firstname.lastname@example.org.
eb-SOA - Relevancy to FWSI • FE • Make use of capabilities of web services and service-oriented architecture works. • IM • None
Provisioning Services TC • Provisioning Services (PS) • Purpose • To define an XML-based framework for exchanging information between Provisioning Service Points. This framework will be referred to as the Service Provisioning Markup Language (SPML). • Current status • Date Formed: Oct-2001 • Active
PS - List Of Deliverables • The PSTC will produce a set of one or more Committee Specifications that will cover the following: • Use cases and requirements • Information model • Protocol(s) • Bindings • Conformance
PS - Major Players • Companies • Abridean, Inc. • BEA Systems, Inc. • Blockade Systems Corp • BMC Software • Business Layers • Computer Associates • CrimsonLogic Pte Ltd • Entrust • IBM • Microsoft Corporation • Netegrity, Inc. • OpenNetwork • RSA Security • Thor Technologies • TruLogica, Inc. • Waveset Technologies • Chairs • Mr Darran Rolls Darran.Rolls@sun.com • Secretaries • Gavenraj Sodhi email@example.com
PS - Relevancy to FWSI • FE • User access management • IM • None
WS-BPEL TC • Web Services Business Process Execution Language (WS-BPEL) • Purpose • To continue work on the business process language published in the Business Process Execution Language for Web Services (BPEL4WS) specification in August 2002. • Current status • Date Formed: May-2003 • Active
WS-BPEL – List Of Deliverables • The specification of the core elements and functionalities of BPEL4WS. • An extension specification for business protocol description • An extension specification for executable process description The two extension specifications for the usage patterns of business protocol description and executable process description are normative, mandatory extensions to the core specification and will include only the essential feature extensions required for the given usage pattern.
WS-BPEL - Major Players • Companies • BAHWAN CYBERTEK INC • BEA Systems, Inc. • Cap Gemini Ernst & Young • IBM • IONA • Microsoft Corporation • NEC Corporation • Novell • Oracle • SAP • SeeBeyond Technology Corporation • Sterling Commerce • Sun Microsystems • Tibco • Unisys Corporation • webMethods, Inc. • Chairs • Mrs Diane Jordan firstname.lastname@example.org • John Evdemon email@example.com
WS-BPEL - Relevancy to FWSI • FE • Sequencing of process activities, especially Web service interactions • Correlation of messages and process instances • Recovery behavior in case of failures and exceptional conditions • IM • None
WS-CAF TC • Web Services Composition Application Framework (WS-CAF) • Purpose • To define a generic and open framework for applications that contain multiple services used in combination (composite applications). • To enable development of composite applications, ranging from simple to complex combinations of web services and encompassing a useful range of transaction and coordination requirements • Current status • Date Formed: Sep-2003 • Active
WS-CAF - List Of Deliverables • A revised WS-Context specification. Draft due within 6 months of first meeting. • A revised WS-Coordination Framework specification. Draft Due within 10 months of first meeting. • A revised WS-Transaction Management specification. Draft due within 14 months of first meeting. • A primer introducing the above specifications, including use cases and scenarios as appropriate.
WS-CAF - Major Players • Companies • Arjuna Technologies Limited • Booz Allen Hamilton • Choreology Ltd • CrimsonLogic Pte Ltd • Cyclone Commerce • Fujitsu • Hewlett-Packard • IONA • Novell • Oracle • SeeBeyond Technology Corporation • Sun Microsystems • Systinet • Chairs • Martin Chapman firstname.lastname@example.org • Eric Newcomer, Eric.Newcomer@iona.com • Secretaries • Mark Little email@example.com
WS-CAF - Relevancy to FWSI • FE • Guide to build capabilities of context, coordination and transaction • IM • Standard way to handle context, coordination and transaction
WSDM TC • Web Services Distributed Management (WSDM) • Purpose • To define web services management, including using web services architecture and technology to manage distributed resources. • This TC will also develop the model of a web service as a manageable resource. • Current status • Date Formed: Apr-2003 • Active
WSDM – List Of Deliverables • Web Services Distributed Management (WSDM) V1.0 Specification, Jan 2004 • This includes WSDL described manageable resources and the XML schema to complete those descriptions. • This document will also define explicit manageability for the components of the Web Services Architecture (WSA) as defined by the W3C.
WSDM - Major Players • Companies • Actional Corporation • AmberPoint • BEA Systems, Inc. • BMC Software • Computer Associates • Hewlett-Packard • IBM • Novell • OpenNetwork • Oracle • Tibco • webMethods, Inc. • Chairs • Heather Kreger firstname.lastname@example.org • Winston Bumpus email@example.com • Secretaries • John DeCarlo firstname.lastname@example.org
WSDM - Relevancy to FWSI • FE • Build capabilities of web service management • IM • None
WSS TC • Web Services Security (WSS) • Purpose • To continue work on the Web Services security foundations as described in the WS-Security specification, which was written within the context of the Web Services Security Roadmap as published in April 2002. • The work of the OASIS WSS TC will form the necessary technical foundation for higher-level security services which are to be defined in other specifications. • The TC shall not further develop the security roadmap, nor shall the roadmap constitute a normative part of the output of the TC. • Current status • Date Formed: Sep-2002 • Active
WSS – List Of Deliverables The "core“ specification (final name TBD) • A SAML profile • An XrML profile • A Kerberos profile • An X.509 profile
WSS - Major Players • Companies • AmberPoint • BEA Systems, Inc. • Betrusted (Baltimore Technologies) • CommerceOne • Computer Associates • Documentum • Entrust • Fujitsu • Hewlett-Packard • Hitachi • IBM • Microsoft Corporation • Netegrity, Inc. • Novell • Oblix • OpenNetwork • Oracle • Reactivity • RSA Security • SAP • Sarvega • SeeBeyond Technology Corporation • Sun Microsystems • Verisign • Chairs • Prateek Mishra email@example.com • Rob Philpott firstname.lastname@example.org • Secretaries • Steve Anderson email@example.com • Jeff Hodges Jeff.Hodges@sun.com • Eve Maler firstname.lastname@example.org
WSS - Relevancy to FWSI • FE • The support of security mechanisms in the following areas: • Using XML signature to provide SOAP message integrity for Web services • Using XML encryption to provide SOAP message confidentiality for Web services • Attaching and/or referencing security tokens in headers of SOAP messages • Carrying security information for potentially multiple, designated actors • Associating signatures with security tokens • IM • None
ASAP TC • Asynchronous Service Access Protocol (ASAP) • Purpose • To create a very simple extension of Simple Object Access Protocol (SOAP) that enables generic asynchronous webservices or long-running webservices • Current status • Date Formed: Aug-2003 • Active
ASAP - List Of Deliverables • Initial draft specification • Introduction with examples • Reference implementation • WSDL specification
ASAP - Major Players • Companies • AmberPoint • Cisco Systems, Inc • Computer Associates • Datapower Technology, Inc • Fujitsu (Chair) • Iopsis Software • Novell • Staffware plc • Workflow Management Coalition • Keith Swenson (Individual, Chair) • Chairs • Mr Jeffrey Ricker, email@example.com • Mr Keith Swenson, firstname.lastname@example.org • Secretaries • John Fuller, email@example.com
ASAP - Relevancy to FWSI • FE • Avoid building asynchronous capabilities • Specific functional elements may rely on • IM • None
ebXML-BP TC • ebXML Business Process (ebXML-BP) • Purpose • To continue work on a royalty-free technology representation and model compatible with an underlying generic metamodel for business processes, activities, and collaboration. • Current status • Date Formed: Jan-2004 • Active
ebXML-BP – List Of Deliverables • Requirements document: Due within 2 months of first meeting. • ebXML Business Process specification and schemas: • This specification will reflect refinements and changes made to the submitted version of ebXML BPSS that are identified by the TC members for additional functionality, semantic clarity and technical robustness within the scope of the TC charter. • Final draft will be due within 6 months of first meeting. • Industry or domain specific examples or implementation guides may be developed. The due dates will be determined after the initial set of deliverables is complete.
ebXML-BP - Major Players • Companies • Cyclone Commerce • Fujitsu • NIST • Sterling Commerce • Sun Microsystems • Chairs • Dale Moberg firstname.lastname@example.org • Ms Monica Martin email@example.com
ebXML-BP - Relevancy to FWSI • FE • Capabilities of generic metamodel for business processes, activities, and collaboration. • IM • None
WSRF TC • Web Services Resource Framework (WSRF) • Purpose • To define a generic and open framework for modeling and accessing stateful resources using Web services. This includes mechanisms to describe views on the state, to support management of the state through properties associated with the Web service, and to describe how these mechanisms are extensible to groups of Web services • Current status • Date Formed: Mar-2004 • Active
WSRF - List Of Deliverables • A revised WS-ResourceProperties specification. Committee Draft due within one year of the first meeting. • A revised WS-ResourceLifetime specification. Committee Draft due within one year of the first meeting. • A WS-RenewableReferences specification, which defines a conventional decoration of a Web service endpoint reference with information needed to retrieve an updated version of an endpoint reference when it becomes invalid. Committee Draft due within one year of the first meeting. • A WS-ServiceGroup specification, which defines an interface to heterogeneous by-reference collections of Web services. Committee Draft due within one year of the first meeting. • A WS-BaseFaults specification, which defines a base fault XML type for use when returning faults in a Web services message exchange. Committee Draft due within one year of the first meeting.
WSRF - Major Players • Companies • AmberPoint • Argonne National Laboratory • Arjuna Technologies Limited • BEA Systems, Inc • BMC Software • Cisco Systems, Inc • Computer Associates • Fujitsu (Chair) • Hewlett-Packard • IBM • Oracle • Infosys Technologies • NEC Corporation • Novell • OpenNetwork • Sonic Software • Sun Microsystems • WebMethods Inc • Chairs • Dr David Snelling, Fujitsu, D.Snelling@fle.Fujitsu.com
WSRF - Relevancy to FWSI • FE • Build stateful info into Web service • Functional element to realize access pattern / interaction with stateful resources • IM • Standard way for web service to access state • Access pattern, standard way to implement access stateful resource
BT TC • Business Transactions (BT) • Purpose • To develop technology for business transactions on the Internet. • BTP is XML based protocol for representing and seamlessly managing complex, multi-step B2B transaction over the Internet • Current status • Date Formed: Jan-2001 • Active
BT - List of Deliverables • The Business Transaction Protocol 1.0 was promoted to OASIS Technical Committee specification on 3rd June 2002
BT - Major Players • Companies • Arjuna Technologies Limited • BEA System,Inc • Choreology Ltd • Fidelity Investments • Oracle • Sun Microsystems • Bill Pope (individual, Chair) • Chairs • Bill Pope, firstname.lastname@example.org • Secretaries • Peter Furniss , email@example.com
BT - Relevancy to FWSI • FE • Capabilities of transaction • IM • Design considerations in transaction aspect
DSS TC • Digital Signature Services (DSS) • Purpose • To develop techniques to support the processing of digital signatures, including defining an interface for requesting that a web service produce and/or verify a digital signature. • Current status • Date Formed: Dec-2002 • Active
DSS – List Of Deliverables The new TC will have the following deliverables: • an XML-based protocol, including a time stamping protocol, providing a method or methods of proving that a key was used during its validity period; • a SOAP binding for the protocol elements in 1); • a WS-Security profile for the elements in 1); • an interface for a digital signature creation web service; and • an interface for a digital signature verification web service.
DSS - Major Players • Companies • BEA Systems, Inc. • Betrusted (Baltimore Technologies) • Entrust • IBM • RSA Security • Chairs • Juan Carlos Cruellas firstname.lastname@example.org • Nick Pope email@example.com • Secretaries • Hal Lockhart firstname.lastname@example.org
DSS - Relevancy to FWSI • FE • The understanding and applicability of XML-based PKI standards as well as other broader Web services and security standardization effort within OASIS of which PKI is a component of. • IM • None
ebMS TC • ebXML Messaging Services (ebMS) • Purpose • To develop and recommend technology for the transport, routing and packaging of business transactions using standard Internet technologies. • Current status • Date Formed: Jul-2001 • Active
ebMS – List Of Deliverables • This Technical Committee will: • address maintenance issues that may arise in the implementation of ebXML Messaging Service Specification Version 1.0, including the development of minor releases of the Specification; • respond to requirements raised by committee members and by the joint OASIS -- UN/CEFACT Requirements and Technical Architecture Committees; • prepare Technical Reports, White Papers and other documents to further the consistent adoption of messaging service specifications; • proactively engage with related activities in external forums, especially the W3C Activities and Working Groups; • coordinate TC activities with other technical committees and work groups operating within OASIS and UN/CEFACT; and • develop future versions of the ebXML Messaging Service Specifications with consideration of related technologies adopted by other forums.
ebMS - Major Players • Companies • Adobe Systems • Cyclone Commerce • Fujitsu • SeeBeyond Technology Corporation • Sun Microsystems • Chairs • Mr Jacques Durand email@example.com • Secretaries • jeffery eck firstname.lastname@example.org
ebMS - Relevancy to FWSI • FE • Standard way to build capabilities of transport, routing and packaging of business transaction using standard internet technologies. • IM • None
ebXML Registry TC • ebXML Registry (ebXML-R) • Purpose • To develop one or more specifications for interoperable registries and repositories for SGML- and XML-related entities. • Current status • Date Formed: Aug-2001 • Active
ebXML-R - List Of Deliverables • Registry Information Model, initial draft 2, first quarter, 2002. • Registry Services Specification, initial draft 2, first quarter, 2002. • Registry information Model, final draft 2, third quarter, 2002. • Registry Services Specification, final draft 2, third quarter 2002. • Technical Reports will be drafted as appropriate. • White Papers will be drafted as appropriate.