E&L-presentatie - Linked Data Benchmark Council
Upcoming SlideShare
Loading in...5
×
 

E&L-presentatie - Linked Data Benchmark Council

on

  • 133 views

 

Statistics

Views

Total Views
133
Views on SlideShare
133
Embed Views
0

Actions

Likes
0
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

E&L-presentatie - Linked Data Benchmark Council E&L-presentatie - Linked Data Benchmark Council Presentation Transcript

  • Heritage & Location Time, space & semantics LDBC Amsterdam, April 3rd 2014
  • Heritage & Location • Project by Digital Heritage Netherlands & many (heritage) institutions: RCE, SBNL, Waag, etc. • Semantics • Spatial • Temporal • Thematic • Tools for visualization, crowdsourcing • Open source, open data (where possible) • Sustainable business model
  • Spatial Spatial triple stores under investigation • uSeekM http://erfgeo.nl/geosparql/geosparql-demo.html • Strabon http://erfgeo.nl/geosparql/strabon-demo.html • Virtuoso http://erfgeo.nl/geosparql/vos-demo.html • Dataset: • 13,014 Dutch archaeological monuments (polygon) • 121,805 archaeological ‘observations’ (point) • Operations: • simple spatial filter • spatial join observation points on monuments polygons
  • Why is this important to us? • Simple spatial filter Municipality:Amsterdam OWL:sameAs http://sws.geonames.org/2759793/: 1 current place • Spatial join http://www.gemeentegeschiedenis.nl/gemeentenaam/Amsterdam or use translated version: 8 contours (multipolygon) Heritage & Location must be able to include (join) results from all previous ‘versions’ of a place
  • Limited results Store H&L uSeekM PiLOD Virtuoso Test repo Strabon Implementation Not optimised Not optimised Optimised? Simple spatial filter Good Reasonable Not so good ‘Point in Polygon’ spatial join Not so good Work in progress Good (how is this possible???) Disclaimer: there is no general validity for these results whatsoever! Consult a proper spatial benchmark for reliable results.
  • Time Consider dates before Christ (BC/ Before Common Era - BCE) ● W3 Time Ontology: “temporal content of Web pages and the temporal properties of Web services” ● CIDOC-CRM ontology: E50_Date datatype XSD:string "1900"; "4-4-1959"; "19-MAR-1922"; "19640604" is hard to implement ● Timeline ontology: atDate^^XSD:date → “Turns out almost no C library handles ISO 8601 dates before 1900.” ● Is Strabon or any other LD store able to handle: “Time:A Time:within Time:B” - a temporal join? Erm, help?