copyright © oasis open, 2003 oasis technical work status february 2003 karl best oasis vice...

Copyright © OASIS Open, 2003

OASIS Technical Work StatusFebruary 2003

Karl BestOASIS Vice President


• This presentation is kept current and available at http://www.oasis-open.org/presentations/tc_status.ppt

• Current list and summaries of TCs at http://www.oasis-open.org/committees/committees.shtml


Summary

• OASIS is a member-lead consortium dedicated to building interoperability specifications

• Open, democratic, neutral member-driven technical process

• Successful in establishing relationships with other orgs; promoting interoperability

• Successful in converging competing efforts, completing work begun elsewhere


Overview• OASIS is a member-led consortium dedicated to

building systems interoperability specifications– Member-elected Board of Directors and Technical

Advisory Board– Member-driven standards process

• We focus on industry applications of structured information standards such as XML

• Members of OASIS are providers, users and specialists of standards-based technologies and include organizations, individuals and industry groups. – 300+ organizational members, ~275 individual members

• International, not-for-profit, open, independent• Successful through industry-wide collaboration


OASIS technical agenda

• The OASIS technical agenda is set by our members; bottom-up approach

• Technical committees formed by the proposal of our members; TC sets its own schedule and deliverables

• Member-elected Board of Directors and Technical Advisory Board


OASIS standards process

• Specifications are created under an open, democratic, vendor-neutral process– Any interested parties may either participate or comment– No one organization can dictate the specification– Ensures that specifications meet everyone’s needs, not just

largest players’

• All discussion open to public inspection and comment• Bi-level approval process

– TC approves Committee Specification– OASIS members approve OASIS Standard

• Resulting work is guaranteed to be representative of the industry as a whole, not just any one vendor’s view


OASIS relationships

• Promote cooperation and liaisons between OASIS TCs– No top-down agenda for which TCs will be

created; overlap possible, so emphasis on coordination

• Joint Committees provide forum for communication between TCs


OASIS relationships (cont.)

• Attempt to cooperate and liaise with other standards organizations as much as possible– Prevent duplication, promote

interoperability

– Gain sanction/authority for OASIS work

• Working relationships with– W3C, OMG, IDEAlliance, OAG, HL7,

CommerceNet, LISA, etc.


OASIS relationships (cont.)

• Formal relationships with– ISO/IEC/ITU/UN-ECE Memorandum of

Understanding (MoU) for E-Business– ISO TC154, e-business standards (Category

A Liaison)– ISO/IEC JTC SC34, markup languages

(Category A Liaison)– ISO/IEC JTC SC6, security (Category A

Liaison)– ITU-T A.4 and A.5 Recognition


What OASIS Offers Its Members

• Opportunity to pursue technical work in a neutral environment– Buy-in and support from developers and

implementers

• Opportunity to set the technical agenda of a recognized industry standards organization– OASIS member-driven technical process


What OASIS Offers Industry

• Time to Market: bring your work here and avoid wasting time and effort setting up– Committee process– Infrastructure (web site, mail lists)– IPR policy and copyright protection– Program management– Marketing/Promotion– Anti-trust

• Use your technical expertise on technical work, not on setting up administrative overhead


What OASIS Offers Industry (cont.)• Opportunity for convergence

– Various OASIS TCs are the result of two or more industry groups or existing specs coming together under the neutral OASIS process


Progression/Approval of OASIS technical work

1. Any three or more OASIS members propose creation of a technical committee (TC)

2. Existing technical work submitted to TC; or TC starts work at the beginning. TC conducts and completes technical work; open and publicly viewable

3. TC votes to approve work as an OASIS Committee Specification

4. TC conducts public review, and three or more OASIS members implement the specification

5. TC votes to submit the Committee Specification to OASIS membership for consideration

6. OASIS membership reviews, approves the Committee Specification as an OASIS Standard


Progression of Specs to Standards• Committee Specs approved as OASIS Standards

– DocBook v4 (Jan 2001)

