Mapping OASIS Technical Work: Where’s Reliability?...

17
Mapping OASIS Technical Work: Where’s Reliability? [email protected] [email protected] New Orleans, April 2004 New Orleans, April 2004

Transcript of Mapping OASIS Technical Work: Where’s Reliability?...

Page 1: Mapping OASIS Technical Work: Where’s Reliability? jamie.clark@oasis-open.orgjamie.clark@oasis-open.org New Orleans, April 2004.

Mapping OASIS Technical Work:

Where’s Reliability?

Mapping OASIS Technical Work:

Where’s Reliability?

[email protected]@[email protected]@oasis-open.orgNew Orleans, April 2004New Orleans, April 2004New Orleans, April 2004New Orleans, April 2004

Page 2: Mapping OASIS Technical Work: Where’s Reliability? jamie.clark@oasis-open.orgjamie.clark@oasis-open.org New Orleans, April 2004.

© OASIS 20042

OverviewOverview

Standards good OASIS good Reliability good

Page 3: Mapping OASIS Technical Work: Where’s Reliability? jamie.clark@oasis-open.orgjamie.clark@oasis-open.org New Orleans, April 2004.

© OASIS 20043

Why do standards matter? Why do standards matter? ROIROI for e-commerce for e-commerceWhy do standards matter? Why do standards matter? ROIROI for e-commerce for e-commerce

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

Things that help: Stable source and versioning Reliable, stated terms of availability Interoperable standards Converging standards

Page 4: Mapping OASIS Technical Work: Where’s Reliability? jamie.clark@oasis-open.orgjamie.clark@oasis-open.org New Orleans, April 2004.

© OASIS 20044

Interoperability & Interoperability & convergenceconvergence

First filter: open standards process Second filter: proximity breeds comparison

& convergence … and customers drive convergence & optimization

Third filter: methods find their place in the marketplace

1 2 3

Page 5: Mapping OASIS Technical Work: Where’s Reliability? jamie.clark@oasis-open.orgjamie.clark@oasis-open.org New Orleans, April 2004.

© OASIS 20045

ReviewReview

Standards good OASIS good

Interoperability & convergence good

Reliability good But what is reliability?

Page 6: Mapping OASIS Technical Work: Where’s Reliability? jamie.clark@oasis-open.orgjamie.clark@oasis-open.org New Orleans, April 2004.

© OASIS 20046 Common transport (HTTP, etc.)

Common language (XML)

Candidate alpha model for Candidate alpha model for mapping OASIS e-Business workmapping OASIS e-Business workCandidate alpha model for Candidate alpha model for mapping OASIS e-Business workmapping OASIS e-Business work

Service Discovery

Service Description

Orchestration & Management

Security & Access

Messaging

Data Content

DRAFT

Work in progress

Loosely coupled model

Approachable to end users

Driven by self-description

Page 7: Mapping OASIS Technical Work: Where’s Reliability? jamie.clark@oasis-open.orgjamie.clark@oasis-open.org New Orleans, April 2004.

© OASIS 20047

Common transport (HTTP, etc.)

Common language (XML)

Each specification is a dotEach specification is a dotEach specification is a dotEach specification is a dot

Service Discovery

Service DescriptionSecurity &

Access

Messaging

DRAFT

UDDI

ebXML RegRep

Orchestration & Management

Data Content

Page 8: Mapping OASIS Technical Work: Where’s Reliability? jamie.clark@oasis-open.orgjamie.clark@oasis-open.org New Orleans, April 2004.

© OASIS 20048

Common transport (HTTP, etc.)

Common language (XML)

Some projects issue more Some projects issue more than one specthan one specSome projects issue more Some projects issue more than one specthan one spec

Service Discovery

Service Description

Orchestration & Management

Security & Access

Messaging

Data Content

DRAFT

Page 9: Mapping OASIS Technical Work: Where’s Reliability? jamie.clark@oasis-open.orgjamie.clark@oasis-open.org New Orleans, April 2004.

© OASIS 20049

Common transport (HTTP, etc.)

Common language (XML)

Specifications are at different Specifications are at different approval stagesapproval stagesSpecifications are at different Specifications are at different approval stagesapproval stages

Service Discovery

Service Description

Orchestration & Management

Security & Access

Messaging

Data Content

DRAFT

Approval levels

Pre-approval

Committee Draft

OASIS Standard

Page 10: Mapping OASIS Technical Work: Where’s Reliability? jamie.clark@oasis-open.orgjamie.clark@oasis-open.org New Orleans, April 2004.

© OASIS 20041

0

Common transport (HTTP, etc.)

Common language (XML)

Service Discovery

Service Description

Orchestration & Management

Security & Access

Messaging

Data Content

DRAFT

Approval levelsOASIS Work (April 2004)OASIS Work (April 2004)OASIS Work (April 2004)OASIS Work (April 2004)

