1. © OASIS 2004 Relationship Between Open Standards and Open Source Software Open Source in Government Washington, DC 15-17 March 2004 Patrick Gannon President & CEO

2. oasis-open.org © OASIS 2004 zWhy Open Standards zWho is OASIS zThe OASIS Conceptual Model zOASIS Standards & Open Source Implementations zBenefits from Participating Agenda

3. © OASIS 2004 Why Open Standards

4. oasis-open.org © OASIS 2004 What is an Open Standard? zJust anything a single vendor declares is a standard? Or anything on which two or more vendors agree? yThese may be “specifications” or “de facto standards”, but not “open standards” from the OASIS point of view zOpen Standards are specifications developed and/or approved under a yPublished, consistent process yFair environment yTransparent, open operations yTransparent output

5. oasis-open.org © OASIS 2004 What is an Open Standard? An open standard is: zpublicly available in stable, persistent versions zdeveloped and approved under a published process zopen to public input: public comments, public archives, no NDAs zsubject to explicit, disclosed IPR terms zSee the US, EU, WTO governmental & treaty definitions of “standards” Anything else is proprietary: zThis is a policy distinction

6. oasis-open.org © OASIS 2004 Coordination of standards at OASIS zOASIS recognizes the many dependencies across standards organizations yPromote interoperability yReduce duplication zOASIS participates in and coordinates with many other standards and industry coordination efforts, e.g., yW3C and OASIS management meetings yISO/IEC/ITU/ECE coordination MoU yRosettaNet, OMA, AIAG, WS-I, GGF, etc. yCat A liaisons with TC154, various JTC1 SCs

7. oasis-open.org © OASIS 2004 Coordination of standards at OASIS zCompleted OASIS standards can be submitted to other SDOs yebXML submitted to ISO TC154 ySAML, XACML submitted to ITU-T SG17

8. oasis-open.org © OASIS 2004 Formula for Sustainable Standards Market Adoption Open Standardization Traction Sanction Proprietary JCVConsortiaSDO SGML ISO XML W3C SOAP v1.1 SOAP v1.2 W3C UDDI v2,3 UDDI.org WSDL v1.2 W3C ebMSG v2 OASIS WSDL v1.1 eb Reg v2 OASIS WS-S v1.0 BPEL4WS WS-BPEL OASIS WSS OASIS WS-- * ? UDDI v2,3 OASIS ebXML ISO 15000

9. © OASIS 2004 Who is OASIS?

10. oasis-open.org © OASIS 2004 Overview zOASIS is an international consortium dedicated to developing and promoting the adoption of e-business specifications zMember-elected Board of Directors and Technical Advisory Board; member-driven standards process zMembers of OASIS are providers, users and specialists of standards-based technologies and include organizations, individuals, industry groups, and government agencies. zInternational, not-for-profit, open, independent zSuccessful through industry-wide collaboration

11. oasis-open.org © OASIS 2004 OASIS Members Represent the Marketplace

12. oasis-open.org © OASIS 2004 International Representation

13. oasis-open.org © OASIS 2004 OASIS technical work zThe OASIS technical agenda is set by our members; bottom-up approach zTechnical committees formed by the proposal of our members zEach Technical Committee sets its own scope, schedule, and deliverables zMore than 60 Technical Committees in a variety of topic areas yE-business ySecurity yWeb services yPublic sector

14. oasis-open.org © OASIS 2004 OASIS standards process zSpecifications are created under an open, democratic, vendor-neutral process yAny interested parties may either participate or comment yNo one organization can dictate the specification yEnsures that specifications meet everyone’s needs, not just largest players’ zAll discussion open to public inspection and comment zBi-level approval process yTC approves Committee Draft yOASIS members approve OASIS Standard zResulting work is representative broad range of industry, not just any one vendor’s view

15. oasis-open.org © OASIS 2004 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 Draft 4.TC conducts public review, and three or more OASIS members must implement the specification 5.TC revises and re-approves the specification 6.TC votes to submit the Committee Draft to OASIS membership for consideration 7.OASIS membership reviews, approves the Committee Draft as an OASIS Standard

16. © OASIS 2004 The OASIS Conceptual Model

17. oasis-open.org © OASIS 2004 zA model to describe the technical activities of industry organizations yDescriptive, not Prescriptive zIdentify overlaps for the purpose of increasing collaboration zIdentify gaps for the purpose of starting new work Purpose of a Conceptual Model

18. oasis-open.org © OASIS 2004 Previous Work: BIC B2B Model Source: Business Internet Consortium (BIC) Whitepaper, “High-Level Conceptual Model for B2B Integration ”, March 02, 2002

19. oasis-open.org © OASIS 2004 OASIS Conceptual Model for eBusiness standards Quality of ServicesManagement S e c u r i t y XML Syntax Network Transport 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 Conformance and Interoperability

20. oasis-open.org © OASIS 2004 OASIS Conceptual Model: populated Q u a l I t y o f S e r v I c e sM a n a g e m e n t S e c u r i t y Network Transport Generalized Processes Specialized Processes Generalized Content Specialized Content Transaction Patterns Transaction Instance XML Syntax Messaging Service Description Language Presentation Description Repository Registry / Directory Process Description Language Content Definition Language Conformance and Interoperabilit y Auto-Repair, C-Trade, Education, eGovernment, ElectionML, eProcurement, Emergency, LegalXML(8), MaterialsML, PLCS, ProdPS, TaxXML 19 ASAP, BCM, BTP, CAM, ebXML-BP, FWSI, TransWS, WSBPEL 8 XACML, AVDL, XCBF, DSS, DSML, XRI, PKI, RLTC, SAML, SPML, WAS, WSDM, WSS 13 Entity-Resolution, RELAX-NG, Topic Maps (3) 5 UIML, WSRP, HumanML 3 DSS, ebXML- RegRep, UDDI 3 ebXML- CPPA 1 ebXML-MSG, WSRM 2 Conformance, ebXML-IIC, XSLT- Conformance 3 CIQ, UBL, Doc- Book, XLIFF, OpenOffice 5