– ebXML RIM (April 2002)

– ebXML RS (April 2002)

– DSML (April 2002)

– ebXML Messaging (July 2002)

– SAML (Nov 2002)

– ebXML CPPA (Nov 2002)

– XACML (Feb 2003)

• ~20 Committee Specs completed; some to be submitted to OASIS members for approval


Current TC status

• Currently 50+ OASIS Technical Committees, two Joint Committees, and three Member Sections

• Growing by ~2 new TCs a month since mid 2001

• Additional proposals in the works...


Current Technical Committees• Access Control (XACML)• Auto Repair• Business Transaction

Protocol (BTP)• Common Biometric Format

(XCBF)• Conformance• Content Assembly

Mechanism (CAM)• Controlled Trade• Customer Information

Quality (CIQ)• Digital Signature Services

(DSS)• Directory Services (DSML)• DocBook• ebXML Collaborative

Partners (CPPA)• ebXML Implementation,

Interoperability (IIC)• ebXML Messaging• ebXML Registry

• Education XML• E-Government• Election and Voter

Services• Emergency XML• Entity Resolution• Extensible Resource

Identifier (XRI)• Human Markup• LegalXML Court Filing• LegalXML eContracts• LegalXML eNotarization• LegalXML Integrated

Justice• LegalXML Lawful

Intercept• LegalXML Legislative

Information• LegalXML Online Dispute

Resolution (ODR)• LegalXML Transcripts• Localization Interchange

(XLIFF)


Current Technical Committees (cont.)• Management Protocol

• Public Key Infrastructure (PKI)

• Open Office XML Format

• Provisioning Services (SPML)

• RELAX NG

• Rights Language (RLTC)

• Security Services (SAML)

• Tax XML

• Topic Maps Published Subjects

• Topic Maps Published Subjects for Geography and Language

• Topic Maps Vocabulary for XML Standards

• Translation Web Services

• UDDI Specifications

• Universal Business Language

• User Interface (UIML)• Web Services

Distributed Mgmt• Web Services for

Interactive Applications (WSIA)

• Web Services Reliable Messaging

• Web Services Remote Portal (WSRP)

• Web Services Security (WSS)

• XSLT Conformance


Technical Committee Details

• Summary and current status of each TC available at http://oasis-open.org/committees/committees.shtml

• TC mail list archives available at http://lists.oasis-open.org/archives/

http://oasis-open.org/committees/committees.shtml

http://oasis-open.org/committees/committees.shtml

http://lists.oasis-open.org/archives/


The OASIS Conceptual Model

• A descriptive, strategic framework to promote coordination of OASIS technical efforts

• A communication vehicle to promote collaboration with other industry standards organizations

• Describes high-level architecture components of business solutions


Qu

ality

of S

erv

ice

s

Conceptual Model For OASIS

Ma

na

ge

me

nt

S e

c u

r i t y

XML Syntax

Network

Transport

Vertical Industry Area

XML and Web Services Area

Generalized Processes

Specialized Processes

Generalized Content

Specialized Content

Messaging

Service Description Language

Presentation Description

Transaction Patterns

Transaction Instance

Repository

Registry / Directory

Process Description Language Content Definition Language

Co

nfo

rma

nc

e a

nd

Inte

rop

era

bility


The Conformance Area


Qu

ality

of S

erv

ice

s


Ma

na

ge

me

nt

S e

c u

r i t y

XML Syntax

Network

Transport





Generalized Content

Specialized Content

Messaging





Repository



Co

nfo

rma

nc

e a

nd

Inte

rop

era

bility


Definitions

• Conformance– Ensuring that an application or

implementation of a specification conforms to that specification through testing


OASIS TCs: Conformance and Interoperability• Conformance

• ebXML Implementation, Interoperability, Conformance (IIC)

• XSLT Conformance

• XML Conformance (completed)


The Vertical Industries Area


Qu

ality

of S

erv

ice

s


Ma

na

ge

me

nt

