The path to an [Hybrid] Open Source Paradigm
Prepared and presented by Jonathan Challener, OECD
International Marketing And Outputs DataBase Conference
Gozd Martuljek, Slovenia
18-22 September 2016

Closed Source Open Source
V

Closed Source (or proprietary software)
means computer programs whose source code
is not published. The source code is not shared
with the public for anyone to look at or change.
Closed source is the opposite of open source.
Most companies who sell their software for
money make it closed source so people cannot
easily change it or copy it for free. [reference: Wikipedia]

Closed Source Software Projects

Open-source software (OSS)
Computer software with its source code made
available with a license in which the copyright
holder provides the rights to study, change, and
distribute the software to anyone and for any
purpose. Open-source software may be
developed in a collaborative public manner and
is the most prominent example of open-source
development. [reference: Wikipedia]

Open Source Software Projects

Closed Source Open Source
V

‘Closed Open Source’
Source Open
V

The SIS-CC is a group of organisations co-developing
software under an agreed framework and governance
model, and leveraging their collective capacity to
enable innovation.

Current SIS-CC model is one where software code is
open for community members with no licensing fee,
but is not accessible to non-members (who are not
contributing to the community activities - support,
coordination, promotion and product development).

‘Closed Open Source’

Closed Source Open Source
V

Closed Source Open Source
V

Open
Standards &
SpecificationsCommunity
Source
Open
Source
Paving the way for a [Hybrid] open source model

Open
Standards &
Specifications
Why?

Open
Standards &
SpecificationsCSPA

Common Statistical Production Architecture “CSPA”
+
{“SDMX”:“JSON”}

Common Statistical Production Architecture “CSPA”
+
{“SDMX”:“JSON”}

Joint project: Framework for Reusable Components for the Web

Many web based applications

Doing the same thing but different application!

Lacking reusability!

Reusable
Components for the
Web

Reusability
Components for the
Web

Enhanceability

Higher Agility

Eased distributed contributions

Eased creation of new products
and user interfaces

Where are we?

What are Reusable Components for the Web?
Reusability: each (type of) piece can be reused
Encapsulation: no piece can modify another piece
Interoperability: each piece has a standard interface
Composition (static): with simple pieces, more complex pieces can be done
Chaining (dynamic): with simple pieces, complex workflow can be done

Tools of choice
React is an open-source JavaScript library providing a
view for data rendered as HTML.
React views are rendered using components that
contain additional components specified as custom
HTML tags.
React gives programmers a model in which
subcomponents cannot directly affect enclosing
components ("data flows down"); efficient updating of
the HTML document when data changes; and a clean
separation between components on a modern single-
page application.
Redux is a predictable state container for
JavaScript apps.
It helps to write applications that behave
consistently, run in different environments
(client, server, and native), and are easy to
test.
It can easily be used together with React, or
with any other view library.

Life-cycle management tools

How to make components for the web reusable?

Getting started

Getting started

Getting started
I plan to build a web application using reusable components
First check the catalogue to see if the components you need exist.
If not, then you can contribute by either building them yourself, or extending
existing components.

Catalogue
 Catalogue of packaged components
 npm like (npmjs.com)
 Features:
 Search + results
 Content:
 Readme (automatic display by npm)
 Version/last changes (Automatic from package)
 Link to Repro
 Licence (Contained in package)
 Collaborators (Automatic linked to Git)
 Statistics (Automatic)
 Demo
 Keywords/tags
 Dependencies (Automatic)

Read more…
Project space
• Introduction to RCW project (short visual presentation)
• Use case descriptions
• Tracking ongoing build
• Issue tracking
• Wiki (background and manifest)

Sharing source code

Licensing?

Open
Standards &
Specifications
Community
Source
Open
Source
Paving the way for a [Hybrid] open source model

What is open?

Closed Source Open Source
V

Closed Source Open Source

Closed Source Open Source
Leverages the progressive full alignment of .Stat with the
webservice-centric (SDMX) and componentised (CSPA)
architecture principles.

Closed Source Open Source
The .Stat Core: consists of the data
warehouse and the internal logic to
support the management, extraction
and importation of data and
metadata, plus the services providing
the connections to common SDMX
services and/or tools, for example
SDMX-RI.
.Stat Core is not seen as an obvious
candidate for going full open source
now.

Closed Source Open Source
The .Stat Components Suite: A suite
of software components on the
output (dissemination) or input (data
lifecycle management) sides, that are
fully compliant with the CSPA
principles and can be reused in
contexts which are CSPA/SDMX
compliant and where .Stat Core is
not being used.
.Stat Components are seen as
obvious candidates for going full
open source.

Motivation

