1 / 10

OASIS and Web Services

OASIS and Web Services. Karl Best OASIS Director of Technical Operations. OASIS Mission. Promote the use of structured information technologies by implementing through Horizontal initiatives Vertical Schemas / DTDs Infrastructure/Interoperability Conformance. OASIS standards process.

leanna
Download Presentation

OASIS and Web Services

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. OASIS and Web Services Karl Best OASIS Director of Technical Operations

  2. OASIS Mission • Promote the use of structured information technologies by implementing through • Horizontal initiatives • Vertical Schemas / DTDs • Infrastructure/Interoperability • Conformance

  3. OASIS standards process • Bottom-up, member driven; do the work our members bring to us • Standards are created under an open, vendor-neutral process • Any interested parties may participate, comment; all activities visible to the public

  4. Where we fit Vertical industry applications OASIS, industry associations Horizontal, interoperability, e-business framework OASIS HTML, XML, XSL, namespace, DOM, etc. W3C Core protocols e.g. HTTP, TCP/IP IETF, etc.

  5. Current Work: ebXML • Teams applicable to Web Services • Messaging • Security • Trading Partners • Registry/Repository • etc. • v1.0 Specifications to be completed May 2001 • Various pieces of ebXML to be continued at UN/CEFACT, as OASIS technical committees, or elsewhere

  6. Current Work: OASIS TCs • Current OASIS technical committees applicable to Web Services • Registry/Repository • Business Transactions • Directory Services (DSML) • Security Assertions (SAML) • Security Access Control (XACML, new)

  7. Areas for Collaboration • Messaging  SOAP, XML Protocol • Security  processing intermediaries • TP, Reg/Rep  UDDI • CPP/CPA  WSDL • BTP  SOAP, transaction processing • etc.

  8. Why Collaborate? • W3C and OASIS – and others – are interested in web services topics, but all have finite resources • Pieces of the work will happen, regardless, at various organizations; take advantage of the work by making it all work together; cooperate in developing the complete picture

  9. How to Collaborate? • Just a suggestion…. • W3C web services WG(?) define the big picture, identify existing pieces • Formal collaboration process and coordination group

  10. A Collaborative Effort W3C OASIS others

More Related