S e

c u

r i t y

XML Syntax

Network

Transport





Generalized Content

Specialized Content

Messaging





Repository



Co

nfo

rma

nc

e a

nd

Inte

rop

era

bility


Definitions

• Business Transaction Patterns– Actual specification of pre-defined combination of

business content and business processes for valid business transactions. The specs also describe rules needed to validate combination of specialize and universal business contents and processes.

• Business Transaction Instance– Particular instance of business transactions generated

between trading partners. Represents real binding of Business Content and Business Process. It includes complex business transactions that compose of several sub-business transactions represented as recursive Business Content and Business Process


Definitions (cont.)

• Business Content Format Definition– Business Content includes everything that composes the

payload of business transactions, which dictionary entries, composition of dictionary entries, special business documents, and attachments. Business Content Format Definition is the specification of the data structures, data types, constraints and code lists of all the items necessary to compose valid business content.

• Specialized Business Content– Industry- or supply chain-specific technical lexicon (terms,

properties, values, taxonomic structures) to be used to extend and specialize the Universal content to construct the content of an industry-specific business document.


Definitions (cont.)

• Universal Business Content– Specifies business terminology and accepted values that

may be universally used in business messages that support a broad range of industries, business models and locales; the vocabulary used to construct the business content of a message. This content covers many domains of discourse, such as product, materials management, finance, quality.

– Note the distinction between "universal" and "specialized" is relative and could change over time and situation. The purpose of this distinction to drive reuse and achieve manageability and economies of scales.


Definitions (cont.)

• Universal Business Process– Specifies business processes that are applicable to a

broad range of businesses, regardless of the vertical industry or locale within which the business operates or of the specific characteristics of the business. These processes cover many domains of activity that businesses engage in, such as collaborative product development, request for quote, supply chain execution, purchasing, and manufacturing.

– Note the distinction between "universal" and "specialized" is relative and could change over time and situation. The purpose of this distinction to drive reuse and achieve manageability and economies of scales.


Definitions (cont.)

• Specialized Business Process– Specifies business processes that are

not Universally applicable but instead are specific to a business operating within a specific industry or supply chain (such as Electronic Components, Pharmaceuticals, Automotive), and locales or business models.


Definitions (cont.)

• Trading Partner Agreement– Dynamic creation and management of

trading partner agreements between partners. Profiles of trading partner’s B2B infrastructure, protocols, contractual agreement for transactions. This layer also defines binding of business processes and business content to complete particular business transactions.


OASIS TCs: Vertical

• Automotive Repair Information• Controlled Trade• Docbook• Education XML• e-Government• Election and Voter Services• Emergency• Human Markup• Tax XML


OASIS TCs: Vertical (cont.)

• LegalXML – Court Filing

– eContracts

– eNotarization

– Integrated Justice

– Lawful Intercept

– Legislative Information

– Online Dispute Resolution (ODR)

– Transcripts


OASIS TCs: Vertical (cont.)

• Generalized Content Definition– Customer Information Quality (CIQ)

– Open Office XML

• Generalized Processes– ebXML CPPA

– Localization Interchange Format (XLIFF)

– Provisioning Services (SPML)

– Translation Web Services

– Content Assembly Mechanism (CAM)


The XML and Web Services Area


Qu

ality

of S

erv

ice

s


Ma

na

ge

me

nt

S e

c u

r i t y

XML Syntax

Network

Transport





Generalized Content

Specialized Content

Messaging





Repository



Co

nfo

rma

nc

e a

nd

Inte

rop

era

bility


Definitions

• Business Process Description Language– Specifies the way in which any business process

(whether Universal or specific in nature) is recorded, such that is understood and executable in a repeatable fashion by a wide array of humans and/or applications.

• Directory and Registry Service– Specifies the structure and access protocol of

registries and repositories that trading entities can access to discover each other’s capabilities and services. Covers naming, directory, registry, privacy, authorization and identification services.


Definitions (cont.)

