1 eb-SOA TC Electronic Business Service Oriented Architecture (eb-SOA) Purpose To continue work on...

1

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

2

eb-SOA – List Of Deliverables1. 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.

2. 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.

3

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 [email protected].

4

eb-SOA - Relevancy to FWSI

• FE– Make use of capabilities of web services and service-

oriented architecture works.

• IM– None

5

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

6

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

7

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 [email protected]

• Secretaries– Gavenraj Sodhi [email protected]

8

PS - Relevancy to FWSI FE

User access management

IM None

9

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

10

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.

11

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 [email protected]

– John Evdemon [email protected]

12

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

13

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

14

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.

15

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 [email protected] – Eric Newcomer, [email protected]

• Secretaries– Mark Little [email protected]

16

WS-CAF - Relevancy to FWSI

• FE– Guide to build capabilities of context, coordination and

transaction

• IM– Standard way to handle context, coordination and

transaction

17

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

18

WSDM – List Of Deliverables1. Web Services Distributed Management (WSDM) V1.0 Specification, Jan 2004

2. This includes WSDL described manageable resources and the XML schema to complete those descriptions.

3. This document will also define explicit manageability for the components of the Web Services Architecture (WSA) as defined by the W3C.

19

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 [email protected] – Winston Bumpus [email protected]

• Secretaries– John DeCarlo [email protected]

20

WSDM - Relevancy to FWSI

• FE– Build capabilities of web service management

• IM– None

21

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

22

WSS – List Of DeliverablesThe "core“ specification (final name TBD) • A SAML profile • An XrML profile • A Kerberos profile • An X.509 profile

23

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 protected] – Rob Philpott [email protected]

• Secretaries– Steve Anderson [email protected]– Jeff Hodges [email protected]– Eve Maler [email protected]

24

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

25

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

26

ASAP - List Of Deliverables

• Initial draft specification • Introduction with examples • Reference implementation • WSDL specification

27

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 protected]– Mr Keith Swenson, [email protected]

• Secretaries– John Fuller, [email protected]

28

ASAP - Relevancy to FWSI

• FE– Avoid building asynchronous capabilities– Specific functional elements may rely on

• IM– None

29

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

30

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.

31

ebXML-BP - Major Players• Companies

– Cyclone Commerce– Fujitsu– NIST– Sterling Commerce– Sun Microsystems

• Chairs– Dale Moberg [email protected] – Ms Monica Martin [email protected]

32

ebXML-BP - Relevancy to FWSI

• FE– Capabilities of generic metamodel for business processes,

activities, and collaboration.

• IM– None

33

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

34

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.

35

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, [email protected]

36

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

37

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


38

BT - List of Deliverables• The Business Transaction Protocol 1.0 was promoted to OASIS

Technical Committee specification on 3rd June 2002

39

BT - Major Players• Companies

– Arjuna Technologies Limited– BEA System,Inc– Choreology Ltd – Fidelity Investments – Oracle – Sun Microsystems– Bill Pope (individual, Chair)

• Chairs– Bill Pope, [email protected]

• Secretaries– Peter Furniss , [email protected]

40

BT - Relevancy to FWSI

• FE– Capabilities of transaction

• IM– Design considerations in transaction aspect

41

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

42

DSS – List Of DeliverablesThe new TC will have the following deliverables:

1. 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;

2. a SOAP binding for the protocol elements in 1);

3. a WS-Security profile for the elements in 1);

4. an interface for a digital signature creation web service; and

5. an interface for a digital signature verification web service.

43

DSS - Major Players• Companies

– BEA Systems, Inc.– Betrusted (Baltimore Technologies)– Entrust– IBM– RSA Security

• Chairs– Juan Carlos Cruellas [email protected]

– Nick Pope [email protected]

• Secretaries– Hal Lockhart [email protected]

44

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

45

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

46

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.

47

ebMS - Major Players• Companies

– Adobe Systems– Cyclone Commerce– Fujitsu– SeeBeyond Technology Corporation– Sun Microsystems

• Chairs– Mr Jacques Durand [email protected]

• Secretaries– jeffery eck [email protected]

48

ebMS - Relevancy to FWSI

• FE– Standard way to build capabilities of transport, routing and

packaging of business transaction using standard internet technologies.

• IM– None

49

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.


50

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.

51

ebXML-R - Major Players

