Web of data to power a Web of services

Slides of the discussion during the Semantic Web Developer's workshop during ESWC 2015 and the conclusion

Transcript

1. a Web of data to power a Web of services SemDev workshop at ESWC 2015 @PieterColpaert
2. We want access to raw open data, not open services
3. A web-service for route planning http://api.{myapp}/?from={A}&to={B} @PieterColpaert
4. Server chooses the functionalities http://api.{myapp}/?from={A}&to={B} &departuretime=2015-04-25T10:45Z &wheelchairaccessible=true &modes=plane,railway,bus,car ... @PieterColpaert
5. What does transit data look like? a vehicle follows this connection departureTime + departureStop arrivalTime + arrivalStop isochrone map by @openov and another connection departureTime + departureStop arrivalTime + arrivalStop
6. time → The Connection Scan Algorithm (CSA) Route planning with a sorted list of connections
7. Resource ... Resource 3 Resource 2 Resource 1 time nextPage nextPage @PieterColpaert Publishing raw data in fragments, enables clients to perform the algorithm
8. Resource ... Resource 3 Resource 2 Resource 1 time nextPage nextPage Route planning algorithm now needs X requests. The fragments are cacheable (serverload/extra user ↓) Clients perform the algorithm on their own @PieterColpaert
9. Discussion Can we apply this reasoning to other problems? Data dumps Web documents query language services Algorithms as a service Data publishing Data services http://linkeddatafragments.org
10. Discussion report Do we need open data instead of open services? → service/api is parameter-driven while websites are self-descriptive ◦ Actually, there is no difference, websites are apis too ◦ And, through hypermedia we can inform clients to more actions ⇒ There’s a thin line between data publishing and data services → Open Data is great, but some companies want to keep underlying things hidden, but do want to answer questions on the web. How? ◦ They don’t need to publish everything? Documents for public and API for others ◦ This is an access control problem: there is a spec for Access Control and the problem can be tackled in very flexible ways: class level, This is about data that is already public through e.g., a HTML or PDF: make it more useful by adding an open license, and by making it Web-queryable through wisely chosen fragments
11. Conclusion Where the data is open, ask for the dataset, not the API Show the merits of web querying to persuade data owners