The COVID-19 global pandemic has raised the already bright visibility of technology to an even higher level. Join Guy Martin, Executive Director at OASIS Open, as he presents this webinar that will discuss how we can make open source and open standards even more effective by helping them recapture their strong partnership.

5. About OASIS
Open
Standards Developing
Organization &
Open Source Host
● Non-profit 501(c)6 founded in 1993
● Member of European MSP on ICT
Standardization
● Liaison relationships with ISO, IEC, ITU
● Broad technical agenda, deep technical
adoption
6 70+ 150+
2000
+
COMMUNITI
ES
STANDARD
S
CONTINEN
TS
PARTICIPAN
TS

6. Why Open Source AND Open
Standards?

7. 8,493 wildland fires • > 5 million acres burned
> 9500 homes lost • 41 lives lost

8. APCO P25 digital radio standard
ensured efficient, safety-critical
communications, but …

9. Definitions
https://opensource.org/osr

10. Back…To The Future!

11. Our window on today’s world

12. Emergency Response

13. Security

14. How Do We Find Common Ground?

15. Coming Together
Interoperability
• Strong IP governance
• Use case definition a priori
• Strong Consensus
• Permissive IP governance
• Iterative development
• Meritocracy/rough
consensus
Choice Innovation
Desired Outcomes

16. Open Development Ecosystem
Interdependency Bridging the IP Gap
APIs Guidance

17. Hidden Gems

18. Balanc
e

19. Culture & Pace

20. The Role of
Foundations/Consortiums

21. Neutrality

22. Fairness

23. Community
Shepherdin
g

24. OASIS Open Projects support shared
community development of code, APIs,
standards, reference implementations,
etc. in one place, under open source
licenses with a path to recognition in
international policy and procurement.

26. Our Approach: Make OSS & Standardization Better Together
● We allow & encourage multiple independent implementations of specs.
○ Promotes user agency & freedom of choice
○ Validates & encourages adoption
● We foster cooperation of OSS & open standards to bring value-add to both.
○ Avoiding vendor-lock & creating “insurance policies”
○ Informing technical designs & creating positive feedback loops
● We use modern tooling with our peer-reviewed standardization processes.
○ Assuring openness, transparency & vendor-neutrality of our open source projects
○ Bringing OSS developer ergonomics to increase efficiency of our standardization activities

27. Our Practice: Working with Open Projects
On Governance:
- All OPs conform to the same simple,
extensible governance model
- Clear requirements for record-keeping,
participation, disclosure bring structure &
rigor to OSS
- Clearly defined roles for approving
outputs, licensing obligations, project
management that correspond with
understood roles in OSS software
development
On Process Flow:
- Agnostic as to whether project begins with
a spec or with code
- Encourage a parallel approach (spec with
implementation) where possible
- Work lives together, so they are
discovered together
On IPR:
- OPs can choose from 7 OSI-sanctioned
and Creative Commons licenses
- License couples with our non-assert
covenant
- CLAs collected on individuals and entities

28. Thank you.
oasis-open.org | info@oasis-open.org