• Companies– Adobe Systems– Booz Allen Hamilton – Individual – Logistics Management Institute – Network Inference – NIST – RosettaNet – Sun Microsystems – The Boeing Company

• Chairs – Ms Kathryn Breininger [email protected]

52

ebXML-R - Relevancy to FWSI

• FE– None

• IM– Develop registry based pattern

53

XACML TC

• eXtensible Access Control Markup Language (XACML)

• Purpose– To define a core schema and corresponding namespace for

the expression of authorization and entitlement policies in XML against objects that are themselves identified / referenced using XML.

• Current status– Date Formed: Apr-2001– Active

54

XACML - List Of Deliverables• Delivered

– OASIS Standard 1.1 (normative) • Specification document:• Policy Schema• Context Schema:

– Other Documents (non-normative)

• Errata for XACML 1.0 Conformance Tests for XACML 1.0 and 1.1 (25 March 2004)

• A Brief Introduction to XACML• The Formal Semantics of XACML

• Work In Progress– XACML 2.0 Work Items– XACML 2.0 Specification Draft– Web-services policy language use-cases and requirements – XACML profile for Web-services (WSPL) – OASIS XACML XML DSig Profile: – LDAP profile for distribution of XACML policies– Implementor's Guide: – Privacy policy profile of XACML – XACML Profile for SAML – XACML delegation use-cases

55

XACML - Major Players• Companies

– Argonne National Laboratory– BEA Systems, Inc. – Computer Associates– Entrust– IBM– National Center for Supercomputing Applications– OpenNetwork– Overxeer – Sun Microsystems– Syracuse University

• Chairs– Hal Lockhart [email protected]– Bill Parducci [email protected]

• Secretaries– Anne Anderson [email protected]

56

XACML - Relevancy to FWSI

• FE– Access control related functional elements– Security related functional elements

• IM– None

57

PKI TC

• Public Key Infrastructure (PKI)• Purpose

• To address issues related to the successful deployment of digital certificates to meet business and security requirements as well as technical and integration/interoperability issues, and

• Increase the awareness of digital certificates as an important component when managing access to network resources.


58

PKI – List Of DeliverablesThe new TC will have the following deliverables:• business implementation guideline white papers • technical implementation guideline white papers • best practice and sample implementations • applications white papers forums for networking, information sharing and

implementation of PKI-related projects • solutions showcase.

59

PKI - Major Players• Companies

– Booz Allen Hamilton– Computer Associates– Entrust– FundSERV Inc.– IBM– KPMG LLP– RSA Security– Sanctum, Inc– Sun Microsystems– VISA International

• Chairs– Mr Steve Hanna [email protected] – Mr John Sabo [email protected]

60

PKI - Relevancy to FWSI• FE

– The development of techniques to support the processing of digital signatures.

– Includes defining an interface for requesting that a web service produce and/or verify a digital signature on a given piece of data, and

– Techniques for proving that a signature was created within its key validity period.

• IM– None

61

SS TC

• Security Services (SS)• Purpose

• To advance the Security Assertion Markup Language (SAML) as an OASIS standard.

• SAML is an XML framework for exchanging authentication and authorization information.

• Current status– Date Formed: Mar-2001

– Active

62

SS – List Of Deliverables• The TC is targeting the V2.0 release for the middle of 2004. The release will

include updates to the following specifications published by the TC for V1.1:

– SAML Assertions and Protocol

– Bindings and Profiles

– Glossary

– Security and Privacy Considerations

– Conformance Program

• Additional documents, such as new SAML profile specifications may also be produced at the Committee's discretion. The TC's intent is to pursue OASIS Standard status for all SSTC Draft Specifications.

63

SS - Major Players• Companies

– BEA Systems, Inc.– Computer Associates– Entrust– Hewlett-Packard– IBM– Netegrity, Inc.– Netscape/AOL– Neustar, Inc.– Oblix– OpenNetwork– RSA Security– SAP– Sun Microsystems– The Boeing Company

• Chairs– Prateek Mishra [email protected] – Rob Philpott [email protected]

• Secretaries– Steve Anderson [email protected]– Jeff Hodges [email protected]– Eve Maler [email protected]

64

SS - Relevancy to FWSI

• FE– Exchanging authentication and authorization information in XML.

• IM– None

65

UBL TC

• Universal Business Language (UBL)• Purpose

– To develop a standard library of XML business documents (purchase orders, invoices, etc.) by modifying an already existing library of XML schemas to incorporate the best features of other existing XML business libraries.

