© oasis 2004 relationship between open standards and open source software open source in government...
TRANSCRIPT
© OASIS 2004
Relationship Between Open Standards and
Open Source Software
Open Source in GovernmentOpen Source in GovernmentWashington, DCWashington, DC
15-17 March 200415-17 March 2004
Patrick Patrick GannonGannonPresident & CEOPresident & CEO
© OASIS 2004
oasis-open.orgoasis-open.org
Why Open Standards
Who is OASIS
The OASIS Conceptual Model
OASIS Standards & Open Source Implementations
Benefits from Participating
Agenda
© OASIS 2004
Why Open Standards
© OASIS 2004
oasis-open.orgoasis-open.orgWhat is an Open Standard?Just anything a single vendor declares is a
standard? Or anything on which two or more vendors agree? These may be “specifications” or “de facto
standards”, but not “open standards” from the OASIS point of view
Open Standards are specifications developed and/or approved under a Published, consistent process Fair environment Transparent, open operations Transparent output
© OASIS 2004
oasis-open.orgoasis-open.orgWhat is an Open Standard?
An open standard is:publicly available in stable, persistent versionsdeveloped and approved under a published
process open to public input: public comments, public
archives, no NDAssubject to explicit, disclosed IPR termsSee the US, EU, WTO governmental & treaty
definitions of “standards”
Anything else is proprietary:This is a policy distinction
© OASIS 2004
oasis-open.orgoasis-open.org
Coordination of standards at OASIS
OASIS recognizes the many dependencies across standards organizations Promote interoperability Reduce duplication
OASIS participates in and coordinates with many other standards and industry coordination efforts, e.g., W3C and OASIS management meetings ISO/IEC/ITU/ECE coordination MoU RosettaNet, OMA, AIAG, WS-I, GGF, etc. Cat A liaisons with TC154, various JTC1 SCs
© OASIS 2004
oasis-open.orgoasis-open.org
Formula for Sustainable StandardsM
arke
t Ado
ptio
n
Open Standardization
Traction
SanctionProprietary JCV Consortia SDO
SGMLISO
XMLW3C
SOAP v1.1 SOAP v1.2W3C
UDDI v2,3UDDI.org
WSDL v1.2W3C
ebMSG v2OASIS
WSDL v1.1
eb Reg v2OASISWS-S v1.0
BPEL4WS WS-BPELOASIS
WSSOASISWS--*
? UDDI v2,3OASIS
ebXMLISO
15000
© OASIS 2004
Who is OASIS?
© OASIS 2004
oasis-open.orgoasis-open.orgOverview
OASIS is an international consortium dedicated to developing and promoting the adoption of e-business specifications
Member-elected Board of Directors and Technical Advisory Board; member-driven standards process
Members of OASIS are providers, users and specialists of standards-based technologies and include organizations, individuals, industry groups, and government agencies.
International, not-for-profit, open, independent
Successful through industry-wide collaboration
© OASIS 2004
oasis-open.orgoasis-open.org
OASIS Members Represent the Marketplace
OASIS Member Organizations
Technology Providers
51%
Users & Influencers
34%
Government & University
15%
© OASIS 2004
oasis-open.orgoasis-open.org
International Representation
Total OASIS Members - 2000
4% 13%
83%
Asia-Pacific Europe North America
Total OASIS Members - 2003
70% 19%
11%
Asia-Pacific Europe North America
© OASIS 2004
oasis-open.orgoasis-open.orgOASIS technical work
The OASIS technical agenda is set by our members; bottom-up approach
Technical committees formed by the proposal of our members
Each Technical Committee sets its own scope, schedule, and deliverables
More than 60 Technical Committees in a variety of topic areas E-business Security Web services Public sector
© OASIS 2004
oasis-open.orgoasis-open.orgOASIS 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 Draft
OASIS members approve OASIS Standard
Resulting work is representative broad range of industry, not just any one vendor’s view
© OASIS 2004
The OASIS Conceptual Model
© OASIS 2004
oasis-open.orgoasis-open.org
A model to describe the technical activities of industry organizations Descriptive, not Prescriptive
Identify overlaps for the purpose of increasing collaboration
Identify gaps for the purpose of starting new work
Purpose of a Conceptual Model
© OASIS 2004
oasis-open.orgoasis-open.orgPrevious Work: BIC B2B Model
Source: Business Internet Consortium (BIC) Whitepaper, “High-Level Conceptual Model for B2B Integration ”, March 02, 2002
© OASIS 2004
oasis-open.orgoasis-open.org
OASIS Conceptual Model for eBusiness standards
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 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
© OASIS 2004
oasis-open.orgoasis-open.org
OASIS Conceptual Model: populated
Q u a l I t y o f S e r
v I c e s
M 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 Interoperability
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
3DSS, ebXML-RegRep, UDDI 3
ebXML-CPPA
1ebXML-MSG, WSRM
2
Conformance, ebXML-IIC, XSLT-Conformance 3
CIQ, UBL, Doc-Book, XLIFF, OpenOffice 5
© OASIS 2004
oasis-open.orgoasis-open.org
OASIS Conceptual Model: populated
Q u a l I t y o f S e r
v I c e s
M 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 Interoperability
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
3DSS, ebXML-RegRep, UDDI 3
ebXML-CPPA
1ebXML-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
© OASIS 2004
OASIS Work that has Produced Open Source Projects and Software
© OASIS 2004
oasis-open.orgoasis-open.org
Open Source Software built on Standards from OASIS TCs
Asynchronous Service Access Protocol (ASAP) Content Assembly Mechanism (CAM) Docbook ebXML Collaboration Protocol Profile & Agreement (CPPA) ebXML Messaging Services ebXML Registry/Repository eXtensible Access Control Markup Language (XACML) Open Office XML Format RelaxNG Schema UDDI Specification Web Services for Remote Portlets (WSRP) Web Services Security (WSS)
© OASIS 2004
oasis-open.orgoasis-open.org
Suggestions for Collaborative efforts
Government and research funding projects should coordinate open standards development with any OSS development
OASIS provides mechanisms to publicize OSS that implements OASIS Standards OASIS TC and Affiliate web pages
OASIS Registry of Implementations
XML.org Focus Areas & CoverPages
OASIS Sponsored Interoperability Tests & Demos
© OASIS 2004
Why Participate in OASIS
© OASIS 2004
oasis-open.orgoasis-open.org
Membership Benefits
Influence
Information
Participation
Education
Co-ordination
Creadibility
Visibility
Openess
© OASIS 2004
oasis-open.orgoasis-open.orgGovernment Benefits
Educate staff to learn about general e-Business frameworks Influence software vendors to develop solutions for your
government Increases number of competitive solutions Lowers cost of implementations for your agencies
Enable cross-government adoption Participate in inter-government standards activities Learn and adopt best practices Coordinate complimentary standards activities – minimise overlap Speed up development and adoption of new technologies and
emerging standards Minimize risk in evaluation of new technology directions Monitor open standards and marketplace up-take for
recommendation in government structure Monitor and evaluate best practises for recommendations to
industries and companies within your country or region
