draft-ietf-geopriv-geo-uri-06.txt   draft-ietf-geopriv-geo-uri-07.txt 
GEOPRIV -- Geographic A. Mayrhofer GEOPRIV -- Geographic A. Mayrhofer
Location/Privacy Working Group IPCom Location/Privacy Working Group IPCom
Internet-Draft C. Spanring Internet-Draft C. Spanring
Intended status: Standards Track April 09, 2010 Intended status: Standards Track April 14, 2010
Expires: October 11, 2010 Expires: October 16, 2010
A Uniform Resource Identifier for Geographic Locations ('geo' URI) A Uniform Resource Identifier for Geographic Locations ('geo' URI)
draft-ietf-geopriv-geo-uri-06 draft-ietf-geopriv-geo-uri-07
Abstract Abstract
This document specifies a Uniform Resource Identifier (URI) for This document specifies a Uniform Resource Identifier (URI) for
geographic locations using the 'geo' scheme name. A 'geo' URI geographic locations using the 'geo' scheme name. A 'geo' URI
identifies a physical location in a two- or three-dimensional identifies a physical location in a two- or three-dimensional
coordinate reference system in a compact, simple, human-readable, and coordinate reference system in a compact, simple, human-readable, and
protocol-independent way. The default coordinate reference system protocol-independent way. The default coordinate reference system
used is WGS-84. used is WGS-84.
skipping to change at page 1, line 36 skipping to change at page 1, line 36
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on October 11, 2010. This Internet-Draft will expire on October 16, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 37 skipping to change at page 2, line 37
3.2. Status . . . . . . . . . . . . . . . . . . . . . . . . . . 6 3.2. Status . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.3. URI Scheme Syntax . . . . . . . . . . . . . . . . . . . . 6 3.3. URI Scheme Syntax . . . . . . . . . . . . . . . . . . . . 6
3.4. URI Scheme Semantics . . . . . . . . . . . . . . . . . . . 7 3.4. URI Scheme Semantics . . . . . . . . . . . . . . . . . . . 7
3.4.1. Coordinate Reference System Identification . . . . . . 7 3.4.1. Coordinate Reference System Identification . . . . . . 7
3.4.2. Component Description for WGS-84 . . . . . . . . . . . 8 3.4.2. Component Description for WGS-84 . . . . . . . . . . . 8
3.4.3. Location Uncertainty . . . . . . . . . . . . . . . . . 8 3.4.3. Location Uncertainty . . . . . . . . . . . . . . . . . 8
3.4.4. URI Comparison . . . . . . . . . . . . . . . . . . . . 9 3.4.4. URI Comparison . . . . . . . . . . . . . . . . . . . . 9
3.4.5. Interpretation of Undefined Altitude . . . . . . . . . 10 3.4.5. Interpretation of Undefined Altitude . . . . . . . . . 10
3.5. Encoding Considerations . . . . . . . . . . . . . . . . . 10 3.5. Encoding Considerations . . . . . . . . . . . . . . . . . 10
3.6. Applications/Protocols that use this URI Scheme . . . . . 10 3.6. Applications/Protocols that use this URI Scheme . . . . . 10
3.7. Interopability Considerations . . . . . . . . . . . . . . 10 3.7. Interopability Considerations . . . . . . . . . . . . . . 11
3.8. Security Considerations . . . . . . . . . . . . . . . . . 11 3.8. Security Considerations . . . . . . . . . . . . . . . . . 11
3.9. Contact . . . . . . . . . . . . . . . . . . . . . . . . . 11 3.9. Contact . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.10. Author/Change controller . . . . . . . . . . . . . . . . . 11 3.10. Author/Change controller . . . . . . . . . . . . . . . . . 11
3.11. References . . . . . . . . . . . . . . . . . . . . . . . . 11 3.11. References . . . . . . . . . . . . . . . . . . . . . . . . 11
4. 'geo' URI Parameters Registry . . . . . . . . . . . . . . . . 11 4. 'geo' URI Parameters Registry . . . . . . . . . . . . . . . . 11
5. URI Operations . . . . . . . . . . . . . . . . . . . . . . . . 12 5. URI Operations . . . . . . . . . . . . . . . . . . . . . . . . 12
6. Use Cases and Examples . . . . . . . . . . . . . . . . . . . . 13 6. Use Cases and Examples . . . . . . . . . . . . . . . . . . . . 13
6.1. Plain 'geo' URI Example . . . . . . . . . . . . . . . . . 13 6.1. Plain 'geo' URI Example . . . . . . . . . . . . . . . . . 13
6.2. Hyperlink . . . . . . . . . . . . . . . . . . . . . . . . 13 6.2. Hyperlink . . . . . . . . . . . . . . . . . . . . . . . . 13
6.3. 'geo' URI in 2-dimensional barcode . . . . . . . . . . . . 14 6.3. 'geo' URI in 2-dimensional barcode . . . . . . . . . . . . 14
6.4. Comparison Examples . . . . . . . . . . . . . . . . . . . 14 6.4. Comparison Examples . . . . . . . . . . . . . . . . . . . 15
7. GML Mappings . . . . . . . . . . . . . . . . . . . . . . . . . 15 7. GML Mappings . . . . . . . . . . . . . . . . . . . . . . . . . 15
7.1. 2D GML 'Point' . . . . . . . . . . . . . . . . . . . . . . 16 7.1. 2D GML 'Point' . . . . . . . . . . . . . . . . . . . . . . 16
7.2. 3D GML 'Point' . . . . . . . . . . . . . . . . . . . . . . 16 7.2. 3D GML 'Point' . . . . . . . . . . . . . . . . . . . . . . 16
7.3. GML 'Circle' . . . . . . . . . . . . . . . . . . . . . . . 16 7.3. GML 'Circle' . . . . . . . . . . . . . . . . . . . . . . . 17
7.4. GML 'Sphere' . . . . . . . . . . . . . . . . . . . . . . . 17 7.4. GML 'Sphere' . . . . . . . . . . . . . . . . . . . . . . . 17
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18
8.1. 'geo' URI Scheme . . . . . . . . . . . . . . . . . . . . . 17 8.1. 'geo' URI Scheme . . . . . . . . . . . . . . . . . . . . . 18
8.2. URI Parameter Registry . . . . . . . . . . . . . . . . . . 18 8.2. URI Parameter Registry . . . . . . . . . . . . . . . . . . 18
8.2.1. Registry Contents . . . . . . . . . . . . . . . . . . 18 8.2.1. Registry Contents . . . . . . . . . . . . . . . . . . 18
8.2.2. Registration Policy . . . . . . . . . . . . . . . . . 18 8.2.2. Registration Policy . . . . . . . . . . . . . . . . . 19
8.3. Sub-Registry for 'crs' Parameter . . . . . . . . . . . . . 18 8.3. Sub-Registry for 'crs' Parameter . . . . . . . . . . . . . 19
8.3.1. Registry Contents . . . . . . . . . . . . . . . . . . 19 8.3.1. Registry Contents . . . . . . . . . . . . . . . . . . 19
8.3.2. Registration Policy . . . . . . . . . . . . . . . . . 19 8.3.2. Registration Policy . . . . . . . . . . . . . . . . . 20
9. Security Considerations . . . . . . . . . . . . . . . . . . . 19 9. Security Considerations . . . . . . . . . . . . . . . . . . . 20
9.1. Invalid Locations . . . . . . . . . . . . . . . . . . . . 19 9.1. Invalid Locations . . . . . . . . . . . . . . . . . . . . 20
9.2. Location Privacy . . . . . . . . . . . . . . . . . . . . . 20 9.2. Location Privacy . . . . . . . . . . . . . . . . . . . . . 20
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 20 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 21
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 20 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 21
11.1. Normative References . . . . . . . . . . . . . . . . . . . 20 11.1. Normative References . . . . . . . . . . . . . . . . . . . 21
11.2. Informative References . . . . . . . . . . . . . . . . . . 21 11.2. Informative References . . . . . . . . . . . . . . . . . . 21
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 21 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 22
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 23 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 23
1. Introduction 1. Introduction
An increasing number of Internet protocols and data formats are An increasing number of Internet protocols and data formats are
extended by specifications for adding spatial (geographic) location. extended by specifications for adding spatial (geographic) location.
In most cases, latitude as well as longitude of simple points are In most cases, latitude as well as longitude of simple points are
added as new attributes to existing data structures. However, all added as new attributes to existing data structures. However, all
those methods are very specific to a certain data format or protocol, those methods are very specific to a certain data format or protocol,
skipping to change at page 9, line 8 skipping to change at page 9, line 8
are never the same thing. are never the same thing.
The single uncertainty value is applied to all dimensions given in The single uncertainty value is applied to all dimensions given in
the URI. the URI.
Note: The number of digits of the values in <coordinates> MUST NOT be Note: The number of digits of the values in <coordinates> MUST NOT be
interpreted as an indication to uncertainty. interpreted as an indication to uncertainty.
3.4.4. URI Comparison 3.4.4. URI Comparison
Comparison of URIs intends to determine whether two URI strings are
equivalent and identify the same resource (rather than comparing the
resources themselves). Therefore, a comparison of two 'geo' URIs
does not compare spatial objects, but only the strings (URIs)
identifying those objects.
The term "mathematically identical" used below specifies that some
components of the URI MUST be compared as normalized numbers rather
than strings to account for the variety in string representations of
identical numbers (for example, the strings "43.10" and "43.1" are
different, but represent the same number).
Two 'geo' URIs are equal only if they fulfill all of the following Two 'geo' URIs are equal only if they fulfill all of the following
general comparison rules: general comparison rules:
o Both URIs use the same CRS, which means that either both have the o Both URIs use the same CRS, which means that either both have the
'crs' parameter omitted, or both have the same <crslabel> value, 'crs' parameter omitted, or both have the same <crslabel> value,
or one has the 'crs' parameter omitted while the other URI or one has the 'crs' parameter omitted while the other URI
specifies the default CRS explicitely with a <crslabel> value of specifies the default CRS explicitely with a <crslabel> value of
"wgs84". "wgs84".
o Their <coord-a>, <coord-b>, <coord-c> and 'u' values are o Their <coord-a>, <coord-b>, <coord-c> and 'u' values are
mathematically identical (including absent <uval> meaning mathematically identical (including absent <uval> meaning
skipping to change at page 15, line 29 skipping to change at page 15, line 43
<geo:70,20;foo=1;bar=white> in a legacy implementation is <geo:70,20;foo=1;bar=white> in a legacy implementation is
undefined, because the normalization rules for 'foo' are not undefined, because the normalization rules for 'foo' are not
known, and hence the implementation cannot identify whether or not known, and hence the implementation cannot identify whether or not
'1.00' is identical to '1' for the 'foo' parameter. '1.00' is identical to '1' for the 'foo' parameter.
o Comparing <geo:47,11;foo=blue;bar=white> and <geo: o Comparing <geo:47,11;foo=blue;bar=white> and <geo:
47,11;bar=white;foo=blue> returns true, because parameter order is 47,11;bar=white;foo=blue> returns true, because parameter order is
insignificant in comparison operations insignificant in comparison operations
o The comparison operation on <geo:22,0;bar=Blue> and <geo: o The comparison operation on <geo:22,0;bar=Blue> and <geo:
22,0;BAR=blue> is undefined, because even though parameter names 22,0;BAR=blue> is undefined, because even though parameter names
are case insensitive, this is not neccessarily the case for the are case insensitive, this is not neccessarily the case for the
values of the unknown 'foo' parameter. values of the unknown 'bar' parameter.
7. GML Mappings 7. GML Mappings
The Geographic Markup Language (GML) by the Open Geospatial The Geographic Markup Language (GML) by the Open Geospatial
Consortium (OGC) is a set of XML schemas to represent geographical Consortium (OGC) is a set of XML schemas to represent geographical
features. Since GML is widely accepted, this document includes features. Since GML is widely accepted, this document includes
instructions on how to transform 'geo' URIs from and to GML instructions on how to transform 'geo' URIs from and to GML
fragments. The instructions in this section are not normative. fragments. The instructions in this section are not normative.
For the following sections, "%lat%", "%lon%", "%alt%" and "%unc%" are For the following sections, "%lat%", "%lon%", "%alt%" and "%unc%" are
skipping to change at page 21, line 36 skipping to change at page 22, line 11
[WGS84] National Imagery and Mapping Agency, "Department of [WGS84] National Imagery and Mapping Agency, "Department of
Defense World Geodetic System 1984, Third Edition", Defense World Geodetic System 1984, Third Edition",
NIMA TR8350.2, January 2000. NIMA TR8350.2, January 2000.
Appendix A. Change Log Appendix A. Change Log
[Note to editors: This section is to be removed before publication - [Note to editors: This section is to be removed before publication -
XML source available on request] XML source available on request]
draft-ietf-geopriv-geo-uri-07
o Additonal text in URI comparison explaining what is being compared
o fixed typo in comparison example
draft-ietf-geopriv-geo-uri-06 draft-ietf-geopriv-geo-uri-06
o Addressed remaining IESG evaluation comments: o Addressed remaining IESG evaluation comments:
o comparison rules for unknown parameters o comparison rules for unknown parameters
o extended examples o extended examples
draft-ietf-geopriv-geo-uri-05 draft-ietf-geopriv-geo-uri-05
o Addressed IESG evaluation comments (some) o Addressed IESG evaluation comments (some)
draft-ietf-geopriv-geo-uri-04 draft-ietf-geopriv-geo-uri-04
o Added "crs" URI parameter registry o Added "crs" URI parameter registry
 End of changes. 16 change blocks. 
19 lines changed or deleted 35 lines changed or added

This html diff was produced by rfcdiff 1.38. The latest version is available from http://tools.ietf.org/tools/rfcdiff/