– To design a mechanism for the generation of context-specific business schemas through the application of transformation rules to the common UBL source library.

• Current status– Date Formed: Oct-2001– Active

66

UBL – List Of Deliverables• The primary deliverable of the UBL TC is a

coordinated set of XML grammatical components that will allow trading partners to unambiguously identify the business documents to be exchanged in a particular business context.

• As currently envisioned, the UBL work will take place in two phases:1. A first phase to align the vocabulary and structures of UBL with the

work of the Joint Core Components initiative and with the vocabulary and structures of other already existing business libraries such as RosettaNet and OAGIS.

2. A second phase to implement a mechanism for the generation of context-specific schemas for basic business documents and their components through the application of transformation rules to a common XML source library.

67

UBL - Major Players• Companies

– CommerceOne– Global Exchange Services– Oracle– SAP– SeeBeyond Technology Corporation– Sterling Commerce– Sun Microsystems– The Boeing Company

• Chairs– Jon Bosak [email protected] – Mark Crawford [email protected]

• Secretaries– Tim McGrath [email protected]– Lisa Seaburg [email protected]

68

UBL - Relevancy to FWSI

• FE– Common Core Data Elements Structure/Representation Web

Service– Functional element to realize data interoperability and

representation

• IM– None

69

UDDI Specification TC

• UDDI Specification (UDDI-S)• Purpose

– To evolve work on the Web services registry foundations. The UDDI specifications form the necessary technical foundation for publication and discovery of Web services implementations both within and between enterprises.


70

UDDI-S - List Of Deliverables

• Accept as input the UDDI version 2.0 and 3.0 specifications published by the members of UDDI.org

71

UDDI-S - Major Players• Companies

– Computer Associates– France Telecom – IBM– Individual – Logistics Management Institute – Microsoft Corporation – Oracle – SAP – Software AG – Systinet – UnitSpace

• Chairs– Mr Tom Bellwood [email protected] – Mr Tony Rogers [email protected] – Mr Luc Clement [email protected]

72

UDDI-S - Relevancy to FWSI

• FE– None

• IM– Apply registry based pattern

73

WSRP TC

• Web Services for Remote Portlets (WSRP)• Purpose

– To develop a web services standard that will allow for the "plug-n-play" of portals, other intermediary web applications that aggregate content, and applications from disparate sources.


74

WSRP - List Of Deliverables• The primary deliverables of the WSRP TC are

specifications that consist of a coordinated set of web service interfaces and technical contracts that will allow businesses to:– Deploy portlets that are interoperable with portlet consumers

(e.g. portals). – Deploy portlet consumers which can easily aggregate these

portlets. – Enable portlet consumers and portlets to cooperate in

customizing the user interface. – Enable portlet consumers to coordinate interactions with

portlets. – Publish meta-information that indicates the portlet's

capabilities – Find and exploit portlet meta-information.

75

WSRP - Major Players• Companies

– BEA Systems, Inc.– Citrix Systems– GlueCode Software– IBM TC– Individual– Novel– Oracle– Plumtree Software– Reed Elsevier– SAP– Sun Microsystems– Thomson Corporation– US Dept of the Navy– Vignette Corporation

• Chairs– Rich Thompson [email protected]

• Secretaries– Richard Jacob [email protected]– Adam Lieber [email protected]

76

WSRP - Relevancy to FWSI

• FE– Package core components as portlet

• IM– None

77

WSRM TC

• Web Services Reliable Messaging (WSRM)• Purpose

• To create a generic and open model for ensuring reliable message delivery for Web services.

• Reliable message delivery is the ability to guarantee message delivery to software applications - Web services or Web service client applications - with a chosen level of quality of service (QoS).

• Current status– Date Formed: Feb-2003– Active

78

WSRM - List Of Deliverables

• Reliability requirements document, such as use cases for WS-RM in EAI, B2B and wireless scenarios. Due within 2 months of first meeting.

• WS-Reliability specification, including description of WS-Reliability bindings to transport protocol(s). This specification will reflect refinements and changes made to the submitted version of WS-Reliability that are identified by the WS-RM TC members for additional functionality and semantic clarity within the scope of the TC charter. Final draft due within 6 months of first meeting.

79

WSRM - Major Players• Companies

– Booz Allen Hamilton – Cyclone Commerce – Fujitsu (Chair)– Hewlett-Packard – Hitachi – NEC Corporation – SAP – SeeBeyond Technology Corporation – Oracle – Sun Microsystems– University of Hong Kong

