UDDI @ OASIS: Accelerating AdoptionWeb Services One ConferenceBoston, MAAugust 27, 2002Patrick GannonPresident & CEO, OASIS

Role of Standards

OASIS Standards: Open and AdoptedMarket AdoptionOpen StandardizationTractionSanctionProprietaryJCVConsortiaSDOSGMLISOXMLW3CSOAP v1.1SOAP v1.2W3CUDDI v3UDDI.orgWSDL v1.2W3Ceb MS v2OASISWSDL v1.1 Standards:UDDI v3xOASISeb Reg v2OASIS

Registry Architecture

The eCo Architecture Specification - Registries CommerceNet eCo Framework WG 1998

Web ServicesStep 1: Description WSDL ebXML CPP Spec and ebXML Business Process SpecStep 2: Publication and DiscoveryUDDIebXML Registry SpecStep 3: Invocation SOAP over HTTPebXML Messaging Spec integrating SOAP, HTTP

OASIS

One Membership Many Opportunities

MissionOASIS drives the development, convergence & adoption of e-business standards.

SummaryOASIS is a member-lead consortium dedicated to building interoperability specificationsOpen, democratic, neutral member-driven technical processSuccessful in establishing relationships with other orgs; promoting interoperabilitySuccessful in converging competing efforts, completing work begun elsewhereSoftware vendors, end-users & government orgs help to insure implementable standards

OASIS technical agendaThe OASIS technical agenda is set by our members; bottom-up approachTechnical committees formed by proposal from our membersMember-elected Technical Advisory Board Attempt to cooperate and liaise with other standards organizations as much as possible

OASIS standards processSpecifications are created under an open, democratic, vendor-neutral processAny interested parties may either participate or commentNo one organization can dictate the specificationEnsures that specifications meet everyones needs, not just largest playersAll discussion open to public commentBi-level approval processTC approves Committee SpecificationOASIS members approve OASIS StandardResulting work is guaranteed to be representative of the industry as a whole, not just any one vendors view

OASIS relationshipsAttempt to cooperate and liaise with other standards organizations as much as possibleAvoid duplication, promote interoperabilityGain sanction/authority for OASIS workWorking and Formal relationships withW3C, OMG, IDEAlliance, OAG, HL7, CommerceNet, LISA, etc.ISO/IEC JTC SC34, ISO TC154 (Cat. A Liaison)ITU-T A.4 and A.5 RecognitionISO, IEC, ITU, UN-ECE Memorandum of Understanding (MoU) for E-Business

Technical Committee ActivitiesOASIS

Current Technical CommitteesAccess Control (XACML)Business Transaction Protocol (BTP)ConformanceControlled Trade MLCustomer Information (CIQ)Directory Services (DSML)DocBookebXML CPPAebXML IICebXML MessagingebXML RegistryElection ServicesEntity ResolutionHuman MarkupProvisioning ServicesRELAX NGRights LanguageSecurity ServicesTopic Maps Published Subj.Topic Maps (Geo & Lang)Universal Business Lang.Vocabulary for XML Stds.Web Services Inter. Appl.Web Services Remote PortalXML Common BiometricXML Localization InterchangeXSLT ConformanceCGM Open (member section)LegalXML (member section)UDDI (member section)

OASIS Technical Committees SecurityAccess Control (XACML)Common Biometric Format (XCBF)Security Services (SAML)Provisioning Services (SPML) Rights Language Web Services Security (WS-S) - - - - - Security Standards Joint Committee

OASIS Technical Committees Web ServicesWeb Services for Interactive Applications (WSIA)Web Services Remote Portal (WSRP)Web Services SecurityUDDI Specification

UDDIAn OASIS Member SectionOASIS

UDDI Specification TC (UDDI)Announced: July 2002Charter: The purpose is to continue work on the Web services registry foundations developed and published by UDDI.org. The UDDI specifications form the necessary technical foundation for publication and discovery of Web services implementations both within and between enterprises.Co-chairs: Tom Bellwood (IBM), and Luc Clement (Microsoft)Current status: first meeting 13 Sept

OASIS Members Form Technical Committee to Advance UDDIUDDI provides a foundation for the infrastructure needed to drive the success of Web services. We are excited to begin work on standardizing the UDDI specification at OASIS, as well as developing and organizing the best practices that relate to its use.