21. oasis-open.org © OASIS 2004 OASIS Conceptual Model: populated Q u a l I t y o f S e r v I c e sM a n a g e m e n t S e c u r i t y Network Transport Generalized Processes Specialized Processes Generalized Content Specialized Content Transaction Patterns Transaction Instance XML Syntax Messaging Service Description Language Presentation Description Repository Registry / Directory Process Description Language Content Definition Language Conformance and Interoperabilit y Auto-Repair, C-Trade, Education, eGovernment, ElectionML, eProcurement, Emergency, LegalXML(8), MaterialsML, PLCS, ProdPS, TaxXML 19 ASAP, BCM, BTP, CAM, ebXML-BP, FWSI, TransWS, WSBPEL 8 XACML, AVDL, XCBF, DSS, DSML, XRI, PKI, RLTC, SAML, SPML, WAS, WSDM, WSS 13 UIML, WSRP, HumanML 3 DSS, ebXML- RegRep, UDDI 3 ebXML- CPPA 1 ebXML-MSG, WSRM 2 CIQ, UBL, Doc- Book, XLIFF, OpenOffice 5 Entity-Resolution, RELAX-NG, Topic Maps (3) 5 Conformance, ebXML-IIC, XSLT- Conformance 3 Final approval (as of Dec 2003) Preliminary approval

22. © OASIS 2004 OASIS Work that has Produced Open Source Projects and Software

23. oasis-open.org © OASIS 2004 Open Source Software built on Standards from OASIS TCs zAsynchronous Service Access Protocol (ASAP) zContent Assembly Mechanism (CAM) zDocbook zebXML Collaboration Protocol Profile & Agreement (CPPA) zebXML Messaging Services zebXML Registry/Repository zeXtensible Access Control Markup Language (XACML) zOpen Office XML Format zRelaxNG Schema zUDDI Specification zWeb Services for Remote Portlets (WSRP) zWeb Services Security (WSS)

24. oasis-open.org © OASIS 2004 Suggestions for Collaborative efforts zGovernment and research funding projects should coordinate open standards development with any OSS development zOASIS provides mechanisms to publicize OSS that implements OASIS Standards yOASIS TC and Affiliate web pages yOASIS Registry of Implementations yXML.org Focus Areas & CoverPages yOASIS Sponsored Interoperability Tests & Demos

25. © OASIS 2004 Why Participate in OASIS

26. oasis-open.org © OASIS 2004 Membership Benefits zInfluence zInformation zParticipation zEducation zCo-ordination zCreadibility zVisibility zOpeness

27. oasis-open.org © OASIS 2004 Software Vendor Benefits zForm a committee to standardize current proprietary processes or schemas zInfluence the direction of an existing committee by submitting materials to the committee zInfluence the direction by articulating preferences zGain early feedback on new concepts and ideas zAccess to early drafts of new specifications zActivly participate in interoperability tests zFind partners and develop joint solutions zBecome part of a ”bigger picture”; especially important for small – medium software vendors zPromote your company thru events and information channel sponsorship zMeet and work with end user organisation as well as industry organisation zIdentify potential customers with a real and expressed needs

28. oasis-open.org © OASIS 2004 End-User Company Benefits zEducate employees on trends and developments of technology zLearn and adopt best practices zInfluence direction and priorities of standards development by providing business requirements zEvaluate and observe vendors in their implementation and product directions zParticipate in interoperability demos by providing business scenarios zSee practical implementation from multiple vendors for given scenarios

29. oasis-open.org © OASIS 2004 Industry Organisation Benefits zEducate staff to learn about general e-Business frameworks zInfluence software vendors to develop solutions for your industry yIncreases number of competitive solutions yLowers cost of implementations for your members zEnable cross-industry adoption zProvide visability for your industry efforts zCoordinate complimentary standards activities – minimise overlap of efforts zSpeed up development and adoption of new technologies and emerging standards into your industry zMinimize risk in evaluation of new technology directions

30. oasis-open.org © OASIS 2004 Government Benefits zEducate staff to learn about general e-Business frameworks zInfluence software vendors to develop solutions for your government yIncreases number of competitive solutions yLowers cost of implementations for your agencies zEnable cross-government adoption zParticipate in inter-government standards activities zLearn and adopt best practices zCoordinate complimentary standards activities – minimise overlap zSpeed up development and adoption of new technologies and emerging standards zMinimize risk in evaluation of new technology directions zMonitor open standards and marketplace up-take for recommendation in government structure zMonitor and evaluate best practises for recommendations to industries and companies within your country or region

31. oasis-open.org © OASIS 2004 University and Research Centre Benefits zMonitor ”state of the art” in technology and standards development zPropose new ideas and get feedback to those ideas zReduce the ”time to market” from concept to wide spread adoption zCreate a broader market for adoption of development from your research projects zGain visability for your project efforts zEstablish closer ties with more busineses and industry organisations

32. oasis-open.org © OASIS 2004 Individual Member Benefits zEducate yourself on trends and developments of technology zHelp start a committee to standardize processes or schemas zInfluence the direction of an existing committee by submitting materials zVote on approval of Committee Draft specifications zGain visability as an active participant and/or leader (Chair, Co-chair, Editor, etc.) zUse opportunities to network with other committee members zLearn leadership and concensus building skills

33. zwww.xml.orgzwww.xml.coverpages.org zwww.oasis-open.org patrick.gannon@oasis-open.org