• Chairs– Mr Tom Rutt, [email protected]

• Secretaries– Doug Bunting, [email protected]– marc goodner, [email protected]– Kazunori Iwasa, [email protected]– Sunil Kunisetty, [email protected]

80

WSRM - Relevancy to FWSI

• FE– Make use of capabilities of reliable SOAP message for

functional elements related with SOAP messaging

• IM– None

81

XDI TC

• XRI Data Interchange (XDI) • Purpose

– To define a generalized, extensible service for sharing, linking, and synchronizing data over the Internet and other data networks using XML documents and XRIs (Extensible Resource Identifiers), a URI-compatible abstract identifier scheme defined by the OASIS XRI Technical Committee.


82

XDI - List Of Deliverables

• The initial deliverables of the OASIS XDI TC and their completion dates are:– XDI Use Cases and Requirements 1.0 - 15 May 2004 – XDI Service Specification 1.0 (includes XDI Meta-Schema

Definition, XDI Addressing Specification, and XDI WSDL Definition and Bindings) - 15 September 2004

– XDI Service Dictionary 1.0 - 15 Nov 2004 – XDI Primer 1.0 - 15 Dec 2004

83

XDI - Major Players• Companies

– Advanced Micro Devices– AmSoft Systems– Attachmate– Booz Allen Hamilton– Cordance– EPOK, Inc.– Individual– Netmino– Neustar, Inc.– NRI Pacific, Inc.– OSS Nokalva– Planetwork, Inc.– XNSorg

• Chairs– Mr Drummond Reed [email protected], – Geoffrey Strongin [email protected].

• Secretaries– Marc Le Maitre [email protected]– Ajay Madhok [email protected]

84

XDI - Relevancy to FWSI

• FE– Design data sharable component

• IM– None

85

ebXML-CPP/A TC• ebXML Collaboration Protocol Profile and

Agreement (ebXML-CPP/A) • Purpose

• To continue to develop the Collaboration Protocol Profiles (CPPs) and Collaboration Protocol Agreements (CPAs), which define a business partner's technical capabilities to engage in electronic business collaborations with other partners, and the technical agreement between two (or more) partners to engage in electronic business collaboration.

• Current status– Date Formed: Jul-2001– Active

86

ebXML-CPP/A – List Of Deliverables

1. 4th Quarter, 2001Assembly and Grouping of Residual and New Requirements and Assignment to SubGroups for Maintenance, new major versions and/or new Specifications. (See above items 3, 4, 5, 7, 8, 10.)

2. 1st Quarter, 2002Maintenance release of the CPP/CPA specification if warranted. (See items 1, 4, 7, 8.)

3. 4th Quarter, 2002Completion of any new major versions of the main Specification and any new Supporting Specifications (for example, Negotiation protocols). (See items 2, 4, 5, 6, 10.)

4. 4th Quarter, 2002Technical Committee reconsiders its charter and scope after its initial 18 month lifetime.

87

ebXML-CPP/A - Major Players• Companies

– Cyclone Commerce– SeeBeyond Technology Corporation– Sterling Commerce– Sun Microsystems

• Chairs– Dale Moberg [email protected].

88

ebXML-CPP/A - Relevancy to FWSI

• FE– None

• IM– None

89

ebXML-IIC TC

• ebXML Implementation, Interoperability and Conformance (ebXML-IIC)

• Purpose– To provide a means for software vendors to create

infrastructure and applications which adhere to the ebXML specifications and are able to interoperate.

• Current status– Date Formed: Aug-2001

– Active

90

ebXML-IIC – List Of Deliverables• The initial deliverable of the IIC TC is a conformance plan that,

at a minimum, deals with the Messaging aspect of ebXML. The participants aim to produce a first draft of this specification by approximately three months from the first meeting of the TC.

• The ultimate deliverable of the TC is to be a coordinated set of implementation guidelines and interoperability tests. In addition, the TC will work with (a) third-party organization(s) to help it (them) establish an ebXML conformance test laboratory.

• The persons proposing the formation of the TC intend to base their work as closely as possible on the ebXML infrastructure specifications. It is the hope of the proposers to finish the first implementation of this concept within a year of TC formation.

91

ebXML-IIC - Major Players• Companies

– Cyclone Commerce– Fujitsu– Global Exchange Services– NIST– SeeBeyond Technology Corporation– Sun Microsystems

