draft-ietf-geopriv-relative-location-03.txt   draft-ietf-geopriv-relative-location-04.txt 
GEOPRIV M. Thomson GEOPRIV M. Thomson
Internet-Draft Microsoft Internet-Draft Microsoft
Intended status: Standards Track B. Rosen Intended status: Standards Track B. Rosen
Expires: January 18, 2013 Neustar Expires: September 20, 2013 Neustar
D. Stanley D. Stanley
Aruba Networks Aruba Networks
G. Bajko G. Bajko
Nokia Nokia
A. Thomson A. Thomson
Cisco Systems, Inc. Cisco Systems, Inc.
July 17, 2012 March 19, 2013
Relative Location Representation Relative Location Representation
draft-ietf-geopriv-relative-location-03 draft-ietf-geopriv-relative-location-04.txt
Abstract Abstract
This document defines an extension to PIDF-LO (RFC4119) for the This document defines an extension to PIDF-LO (RFC4119) for the
expression of location information that is defined relative to a expression of location information that is defined relative to a
reference point. The reference point may be expressed as a geodetic reference point. The reference point may be expressed as a geodetic
or civic location, and the relative offset may be one of several or civic location, and the relative offset may be one of several
shapes. Optionally, a reference to a secondary document (such as a shapes. Optionally, a reference to a secondary document (such as a
map image) can be included, along with the relationship of the map map image) can be included, along with the relationship of the map
coordinate system to the reference/offset coordinate system to allow coordinate system to the reference/offset coordinate system to allow
skipping to change at page 1, line 47 skipping to change at page 1, line 47
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 January 18, 2013. This Internet-Draft will expire on September 20, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the
Copyright (c) 2013 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Conventions used in this document . . . . . . . . . . . . . . 4 2. Conventions used in this document . . . . . . . . . . . . . . 3
3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Relative Location . . . . . . . . . . . . . . . . . . . . . . 7 4. Relative Location . . . . . . . . . . . . . . . . . . . . . . 6
4.1. Relative Coordinate System . . . . . . . . . . . . . . . . 7 4.1. Relative Coordinate System . . . . . . . . . . . . . . . 6
4.2. Placement of XML Elements . . . . . . . . . . . . . . . . 7 4.2. Placement of XML Elements . . . . . . . . . . . . . . . . 7
4.3. Binary Format . . . . . . . . . . . . . . . . . . . . . . 8 4.3. Binary Format . . . . . . . . . . . . . . . . . . . . . . 7
4.4. Distances and Angles . . . . . . . . . . . . . . . . . . . 8 4.4. Distances and Angles . . . . . . . . . . . . . . . . . . 8
4.5. Value Encoding . . . . . . . . . . . . . . . . . . . . . . 9 4.5. Value Encoding . . . . . . . . . . . . . . . . . . . . . 8
4.6. Relative Location Restrictions . . . . . . . . . . . . . . 9 4.6. Relative Location Restrictions . . . . . . . . . . . . . 8
4.7. Baseline TLVs . . . . . . . . . . . . . . . . . . . . . . 9 4.7. Baseline TLVs . . . . . . . . . . . . . . . . . . . . . . 8
4.8. Reference TLV . . . . . . . . . . . . . . . . . . . . . . 9 4.8. Reference TLV . . . . . . . . . . . . . . . . . . . . . . 8
4.9. Shapes . . . . . . . . . . . . . . . . . . . . . . . . . . 9 4.9. Shapes . . . . . . . . . . . . . . . . . . . . . . . . . 9
4.9.1. Point . . . . . . . . . . . . . . . . . . . . . . . . 10 4.9.1. Point . . . . . . . . . . . . . . . . . . . . . . . . 9
4.9.2. Circle or Sphere Shape . . . . . . . . . . . . . . . . 11 4.9.2. Circle or Sphere Shape . . . . . . . . . . . . . . . 10
4.9.3. Ellipse or Ellipsoid Shape . . . . . . . . . . . . . . 12 4.9.3. Ellipse or Ellipsoid Shape . . . . . . . . . . . . . 11
4.9.4. Polygon or Prism Shape . . . . . . . . . . . . . . . . 14 4.9.4. Polygon or Prism Shape . . . . . . . . . . . . . . . 13
4.9.5. Arc-Band Shape . . . . . . . . . . . . . . . . . . . . 17 4.9.5. Arc-Band Shape . . . . . . . . . . . . . . . . . . . 15
4.10. Dynamic Location TLVs . . . . . . . . . . . . . . . . . . 18 4.10. Dynamic Location TLVs . . . . . . . . . . . . . . . . . . 17
4.10.1. Orientation . . . . . . . . . . . . . . . . . . . . . 19 4.10.1. Orientation . . . . . . . . . . . . . . . . . . . . 17
4.10.2. Speed . . . . . . . . . . . . . . . . . . . . . . . . 19 4.10.2. Speed . . . . . . . . . . . . . . . . . . . . . . . 17
4.10.3. Heading . . . . . . . . . . . . . . . . . . . . . . . 19 4.10.3. Heading . . . . . . . . . . . . . . . . . . . . . . 17
4.11. Secondary Map Metadata . . . . . . . . . . . . . . . . . . 19 4.11. Secondary Map Metadata . . . . . . . . . . . . . . . . . 17
4.11.1. Map URL . . . . . . . . . . . . . . . . . . . . . . . 20 4.11.1. Map URL . . . . . . . . . . . . . . . . . . . . . . 18
4.11.2. Map Coordinate Reference System . . . . . . . . . . . 20 4.11.2. Map Coordinate Reference System . . . . . . . . . . 18
4.11.3. Map Example . . . . . . . . . . . . . . . . . . . . . 22 4.11.3. Map Example . . . . . . . . . . . . . . . . . . . . 20
5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.1. Civic PIDF with Polygon Offset . . . . . . . . . . . . . . 23 5.1. Civic PIDF with Polygon Offset . . . . . . . . . . . . . 21
5.2. Geo PIDF with Circle Offset . . . . . . . . . . . . . . . 24 5.2. Geo PIDF with Circle Offset . . . . . . . . . . . . . . . 22
5.3. Civic TLV with Point Offset . . . . . . . . . . . . . . . 26 5.3. Civic TLV with Point Offset . . . . . . . . . . . . . . . 23
6. Schema Definition . . . . . . . . . . . . . . . . . . . . . . 26 6. Schema Definition . . . . . . . . . . . . . . . . . . . . . . 24
7. Security Considerations . . . . . . . . . . . . . . . . . . . 29 7. Security Considerations . . . . . . . . . . . . . . . . . . . 26
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 29 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27
8.1. Relative Location Registry . . . . . . . . . . . . . . . . 29 8.1. Relative Location Registry . . . . . . . . . . . . . . . 27
8.2. URN Sub-Namespace Registration . . . . . . . . . . . . . . 30 8.2. URN Sub-Namespace Registration . . . . . . . . . . . . . 28
8.3. XML Schema Registration . . . . . . . . . . . . . . . . . 31 8.3. XML Schema Registration . . . . . . . . . . . . . . . . . 29
8.4. CRS public identifier registration . . . . . . . . . . . . 31 8.4. CRS public identifier registration . . . . . . . . . . . 30
8.5. CAtype Registration . . . . . . . . . . . . . . . . . . . 33 8.5. CAtype Registration . . . . . . . . . . . . . . . . . . . 31
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 33 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 31
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 33 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 31
10.1. Normative References . . . . . . . . . . . . . . . . . . . 33 10.1. Normative References . . . . . . . . . . . . . . . . . . 31
10.2. Informative References . . . . . . . . . . . . . . . . . . 35 10.2. Informative References . . . . . . . . . . . . . . . . . 33
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 33
1. Introduction 1. Introduction
This document describes a format for the expression of relative This document describes a format for the expression of relative
location information. location information.
A relative location is formed of a reference location, plus a A relative location is formed of a reference location, plus a
relative offset from that reference location. The reference location relative offset from that reference location. The reference location
can be represented in either civic or geodetic form. The reference can be represented in either civic or geodetic form. The reference
location can also have dynamic components such as velocity. The location can also have dynamic components such as velocity. The
skipping to change at page 5, line 41 skipping to change at page 5, line 6
3-dimensional), or a shape that includes uncertainty: circle, sphere, 3-dimensional), or a shape that includes uncertainty: circle, sphere,
ellipse, ellipsoid, polygon, prism or arc-band. Descriptions of ellipse, ellipsoid, polygon, prism or arc-band. Descriptions of
these shapes can be found in [RFC5491]. these shapes can be found in [RFC5491].
Optionally, a reference to a 'map' document can be provided. The Optionally, a reference to a 'map' document can be provided. The
reference is a URI. The document could be an image or dataset that reference is a URI. The document could be an image or dataset that
represents a map, floorplan or other form. The type of document the represents a map, floorplan or other form. The type of document the
URI points to is described as a MIME media type. Metadata in the URI points to is described as a MIME media type. Metadata in the
relative location can include the location of the reference point in relative location can include the location of the reference point in
the map as well as an orientation (angle from North) and scale to the map as well as an orientation (angle from North) and scale to
align the document CRS with the WGS-84 CRS. The document is assumed align the document Co-ordinate Reference System (CRS) with the WGS84
to be useable by the application receiving the PIDF with the relative [WGS84] CRS. The document is assumed to be useable by the
location to locate the reference point in the map. This document application receiving the PIDF with the relative location to locate
does not describe any mechanisms for displaying or manipulating the the reference point in the map. This document does not describe any
document other than providing the reference location, orientation and mechanisms for displaying or manipulating the document other than
scale. providing the reference location, orientation and scale.
As an example, consider a relative location expressed as a point, As an example, consider a relative location expressed as a point,
relative to a civic location: relative to a civic location:
<presence xmlns="urn:ietf:params:xml:ns:pidf" <presence xmlns="urn:ietf:params:xml:ns:pidf"
xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model" xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model"
xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10" xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10"
xmlns:ca="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr" xmlns:ca="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr"
xmlns:rel="urn:ietf:params:xml:ns:pidf:geopriv10:relative" xmlns:rel="urn:ietf:params:xml:ns:pidf:geopriv10:relative"
xmlns:gml="http://www.opengis.net/gml" xmlns:gml="http://www.opengis.net/gml"
skipping to change at page 7, line 49 skipping to change at page 7, line 16
location alters relative coordinate system. The resulting Cartesian location alters relative coordinate system. The resulting Cartesian
coordinate system axes are rotated so that the 'y' axis is oriented coordinate system axes are rotated so that the 'y' axis is oriented
along the direction described by the <orientation> element. The along the direction described by the <orientation> element. The
coordinate system also moves as described by the <speed> and coordinate system also moves as described by the <speed> and
<heading> elements. <heading> elements.
4.2. Placement of XML Elements 4.2. Placement of XML Elements
The baseline of the reference location is represented as <location- The baseline of the reference location is represented as <location-
info> like a normal PIDF-LO. Relative location adds a new <relative- info> like a normal PIDF-LO. Relative location adds a new <relative-
location> element to <location-info> Within <relative-location> location> element to <location-info>. Within <relative-location>,
<reference> and <offset> elements are described. Within <offset> are <reference> and <offset> elements are described. Within <offset> are
shape elements described below. This document extends PIDF-LO as the shape elements described below. This document extends PIDF-LO as
described in [I-D.ietf-geopriv-local-civic]. described in [RFC6848].
4.3. Binary Format 4.3. Binary Format
This document describes a way to encode the relative location in a This document describes a way to encode the relative location in a
binary TLV form for use in other protocols that use TLVs to represent binary TLV form for use in other protocols that use TLVs to represent
location. location.
A type-length-value encoding is used. A type-length-value encoding is used.
+------+------+------+------+------+------+------+ +------+------+------+------+------+------+------+
| Type |Length| Value ... | Type |Length| Value ...
+------+------+------+------+------+------+ +------+------+------+------+------+------+
| X | N | Value label ... | X | N | Value ...
+------+------+------+------+------+------+------+ +------+------+------+------+------+------+------+
Figure 1: TLV-tuple format Figure 1: TLV-tuple format
Type field (X) is defined as a single byte. The type codes used are Type field (X) is defined as a single byte. The type codes used are
registered an IANA managed 'RLtypes' registry defined by this registered an IANA-managed 'RLtypes' registry defined by this
document, and restricted to not include the values defined by the document, and restricted to not include the values defined by the
CAtypes registry. This restriction permits a location reference and CAtypes registry. This restriction permits a location reference and
offset to be coded with unique TLVs. offset to be coded with unique TLVs.
The Length field (N) is defined as an unsigned integer that is one The Length field (N) is defined as an unsigned integer that is one
byte in length. This field can encode values from 0 to 255. The byte in length. This field can encode values from 0 to 255. The
length field describes the number of bytes in the Value. Length does length field describes the number of bytes in the Value. Length does
not count the bytes used for the Type or Length. not count the bytes used for the Type or Length.
The Value field is defined separately for each type. The Value field is defined separately for each type.
Each element of the relative location has a unique TLV assignment. A Each element of the relative location has a unique TLV assignment. A
relative location encoded in TLV would have the baseline location relative location encoded in TLV would have the baseline location
TLVs, a reference location TLV which contains within it the reference TLVs and a reference location TLV which contains within it the
refinement TLVs. The reference TLVs are followed by the relative reference refinement TLVs. The reference TLVs are followed by the
offset, and optional map TLDs described in this document. relative offset, and optional map TLDs described in this document.
4.4. Distances and Angles 4.4. Distances and Angles
All distance measures used in shapes are expressed in meters. All distance measures used in shapes are expressed in meters.
All orientation angles used in shapes are expressed in degrees. All orientation angles used in shapes are expressed in degrees.
Orientation angles are measured from WGS84 Northing to Easting with Orientation angles are measured from WGS84 Northing to Easting with
zero at Northing. Orientation angles in the relative coordinate zero at Northing. Orientation angles in the relative coordinate
system start from the second coordinate axis (y or Northing) and system start from the second coordinate axis (y or Northing) and
increase toward the first axis (x or Easting). increase toward the first axis (x or Easting).
4.5. Value Encoding 4.5. Value Encoding
The binary form uses single-precision floating point values [IEEE754] The binary form uses single-precision floating point values IEEE 754
to represent coordinates, distance and angle measures. Single [IEEE.754] to represent coordinates, distance and angle measures.
precision values are 32-bit values with a sign bit, 8 exponent bits Single precision values are 32-bit values with a sign bit, 8 exponent
and 23 fractional bits. bits and 23 fractional bits.
Binary-encoded coordinate values are considered to be a single value Binary-encoded coordinate values are considered to be a single value
without uncertainty. When encoding a value that cannot be exactly without uncertainty. When encoding a value that cannot be exactly
represented, the best approximation is chosen according to represented, the best approximation MUST be selected according to
[Clinger1990]. [Clinger1990].
4.6. Relative Location Restrictions 4.6. Relative Location Restrictions
More than one relative shape MUST NOT be included in either a PIDF-LO More than one relative shape MUST NOT be included in either a PIDF-LO
or TLV encoding of location for a given reference point. or TLV encoding of location for a given reference point.
Any error in the reference point transfers to the location described Any error in the reference point transfers to the location described
by the relative location. Any errors arising from an implementation by the relative location. Any errors arising from an implementation
not supporting or understanding elements of the reference point not supporting or understanding elements of the reference point
directly increases the error (or uncertainty) in the resulting directly increases the error (or uncertainty) in the resulting
location. location.
4.7. Baseline TLVs 4.7. Baseline TLVs
Baseline locations is described using the formats defined in Baseline locations are described using the formats defined in
[RFC4776] or [RFC6225]. [RFC4776] or [RFC6225].
4.8. Reference TLV 4.8. Reference TLV
When a reference is encoded in binary form, the baseline and When a reference is encoded in binary form, the baseline and
reference locations are combined in a reference TLV. This TLV reference locations are combined in a reference TLV. This TLV
contains civic address TLVs (if the baseline was a civic) or geo TLVs contains civic address TLVs (if the baseline was a civic) or geo TLVs
(if the baseline was a geo). (if the baseline was a geo).
+------+------+------+------+------+------+ +------+------+------+------+------+------+
skipping to change at page 10, line 11 skipping to change at page 9, line 24
reference and relative locations. Shape data in the reference reference and relative locations. Shape data in the reference
location uses a [WGS84] CRS. Shape data in the relative location location uses a [WGS84] CRS. Shape data in the relative location
uses a relative CRS. uses a relative CRS.
The XML form for shapes uses Geography Markup Language (GML) The XML form for shapes uses Geography Markup Language (GML)
[OGC.GML-3.1.1], consistent with the rules in [RFC5491]. Reference [OGC.GML-3.1.1], consistent with the rules in [RFC5491]. Reference
locations use the CRS URNs specified in [RFC5491]; relative locations locations use the CRS URNs specified in [RFC5491]; relative locations
use either a 2D CRS (urn:ietf:params:geopriv:relative:2d), or a 3D use either a 2D CRS (urn:ietf:params:geopriv:relative:2d), or a 3D
(urn:ietf:params:geopriv:relative:3d), depending on the shape type. (urn:ietf:params:geopriv:relative:3d), depending on the shape type.
The binary form of each shape uses a different shape types for 2d and The binary form of each shape uses a different shape type for 2d and
3d shapes. 3d shapes.
Nine shape type codes are defined. Nine shape type codes are defined.
4.9.1. Point 4.9.1. Point
A point "shape" describes a single point with unknown uncertainty. A point "shape" describes a single point with unknown uncertainty.
It consists of a single set of coordinates. It consists of a single set of coordinates.
In a two-dimensional CRS, the coordinate includes two values; in a In a two-dimensional CRS, the coordinate includes two values; in a
three-dimensional CRS, the coordinate includes three values. three-dimensional CRS, the coordinate includes three values.
4.9.1.1. XML encoding 4.9.1.1. XML encoding
A point is represented in GML using the following template: A point is represented in GML using the following template:
<gml:Point xmlns:gml="http://www.opengis.net/gml" <gml:Point xmlns:gml="http://www.opengis.net/gml"
srsName="$CRS-URN$"> srsName="$CRS-URN$">
<gml:pos>$Coordinate-1 $Coordinate-2$ $Coordinate-3$</gml:pos> <gml:pos>$Coordinate-1 $Coordinate-2$ $Coordinate-3$</gml:pos>
</gml:Point> </gml:Point>
GML Point Template GML Point Template
Where "$CRS-URN$" is replaced by a Where "$CRS-URN$" is replaced by a
urn:ietf:params:geopriv:relative:2d or urn:ietf:params:geopriv:relative:2d or
urn:ietf:params:geopriv:relative:3d and "$Coordinate-3$" is omitted urn:ietf:params:geopriv:relative:3d and "$Coordinate-3$" is omitted
if the CRS is two-dimensional. if the CRS is two-dimensional.
4.9.1.2. TLV encoding 4.9.1.2. TLV encoding
skipping to change at page 11, line 23 skipping to change at page 10, line 37
In a two-dimensional CRS, the coordinate includes two values and the In a two-dimensional CRS, the coordinate includes two values and the
resulting shape forms a circle. In a three-dimensional CRS, the resulting shape forms a circle. In a three-dimensional CRS, the
coordinate includes three values and the resulting shape forms a coordinate includes three values and the resulting shape forms a
sphere. sphere.
4.9.2.1. XML encoding 4.9.2.1. XML encoding
A circle is represented in and converted from GML using the following A circle is represented in and converted from GML using the following
template: template:
<gs:Circle xmlns:gml="http://www.opengis.net/gml" <gs:Circle xmlns:gml="http://www.opengis.net/gml"
xmlns:gs="http://www.opengis.net/pidflo/1.0" xmlns:gs="http://www.opengis.net/pidflo/1.0"
srsName="urn:ietf:params:geopriv:relative:2d"> srsName="urn:ietf:params:geopriv:relative:2d">
<gml:pos>$Coordinate-1 $Coordinate-2$</gml:pos> <gml:pos>$Coordinate-1 $Coordinate-2$</gml:pos>
<gs:radius uom="urn:ogc:def:uom:EPSG::9001"> <gs:radius uom="urn:ogc:def:uom:EPSG::9001">
$Radius$ $Radius$
</gs:radius> </gs:radius>
</gs:Circle> </gs:Circle>
GML Circle Template GML Circle Template
A sphere is represented in and converted from GML using the following A sphere is represented in and converted from GML using the following
template: template:
<gs:Sphere xmlns:gml="http://www.opengis.net/gml" <gs:Sphere xmlns:gml="http://www.opengis.net/gml"
xmlns:gml="http://www.opengis.net/pidflo/1.0" xmlns:gs="http://www.opengis.net/pidflo/1.0"
srsName="urn:ietf:params:geopriv:relative:3d"> srsName="urn:ietf:params:geopriv:relative:3d">
<gml:pos>$Coordinate-1 $Coordinate-2$ $Coordinate-3$</gml:pos> <gml:pos>$Coordinate-1 $Coordinate-2$ $Coordinate-3$</gml:pos>
<gs:radius uom="urn:ogc:def:uom:EPSG::9001"> <gs:radius uom="urn:ogc:def:uom:EPSG::9001">
$Radius$ $Radius$
</gs:radius> </gs:radius>
</gs:Sphere> </gs:Sphere>
GML Sphere Template GML Sphere Template
4.9.2.2. TLV encoding 4.9.2.2. TLV encoding
A circular shape is introduced by a type code of 115. A spherical A circular shape is introduced by a type code of 115. A spherical
shape is introduced by a type code of 116. shape is introduced by a type code of 116.
+------+------+ +------+------+
| 115/6|Length| | 115/6|Length|
skipping to change at page 13, line 10 skipping to change at page 12, line 5
semi-major axis, a semi-minor axis, a semi-major axis orientation semi-major axis, a semi-minor axis, a semi-major axis orientation
(clockwise from North). In a three-dimensional CRS, the coordinate (clockwise from North). In a three-dimensional CRS, the coordinate
includes three values and in addition to the two-dimensional values, includes three values and in addition to the two-dimensional values,
an altitude uncertainty (semi-vertical) is added. an altitude uncertainty (semi-vertical) is added.
4.9.3.1. XML encoding 4.9.3.1. XML encoding
An ellipse is represented in and converted from GML using the An ellipse is represented in and converted from GML using the
following template: following template:
<gs:Ellipse xmlns:gml="http://www.opengis.net/gml" <gs:Ellipse xmlns:gml="http://www.opengis.net/gml"
xmlns:gs="http://www.opengis.net/pidflo/1.0" xmlns:gs="http://www.opengis.net/pidflo/1.0"
srsName="urn:ietf:params:geopriv:relative:2d"> srsName="urn:ietf:params:geopriv:relative:2d">
<gml:pos>$Coordinate-1 $Coordinate-2$</gml:pos> <gml:pos>$Coordinate-1 $Coordinate-2$</gml:pos>
<gs:semiMajorAxis uom="urn:ogc:def:uom:EPSG::9001"> <gs:semiMajorAxis uom="urn:ogc:def:uom:EPSG::9001">
$Semi-Major$ $Semi-Major$
</gs:semiMajorAxis> </gs:semiMajorAxis>
<gs:semiMinorAxis uom="urn:ogc:def:uom:EPSG::9001"> <gs:semiMinorAxis uom="urn:ogc:def:uom:EPSG::9001">
$Semi-Minor$ $Semi-Minor$
</gs:semiMinorAxis> </gs:semiMinorAxis>
<gs:orientation uom="urn:ogc:def:uom:EPSG::9102"> <gs:orientation uom="urn:ogc:def:uom:EPSG::9102">
$Orientation$ $Orientation$
</gs:orientation> </gs:orientation>
</gs:Ellipse> </gs:Ellipse>
GML Ellipse Template GML Ellipse Template
An ellipsoid is represented in and converted from GML using the An ellipsoid is represented in and converted from GML using the
following template: following template:
<gs:Ellipsoid xmlns:gml="http://www.opengis.net/gml" <gs:Ellipsoid xmlns:gml="http://www.opengis.net/gml"
xmlns:gs="http://www.opengis.net/pidflo/1.0" xmlns:gs="http://www.opengis.net/pidflo/1.0"
srsName="urn:ietf:params:geopriv:relative:3d"> srsName="urn:ietf:params:geopriv:relative:3d">
<gml:pos>$Coordinate-1 $Coordinate-2$ $Coordinate-3$</gml:pos> <gml:pos>$Coordinate-1 $Coordinate-2$ $Coordinate-3$</gml:pos>
<gs:semiMajorAxis uom="urn:ogc:def:uom:EPSG::9001"> <gs:semiMajorAxis uom="urn:ogc:def:uom:EPSG::9001">
$Semi-Major$ $Semi-Major$
</gs:semiMajorAxis> </gs:semiMajorAxis>
<gs:semiMinorAxis uom="urn:ogc:def:uom:EPSG::9001"> <gs:semiMinorAxis uom="urn:ogc:def:uom:EPSG::9001">
$Semi-Minor$ $Semi-Minor$
</gs:semiMinorAxis> </gs:semiMinorAxis>
<gs:verticalAxis uom="urn:ogc:def:uom:EPSG::9001"> <gs:verticalAxis uom="urn:ogc:def:uom:EPSG::9001">
$Semi-Vertical$ $Semi-Vertical$
</gs:verticalAxis> </gs:verticalAxis>
<gs:orientation uom="urn:ogc:def:uom:EPSG::9102"> <gs:orientation uom="urn:ogc:def:uom:EPSG::9102">
$Orientation$ $Orientation$
</gs:orientation> </gs:orientation>
</gs:Ellipsoid> </gs:Ellipsoid>
GML Ellipsoid Template GML Ellipsoid Template
4.9.3.2. TLV encoding 4.9.3.2. TLV encoding
An ellipse is introduced by a type code of 117 and an ellipsoid is An ellipse is introduced by a type code of 117 and an ellipsoid is
introduced by a type code of 118. introduced by a type code of 118.
+------+------+ +------+------+
| 117/8|Length| | 117/8|Length|
skipping to change at page 15, line 10 skipping to change at page 13, line 33
At least 3 points MUST be included in a polygon. In order to At least 3 points MUST be included in a polygon. In order to
interoperate with existing systems, an encoding SHOULD include 15 or interoperate with existing systems, an encoding SHOULD include 15 or
fewer points, unless the recipient is known to support larger fewer points, unless the recipient is known to support larger
numbers. numbers.
4.9.4.1. XML Encoding 4.9.4.1. XML Encoding
A polygon is represented in and converted from GML using the A polygon is represented in and converted from GML using the
following template: following template:
<gml:Polygon xmlns:gml="http://www.opengis.net/gml" <gml:Polygon xmlns:gml="http://www.opengis.net/gml"
srsName="urn:ietf:params:geopriv:relative:2d"> srsName="urn:ietf:params:geopriv:relative:2d">
<gml:exterior> <gml:exterior>
<gml:LinearRing> <gml:LinearRing>
<gml:posList> <gml:posList>
$Coordinate1-1$ $Coordinate1-2$ $Coordinate1-1$ $Coordinate1-2$
$Coordinate2-1$ $Coordinate2-2$ $Coordinate2-1$ $Coordinate2-2$
$Coordinate3-1$ ... $Coordinate3-1$ ...
... ...
$CoordinateN-1$ $CoordinateN-2$ $CoordinateN-1$ $CoordinateN-2$
$Coordinate1-1$ $Coordinate1-2$ $Coordinate1-1$ $Coordinate1-2$
</gml:posList> </gml:posList>
</gml:LinearRing> </gml:LinearRing>
</gml:exterior> </gml:exterior>
</gml:Polygon> </gml:Polygon>
GML Polygon Template GML Polygon Template
Alternatively, a series of "pos" elements can be used in place of the Alternatively, a series of "pos" elements can be used in place of the
single "posList". Each "pos" element contains two or three single "posList". Each "pos" element contains two or three
coordinate values. coordinate values.
Note that the first point is repeated at the end of the sequence of Note that the first point is repeated at the end of the sequence of
coordinates and no explicit count of the number of points is coordinates and no explicit count of the number of points is
provided. provided.
A GML polygon that includes altitude cannot be represented completely A GML polygon that includes altitude cannot be represented completely
in binary. When converting to the binary representation, a two in binary. When converting to the binary representation, a two
dimensional CRS is used and altitude is removed from each coordinate. dimensional CRS is used and altitude is removed from each coordinate.
A prism is represented in and converted from GML using the following A prism is represented in and converted from GML using the following
template: template:
<gs:Prism xmlns:gml="http://www.opengis.net/gml" <gs:Prism xmlns:gml="http://www.opengis.net/gml"
xmlns:gs="http://www.opengis.net/pidflo/1.0" xmlns:gs="http://www.opengis.net/pidflo/1.0"
srsName="urn:ietf:params:geopriv:relative:3d"> srsName="urn:ietf:params:geopriv:relative:3d">
<gs:base> <gs:base>
<gml:Polygon> <gml:Polygon>
<gml:exterior> <gml:exterior>
<gml:LinearRing> <gml:LinearRing>
<gml:posList> <gml:posList>
$Coordinate1-1$ $Coordinate1-2$ $Coordinate1-3$ $Coordinate1-1$ $Coordinate1-2$ $Coordinate1-3$
$Coordinate2-1$ $Coordinate2-2$ $Coordinate2-3$ $Coordinate2-1$ $Coordinate2-2$ $Coordinate2-3$
$Coordinate2-1$ ... ... $Coordinate2-1$ ... ...
... ...
$CoordinateN-1$ $CoordinateN-2$ $CoordinateN-3$ $CoordinateN-1$ $CoordinateN-2$ $CoordinateN-3$
$Coordinate1-1$ $Coordinate1-2$ $Coordinate1-3$ $Coordinate1-1$ $Coordinate1-2$ $Coordinate1-3$
</gml:posList> </gml:posList>
</gml:LinearRing> </gml:LinearRing>
</gml:exterior> </gml:exterior>
</gml:Polygon> </gml:Polygon>
</gs:base> </gs:base>
<gs:height uom="urn:ogc:def:uom:EPSG::9001"> <gs:height uom="urn:ogc:def:uom:EPSG::9001">
$Height$ $Height$
</gs:height> </gs:height>
</gs:Prism> </gs:Prism>
GML Prism Template GML Prism Template
Alternatively, a series of "pos" elements can be used in place of the Alternatively, a series of "pos" elements can be used in place of the
single "posList". Each "pos" element contains three coordinate single "posList". Each "pos" element contains three coordinate
values. values.
4.9.4.2. TLV Encoding 4.9.4.2. TLV Encoding
A polygon containing 2D points uses a type code of 119. A polygon
A polygon containing 2D points is uses a type code of 119. A polygon
with 3D points uses a type code of 120. A prism uses a type code of with 3D points uses a type code of 120. A prism uses a type code of
121. 121. The number of points can be inferred from the length of the
TLV.
+------+------+ +------+------+
|119-21|Length| |119-21|Length|
+------+------+------+------+------+------+ +------+------+------+------+
| Count | (3D-only) Height | | (3D-only) Height |
+------+------+------+------+------+------+ +------+------+------+------+
| Coordinate1-1 | | Coordinate1-1 |
+------+------+------+------+ +------+------+------+------+
| Coordinate1-2 | | Coordinate1-2 |
+------+------+------+------+ +------+------+------+------+
| (3D-only) Coordinate1-3 | | (3D-only) Coordinate1-3 |
+------+------+------+------+ +------+------+------+------+
| Coordinate2-1 | | Coordinate2-1 |
+------+------+------+------+ +------+------+------+------+
... ...
+------+------+------+------+ +------+------+------+------+
| CoordinateN-1 | | CoordinateN-1 |
+------+------+------+------+ +------+------+------+------+
| CoordinateN-2 | | CoordinateN-2 |
+------+------+------+------+ +------+------+------+------+
| (3D-only) CoordinateN-3 | | (3D-only) CoordinateN-3 |
+------+------+------+------+ +------+------+------+------+
Polygon or Prism Encoding Polygon or Prism Encoding
Note that unlike the polygon representation in GML, the first and Note that unlike the polygon representation in GML, the first and
last points are not the same point to be the same in the TLV last points are not the same point in the TLV representation. The
representation. The duplicated point is removed from the binary duplicated point is removed from the binary form.
form.
4.9.5. Arc-Band Shape 4.9.5. Arc-Band Shape
A arc-band describes a region constrained by a range of angles and A arc-band describes a region constrained by a range of angles and
distances from a predetermined point. This shape can only be distances from a predetermined point. This shape can only be
provided for a two-dimensional CRS. provided for a two-dimensional CRS.
Distance and angular measures are defined in meters and degrees Distance and angular measures are defined in meters and degrees
respectively. Both are encoded as single precision floating point respectively. Both are encoded as single precision floating point
values. values.
4.9.5.1. XML encoding 4.9.5.1. XML encoding
An arc-band is represented in and converted from GML using the An arc-band is represented in and converted from GML using the
following template: following template:
<gs:ArcBand xmlns:gml="http://www.opengis.net/gml" <gs:ArcBand xmlns:gml="http://www.opengis.net/gml"
xmlns:gs="http://www.opengis.net/pidflo/1.0" xmlns:gs="http://www.opengis.net/pidflo/1.0"
srsName="urn:ietf:params:geopriv:relative:2d"> srsName="urn:ietf:params:geopriv:relative:2d">
<gml:pos>$Coordinate-1 $Coordinate-2$</gml:pos> <gml:pos>$Coordinate-1 $Coordinate-2$</gml:pos>
<gs:innerRadius uom="urn:ogc:def:uom:EPSG::9001"> <gs:innerRadius uom="urn:ogc:def:uom:EPSG::9001">
$Inner-Radius$ $Inner-Radius$
</gs:innerRadius> </gs:innerRadius>
<gs:outerRadius uom="urn:ogc:def:uom:EPSG::9001"> <gs:outerRadius uom="urn:ogc:def:uom:EPSG::9001">
$Inner-Radius$ $Inner-Radius$
</gs:outerRadius> </gs:outerRadius>
<gs:startAngle uom="urn:ogc:def:uom:EPSG::9102"> <gs:startAngle uom="urn:ogc:def:uom:EPSG::9102">
$Start-Angle$ $Start-Angle$
</gs:startAngle> </gs:startAngle>
<gs:openingAngle uom="urn:ogc:def:uom:EPSG::9102"> <gs:openingAngle uom="urn:ogc:def:uom:EPSG::9102">
$Opening-Angle$ $Opening-Angle$
</gs:openingAngle> </gs:openingAngle>
</gs:Ellipsoid> </gs:ArcBand>
GML Arc-Band Template GML Arc-Band Template
4.9.5.2. TLV Encoding 4.9.5.2. TLV Encoding
An arc-band is introduced by a type code of 122. An arc-band is introduced by a type code of 122.
+------+------+ +------+------+
| 122 |Length| | 122 |Length|
+------+------+------+------+ +------+------+------+------+
skipping to change at page 19, line 26 skipping to change at page 17, line 30
Dynamic Orientation TLVs Dynamic Orientation TLVs
4.10.2. Speed 4.10.2. Speed
The speed of the target is a scalar value in meters per second. The speed of the target is a scalar value in meters per second.
+------+------+ +------+------+
| 124 |Length| | 124 |Length|
+------+------+------+------+ +------+------+------+------+
| Length |
+------+------+------+------+
| Speed | | Speed |
+------+------+------+------+ +------+------+------+------+
Dynamic Speed TLVs Dynamic Speed TLVs
4.10.3. Heading 4.10.3. Heading
The heading, or direction of travel, is described using one or two The heading, or direction of travel, is described using one or two
angles. angles.
skipping to change at page 21, line 16 skipping to change at page 19, line 21
For image maps, coordinates start from the upper left corner and For image maps, coordinates start from the upper left corner and
coordinates are first counted by column with positive values to the coordinates are first counted by column with positive values to the
right; then rows are counted with positive values toward the bottom right; then rows are counted with positive values toward the bottom
of the image. For such an image, the first item is columns, the of the image. For such an image, the first item is columns, the
second rows and any third value applies to any third dimension used second rows and any third value applies to any third dimension used
in the image coordinate space. in the image coordinate space.
The <offset> element contains 2 (or 3) coordinates similar to a GML The <offset> element contains 2 (or 3) coordinates similar to a GML
"pos", For example: "pos", For example:
<offset> 2670.0 1124.0 1022.0</offset> <offset> 2670.0 1124.0 1022.0</offset>
Map Reference Point Example XML Map Reference Point Example XML
+------+------+ +------+------+
| 128 |Length| | 128 |Length|
+------+------+------+------+ +------+------+------+------+
| Coordinate-1 | | Coordinate-1 |
+------+------+------+------+ +------+------+------+------+
| Coordinate-2 | | Coordinate-2 |
+------+------+------+------+ +------+------+------+------+
| (3D-only) Coordinate-3 | | (3D-only) Coordinate-3 |
+------+------+------+------+ +------+------+------+------+
Map Reference Point Coordinates TLV Map Reference Point Coordinates TLV
If omitted, a value containing all zeros is assumed. If the If omitted, a value containing all zeros is assumed. If the
coordinates provided contain fewer values than are needed, the first coordinates provided contain fewer values than are needed, the first
value from the set is applied in place of any missing values. value from the set is applied in place of any missing values.
4.11.2.2. Map Orientation 4.11.2.2. Map Orientation
The map orientation includes the orientation of the map direction in The map orientation includes the orientation of the map direction in
relation to the Earth. Map orientation is expressed relative to the relation to the Earth. Map orientation is expressed relative to the
orientation of the relative coordinate system. This means that map orientation of the relative coordinate system. This means that map
orientation with respect to WGS84 North is the sum of th orientation orientation with respect to WGS84 North is the sum of the orientation
field, plus any orientation included in a dynamic portion of the field, plus any orientation included in a dynamic portion of the
reference location. Both values default to zero if no value is reference location. Both values default to zero if no value is
specified. specified.
This type uses a single precision floating point value of degrees This type uses a single precision floating point value of degrees
relative to North. relative to North.
In XML, the <orientation> element contains a single floating point In XML, the <orientation> element contains a single floating point
value, example <orientation>67.00</orientation>. In TLV form: value, example <orientation>67.00</orientation>. In TLV form:
skipping to change at page 22, line 19 skipping to change at page 20, line 22
Map Orientation TLV Map Orientation TLV
4.11.2.3. Map Scale 4.11.2.3. Map Scale
The optional map scale describes the relationship between the units The optional map scale describes the relationship between the units
of measure used in the map, relative to the meters unit used in the of measure used in the map, relative to the meters unit used in the
relative coordinate system. relative coordinate system.
This type uses a sequence of IEEE 754 [IEEE.754] single precision This type uses a sequence of IEEE 754 [IEEE.754] single precision
floating point values to represent scale as a sequence of numeric floating point values to represent scale as a sequence of numeric
values. The units of these values is dependent on the type of map, values. The units of these values are dependent on the type of map,
and could for example be pixels per meter for an image. and could for example be pixels per meter for an image.
A scaling factor is provided for each axis in the coordinate system. A scaling factor is provided for each axis in the coordinate system.
For a two-dimensional coordinate system, two values are included to For a two-dimensional coordinate system, two values are included to
allow for different scaling along the x and y axes independently. allow for different scaling along the x and y axes independently.
For a three-dimensional coordinate system, three values are specified For a three-dimensional coordinate system, three values are specified
for the x, y and z axes. for the x, y and z axes. Decoders can determine the number of
scaling factors by examining the length field.
Alternatively, a single scaling value MAY be used to apply the same Alternatively, a single scaling value MAY be used to apply the same
scaling factor to all coordinate components. scaling factor to all coordinate components.
Images that use a rows/columns coordinate system often use a left- Images that use a rows/columns coordinate system often use a left-
handed coordinate system. A negative value for the y/rows-axis handed coordinate system. A negative value for the y/rows-axis
scaling value can be used to account for any change in direction scaling value can be used to account for any change in direction
between the y-axis used in the relative coordinate system and the between the y-axis used in the relative coordinate system and the
rows axis of the image coordinate system. rows axis of the image coordinate system.
skipping to change at page 22, line 48 skipping to change at page 21, line 4
may contain 2 (or 3) values similar to a GML "pos" with separate may contain 2 (or 3) values similar to a GML "pos" with separate
scale values. In TLV form: scale values. In TLV form:
+------+------+------+------+------+ +------+------+------+------+------+
| 130 |Length| Scales ... | 130 |Length| Scales ...
+------+------+------+------+------+ +------+------+------+------+------+
Map Scale TLV Map Scale TLV
4.11.3. Map Example 4.11.3. Map Example
An example of expressing a map is: An example of expressing a map is:
<rel:map> <rel:map>
<rel:url type="image/jpeg"> <rel:url type="image/jpeg">
http://example.com/map.jpg http://example.com/map.jpg
</rel:url> </rel:url>
<rel:offset>200 210</rel:offset> <rel:offset>200 210</rel:offset>
<rel:orientation>68</rel:orientation> <rel:orientation>68</rel:orientation>
<rel:scale>2.90 -2.90</rel:scale> <rel:scale>2.90 -2.90</rel:scale>
</rel:map> </rel:map>
Map Example Map Example
5. Examples 5. Examples
5.1. Civic PIDF with Polygon Offset 5.1. Civic PIDF with Polygon Offset
<presence xmlns="urn:ietf:params:xml:ns:pidf" <presence xmlns="urn:ietf:params:xml:ns:pidf"
xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model" xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model"
xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10" xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10"
skipping to change at page 24, line 15 skipping to change at page 22, line 17
<gml:pos>433.0 -734.0</gml:pos> <!--A--> <gml:pos>433.0 -734.0</gml:pos> <!--A-->
<gml:pos>431.0 -733.0</gml:pos> <!--F--> <gml:pos>431.0 -733.0</gml:pos> <!--F-->
<gml:pos>431.0 -732.0</gml:pos> <!--E--> <gml:pos>431.0 -732.0</gml:pos> <!--E-->
<gml:pos>433.0 -731.0</gml:pos> <!--D--> <gml:pos>433.0 -731.0</gml:pos> <!--D-->
<gml:pos>434.0 -732.0</gml:pos> <!--C--> <gml:pos>434.0 -732.0</gml:pos> <!--C-->
<gml:pos>434.0 -733.0</gml:pos> <!--B--> <gml:pos>434.0 -733.0</gml:pos> <!--B-->
<gml:pos>433.0 -734.0</gml:pos> <!--A--> <gml:pos>433.0 -734.0</gml:pos> <!--A-->
</gml:LinearRing> </gml:LinearRing>
</gml:exterior> </gml:exterior>
</gml:Polygon> </gml:Polygon>
<rel:offset> </rel:offset>
</rel:relative-location> </rel:relative-location>
</gp:location-info> </gp:location-info>
<gp:usage-rules/> <gp:usage-rules/>
<gp:method>GPS</gp:method> <gp:method>GPS</gp:method>
</gp:geopriv> </gp:geopriv>
<dm:deviceID>mac:1234567890ab</dm:deviceID> <dm:deviceID>mac:1234567890ab</dm:deviceID>
<dm:timestamp>2007-06-22T20:57:29Z</dm:timestamp> <dm:timestamp>2007-06-22T20:57:29Z</dm:timestamp>
</dm:device> </dm:device>
</presence> </presence>
5.2. Geo PIDF with Circle Offset 5.2. Geo PIDF with Circle Offset
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<presence xmlns="urn:ietf:params:xml:ns:pidf" <presence xmlns="urn:ietf:params:xml:ns:pidf"
xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model" xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model"
xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10" xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10"
xmlns:rel="urn:ietf:params:xml:ns:pidf:geopriv10:relative" xmlns:rel="urn:ietf:params:xml:ns:pidf:geopriv10:relative"
xmlns:gml="http://www.opengis.net/gml" xmlns:gml="http://www.opengis.net/gml"
entity="pres:point2d@example.com"> xmlns:gs="http://www.opengis.net/pidflo/1.0"
<dm:device id="point2d"> entity="pres:point2d@example.com">
<gp:geopriv> <dm:device id="point2d">
<gp:location-info> <gp:geopriv>
<gml:Circle srsName="urn:ogc:def:crs:EPSG::4326"> <gp:location-info>
<gml:pos>-34.407 150.883</gml:pos> <gs:Circle srsName="urn:ogc:def:crs:EPSG::4326">
<gs:radius uom="urn:ogc:def:uom:EPSG::9001"> <gml:pos>-34.407 150.883</gml:pos>
50.0 <gml:radius uom="urn:ogc:def:uom:EPSG::9001">
</gs:radius> 50.0
</gml:Circle> </gml:radius>
<rel:relative-location> </gs:Circle>
<rel:reference> <rel:relative-location>
<gml:Point srsName="urn:ogc:def:crs:EPSG::4326"> <rel:reference>
<gml:pos>-34.407 150.883</gml:pos> <gml:Point srsName="urn:ogc:def:crs:EPSG::4326">
</gml:Point> <gml:pos>-34.407 150.883</gml:pos>
</rel:reference>
<rel:offset> </gml:Point>
<gml:Circle xmlns:gml="http://www.opengis.net/gml" </rel:reference>
srsName="urn:ietf:params:geopriv:relative:2d"> <rel:offset>
<gml:pos>500.0 750.0</gml:pos> <gml:Circle xmlns:gml="http://www.opengis.net/gml"
<gml:radius uom="urn:ogc:def:uom:EPSG::9001"> srsName="urn:ietf:params:geopriv:relative:2d">
5.0 <gml:pos>500.0 750.0</gml:pos>
</gml:radius> <gml:radius uom="urn:ogc:def:uom:EPSG::9001">
</gml:Circle> 5.0
</rel:relative-location> </gml:radius>
<map:map> </gml:Circle>
<map:urltype="image/png"> </rel:offset>
https://www.example.com/flrpln/123South/flr-2</gp:url> <rel:map>
<map:offset> 2670.0 1124.0 1022.0</gp:offset> <rel:urltype="image/png">
<map:orientation>67.00</gp:orientation> https://www.example.com/flrpln/123South/flr-2
<map:scale>10</gp:scale> </rel:url>
</map:map> <rel:offset> 2670.0 1124.0 1022.0</rel:offset>
</gp:location-info> <rel:orientation>67.00</rel:orientation>
<gp:usage-rules/> <rel:scale>10</rel:scale>
<gp:method>Wiremap</gp:method> </rel:map>
</rel:relative-location>
</gp:location-info>
<gp:usage-rules/>
<gp:method>Wiremap</gp:method>
</gp:geopriv>
<dm:deviceID>mac:1234567890ab</dm:deviceID>
<dm:timestamp>2007-06-22T20:57:29Z</dm:timestamp>
</dm:device>
</gp:geopriv> </gp:geopriv>
<dm:deviceID>mac:1234567890ab</dm:deviceID> </status>
<dm:timestamp>2007-06-22T20:57:29Z</dm:timestamp> <timestamp>2003-06-22T20:57:29Z</timestamp>
</dm:device> </tuple>
</gp:geopriv> </presence>
</status>
<timestamp>2003-06-22T20:57:29Z</timestamp>
</tuple>
</presence>
5.3. Civic TLV with Point Offset 5.3. Civic TLV with Point Offset
+--------+-------------------------------------------------+ +--------+-------------------------------------------------+
| Type | Value | | Type | Value |
+--------+-------------------------------------------------+ +--------+-------------------------------------------------+
| 0 | en | | 0 | en |
| | | | | |
| 1 | IL | | 1 | IL |
| | | | | |
| 3 | Chicago | | 3 | Chicago |
| | | | | |
| 34 | Wacker | | 34 | Wacker |
| | | | | |
| 18 | Drive | | 18 | Drive |
| | | | | |
| 19 | 3400 | | 19 | 3400 |
| | | | | |
| 112 | Reference | | 112 | Reference |
| | | | | |
| 40 | BBuilding|A | | 25 | Building A |
| | | | | |
| 40 | AFloor|6th | | 27 | Floor 6 |
| | | | | |
| 40 | BSuite|213 | | 26 | Suite 213 |
| | | | | |
| 40 | ADoor|Front | | 28 | Reception Area |
| | | | | |
| 115 | 100 70 | | 115 | 100 70 |
| | | | | |
| 126 | image/png | | 126 | image/png |
| | | | | |
| 127 | http://maps.example.com/3400Wacker/A6 | | 127 | http://maps.example.com/3400Wacker/A6 |
| | | | | |
| 128 | 0.0 4120.0 | | 128 | 0.0 4120.0 |
| | | | | |
| 129 | 113.0 | | 129 | 113.0 |
| | | | | |
| 130 | 10.6 | | 130 | 10.6 |
+--------+-------------------------------------------------+ +--------+-------------------------------------------------+
6. Schema Definition 6. Schema Definition
<?xml version="1.0"?> <?xml version="1.0"?>
<xs:schema <xs:schema
xmlns:rel="urn:ietf:params:xml:ns:pidf:geopriv10:relative" xmlns:rel="urn:ietf:params:xml:ns:pidf:geopriv10:relative"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:gml="http://www.opengis.net/gml" xmlns:gml="http://www.opengis.net/gml"
targetNamespace="urn:ietf:params:xml:ns:pidf:geopriv10:relative" targetNamespace="urn:ietf:params:xml:ns:pidf:geopriv10:relative"
elementFormDefault="qualified" elementFormDefault="qualified"
skipping to change at page 28, line 42 skipping to change at page 26, line 29
<xs:complexType name="mapUrlType"> <xs:complexType name="mapUrlType">
<xs:simpleContent> <xs:simpleContent>
<xs:extension base="xs:anyURI"> <xs:extension base="xs:anyURI">
<xs:attribute name="type" type="rel:mimeType" <xs:attribute name="type" type="rel:mimeType"
default="application/octet-stream"/> default="application/octet-stream"/>
</xs:extension> </xs:extension>
</xs:simpleContent> </xs:simpleContent>
</xs:complexType> </xs:complexType>
<!-- From draft-ietf-httpbis-p3-payload-09, excluding
the obsolete parts -->
<xs:simpleType name="mimeType"> <xs:simpleType name="mimeType">
<xs:restriction base="xs:token"> <xs:restriction base="xs:token">
<xs:pattern value="[!#$%&amp;'\*\+\-\.\dA-Z^_`a-z\|~]+ <xs:pattern value="[!#$%&amp;'\*\+\-\.\dA-Z^_`a-z\|~]+
/[!#$%&amp;'\*\+\-\.\dA-Z^_`a-z\|~]+([\t ]*;([\t ])*[!#$%&amp; /[!#$%&amp;'\*\+\-\.\dA-Z^_`a-z\|~]+([\t ]*;([\t ])*[!#$%&amp;
'\*\+\-\.\dA-Z^_`a-z\|~]+=([!#$%&amp;'\*\+\-\.\dA-Z^_`a-z\|~]+| '\*\+\-\.\dA-Z^_`a-z\|~]+=([!#$%&amp;'\*\+\-\.\dA-Z^_`a-z\|~]+|
&quot;([!#-\[\]-~]|[\t ]*|\\[\t !-~])*&quot;))*"/> &quot;([!#-\[\]-~]|[\t ]*|\\[\t !-~])*&quot;))*"/>
</xs:restriction> </xs:restriction>
</xs:simpleType> </xs:simpleType>
<xs:simpleType name="doubleList"> <xs:simpleType name="doubleList">
<xs:list itemType="xs:double"/> <xs:list itemType="xs:double"/>
</xs:simpleType> </xs:simpleType>
</xs:schema> </xs:schema>
xml schema relative-location xml schema relative-location
7. Security Considerations 7. Security Considerations
skipping to change at page 29, line 22 skipping to change at page 27, line 10
7. Security Considerations 7. Security Considerations
This document describes a data format. To a large extent, security This document describes a data format. To a large extent, security
properties of this depend on how this data is used. properties of this depend on how this data is used.
Privacy for location data is typically important. Adding relative Privacy for location data is typically important. Adding relative
location may increase the precision of the location, but does not location may increase the precision of the location, but does not
otherwise alter its privacy considerations, which are discussed in otherwise alter its privacy considerations, which are discussed in
[RFC4119] [RFC4119]
[[Not that interesting, but it could be relevant ?]] The fractional The fractional bits in IEEE 754 [IEEE.754] floating point values can
bits in IEEE 754 [IEEE.754] floating point values can be used as a be used as a covert channel. For values of either zero or infinity,
covert channel. For values of either zero or infinity, non-zero non-zero fraction bits could be used to convey information. If the
fraction bits could be used to convey information. If the presence presence of covert channels is not desired then the fractional bits
of covert channels is not desired then the fractional bits MUST be MUST be set to zero. There is no need to represent NaN (not a
set to zero. There is no need to represent NaN (not a number) in number) in this encoding.
this encoding.
8. IANA Considerations 8. IANA Considerations
8.1. Relative Location Registry 8.1. Relative Location Registry
This document creates a new registry called 'Relative Location This document creates a new registry called 'Relative Location
Parameters'. As defined in [RFC5226], this registry operates under Parameters'. As defined in [RFC5226], this registry operates under
"IETF Consensus" rules. "IETF Review" rules.
The content of this registry includes: The content of this registry includes:
Relative Location Code: Numeric identifier, assigned by IANA. Relative Location Code: Numeric identifier, assigned by IANA.
Brief description: Short description identifying the meaning of the Brief description: Short description identifying the meaning of the
element. element.
Reference to published specification: A stable reference to an RFC Reference to published specification: A stable reference to an RFC
which describes the value in sufficient detail so that which describes the value in sufficient detail so that
interoperability between independent implementations is possible. interoperability between independent implementations is possible.
IANA is requested to not permit values to be assigned into this Values requested to be assigned into this registry MUST NOT conflict
registry which conflict with values assigned in the CAtypes registry with values assigned in the CAtypes registry or vice versa, unless
or to permit values to be assigned into the CAtypes registry which the IANA considerations section for the new value explicitly
conflict with values assigned to to this registry unless the IANA overrides this prohibition and the document defining the value
considerations section for the new value explicitly overrides this describes how conflicting TLV codes will be interpreted by
prohibition, and the document defining the value describes how implementations.
conflicting TLV codes will be interpreted by implementations
The values defined are: The values defined are:
+--------+----------------------------------------+-----------+ +--------+----------------------------------------+-----------+
| RLtype | description | Reference | | RLtype | description | Reference |
+--------+-------+--------------------------------+-----------+ +--------+-------+--------------------------------+-----------+
| 111 | relative location reference | this RFC | | 111 | relative location reference | this RFC |
| 112 | relative location angle | this RFC | | 113 | relative location shape 2D point | this RFC |
| 113 | relative location shape 2D point | this RFC | | 114 | relative location shape 3D point | this RFC |
| 114 | relative location shape 3D point | this RFC | | 115 | relative location shape circular | this RFC |
| 115 | relative location shape circular | this RFC | | 116 | relative location shape spherical | this RFC |
| 116 | relative location shape spherical | this RFC | | 117 | relative location shape elliptical | this RFC |
| 117 | relative location shape elliptical | this RFC | | 118 | relative location shape ellipsoid | this RFC |
| 118 | relative location shape ellipsoid | this RFC | | 119 | relative location shape 2D polygon | this RFC |
| 119 | relative location shape 2D polygon | this RFC | | 120 | relative location shape 3D polygon | this RFC |
| 120 | relative location shape 3D polygon | this RFC | | 121 | relative location shape prism | this RFC |
| 121 | relative location shape prism | this RFC | | 122 | relative location shape arc-band | this RFC |
| 122 | relative location shape arc-band | this RFC | | 123 | relative location dynamic orientation | this RFC |
| 123 | relative location dynamic orientation | this RFC | | 124 | relative location dynamic speed | this RFC |
| 124 | relative location dynamic speed | this RFC | | 125 | relative location dynamic heading | this RFC |
| 125 | relative location dynamic heading | this RFC | | 126 | relative location map type | this RFC |
| 126 | relative location map type | this RFC | | 127 | relative location map URI | this RFC |
| 127 | relative location map URI | this RFC | | 128 | relative location map coordinates | this RFC |
| 128 | relative location map coordinates | this RFC | | 129 | relative location map angle | this RFC |
| 129 | relative location map angle | this RFC | | 130 | relative location map scale | this RFC |
| 130 | relative location map scale | this RFC | +--------+-------+--------------------------------+-----------+
+--------+-------+--------------------------------+-----------+
8.2. URN Sub-Namespace Registration 8.2. URN Sub-Namespace Registration
This document registers a new XML namespace, as per the guidelines in This document registers a new XML namespace, as per the guidelines in
[RFC3688]) that has been registered with IANA. [RFC3688]).
URI: urn:ietf:params:xml:ns:pidf:geopriv10:relative URI: urn:ietf:params:xml:ns:pidf:geopriv10:relative
Registrant Contact: IETF, GEOPRIV working group (geopriv@ietf.org), Registrant Contact:IETF, GEOPRIV working group (geopriv@ietf.org),
Martin Thomson (martin.thomson@andrew.com). Martin Thomson (martin.thomson@skype.net).
XML: XML:
BEGIN BEGIN
<?xml version="1.0"?> <?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head> <head>
<title>GEOPRIV Relative Location</title> <title>GEOPRIV Relative Location</title>
</head> </head>
<body> <body>
<h1>Format for representing relative location in GEOPRIV</h1> <h1>Format for representing relative location</h1>
<h2>urn:ietf:params:xml:ns:pidf:geopriv10:relative</h2> <h2>urn:ietf:params:xml:ns:pidf:geopriv10:relative</h2>
<p>See <a href="http://www.rfc-editor.org/rfc/rfcXXXX.txt"> <p>See <a href="http://www.rfc-editor.org/rfc/rfcXXXX.txt">
RFCXXXX</a>.</p> RFCXXXX</a>.</p>
</body> </body>
</html> </html>
<!-- [[NOTE TO RFC-EDITOR: Please replace all instances of RFCXXXX <!-- [[NOTE TO RFC-EDITOR: Please replace all instances of RFCXXXX
with the number of the published with the number of the published
document and remove this note.]] --> document and remove this note.]] -->
END END
8.3. XML Schema Registration 8.3. XML Schema Registration
This section registers an XML schema as per the procedures in This section registers an XML schema as per the procedures in
[RFC3688]. [RFC3688].
URI: urn:ietf:params:xml:schema:pidf:geopriv10:relativeLocation URI: urn:ietf:params:xml:schema:pidf:geopriv10:relativeLocation
Registrant Contact: IETF, GEOPRIV working group (geopriv@ietf.org), Registrant Contact:IETF, GEOPRIV working group (geopriv@ietf.org),
Martin Thomson (martin.thomson@andrew.com). Martin Thomson (martin.thomson@skype.net).
The XML for this schema can be found as the entirety of Section 7 The XML for this schema is the entirety of Section 6
of this document. of this document.
8.4. CRS public identifier registration 8.4. CRS public identifier registration
This section registers two public identifiers as per the procedures This section registers two public identifiers as per the procedures
in [RFC3688]. in [RFC3688].
URI: urn:ietf:params:xml:ns:pidf:geopriv10:relative:2d URI: urn:ietf:params:xml:ns:pidf:geopriv10:relative:2d
Registrant Contact: IETF, GEOPRIV working group (geopriv@ietf.org),
Martin Thomson (martin.thomson@andrew.com).
XML: Registrant Contact:IETF, GEOPRIV working group (geopriv@ietf.org),
Martin Thomson (martin.thomson@skype.net).
BEGIN XML:
<?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
<title>GEOPRIV Relative Location 2d CRS</title>
</head>
<body>
<h1>Identifier for a 2D CRS in GEOPRIV relative location</h1>
<h2>urn:ietf:params:xml:ns:pidf:geopriv10:relative:2d</h2>
<p>See <a href="http://www.rfc-editor.org/rfc/rfcXXXX.txt">
RFCXXXX</a>.</p>
</body>
</html>
<!-- [[NOTE TO RFC-EDITOR: Please replace all instances of RFCXXXX
with the number of the published document
and remove this note.]] -->
END
URI: urn:ietf:params:xml:ns:pidf:geopriv10:relative:3d BEGIN
<?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
<title>GEOPRIV Relative Location 2d CRS</title>
</head>
<body>
<h1>Identifier for a 2D CRS in relative location</h1>
<h2>urn:ietf:params:xml:ns:pidf:geopriv10:relative:2d</h2>
<p>See <a href="http://www.rfc-editor.org/rfc/rfcXXXX.txt">
RFCXXXX</a>.</p>
</body>
</html>
<!-- [[NOTE TO RFC-EDITOR: Please replace all instances of RFCXXXX
with the number of the published document
and remove this note.]] -->
END
Registrant Contact: IETF, GEOPRIV working group (geopriv@ietf.org), URI: urn:ietf:params:xml:ns:pidf:geopriv10:relative:3d
Martin Thomson (martin.thomson@andrew.com).
XML: Registrant Contact:IETF, GEOPRIV working group (geopriv@ietf.org)
Martin Thomson (martin.thomson@skype.net).
BEGIN XML:
<?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" BEGIN
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <?xml version="1.0"?>
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en"> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
<head> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<title>GEOPRIV Relative Location 3d CRS</title> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
</head> <head>
<body> <title>GEOPRIV Relative Location 3d CRS</title>
<h1>Identifier for a 3D CRS in GEOPRIV relative location</h1> </head>
<h2>urn:ietf:params:xml:ns:pidf:geopriv10:relative:3d</h2> <body>
<p>See <a href="http://www.rfc-editor.org/rfc/rfcXXXX.txt"> <h1>Identifier for a 3D CRS in relative location</h1>
RFCXXXX</a>.</p> <h2>urn:ietf:params:xml:ns:pidf:geopriv10:relative:3d</h2>
</body> <p>See <a href="http://www.rfc-editor.org/rfc/rfcXXXX.txt">
</html> RFCXXXX</a>.</p>
<!-- [[NOTE TO RFC-EDITOR: Please replace all instances of RFCXXXX </body>
with the number of the published </html>
document and remove this note.]] --> <!-- [[NOTE TO RFC-EDITOR: Please replace all instances of RFCXXXX
END with the number of the published
document and remove this note.]] -->
END
8.5. CAtype Registration 8.5. CAtype Registration
This section adds a new entry to the CAtype registry defined by This section adds a new entry to the CAtype registry defined by
[I-D.ietf-geopriv-local-civic]. [RFC6848].
Namespace URI: urn:ietf:params:xml:ns:pidf:geopriv10:relative Namespace URI: urn:ietf:params:xml:ns:pidf:geopriv10:relative
Local Name: REL Local Name: REL
Description: Relative location from a reference point Description: Relative location from a reference point
Contact: The IESG (iesg@ietf.org); the GEOPRIV working group Contact: The IESG (iesg@ietf.org); the GEOPRIV working group
(geopriv@ietf.org). (geopriv@ietf.org).
skipping to change at page 33, line 38 skipping to change at page 31, line 46
9. Acknowledgements 9. Acknowledgements
This is the product of a design team on relative location. Besides This is the product of a design team on relative location. Besides
the authors, this team included: Marc Linsner, James Polk, and James the authors, this team included: Marc Linsner, James Polk, and James
Winterbottom. Winterbottom.
10. References 10. References
10.1. Normative References 10.1. Normative References
[RFC2119] Bradner, S., "Key words for use in [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
RFCs to Indicate Requirement Levels", Requirement Levels", BCP 14, RFC 2119, March 1997.
BCP 14, RFC 2119, March 1997.
[RFC4119] Peterson, J., "A Presence-based [RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object
GEOPRIV Location Object Format", Format", RFC 4119, December 2005.
RFC 4119, December 2005.
[RFC4776] Schulzrinne, H., "Dynamic Host [RFC4776] Schulzrinne, H., "Dynamic Host Configuration Protocol
Configuration Protocol (DHCPv4 and (DHCPv4 and DHCPv6) Option for Civic Addresses
DHCPv6) Option for Civic Addresses Configuration Information", RFC 4776, November 2006.
Configuration Information", RFC 4776,
November 2006.
[RFC5139] Thomson, M. and J. Winterbottom, [RFC5139] Thomson, M. and J. Winterbottom, "Revised Civic Location
"Revised Civic Location Format for Format for Presence Information Data Format Location
Presence Information Data Format Object (PIDF-LO)", RFC 5139, February 2008.
Location Object (PIDF-LO)", RFC 5139,
February 2008.
[RFC5226] Narten, T. and H. Alvestrand, [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
"Guidelines for Writing an IANA IANA Considerations Section in RFCs", BCP 26, RFC 5226,
Considerations Section in RFCs", May 2008.
BCP 26, RFC 5226, May 2008.
[RFC5491] Winterbottom, J., Thomson, M., and H. [RFC5491] Winterbottom, J., Thomson, M., and H. Tschofenig, "GEOPRIV
Tschofenig, "GEOPRIV Presence Presence Information Data Format Location Object (PIDF-LO)
Information Data Format Location Usage Clarification, Considerations, and Recommendations",
Object (PIDF-LO) Usage Clarification, RFC 5491, March 2009.
Considerations, and Recommendations",
RFC 5491, March 2009.
[RFC5962] Schulzrinne, H., Singh, V., [RFC5962] Schulzrinne, H., Singh, V., Tschofenig, H., and M.
Tschofenig, H., and M. Thomson, Thomson, "Dynamic Extensions to the Presence Information
"Dynamic Extensions to the Presence Data Format Location Object (PIDF-LO)", RFC 5962,
Information Data Format Location September 2010.
Object (PIDF-LO)", RFC 5962,
September 2010.
[RFC6225] Polk, J., Linsner, M., Thomson, M., [RFC6225] Polk, J., Linsner, M., Thomson, M., and B. Aboba, "Dynamic
and B. Aboba, "Dynamic Host Host Configuration Protocol Options for Coordinate-Based
Configuration Protocol Options for Location Configuration Information", RFC 6225, July 2011.
Coordinate-Based Location
Configuration Information", RFC 6225,
July 2011.
[I-D.ietf-geopriv-local-civic] Winterbottom, J., Thomson, M., [RFC6848] Winterbottom, J., Thomson, M., Barnes, R., Rosen, B., and
Barnes, R., Rosen, B., and R. George, R. George, "Specifying Civic Address Extensions in the
"Specifying Civic Address Extensions Presence Information Data Format Location Object (PIDF-
in PIDF-LO", LO)", RFC 6848, January 2013.
draft-ietf-geopriv-local-civic-03
(work in progress), February 2012.
[OGC.GML-3.1.1] Cox, S., Daisey, P., Lake, R., [OGC.GML-3.1.1]
Portele, C., and A. Whiteside, Cox, S., Daisey, P., Lake, R., Portele, C., and A.
"Geographic information - Geography Whiteside, "Geographic information - Geography Markup
Markup Language (GML)", OpenGIS 03- Language (GML)", OpenGIS 03-105r1, April 2004, <http://
105r1, April 2004, <http:// portal.opengeospatial.org/files/?artifact_id=4700>.
portal.opengeospatial.org/files/
?artifact_id=4700>.
[OGC.GeoShape] Thomson, M. and C. Reed, "GML 3.1.1 [OGC.GeoShape]
PIDF-LO Shape Application Schema for Thomson, M. and C. Reed, "GML 3.1.1 PIDF-LO Shape
use by the Internet Engineering Task Application Schema for use by the Internet Engineering
Force (IETF)", OGC Best Practice 06- Task Force (IETF)", OGC Best Practice 06-142r1, Version:
142r1, Version: 1.0, April 2007. 1.0, April 2007.
[IEEE.754] IEEE, "IEEE Standard for Binary [IEEE.754]
Floating-Point Arithmetic", IEEE IEEE, "IEEE Standard for Binary Floating-Point
Standard 754-1985, January 2003. Arithmetic", IEEE Standard 754-1985, January 2003.
[Clinger1990] Clinger, W., "How to Read Floating [Clinger1990]
Point Numbers Accurately", Clinger, W., "How to Read Floating Point Numbers
Proceedings of Conference on Accurately", Proceedings of Conference on Programming
Programming Language Design and Language Design and Implementation pp. 92-101, 1990, <ftp:
Implementation pp. 92-101, 1990, <ftp //ftp.ccs.neu.edu/pub/people/will/howtoread.ps>.
://ftp.ccs.neu.edu/pub/people/will/
howtoread.ps>.
10.2. Informative References 10.2. Informative References
[RFC3688] Mealling, M., "The IETF XML [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
Registry", BCP 81, RFC 3688, January 2004.
January 2004.
[RFC3986] Berners-Lee, T., Fielding, R., and L. [WGS84] US National Imagery and Mapping Agency , ""Department of
Masinter, "Uniform Resource Defense (DoD) World Geodetic System 1984 (WGS 84), Third
Identifier (URI): Generic Syntax", Edition"", NIMA TR8350.2, January 2000.
STD 66, RFC 3986, January 2005.
Authors' Addresses Authors' Addresses
Martin Thomson Martin Thomson
Microsoft Microsoft
3210 Porter Drive 3210 Porter Drive
Palo Alto, CA 94304 Palo Alto, CA 94304
US US
Phone: +1 650-353-1925 Phone: +1 650-353-1925
 End of changes. 77 change blocks. 
484 lines changed or deleted 462 lines changed or added

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