Page 11: Mapping OASIS Technical Work: Where’s Reliability? jamie.clark@oasis-open.orgjamie.clark@oasis-open.org New Orleans, April 2004.

© OASIS 20041

1

Common transport (HTTP, etc.)

Common language (XML)

Service Discovery

Service Description

Orchestration & Management

Security & Access

Messaging

Data Content

ebXML CPPA

HumanML, UIML, WSRP

UDDI

DITA*, EntityRes, RELAX-NG, Topic Maps (3), XDI, XRI

ebXML MSG, WS-Rel.

[Conformance], ebXML IIC, XSLT Conf,

DSS, PKI, SAML, WSS, XCBF

[DSML], RLTC, XACML, SPML

WSDM, WSRF*, WSN*

ASAP, BTP, ebXML-BP, WSBPEL, WSCAF

[Auto Repair], AVDL, eGov, Election, eProc, Emerg, Legal XML(7), Materials, PLCS, PPS, TaxML, WAS

ebXML RegRep

DRAFT

Approval levels

FWSI, TransWS, BCM, ebSOA*

OASIS Work (April 2004)OASIS Work (April 2004)OASIS Work (April 2004)OASIS Work (April 2004) CIQ, DocBook, OpenOffice, UBL, XLIFFCAM

* New TCs

Page 12: Mapping OASIS Technical Work: Where’s Reliability? jamie.clark@oasis-open.orgjamie.clark@oasis-open.org New Orleans, April 2004.

© OASIS 20041

2

Common transport (HTTP, etc.)

Common language (XML)

Service Discovery

Service Description

Orchestration & Management

Security & Access

Messaging

Data Content

DRAFT

Approval levelsWhere’s Where’s “Reliability”?“Reliability”?Where’s Where’s “Reliability”?“Reliability”?

Page 13: Mapping OASIS Technical Work: Where’s Reliability? jamie.clark@oasis-open.orgjamie.clark@oasis-open.org New Orleans, April 2004.

© OASIS 20041

3

Common transport (HTTP, etc.)

Common language (XML)

Service Discovery

Service Description

Orchestration & Management

Security & Access

Messaging

Data Content

DRAFT

Approval levelsMonday A.M.: TRANSACTIONSMonday A.M.: TRANSACTIONSMonday A.M.: TRANSACTIONSMonday A.M.: TRANSACTIONS

WSDM, WSRF, WSN

ASAP, BTP, ebXML-BP, WSBPEL, WSCAF

CAM

Page 14: Mapping OASIS Technical Work: Where’s Reliability? jamie.clark@oasis-open.orgjamie.clark@oasis-open.org New Orleans, April 2004.

© OASIS 20041

4

Common transport (HTTP, etc.)

Common language (XML)

Service Discovery

Service Description

Orchestration & Management

Security & Access

Messaging

Data Content

DRAFT

Approval levelsMonday P.M.: SECURITYMonday P.M.: SECURITYMonday P.M.: SECURITYMonday P.M.: SECURITY

DSS, PKI, SAML, WSS, XCBF

DSML, RLTC, XACML, SPML

Page 15: Mapping OASIS Technical Work: Where’s Reliability? jamie.clark@oasis-open.orgjamie.clark@oasis-open.org New Orleans, April 2004.

© OASIS 20041

5

Common transport (HTTP, etc.)

Common language (XML)

Service Discovery

Service Description

Orchestration & Management

Security & Access

Messaging

Data Content

DRAFT

Approval levelsTuesday A.M.: MESSAGINGTuesday A.M.: MESSAGINGTuesday A.M.: MESSAGINGTuesday A.M.: MESSAGING

ebXML MSG, WS-Rel.

Page 16: Mapping OASIS Technical Work: Where’s Reliability? jamie.clark@oasis-open.orgjamie.clark@oasis-open.org New Orleans, April 2004.

© OASIS 20041

6

Common transport (HTTP, etc.)

Common language (XML)

Service Discovery

Service Description

Orchestration & Management

Security & Access

Messaging

Data Content

DRAFT

Approval levelsTuesday P.M.: METADATA & Tuesday P.M.: METADATA & USE CASESUSE CASESTuesday P.M.: METADATA & Tuesday P.M.: METADATA & USE CASESUSE CASES

UDDI

Auto Repair, AVDL, Ctrade, Educ, eGov, Election, eProc, Emerg, Legal XML(8), Materials, PLCS, PPS, TaxML, WAS

ebXML RegRep

CIQ, DocBook, OpenOffice, UBL, XLIFF

Page 17: Mapping OASIS Technical Work: Where’s Reliability? jamie.clark@oasis-open.orgjamie.clark@oasis-open.org New Orleans, April 2004.

Mapping OASIS Technical Work:

Where’s Reliability?

Mapping OASIS Technical Work:

Where’s Reliability?

[email protected]@[email protected]@oasis-open.orgNew Orleans, April 2004New Orleans, April 2004New Orleans, April 2004New Orleans, April 2004