Your SlideShare is downloading. ×
0
Geospatial Linked Open Services
Geospatial Linked Open Services
Geospatial Linked Open Services
Geospatial Linked Open Services
Geospatial Linked Open Services
Geospatial Linked Open Services
Geospatial Linked Open Services
Geospatial Linked Open Services
Geospatial Linked Open Services
Geospatial Linked Open Services
Geospatial Linked Open Services
Geospatial Linked Open Services
Geospatial Linked Open Services
Geospatial Linked Open Services
Geospatial Linked Open Services
Geospatial Linked Open Services
Geospatial Linked Open Services
Geospatial Linked Open Services
Geospatial Linked Open Services
Geospatial Linked Open Services
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Geospatial Linked Open Services

1,545

Published on

Published in: Education
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,545
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
30
Comments
0
Likes
2
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • The upper right is standard application of Linked Data principles – if you request (state, in the request header, that you accept) HTML, you are redirected to a ‚page‘ URI; if you request RDF, you are redirected to a ‚data‘ URI (i.e. page/data is, in our implementation, appended to the end of the resource‘s URI). This is because the original URI actually identifies the airport but, since the airport is a real thing, not an information resource, you can‘t actually retrieve it in itself, only a related information resource.

    The bottom right is how we extend in LOS – under the same URI scheme you can ask for a computation relative to the resource by POSTing to a URI representing the weather under it (the airport).
  • Implicit knowledge – if you call a service with input ‚Vienna‘ and get output ‚20C‘, the implicit knowledge is that 20C is the temperature at the last report in Vienna (+ provenenance = ‚according to...‘)
  • Transcript

    • 1. KIT – University of the State of Baden-Württemberg and National Laboratory of the Helmholtz Association KARLSRUHE SERVICE RESEARCH INSTITUTE (KSRI) INSTITUTE OF APPLIED INFORMATICS AND FORMAL DESCRIPTION METHODS (AIFB) www.ksri.kit.edu SEMANTIC TECHNOLOGIES INSTITUTE (STI) Leopold-Franzens-Universität Innsbruck Geospatial Linked Open Services Barry Norton, Reto Krummenacher Towards Digital Earth @ FIS2010, September 20, 2010
    • 2. Karlsruhe Service Research Institute www.ksri.kit.edu Semantic Technologies Institute www.sti2.at Geospatial Linked Open Services Barry Norton and Reto Krummenacher 20.09.2010 Linked Open Data Cloud 2007
    • 3. Karlsruhe Service Research Institute www.ksri.kit.edu Semantic Technologies Institute www.sti2.at Linked Open Data Cloud 2008 Geospatial Linked Open Services Barry Norton and Reto Krummenacher 20.09.2010
    • 4. Karlsruhe Service Research Institute www.ksri.kit.edu Semantic Technologies Institute www.sti2.at Linked Open Data Cloud 2009 Geospatial Linked Open Services Barry Norton and Reto Krummenacher 20.09.2010
    • 5. Karlsruhe Service Research Institute www.ksri.kit.edu Semantic Technologies Institute www.sti2.at State of the Art – GeoNames.org Geospatial Linked Open Services Barry Norton and Reto Krummenacher 20.09.2010
    • 6. Karlsruhe Service Research Institute www.ksri.kit.edu Semantic Technologies Institute www.sti2.at State of the Art – GeoNames.org Services Geospatial Linked Open Services Barry Norton and Reto Krummenacher 20.09.2010
    • 7. Karlsruhe Service Research Institute www.ksri.kit.edu Semantic Technologies Institute www.sti2.at State of the Art – GeoNames.org Services Geospatial Linked Open Services Barry Norton and Reto Krummenacher 20.09.2010
    • 8. Karlsruhe Service Research Institute www.ksri.kit.edu Semantic Technologies Institute www.sti2.at State of the Art – GeoNames.org Weather Service Geospatial Linked Open Services Barry Norton and Reto Krummenacher 20.09.2010
    • 9. Karlsruhe Service Research Institute www.ksri.kit.edu Semantic Technologies Institute www.sti2.at State of the Art – GeoNames.org Weather Service {"weatherObservation": {"clouds":"broken clouds", "weatherCondition":"drizzle", "observation":"LESO 251300Z 03007KT 340V040 CAVOK 23/15 Q1010", "windDirection":30, Geospatial Linked Open Services Barry Norton and Reto Krummenacher 20.09.2010
    • 10. Karlsruhe Service Research Institute www.ksri.kit.edu Semantic Technologies Institute www.sti2.at State of the Art – GeoNames.org Weather Service {"weatherObservation": {"clouds":"broken clouds", "weatherCondition":"drizzle", "observation":"LESO 251300Z 03007KT 340V040 CAVOK 23/15 Q1010", "windDirection":30, "ICAO":"LESO", ... Geospatial Linked Open Services Barry Norton and Reto Krummenacher 20.09.2010
    • 11. Karlsruhe Service Research Institute www.ksri.kit.edu Semantic Technologies Institute www.sti2.at METAR Ontology Geospatial Linked Open Services Barry Norton and Reto Krummenacher 20.09.2010  Existing METAR Ontology (somewhat outdated)
    • 12. Karlsruhe Service Research Institute www.ksri.kit.edu Semantic Technologies Institute www.sti2.at METAR Ontology Geospatial Linked Open Services Barry Norton and Reto Krummenacher 20.09.2010  Existing METAR Ontology (somewhat outdated)
    • 13. Karlsruhe Service Research Institute www.ksri.kit.edu Semantic Technologies Institute www.sti2.at Geonames Airports Geospatial Linked Open Services Barry Norton and Reto Krummenacher 20.09.2010 ‘alternateName’ for both labels and identification schemes (ICAO, IATA) Only ~100 resources WGS84 geospatial, but only lat/long (not alt)
    • 14. Karlsruhe Service Research Institute www.ksri.kit.edu Semantic Technologies Institute www.sti2.at DBPedia Airports Geospatial Linked Open Services Barry Norton and Reto Krummenacher 20.09.2010 Some ICAO, IATA (with specific properties) but noisy Some WGS84, but not consistently ~3500 verifiable airports (see next)
    • 15. Karlsruhe Service Research Institute www.ksri.kit.edu Semantic Technologies Institute www.sti2.at NCAR METAR Station List Geospatial Linked Open Services Barry Norton and Reto Krummenacher 20.09.2010 ~8500 airports and other METAR reporting stations
    • 16. Karlsruhe Service Research Institute www.ksri.kit.edu Semantic Technologies Institute www.sti2.at LOS METAR Data Geospatial Linked Open Services Barry Norton and Reto Krummenacher 20.09.2010 Uniform WGS84 lat/long/alt ICAO and IATA- based URIs plus skos:notation to originals owl:sameAs • between ICAO/IATA • to Geonames (108) • to DBPedia (1159) http://www.linkedopenservices.org/data/METARStations.rdf.xml
    • 17. Karlsruhe Service Research Institute www.ksri.kit.edu Semantic Technologies Institute www.sti2.at LOS Weather Service Geospatial Linked Open Services Barry Norton and Reto Krummenacher 20.09.2010
    • 18. Karlsruhe Service Research Institute www.ksri.kit.edu Semantic Technologies Institute www.sti2.at LOS Geo Resources Geospatial Linked Open Services Barry Norton and Reto Krummenacher 20.09.2010
    • 19. Karlsruhe Service Research Institute www.ksri.kit.edu Semantic Technologies Institute www.sti2.at Resource-Based Linked Open Services GET Accept: text/html 303 REDIRECT /page GET Accept: application/rdf+xml (or text/n3) 303 REDIRECT /data LinkedDataLinkedService GET /weather Accept: application/rdf+xml (or text/n3) 200 <rdf:Description> Geospatial Linked Open Services Barry Norton and Reto Krummenacher 20.09.2010
    • 20. Karlsruhe Service Research Institute www.ksri.kit.edu Semantic Technologies Institute www.sti2.at Conclusion  We offer the following principles to guide the formation of Linked Open Services: 1. Describe services as LOD prosumers with input and output descriptions as SPARQL graph patterns 2. Communicate RDF by RESTful content negotiation 3. Communicate and describe the knowledge contribution resulting from service interaction, including implicit knowledge relating input, output and service provider  Associated with the last principle is an optional fourth: 4. When wrapping non-LOS services, extend the (lifted, if non-RDF) message to make explicit the implicit knowledge, and to use Linked Data vocabularies, using SPARQL CONSTRUCT queries  We have produced, hand-in-hand, a new dataset for LOD and several services of this form

    ×