• Repository– Standardized dictionary and repository services

that specifies the structure and access protocol and schemas for business content storage and retrieval, which includes the term, its constraints, its representations, etc.

• Presentation Description Language– This layer describes tools and protocols for user

interfaces and user interactions. It also provides specs for different formats needed for effective visual communication with end users, therefore, enhance end-user experience with applications.


Definitions (cont.)

• Service Description Language– This layer describes the tools and languages for service

implementation and service interface, which is key to achieving loosely coupled architecture and reducing the amount of custom programming and the effort of integration between service requester and service provider.

• Messaging– Standardized message and envelope structure and layout

definitions, which have specific technical purposes. This layer addresses the need to record session and communication settings for message transport in order to enable coordination between parties in a business transaction, including parameters that control Reliable Messaging, Secured Messaging, etc.


Definitions (cont.)

• Security– This layer spans a wide range of abstractions from basic

encryption, authentication and authorization on the core XML layer to non-repudiation and security policies in the business process layer.

• Management– This layer specifies system management tools and

standards that can be used to discover the existence,availability and health of a B2B solution. Furthermore, the management tools should also be able to control and configure the components.


Definitions (cont.)

• Quality of Service– This layer is closely related with the Management layer. It

focus overall service-level management issues and related protocols at all level to enable policy management of service-levels and monitor the services provided by applications.


OASIS TCs: XML and Web Services• Registries, Repositories, and Directories

– Directory Services (DSML)

– ebXML Registry

– UDDI Specs

• Messaging– ebXML Messaging

– Web Services Reliable Messaging

• Content Definition Language– Universal Business Language (UBL)


OASIS TCs: XML and Web Services (cont.)• XML Syntax

– Entity Resolution

– RELAX NG

– Topic Maps Published Subjects

– Topic Maps PS Geography /Languages

– Topic Maps PS XML Standards Vocabulary


OASIS TCs: XML and Web Services (cont.)• Security

– Access Control (XACML)

– Common Biometric Format (XCBF)

– Digital Signature Services (DSS)

– Extensible Resource Identifier (XRI)

– Public Key Infrastructure (PKI)

– Rights Language (RLTC)

– Security Services (SAML)

– Web Services Security (WSS)


OASIS TCs: XML and Web Services (cont.)• Process Description Language

– Business Transaction Protocol (BTP)

• Presentation Description– User Interface (UIML)– Web Services for Interactive Applications

(WSIA)– Web Services Remote Portal (WSRP)

• Management– Management Protocol – Web Services Distributed Management


The non-OASIS Area


Qu

ality

of S

erv

ice

s


Ma

na

ge

me

nt

S e

c u

r i t y

XML Syntax

Network

Transport





Generalized Content

Specialized Content

Messaging





Repository



Co

nfo

rma

nc

e a

nd

Inte

rop

era

bility


Definitions

• Network Transport– This layer addresses the basic messaging transport

protocols needed to communicate on the Internet, messaging services that provide for asynchronous publish/subscribe, asynchronous message queuing, and synchronous request/reply, and how messages are placed on the transport bus and taken off the bus. These standards specify mechanisms for transporting messages in a secure and reliable way

• Core XML Standards– XML 1.0 is the World Wide Web Consortium (W3C) standard

for document syntax. There are associated W3C standards for defining document types and for accessing the data within the documents. This syntax is used to express specifications in the layers above "Core XML Standards" in the Conceptual Model.


TC details...


Access Control (XACML)

• Started: May 2001• Charter: develop XACML, a

specification for expressing policies for information access over the Internet

• Co-chairs: Carlisle Adams, Entrust; Hal Lockhart, BEA

• Current status: Approved OASIS Standard, January 2003


Automotive Repair Information

• Started: July 2002

• Charter: develop XML syntax for exchange of automotive repair information between manufacturers and repair facilities

• Chair: Paul Greening, individual member

• Current status: work in progress


Business Transaction Protocol (BTP)• Started: March 2001