The international agenda
Strong contribution by SIS-CC
to the HLG agenda
CSPA
Increase the adoption of
international standards

Beneficiaries

ILO project to develop Labour Statistics
portal for CARICOM countries.
MENA Fund (Deauville partnership) to
overhaul Tunisia’s INS based on .Stat
and SIS-CC support.

Support model 1: No support
provided (components are made
available, with documentation, and it
is up to the ecosystem to seize them
and factor them into solutions) – and
support is provided only to regular
SIS-CC members.
Support model 2: One or several of
the partner organisations or a market
partner takes on the fixed cost for
providing a minimum level of support,
with a premium services support
model for advanced support services.
Targeted support model?

Tentative progressive SIS-CC journey towards open source
Step 1: Baseline scenario for end 2016 and
2017 (Hybrid Open Source), to be developed
in details:
A. Licencing model to be adopted
B. Branding and communication strategy to be
developed
C. Initial support and partnership model to be
decided
D. Initial model to manage contributions by non-SIS-
CC members
Step 2: More radical evolution on the longer
term, to be analysed at a future date.

Credits
Images
• GitHub Octocats: https://octodex.github.com/images/repo.png
• Come in we’re open source: https://c1.staticflickr.com/7/6029/6000224458_6baf0fc3a3_z.jpg
• Jack stands: http://www.gregsmithequipment.com/images/carJackStands.jpg
• SDMX logo: http://sdmx.org
• CSPA logo:
http://www1.unece.org/stat/platform/plugins/servlet/pptslide?attachment=CSPA.pptx&attachmentId=112394379&attachmentVer=1&pageId=112132835&slide=0
• Open Source tree:
https://media.licdn.com/mpr/mpr/shrinknp_800_800/AAEAAQAAAAAAAAYJAAAAJDhlYzAxYTE4LTE3MzUtNDFkZC1hMTA2LWE1MmI3NmRmNTZhMg.png
• Car components: http://www.autocarpro.in/IMG/137/6137/car-parts5000-699x380.jpg?1405682720
• Redux logo: https://raw.githubusercontent.com/reactjs/redux/master/logo/logo-title-dark.png
• React logo: http://mateoclarke.github.io/atxhackforchange-workshop/img/react.jpg
• Google Map pin: http://images.clipartbro.com/117/google-pin-117326.png
• Lego builders: http://assets.inhabitat.com/wp-content/blogs.dir/1/files/2015/06/LEGO-sustainable-building-brick.jpg
• Skydivers: http://s.hswstatic.com/gif/skydiving-picture-7.jpg
• Hares: http://www.moorhen.me.uk/imgofday/2012/20120603_df1_20120506_1810_231-
234%20hare%20running%20out%20of%20crop%20over%20hedge%20to%20south%20over%20track%20onto%20bare%20ground%20to%20se%2018-
21%20of%2037%20(accurate%20montage)(r+mb%20id@1024).jpg
• Blurred/enhanced city view: http://mikewires.com/wp-content/uploads/2014/06/640px-Refraction_through_glasses_090306.jpg
• Boy looking out of window: http://i.huffpost.com/gen/1703217/thumbs/o-BOYS-LOOKING-OUT-WINDOW-facebook.jpg
• Rocket: http://www.manufacturing.net/sites/manufacturing.net/files/spacex%20rockets_0.jpg
• Announcer: http://meetcontent.com/wp-content/images/announcer-250x250.png
• I want you poster: http://4.bp.blogspot.com/_Qvo9maGtaUY/TDDLs-9ma3I/AAAAAAAABOQ/GNupiSHFr-4/w1200-h630-p-nu/uncle-sam-open-source-311x400.png
• Animated plug: https://s-media-cache-ak0.pinimg.com/originals/59/df/95/59df95ecfb490ed3bab39a283ae7d8fa.gif
• Twinings tea: http://www.englishteastore.com/media/catalog/product/cache/6/thumbnail/9df78eab33525d08d6e5fb8d27136e95/t/t/ttwnlt3_enb_-01_twinings-
english-breakfast-3_1.jpg
• Used tea bags: http://www.healthyfoodelements.com/wp-content/uploads/2016/01/used-tea-bags.jpg

Jonathan Challener
Product Manager, and External Community Engagement
Organisation for Economic Co-operation and Development (OECD)
Email: jonathan.challener@oecd.org
LinkedIn: fr.linkedin.com/in/jonathanchallener
Twitter: @Challener
Web: siscc.oecd.org
Stats: stats.oecd.org
International Marketing And Outputs DataBase Conference
Gozd Martuljek, Slovenia
18-22 September 2016
The path to an
[Hybrid] Open
Source Paradigm