Tom BellwoodIBM

OASIS Members Form Technical Committee to Advance UDDIAdvancing UDDI within OASIS will help accelerate adoption and benefit the entire industry. Interest from OASIS member organizations in moving UDDI forward is high, and we look forward to input from a wide variety of companies.

Luc ClementMicrosoft

OASIS Members Form Technical Committee to Advance UDDIWe believe security for Web services will provide dramatic benefits for governments and enterprises extending their business processes over the Internet. UDDI within OASIS is an important initiative in defining a solution and we intend to continue to support its efforts.Al DeLorenziVP, New Product Portfolio Entrust, Inc.

OASIS Members Form Technical Committee to Advance UDDIBringing UDDI under the OASIS umbrella is a natural fit. With the improved security, subscription capability, and WSDL support in Version 3 of UDDI, it is now critical to focus on the widespread adoption of this core component of Web services.

Andy SweetCTOPerficient

OASIS Members Form Technical Committee to Advance UDDIOASIS is the right body to promote UDDI because of its continuously growing confidence and strong membership from various industry sectors such as vendors, solution providers, end-users, individuals, and research groups. By overseeing UDDI, along with other Web services standards, OASIS is now the central body for Web services standards, and this is great news.Ram KumarChief Technologist and Architect MSI Business Solutions

OASIS Members Form Technical Committee to Advance UDDIToday's collaborative processes build on reliable and seamless publication and discovery of Web services. UDDI provides necessary building blocks to deploy Web services in a standardized manner. To facilitate rapid adoption at the business side, SAP will continue to contribute its customers requirements and long standing industry experience to further drive and enhance UDDI as an OASIS standard. Franz-Josef FritzVP of Technology Product Mgmt. & ArchitectureSAP AG

OASIS Members Form Technical Committee to Advance UDDITIBCO is proud to lend its expertise and experience to the UDDI Specification Technical Committee's goal of refining and changing specifications for Web services. Searching, aggregating, and managing Web services will become critical as these services are deployed.

Ramin SayarDirector of Products and SolutionsTIBCO Software

UDDI Business Registry DataBusiness NameText DescriptionContact InfoKnown Identifiers D-U-N-S, GLN, otherBusiness CategoriesIndustry: NAICSProducts/Services: UNSPSCLocation: ISO 3166Custom categorieseBusiness InfoBusiness servicesService typeBinding information

Simple Question: Isnt UDDI only good for ... the dynamic Discovery of new Trading Partners and their B2B Services in a public Registry?

No, UDDI is also good for ...

The Future for UDDI at OASISMember Driven [the following are just options]UDDI Member SectionPromotion, AdoptionMultiple TC CoordinationLiaison within OASISSecurity JC & TCsOther Web Services TCsebXML Registry TCLiaison with other OrganizationsW3CWS Interoperability (WS-I)

Your Options to ParticipateOutside ObserverMonitor UDDI TC email archivesSubmit suggestions to TC Comment ListCurrent OASIS MemberSend email to TC Co-Chairs by 29 Aug.Not an OASIS MemberJoin OASIS as Organization or IndividualSend email to TC Co-Chairs by 29 Aug.http://www.oasis-open.org/committees/uddi-spec/

OASIS ValueNine years demonstrated successNeutral and independentTechnical and procedural competenceWorldwide visibility and outreachClose coordination with peer standards organizations on a global level

For more information...www.oasis-open.orgxml.coverpages.org/www.xml.org

Patrick GannonPresident & CEOpatrick.gannon@oasis-open.org+1.978.667.5115 x201 (office)+1.408.242.1018 (mobile)

The eCo Framework Architecture is useful to help understand the concept of multiple levels of inter-related meta-data and data. In the real world, there will not be one universal registry or repository covering all levels with every possible entry. The eCo Framework model assumes a network of inter-related registries and repositories that use common interfaces, but are built and maintained to meet specific needs of specific groups.

The left side of the eCo Architecture graphic shows examples of types of registries and within the registries some of the types of information that could be maintained.

The TSIED Core Business Data Repository would be a repository at the Business Environment level and contain structured data on actual businesses. The schema which describes the specific data elements, structure and code lists of types of data would be defined in a Registry of Business Types.