1 / 9

Alexander Mayrhofer, Christian Spanring IETF 68, Praha, CZ

The "geo" URI Scheme Uniform Resource Identifier Scheme for Geographic Locations http://geouri.org/. Alexander Mayrhofer, Christian Spanring IETF 68, Praha, CZ. Motivation. Location information is everywhere Protocols, data formats adding location fields Location info goes mainstream

makara
Download Presentation

Alexander Mayrhofer, Christian Spanring IETF 68, Praha, CZ

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The "geo" URI SchemeUniform Resource Identifier Scheme for Geographic Locationshttp://geouri.org/ Alexander Mayrhofer, Christian Spanring IETF 68, Praha, CZ GEOPRIV, IETF 68, Prague

  2. Motivation • Location information is everywhere • Protocols, data formats adding location fields • Location info goes mainstream • Some formats have unclear definitions • Reference system, esp. elevation datum. • Sometimes even no definition • No scheme which just identifies a location • All tied to a protocol, a data format, or a specific representation of the location (map) GEOPRIV, IETF 68, Prague

  3. Requirements • Not tied to a specific protocol/data format • But usable in most of them • Just identify location, not it's use/representation • User's choice, Context • Clear definition of reference system / semantics • As simple as possible • Easy authoring from GPS data • Readable & short – able to jot it down • Easy to parse • Distinguishable from "plain data"  came up with the idea of an URI scheme GEOPRIV, IETF 68, Prague

  4. The "geo" URI Scheme ‘Geo’ URIs identify a geographic location by the textual representation of the location’s spatial coordinates in either two or 3 dimensions (latitude, longitude, and optionally altitude). An optional query string contains additional parameters. ("ahh, URIs addressing geo locations"…) GEOPRIV, IETF 68, Prague

  5. Example geo:50.09318,14.43892,203?type=building • geo: • URI Scheme Name ("geo") and Separator (req.) • 50.09318 • Latitude (WGS 84, decimal degrees, required) • 14.43892 • Longitude (WGS 84, decimal degrees, required) • 203 • Altitude (WGS 84 MSL, decimal meters, optional) • type=building • Query parameters (optional) GEOPRIV, IETF 68, Prague

  6. Use cases • Hyperlink<p>IETF 68 is taking place in the <a href='geo:50.09318,14.43892,203?type=building'>Hilton Hotel, Prague</a></p> (Protocol handler [quickly hacked Firefox Extension] plus examples available at http://geouri.org) Alternative JavaScript implmentation to automatically embed maps at http://www.spanring.eu/geouri/ • Header FieldContact: <geo:50.09318,14.43892,203?type=building> • Simple NoteJoe, meet you at IETF 68 (geo:50.09318,14.43892,203) ? • Whereever URIs go!QR code on business cards and in newspapers..? GEOPRIV, IETF 68, Prague

  7. What this is not about • NOT touching PIDF-LO • NOT a LoST URI replacement • NOT a description of more complicated spatial objects (GML) • NOT just simple data (semantics behind!) GEOPRIV, IETF 68, Prague

  8. Feedback received • Received comments from about 10 people (from "GIS" as well as "IETF" world) • Appreciation of the idea as well as sceptisism • Privacy considerations • Relation to / distinction from other GEOPRIV topics • Query parameters underspecified • Semantics unclear • Other options than a URI scheme? • Isn't that just data? GEOPRIV, IETF 68, Prague

  9. Planned work • Draft/URI scheme • Revamp of "Query string" – probably URI parameters with registry? • Clarification of semantics • More sensible examples • Please provide feedback! • Early Implementations • Update to Firefox extension (configurable choice of maps) GEOPRIV, IETF 68, Prague

More Related