difficult questions to the server Dataset 2 Dataset 1 Dataset 3 Dataset 4 Interoperability? Provenance? Data Quality? Trust? Has an Open World assumption
difficult questions to the server Harvested each X days «Client» Asks difficult questions to the server «Client» Asks difficult questions to the server «Client» Asks difficult questions to the server «Client» Asks difficult questions to the server «Client» Asks difficult questions to the server «Client» Asks difficult questions to the server «Client» Asks difficult questions to the server Linked Open Data High Availability problems Expensive to host Not “Web” querying Hard to cache
simple smart questions Queried on last data published The LDF enabled Web: datasets with triple pattern support & counts Low cost, highly available HTTP caching Paper: http://LinkedDataFragments.org Querying the Web CONSTRUCT { … } WHERE { ?s1 ?p1 ?o1 . ?o1 ?p2 ?o2 . } ?s1 ?p1 ?o1 <o1> ?p2 ?o2
problems be fixed querying the Web in reasonable time? Evaluate by listing common problems and compare availability and user response times with state of the art
al. "Intriguingly simple and fast transit routing." Experimental Algorithms. Springer Berlin Heidelberg, 2013. 43-54. Minimum Expected Arrival Time (MEAT)
set of simple smart questions The LDF enabled Web: datasets with triple pattern support, counts & ordering handles? Low cost, highly available HTTP caching CONSTRUCT { … } WHERE { ?station transit:departures ?departures . ?departures ?p2 ?o2 . } ORDER BY ?departures Extra handles for helping route planning algorithms Querying the Web