• Charter: develop BTP, an XML-based protocol for managing complex, persistent B2B Internet transactions

• Chair: Bill Pope, individual member

• Current status: Committee Specification approved


Common Biometric Format (XCBF)• Started: March 2002

• Charter: develop XCBF, a standard XML schema for description of biometric information

• Chair: Phil Griffin, individual member



Conformance

• Started: 1999• Charter: develop guidelines and

resources for the creation of conformance test suites

• Chair: Lynne Rosenthal, NIST; Mark Skall, NIST

• Current status: Committee Specification approved; continuing work


Content Assembly Mechanism

• Started: December 2002

• Charter: develop a generalized mechanism in XML for business process context and business rules

• Chair: David Webber, XML Global

• Current status: first mtg December 2002


Controlled Trade

• Started: June 2002

• Charter: develop a unified vocabulary for trade activities related to controlled products

• Chair: Todd Harbour, individual member



Customer Information Quality (CIQ)• Started: early 2000

• Charter: develop XML-based specifications for customer profile and addressing information

• Chair: Ram Kumar, Mastersoft

• Current status: Committee Specifications approved; continuing work


Digital Signature Services (DSS)


• Charter: develop applications of Digital Signature

• Chair: Robert Zuccherato, Entrust

• Current status: first meeting December 2002


Directory Services (DSML)

• Started: 1999

• Charter: develop DSML, an XML-specification for marking up directory services information

• Co-chairs: James Tauber, mValent; Winston Bumpus, Novell

• Current status: DSML v2.0 approved as OASIS Standard, April 2002


DocBook

• Started: 1992 as Davenport Group; moved to OASIS in 1998

• Charter: develop the DocBook DTD/Schema for computer documentation

• Chair: Norm Walsh, Sun Microsystems

• Current status: v4.1 approved as an OASIS Standard in January 2001; v4.2 approved as a Committee Spec; continuing work


ebXML Collaborative Partners (CPPA)• Started: July 2001

• Charter: continued development of ebXML CPP and CPA specifications

• Chair: Dale Moberg, Cyclone Commerce

• Current status: CPPA approved as OASIS Standard, October 2002


ebXML Implementation, Interop, Conformance (IIC)• Started: August 2001

• Charter: develop guidelines and tools for interoperability, implementation, and conformance of the ebXML specs in order to promote their adoption

• Co-chairs: Jacques Durand, Fujitsu; Jeff Eck, GE Global



ebXML Messaging


• Charter: continue development of the ebXML Messaging specification

• Chair: Ian Jones, individual member

• Current status: Messaging v2 approved as OASIS Standard in July 2002; continuing work


ebXML Registry

• Started: 1999• Charter: continue development of

ebXML Registry & Repository specification

• Chair: Kathryn Breininger, Boeing• Current status: RS and RIM v2

approved as OASIS Standards in April 2002; v2.1 approved as Committee Specs; continuing work


Education XML

• Started: March 2003

• Charter: gather requirements and develop XML specifications for Pre-Kindergarten through 12th grade education

• Chair: Thomas Vreeland, OpenVES

• Current status: first meeting March 2003


e-Government


• Charter: gather requirements for e-government use of XML standards

• Chair: John Borras, UK Office of E-Envoy



Election and Voter Services

• Started: May 2001• Charter: develop XML-based

specification for the standardization of election and voter information

• Co-chairs: Anwar Choudhury and John Borras, UK Office of E-Envoy



Emergency XML

• Started: Feb 2003

• Charter: creation of schemas for the exchange of public emergency information

• Chair: Allen Wyke, Blue292

• Current status: first meeting 6 February 2003


Entity Resolution

• Started: November 2000

• Charter: revision of SGML Open Catalog Specification (TR 9401:1997; “SOCat”) for XML compliance

• Chair: Lauren Wood

• Current status: Committee Specification approved; seeking implementations


Extensible Resource Identifier (XRI)• Started: January 2003

• Charter: define a URI scheme for distributed directory services that enables the identification of resources

