3. “Data is new oil for a digital era”
Neelie Kroes
2
4. 3
Open Data definition
“A piece of data or content is open if anyone is free to use,
reuse, and redistribute it — subject only, at most, to the
requirement to attribute and/or share-alike.”
[http://opendefinition.org/#sthash.6ieidzit.dpuf]
5. Open Data definition
4
Accesibility to anyone
Re-usage possibilities
Updated
Quality
Linkable
Every public body, private Company or citizen
should have equal rights to get the data
[European directive on PSI, 2003]
6. Open Data definition
Open Data vs Public Sector Information
Levels of openness of data [TBL 2010]
• Online but not re-usable on open licenses
• Online and open-licensed but only human-readable
• Online, open-licensed and structured
• Online, open-licensed and structured (non-proprietary format)
• All of above and identifiable with URI
• All of above and linkable to get network-effect and added-value
5
Public data can be completely useful only if it
has an ability to be linked with other data sets
and create new social and economical value
[Sashinskaya, M. 2014]
8. Open Data for Smart Cities
Smart people are the most important component of a Smart city
• User-oriented participation
• Talent
• Entrepreneurship
City government may not need to produce the apps, but can provide the platform being a
facilitator
A modern city has many data generated and collected by citizens every day
• This data can create added value (social and economical) specially if is linkable and
combined with other public data
7
11. Different Sources of Context
Context information may come from many sources which may vary over time:
• Existing Systems dealing with management of municipal services
• Sensor networks (Internet of Things)
• Third-party smart city APPs
Source of information needs to be transparent to applications accessing context information
NGSI Standard API
Current traffic
in street “X”
A sensor in a
pedestrian street
Citizen’s car app or
smartphone
Notify traffic
in street “X”
Current traffic
in street “X”
Public Transport System
12. 11
Once context information is gathered, a lot of useful
complementary FIWARE enablers can be used
Open data publication
Advanced Web-based UI
(AR, 3D)
Data/Apps visualization
Big Data Analysis
Complex Event
Processing
Multimedia processing
IoT-enabled
Context Information
Management
14. 13
CKAN is a data management
platform that makes data
accessible by enabling the
publication, search, and usage
of the data
CKAN Open Data Platform
15. CKAN Open Data Platform
De facto standard platform for Open Data in Europe and beyond
Plenty of extensions: harvesting, geographical information, data visualization…
Search & Discover Data:
• Search by keywords
• Browse by facets
• Explore data with previews & visualization
• REST/JSON APIs to access data and metadata
Data Management for publishers
• Easy store & update of metadata
14
16. FIWARE Extended CKAN
Integrated with FIWARE Lab IdM (OAuth2)
• Users do not need to have different accounts
• Same user than in the rest of FIWARE Portals
• Users can access the portal without log in to read open data
Ability to create private datasets
• Accessible only by certain users
Ability to publish datasets in the Business API Ecosystem
• Manage the users that can access private datasets
• Charge users for accessing your data
• Ensure that users only access your data under some legal terms
• …
https://data.lab.fiware.org
15
19. 18
FIWARE Extended CKAN
NGSI Extension
• NGSI queries published as
datasets
• Support for secured
Context Brokers
• Support for tenants and
service paths
21. 20
FIWARE Extended CKAN
WireCloud view Extension
• Rich visualizations for
data
• Support for existing
dashboards
• Wizard for basic
visualizations
22. 21
FIWARE Extended CKAN
Data requests Extension
• Users can ask for data
• Support for creating,
closing, and resolving
data requests
23. 22
FIWARE NGSI components as live data sources
Integration with any NGSI-enabled component in FIWARE
Live-update of data (context information) for interactive applications
• IoT
Context Broker
Traditional (static) historical
data
CKAN
Context sources
24. 23
CKAN NGSI datasets access control
CKAN
IdM
PEP
PDP
Context
Broker
Authenticate user
Access token
Validate token
Check permissions
27. Business API ecosystem RI
Monetizing data
• Or only “Terms of use”
Not only data
• Visualization
• APIs
• Applications
Revenue sharing
Value-chain (future)
26
28. Business API ecosystem RI
27
Integration of standard
TMForum APIs with the
former FIWARE Business
Framework GEs for DS
Management
Key Features:
• Management of catalogs, products, and offerings
• Rich pricing models, including recurring payments,
pay-per-use, etc
• Accounting callbacks
• Billing and charging
• Revenue sharing, including models with multiple
stakeholders involved
29. 28
Aligned with TM Forum
TM Forum & FIWARE APIs are part of a Business
Framework that serves the emerging economy of data.
30. TM Forum Ecosystem APIs
REST based APIs that enable rapid, repeatable, and flexible integration among operations
and management systems.
Making it easier to create, build and operate complex innovative services.
31. 30
FIWARE/TMF Business API Ecosystem GE
Rating/
OM
RSS
Payment
Portal
TMF API
Catalog
API Orchestrator
(Authentication/Authorization)
Identity Manager
TMF API
Product
Inventory
TMF API
Product
ordering
TMF API
Billing
TMF API
Usage
TMF API
Party/Custome
r
Accounting
32. 31
CKAN NGSI datasets monetization
Business API
Ecosystem
CKAN
Dataset
Extension
CKAN
IdM
notif (type, user, dataset)
Product, offering
PEP
PDP
Context
Broker
grant (role, user)
revoke (role, user)
33. 32
Where to get more information?
CKAN Documentation
• https://ckan.org/
NGSI Documentation
• https://fiware-orion.readthedocs.io/en/master/
How to publish context information guide
• http://fiwaretourguide.readthedocs.io/en/latest/publishing-open-data-in-
fiware/introduction/
34. 33
Where to get more information?
BAE Technical documentation
• https://business-api-ecosystem.readthedocs.io/en/latest/
The fast way
• https://hub.docker.com/r/fiware/business-api-ecosystem/
Courses at
• https://edu.fiware.org/course/view.php?id=150
Interesting Economy of Data stuff during FIWARE Summit
• Tuesday 30th 15:00-15:45: “How to ”, Francisco de la Vega
Let’s start with a sentence by former Digital Agenda Commissioner, who puts the focus on data as the main driver for a digital era
Re-usage – non-propietary formats NGSI
Linkable – Data models Data can be linked and merged to generate added value data
Link the concept of NGSI with all the data requirements already presented
In a smart city, the applications build on top of the platform require to gather and manage context information, referring to any relevant data available in the city. In this way, context information may come from very different sources, such as real time data coming from an IoT layer, static datasets published in a data platform, information published by the city hall, dynamic data generated by third party applications, etc.
It can be seen, that dealing with all these heterogeneous data sources might be difficult,
slowing down the innovation in the city. To deal with this problem, FIWARE provides an
standard API for the management of context information, so it is exposed using a single
format, which makes transparent the source of the data.
Not only static resources are to be stored in CKAN, but also live-data, as any other data coming through starndard APIs of NGSI from other components/apps/services
In a smart city, the applications build on top of the platform require to gather and manage context information, referring to any relevant data available in the city. In this way, context information may come from very different sources, such as real time data coming from an IoT layer, static datasets published in a data platform, information published by the city hall, dynamic data generated by third party applications, etc.
It can be seen, that dealing with all these heterogeneous data sources might be difficult,
slowing down the innovation in the city. To deal with this problem, FIWARE provides an
standard API for the management of context information, so it is exposed using a single
format, which makes transparent the source of the data.
Towards a real ecosystem of apps and data
The situation presented untill now does foster innovation by offering the tools to create value with open data. The OD platform, the standards, the freedom to re-use the data are key factors that leverage the potential for a wide ecosystem of smart applications and services. Though there is a step forward in the path for smart cities, which means monetization. Monetization of the data, the apps, the services, so as to create a value-added chain that attracts even more attention to the development of those services.
For accomplishing that, it is neccessary
- The means for identity management and authentication
- Management of access rights for data, apps and services
- Having an inventory of existing data sources, and services (Activation and
configuration API)
- Bind a pricing model to data, apps and services
- make available data, apps, and services to potential customers
- Allow to acquire products (automatic permission management for service activation)
- Allow to manage acquired products (renew, suspend, terminate, show usage, etc)
- Data and service acquisition need pay-per-use
- Usage data management
- Accounting
- Management of charges and payments (Charges and settlement notes)
- Management of revenue sharing
- Management of agreements and engaged parties
Business API standardization is a key factor for the creation of a real ecosystem of apps and data. Without strong standardization efforts, full maturity level of smart cities (third parties enriching city-supplied data and enabling monetization) is complicated.
Without standardization, a real apps and data ecosystem would be severely limited.
In this sense, TM Forum has standardized a set of Business Ecosystem APIs that enables repeatable and flexible integration among operations and management systems, making it easier to create, build and operate complex innovative services. FIWARE, and specifically the Business API Ecosystem GE, has become the first integrated implementation of first set of available APIs, and is evolving to put the newly released ones in place.
Therefore, besides being a marketplace with the obvious benefits from the monetization of apps and data, it takes advantage of the benefits on operation and management offered by such standards.
Since all of the interactions with the enabler are standard, companies that plan to offer data and apps in such ecosystem do not need to ad-hoc adapt their systems.
In the age of the digital economy, services are typically delivered through a sophisticated partnering of multiple providers who are all using different systems and interfaces. TM Forum REST based APIs are designed for use on anything from IoT device management to complex B2B value fabrics and they apply to all the topics our members are focused on: IoT, Digital Health, Smart Grid, Big Data, NFV, Next Generation OSS/BSS and more.
TM Forum’s Ecosystem APIs provide end-to-end management capabilities to improve the consistency and effectiveness of communications across boundaries.
One of the most important parts of the TM Forum API program is a set of standard REST based APIs that enable rapid, repeatable, and flexible integration among operations and management systems.
Multi-partner environments
Covering: IoT Digital Health Smart Grid Big Data NFV Next gen OSS/BSS * ...