FI-WARE and Open Data Juanjo Hierro – Chief Architect FI-WARE

Open Data (1/2)  Open data is the idea that certain data should be freely available to everyone to use and republish as they wish, without restrictions from copyright, patents or other mechanisms of control.  More formally: “A piece of data 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.”  Several local, regional or national governments have created web sites to distribute a portion of the data they collect. The whole idea is put this data “at the service” of citizens and application providers who can create innovative applications based on that data. A list of 250+ local, regional and national open data catalogues is available on the open source datacatalogs.org projectdatacatalogs.org The US government has strongly embraced this movement (  The Open Data approach may apply also to businesses

Open Data (2/2)  Open Data is a concept, therefore, technology-agnostic  Therefore, Open Data =/= Linked Open Data !!  Linked Data is a technology some people is pushing to be adopted in order to implement the Open Data concept Heavily based on Semantic Web technologies (RDF, SPARQL, …)  Many organizations wish to open their data but their data sources are available on more “traditional” technologies (RDBMS, files, …)

FI-WARE Context/Data Management Platform 3 Context/Data Management Platform Applications FI-WARE NGSI-9/10 Processing/Analysis Algorithms Gathered data is injected for processing/ana lysis Distributed Context Sources Complex Event Processing - CEP (IBM’s PROTON) BigData Analysis/Processing (COSMOS = SAMSON + Hadoop) Pub/Sub Context Broker (Gathering / Publication) Processed data is injected for processing/ana lysis Data generated either by CEP or BigData is published Gathered data injected for CEP-like processing

FI-WARE and Open Data  FI-WARE NGSI APIs enable management of Context Information relevant to “entities”, although entities can be anything (applications, users, things, …)  Open Data can always be defined as associated to entities (real or virtual) so that FI-WARE NGSI APIs can be used to publish and consumer open data 4 Context/Data Management Platform Applications Open Data sourcesApplication-owned dataFI-WARE Instance Data FI-WARE NGSI- 9/10

Context Elements  Context Information in FI-WARE NGSI is communicated using data structures called context elements which have associated: An EntityId and EntityType, uniquely identifying the entity to which the context information refers. A sequence of one or more data element attributes ( triplets) Optional meta-data linked to attributes (also triplets)  As an example, we may consider the context element linked to updates on: attributes “speed”, “geolocation”, “current established route” of a given car attributes “message geolocation”, “message contents” of a given user  The EntityId is a string, and can be used to designate “anything”, not necessarely “things” in the “real world” but also application entities  Bottom line, Context Elements can be used to propagate open data 5 Meta-data Name Type Value Context Element attributes Name Type Value Context Element EntityId EntityType 1n1n “has”

Consuming Open Data (pull mode)  Context Consumers can retrieve data/context elements by invoking the queryContext operation on a Context Broker  Context information is kept persistent by Context Brokers and available to applications while not exceeding a given expiration time. This is a distinguishing feature of the OMA Context Management model as compared to some Event Brokering standards.  Complex queries supported but also convenience RESTful operations: WARE_NGSI_Open_RESTful_API_Specification_(PRELIMINARY) WARE_NGSI_Open_RESTful_API_Specification_(PRELIMINARY 6 Context Consumer queryContext Context (Publish/Subscribe) Broker

Consuming open data (push mode)  Some Context Consumers can be subscribed to reception of data/context elements which comply with certain conditions, using the subscribeContext operation a ContextBroker exports. Such subscriptions may have a duration.  Subscribed consumers spontaneously receive data/context elements compliant with that subscription through the notifyContext operation they export  Note that the Application which subscribes a particular Context Consumer may or may not be the/a Context Consumer itself 7 Application subscription_id = subscribeContext (consumer, expr, duration) Context ConsumerContext (Publish/Subscribe) Broker notifyContext (subscription_id, data/context)

Publishing Open Data (push & pull mode)  Context Producers may publish data/context elements by invoking the updateContext operation on a Context (Publish/Subscribe) Broker.  Context Producers may export a queryContext operation instead of pushing open data. They are registered by invoking a registerContext operation that the Contex Broker exports  Note that the Application which subscribes a particular Context Producer may or may not be the/a Context Producer itself 8 Application registerContext (producer-1 URI, registration data, duration, registration_id) Context Producer-1 Context (Publish/Subscribe) Broker queryContext Context Producer-2 updateContext

FI-WARE IoT-M2M & Context/Management altogether NGSI IoT Adapter Backend Device Management GE Backend Applications FI-WARE NGSI-9/10 (entities: things) (entities: things, other) FI-WARE NGSI- 9/10 Things Management GE Device-level Management API Pub/Sub Context Broker GE IoT-enabled Context Management Backend BigData GECEP Other source s FI-WARE NGSI- 9/10 Gateway/Device Platform GEs

Combining data from different sources  FI-WARE NGSI APIs enable management of Context Information relevant to “entities”, although entities can be anything (applications, users, things, …)  Open Data can always be defined as associated to entities (real or virtual) so that FI-WARE NGSI APIs can be used to publish and consumer open data 10 Context/Data Management Platform Applications Open Data sourcesApplication-owned dataFI-WARE Instance Data FI-WARE NGSI- 9/10

Composing data services  Open data can be made available through services that can orchestrated Composition Editor Application provider FI-WARE Instance End user Context/Data Management Platform App 1 App 2 frontend services (UI, REST) Application backend components

frontend services (UI, REST) Application backend components Mashing up data services  Open data can be made available through gadgets that can be mashed up Composition Editor Application provider End user Context/Data Management Platform App 1 App 2 FI-WARE Instance

Monetizing Open Data  Open Data services can be monetized using marketplace functionality Application provider Market- place Revenue Share System 3 rd party stores End user Services repository RESTUIs Store FI-WARE Instance / Testbed App 1 App n Context/Data Management Platform FI-WARE Instance 3 rd party application

FI-WARE Open Innovation Lab  FI-WARE will work towards building an Open Innovation Lab which combines: The FI-WARE Testbed The FI-WARE Development Support Infrastructure (forge + additional community tools)  It is intended that this Open Innovation Lab be available to third parties (specially SMEs) after the second year 14

Connection to FI-WARE Open Innovation Lab FI-WARE Open Innovation Lab Trial (Production) environment Context Management Platform FI-WARE Testbed FI-WARE Instance (Trial) Infrastructure of sensors Published Open Data IoT Services Enablement Platform

Linked Open Data  Linked Open Data have to do with implementing the Open Data concept using Linked Data principles and technologies: Use URIs as names for entities (things, people, apps, …) Use HTTP URIs, so that people can look up those names When someone looks up a URI, provide useful information, using some of the semantic web standards (RDF, SPARQL) Include links to other URIs, so that they can discover more things  With RDFs linked to URIs, you can represent: Values assigned to attributes describing an entity (Literal triples) Relationships between entities (RDF Links) Attribute names and Relationship names are also represented by URIs Subject / EntityPredicate / AttributeValue

Can we support Linked Open Data in FI-WARE ?  The good news: The NGSI model is fundamentally equivalent to the RFD Model: › =  Points to be investigated for the second release: Can we extend the FI-WARE NGSI API so that operations can return RDFs linked to Context Elements ? (sounds like feasible) Can we connect a SPARQL engine to the Pub/Sub Context Broker ? How as to not sacrifice performance/scalability ?

Thanks !! 18