• Co-chairs: Drummond Reed, OneName; Gabe Wachob, Visa Int’l

• Current status: first mtg January 2003


Human Markup

• Started: September 2001

• Charter: develop XML-based descriptions of human communication

• Chair: Ranjeeth Kumar Thunga, individual member

• Current status: Committee Spec in public review


LegalXML Court Filing

• Started: June 2002

• Charter: develop specifications for XML-based exchange between courts and attorneys

• Chair: John M. Greacen, individual member



LegalXML eContracts

• Started: Nov 2002

• Charter: develop open XML standards for the markup of legal contract documents

• Chair: Dan Greenwood, individual member

• Current status: First meeting November 2002


LegalXML eNotarization

• Started: Sept 2002

• Charter: develop an agreed set of technical requirements to govern self-proving electronic legal information

• Chair: John Messing, individual member



LegalXML Integrated Justice


• Charter: develop XML specifications for exchanging data among justice system branches and agencies

• Chair: David Roberts, individual member



LegalXML Lawful Intercept

• Started: January 2003

• Charter: produce a lawful interception process framework consisting of XML standards and authentication mechanisms

• Chair: Tony Rutkowski, Verisign

• Current status: first meeting January 2003


LegalXML Legislative Information

• Started: Oct 2002

• Charter: develop XML specifications for markup and exchange of legislative information

• Co-chairs: Daniel Bennett, individual member; Chet Ensign, Lexis Nexis



LegalXML Online Dispute Resolution (ODR)• Started: Dec 2002

• Charter: Develop specifications for online dispute resolution

• Co-chairs: Jim Keane, individual; Debi Miller-Moore, individual

• Current status: First meeting December 2002


LegalXML Transcripts

• Started: Sept 2002• Charter: develop an XML compliant

syntax for representing legal transcript documents either as stand-alone structured content or as part of other legal records

• Chair: Eddie O’Brien, Ringtail Solutions



Localization Interchange (XLIFF)


• Charter: develop XML-based file format for interchange of localization information

• Chair: Tony Jewtushenko, Oracle



Management Protocol


• Charter: develop XML syntax for management protocols

• Chair: Winston Bumpus, Novell



Public Key Infrastructure (PKI)


• Charter: develop white papers, best practices, etc. for the promotion and adoption of PKI

• Chair: Terry Leahy, Wells Fargo

• Current status: first meeting Janaury 2003


Open Office XML Format


• Charter: create an open, XML-based file format specification for office applications

• Chair: Michael Brauer, Sun Microsystems

• Current status: first meeting 16 December


Provisioning Services

• Started: November 2001

• Charter: define Service Provisioning Markup Language (SPML), an XML-based framework for exchanging user, resource, and service provisioning information.

• Chair: Darran Rolls, Waveset



RELAX NG

• Started: February 2001

• Charter: combine TREX and RELAX proposals into a single light-weight XML schema specification

• Chair: James Clark, individual member

• Current status: Committee Specification approved; submitted to ISO/IEC JTC1 SC34; continuing work


Rights Language

• Started: May 2002

• Charter: develop digital rights language

• Chair: Hari Reddy, ContentGuard



Security Services (SAML)

• Started: March 2001• Charter: develop XML specification for

the description of authentication and authorization of internet communications

• Co-chairs: Prateek Mishra, Netegrity; Rob Philpott, RSA

• Current status: SAML approved as OASIS Standard, Oct 2002


Tax XML


• Charter: develop XML syntax for exchange of tax information

• Chair: Gregory Carson, US IRS

• Current status: first meeting 12 December


Topic Maps Published Subjects

• Started: October 2001• Charter: develop guidelines,

recommendations, and applications to promote adoption of Topic Maps Published Subjects (part of ISO 13250 and XML Topic Maps (XTM) 1.0 Specification).

• Chair: Bernard Vatant, Mondeca• Current status: work in progress


TM Published Subjects for Geography and Language• Started: January 2002

