Presentation given at the face to face meeting of the Web of Things Interest Group of W3C. Munich April 2015.

1. Text
Web of Things — Semantics & Interoperability
Dr. Carlos Pedrinaci - The Open University

3. Verticals
Full integrated solution
Direct commercial value to
customers
Leads to solution silos
No domain-wide cross-
aggregation
Web API for cross-domain reuse

4. Horizontals
General purpose
Powerful
Requires ad-hoc
application development
Intra-platform cross-
aggregation
Exposed via Web API

5. The value and power of the Web of Things will lie
on its ability to help us combine and repurpose
highly heterogeneous and distributed Things to
develop advanced solutions

6. Achieving this requires having the ability to
• Find existing Things
• Understand what they do
• Interact with them
• Combine them easily at scale to achieve
possibly unanticipated new goals
… and this needs to happen despite vendor-specific silos

7. On the Web working with Things will be
indistinguishable from working with Web APIs
We should be able to interleave Things and Web
APIs as needed

12. Looking back at Web APIs
Very popular & Very heterogeneous
REST vs RPC
No standard yet — RAML vs Swagger vs … vs HTML!
REST is seldom implemented entirely properly
Semantics are essential
SAWSDL is the only standard for the semantics of services
Very basic. Mainly pointers. Complex enough!

14. Description
Provide a rich
description of the Things
Services, APIs, Things
treated homogeneously
Better support their
integration and
interleaving within apps

16. Text
Description
Data Mining and Enrichment
Exposed as Linked Open Data

17. Text
Describing Things
Support Discovery and Use

18. Text
Things Functionality
High-level description of what the Thing does

19. Text
Things Interfaces
What to Expect from Things

20. Text
Describing Sensors
Using Wikidata as a reference ontology
500 sensor types — 700 units of measurement

21. Discover
What things are there?
What do they provide/do?
Heterogeneity
Large-scale
Dynamicity
Repurposing
Reliability

23. Interact
How to invoke services?
What is their interface?
What data do they need
and provide?
All over the Web

25. Combine
Large-scale
Heterogeneity
Tightly integrated with
discovery
Demanding performance
requirements

26. Text
Composition
High Performance Data Driven Composition
Support for Distributed Registries
Graph-Based
Optimizations
Comp.
Request
Optimal
Composition
Search
Search
Optimizations
Input/Output
service composition
description
Service Registries
Concept
Matchmaking
Composition
Graph
Generation
Service
Discovery
Optimal
Composition
Workflow
Optimized composition
graph
Semantic
Reasoner MATCHMAKING / DISCOVERY
Composition Graph
GRAPH-BASED COMPOSITION

27. Thanks for your attention
Contact: carlos.pedrinaci@open.ac.uk
More Information
iServe: http://iserve.kmi.open.ac.uk
ComposIT: https://github.com/citiususc/composit
SAWSDL: http://www.w3.org/2002/ws/sawsdl/
Schema.org: http://schema.org
Wikidata: http://www.wikidata.org
COMPOSE: http://www.compose-project.eu