• Chairs– Mr Jacques Durand [email protected]

• Secretaries– jeffery eck [email protected]

92

ebXML-IIC - Relevancy to FWSI

• FE– None

• IM– Standard way for implementation, interoperability and

conformance

93

XRI TC• eXtensible Resource Identifier (XRI) • Purpose

– To define an URI-compatible identifier scheme and resolution protocol for abstract identifiers, i.e., identifiers that are location-, application-, and transport-independent, and thus can be shared across any number of domains and directories. The TC will also define an XRI secure resolution protocol and a special set of identifiers for XRI metadata (identifiers that describe other identifiers).

• Current status– Date Formed: Dec-2002– Active

94

XRI - List Of Deliverables • Published the XRI Requirements and Glossary v1.0 in June

2003 • Published XRI Syntax and Resolution Specification v1.0 in

December 2003. • the additional deliverables from the TC include:

– XRI Primer v1.0 - a non-normative introduction to XRIs and their uses - January 2004.

– XRI Metadata Specification v1.0 - a registry of special XRI identifiers used to describe other XRI identifiers - February 2004.

– XRI Secure Resolution Specification v1.0 - extensions to the base XRI resolution protocol for digitally verifying resolution results - March 2004.

– XRI Syntax and Resolution Specification v1.1 - a revision incorporating implementation experience and feedback - June 2004.

95

XRI - Major Players• Companies

– Advanced Micro Devices– AmSoft Systems– Attachmate– Cordance– EPOK, Inc. – Individual – Infosys Technologies – Neustar, Inc. – NRI Pacific, Inc. – Planetwork, Inc. – TSO – VISA International

• Chairs – Mr Drummond Reed [email protected], – Mr Gabriel Wachob [email protected].

• Secretaries– Marc Le Maitre [email protected]

96

XRI - Relevancy to FWSI

• FE– None

• IM– None

97

Translation Web Services TC

• Translation Web Services (TWS)• Purpose

– To define industry standard business process terminology for service types that are relevent to the software/content localisation and translation industry; this terminology will then drive the development of an industry standard WSDL file and UDDI business service entries.

• Current status– Date Formed: Nov-2002– Active

98

TWS - List Of Deliverables

• TwS 1.0 TWS Business Process Terminology Specification; 12 weeks after 1st meeting

• TwS 1.0 WSDL Documents; 20 weeks after 1st meeting

• TwS 1.0 UDDI Deploy WSDL as UDI tModels; 24 weeks after 1st meeting

99

TWS - Major Players

• Companies– Bowne Global Solutions – Connect Global Solutions – Individual – Limerick Localisation Research Centre – Localization Industry Standards Assoc. (LISA) – Microsoft Corporation – Oracle – SAP

– WSCC

• Chairs– Peter Reynolds [email protected]

• Secretaries– Tony Jewtushenko [email protected]

100

TWS - Relevancy to FWSI

• FE– None

• IM– Guideline for term usage

101

WSIA TC

• Web Services Interactive Applications (WSIA)

• Purpose– To create an XML and web services centric framework for

interactive web applications; harmonize the specification as far as practical with existing web application programming models, with the work of the W3C, emerging web services standards, and with the work of other appropriate business information bodies.

• Current status– Date Formed: Oct-2001– Completed

102

WSIA - List Of Deliverables

• The primary deliverable of the WSIA TC is a coordinated set of XML vocabularies and Web Services interfaces that will allow businesses to: – Deliver web applications to end users through a diversity of

deployment channels: directly to a browser or mobile device, indirectly through a portal, or by embedding into a 3rd party web application;

– Create web applications that can be easily be modified, adapted, aggregated, coordinated, synchronized or integrated by simple declarative means to ultimately leverage a worldwide pallet of web application components.

103

WSIA - Major Players

• Companies– IBM– BEA Systems, Inc., Member– Individual, Member– Kinzan, Member– Plumtree Software, Member– Sun Microsystems, Member– Vignette Corporation, Member– Webcollage, Member

• Chairs– Charles Wiecha, IBM

104

WSIA - Relevancy to FWSI

• FE– Package core components as portlet

• IM– None

1 eb-SOA TC Electronic Business Service Oriented Architecture (eb-SOA) Purpose To continue work on...

Documents

Transcript of 1 eb-SOA TC Electronic Business Service Oriented Architecture (eb-SOA) Purpose To continue work on...