Presentation at European Commission workshop Open Source Beyond 2020 in Brussels, 14-15 Nov 2019.

1. © 2019 IBM Corporation
Standardisation
and
Open Source
#Disruptive
#Complementary
#Synergetic
European Commission Workshop
Brussels, 14 – 15 November 2019
Dr. Jochen Friedrich – Technical Relations Executive
jochen@de.ibm.com

2. © 2019 IBM Corporation2 Standardisation and Open Source | Dr. Jochen Friedrich | jochen@de.ibm.com
Standards versus Open Source
Open Innovation
Open Technologies
Standards
A building plan (methods,
processes, protocols, …)
Developed collaboratively in
standards developing organisations
in open and transparent processes
Not controlled by one single vendor
or group of vendors
Available for free, for small
administrative fee, or for sale
May include patented technologies
Open Source
Source code (Software)
Developed collaboratively in
open source projects /
communities / foundations
Open source governance for
decision making
Openly available
Licensed under open source
license (typically OSI approved
license)

3. © 2019 IBM Corporation3 Standardisation and Open Source | Dr. Jochen Friedrich | jochen@de.ibm.com
Standardisation and Openness
Open Standards ≠ Open Source!
Open, transparent development process, not
dominated by single vendor or group of vendors
Available for free, typically download from the
web
Available for implementation at Royalty-free (or
even Restriction-free) terms and conditions

4. © 2019 IBM Corporation4 Standardisation and Open Source | Dr. Jochen Friedrich | jochen@de.ibm.com
Challenging
Several things that used to be
done in standards bodies …
Open Source is highly disruptive to traditional standardisation
Open Source is running code – fast way from innovative
development to deployment
Standards bodies are looking for ways how to include Open
Source into their scope and work
… are now being done
in Open Source projects

5. © 2019 IBM Corporation5 Standardisation and Open Source | Dr. Jochen Friedrich | jochen@de.ibm.com
Aspects regarding the Relation of StandardisationAspects regarding the Relation of Standardisation
and Open Sourceand Open Source
Open Source implements
standards
Standards are developed
in open source
Standards are maintained
in open source
Reference implementations
Promulgation of standards
Standard needs to be implementable in
open source (IPRs / patents)
E.g. APIs, interfaces
Processes, release cycles
Dynamic improvements and feedback
cycles
Processes, release cycles

6. © 2019 IBM Corporation6 Standardisation and Open Source | Dr. Jochen Friedrich | jochen@de.ibm.com
Standards Bodies addressing Open Source
Standards Body cooperates
in some way with an open
source project
Some formal agreement
(MoU or similar) may be set
up (if possible)
Processes may have to be
adapted
Standards Body hosts open
source projects in-house
Processes may have to be
adapted or new processes
designed, including
processes for making
software available
Legal issues (liability) may
have to clarified
In-house Co-operation

7. © 2019 IBM Corporation7 Standardisation and Open Source | Dr. Jochen Friedrich | jochen@de.ibm.com
Challenges – Some Aspects
IPR Policy
versus Open
Source Licenses
Find ways how IPR policy and open source licenses
can work together – not everything may be possible
Balance between patent protection and open
technology development
Business Model Balance between selling standards and open
technology development
Static versus
dynamic
Differences in governance – more static membership
model of standardisation versus highly dynamic
community model of open source developments
Legal entity versus community

8. © 2019 IBM Corporation8 Standardisation and Open Source | Dr. Jochen Friedrich | jochen@de.ibm.com
Ongoing Work in ETSI on a Framework for Open SourceOngoing Work in ETSI on a Framework for Open Source
Open Source work has been done in
some ETSI committees already
ETSI Forge established as platform for
making collaborative software available
Open Source is
key strategic
objective in
ETSI’s Long Term
Strategy
Cooperation with external Open Source
projects
Processes for doing Open Source work
within ETSI groups without undermining
ETSI IPR policy
What are use cases? What can be
done? In which ways? What are risks?
Focus on processes, licenses, models.
Work in
progress

9. © 2019 IBM Corporation9 Standardisation and Open Source | Dr. Jochen Friedrich | jochen@de.ibm.com
Concluding Remarks
Open Source is a major driver of innovation in the market place.
Open Source challenges traditional standardisation.
Standards bodies need to find their own ways of how to best
integrate or interact with Open Source. There is no perfect
formula for that.
There are many ways of how standards bodies can approach
Open Source. Open Source may be the way of developing
standards; it may complement standardisation work; it may be
used to develop test environments; etc.
The discussion should not be reduced to an IPR policy
discussion. An IPR policy is no blocker for a standards body to
implement processes for Open Source work.

10. © 2019 IBM Corporation10 Standardisation and Open Source | Dr. Jochen Friedrich | jochen@de.ibm.com