• Charter: Define TM published subjects for geography and language based on ISO specs

• Chair: Lars Marius Garshol, individual member



TM Vocabulary for XML Standards• Started: January 2002

• Charter: define a vocabulary for the domain of XML standards and technologies

• Chair: Holger Rath, empolis



UDDI Specifications

• Started: September 2002

• Charter: further development of UDDI registry specification

• Co-chairs: Tom Bellwood, IBM; Luc Clement, Microsoft



Universal Business Language (UBL)• Started: October 2001

• Charter: develop a standard XML business library based on other pre-existing libraries

• Chair: Jon Bosak, Sun Microsystems



User Interface (UIML)


• Charter: develop a specification for an abstract meta-language that can provide a canonical XML representation of any user interface (UI)

• Chair: Didier Courtand, Assoc. Aristote



Web Services Distributed Management (WSDM)• Started: April 2003• Charter: To define XML specifications

for web services architecture and technology to manage distributed resources

• Co-chairs: Winston Bumpus, Novell; Heather Kreger, IBM

• Current status: First meeting April 2003


Web Services for Interactive Applications (WSIA)• Started: November 2001

• Charter: Create an XML and web services centric component model for interactive web applications

• Chair: Charles Wiecha, IBM



Web Services Remote Portal (WSRP)• Started: March 2002

• Charter: Create specification for web services “plug-n-play” portlet to provide content and applications

• Chair: Thomas Schaeck, IBM



Web Services Reliable Messaging (WSRM)• Started: March 2003

• Charter: Create a generic and open model for ensuring reliable message delivery for Web services

• Chair: Tom Rutt, Fujitsu

• Current status: First meeting March 2003


Web Services Security (WSS)


• Charter: Continue work on the Web services security foundations published in the WS-Security specification.

• Co-chairs: Kelvin Lawrence, IBM; Chris Kaler, Microsoft



XSLT Conformance

• Started: 1999

• Charter: develop test suites for testing XSLT application conformance against the W3C XSLT Recommendation

• Chair: Jeff Kenton, DataPower



Joint Committees

• Purpose: coordination between various OASIS TCs– ebXML JC

– Security Standards JC


ebXML Joint Committee

• Purpose: coordination between the ebXML OASIS TCs– Registry

– CPPA

– Messaging

– IIC

• Chair: Dale Moberg, Cyclone Commerce


Security Standards Joint Committee• Purpose: coordination between the

various security-related OASIS TCs– Access Control

– Biometrics

– Provisioning

– Rights Language

– Security Services

• Chair: Phil Griffin, Griffin Consulting


OASIS Member Sections

• A group of technical committees or OASIS members, with its own identity and governance, devoted to a specific technical topic– LegalXML

– PKI

– UDDI


LegalXML (member section)

• Started: 1998, joined OASIS 2002

• Charter: development of XML standards for the legal profession

• Chair: Don Bergeron, LexisNexis

• Current status: eight technical committees

• www.legalxml.org

http://www.legalxml.org/


PKI (member section)

• Started: 1999, joined OASIS 2002

• Charter: development of PKI applications and promotion of PKI technology

• Chair: Terry Leahy, Wells Fargo

• Current status: member section formed November 2002; one technical committee


UDDI (member section)

• Started: 2000, joined OASIS 2002• Charter: development and

implementation of UDDI registry specification

• Chair: George Zagelow, IBM• Current status: member section

formed July 2002, one technical committee

• www.uddi.org

http://www.uddi.org/


Technical Advisory Board (TAB)

• Purpose: – Advise the OASIS Board of Directors on

technical topics that OASIS could pursue– Develop technical architectures in order

to promote coordination between OASIS TCs

• Formed June 2002• Chair: Eduardo Gutentag, Sun

Microsystems


For more information...

• www.oasis-open.org

• xml.coverpages.org

• www.xml.org

copyright © oasis open, 2003 oasis technical work status february 2003 karl best oasis vice...

Documents