One document matched: draft-ietf-geopriv-relative-location-02.xml
<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!ENTITY RFC2119 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
<!ENTITY RFC3688 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3688.xml">
<!ENTITY RFC3986 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3986.xml">
<!ENTITY RFC4119 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4119.xml">
<!ENTITY RFC4776 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4776.xml">
<!ENTITY RFC5139 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5139.xml">
<!ENTITY RFC5226 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5226.xml">
<!ENTITY RFC5491 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5491.xml">
<!ENTITY RFC5962 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5962.xml">
<!ENTITY RFC6225 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.6225.xml">
<!ENTITY draft-ietf-geopriv-local-civic SYSTEM "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.ietf-geopriv-local-civic.xml">
]>
<?rfc rfcedstyle="yes"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="no"?>
<?rfc iprnotified="yes"?>
<?rfc strict="yes"?>
<?rfc toc="yes"?>
<?rfc tocindent="yes"?>
<rfc category="std" ipr="trust200902">
<front>
<title abbrev="Relative Location">
Relative Location Representation
</title>
<author initials="M." surname="Thomson" fullname="Martin Thomson">
<organization>Andrew Corporation</organization>
<address>
<postal>
<street>Andrew Building (39)</street>
<street>Wollongong University Campus</street>
<street>Northfields Avenue</street>
<city>Wollongong</city>
<region>NSW</region>
<code>2522</code>
<country>AU</country>
</postal>
<email>martin.thomson@andrew.com</email>
</address>
</author>
<author initials="B." surname="Rosen" fullname="Brian Rosen">
<organization>Neustar</organization>
<address>
<postal>
<street>470 Conrad Dr</street>
<city>Mars</city>
<region>PA</region>
<code>16046</code>
<country>US</country>
</postal>
<email>br@brianrosen.net</email>
</address>
</author>
<author initials="D." surname="Stanley" fullname="Dorothy Stanley">
<organization>Aruba Networks</organization>
<address>
<postal>
<street>1322 Crossman Ave</street>
<city>Sunnyvale</city>
<region>CA</region>
<code>94089</code>
<country>US</country>
</postal>
<email>dstanley@arubanetworks.com</email>
</address>
</author>
<author initials="G." surname="Bajko" fullname="Gabor Bajko">
<organization>Nokia</organization>
<address>
<postal>
<street>323 Fairchild Drive</street>
<city>Mountain View</city>
<region>CA</region>
<code>94043</code>
<country>US</country>
</postal>
<email>gabor.bajko@nokia.com</email>
</address>
</author>
<author initials="A." surname="Thomson" fullname="Allan Thomson">
<organization>Cisco Systems, Inc.</organization>
<address>
<postal>
<street>170 West Tasman Drive</street>
<city>San Jose</city>
<region>CA</region>
<code>95134</code>
<country>US</country>
</postal>
<email>althomso@cisco.com</email>
</address>
</author>
<date year="2011"/>
<area>RAI</area>
<workgroup>GEOPRIV</workgroup>
<keyword>Internet-Draft</keyword>
<keyword>Relative</keyword>
<keyword>location</keyword>
<abstract>
<t>This document defines an extension to PIDF-LO (RFC4119) for the expression of location information that is defined relative to a reference point. The reference point may be expressed as a geodetic or civic location, and the relative offset may be one of several shapes. Optionally, a reference to a secondary document (such as a map image) can be included, along with the relationship of the map coordinate system to the reference/offset coordinate system to allow display of the map with the reference point and the relative offset. Also included in this document is a Type/Length/Value (TLV) representation of the relative location for use in other protocols that use TLVs.
</t>
</abstract>
</front>
<middle>
<section title="Introduction">
<t>This document describes a format for the expression of relative location information.
</t>
<t>
A relative location is formed of a reference location, plus a relative offset from that reference location. The reference location can be represented in either civic or geodetic form. The reference location can also have dynamic components such as velocity. The relative offset is specified in meters using a Cartesian coordinate system.
</t><t>
In addition to the relative location, an optional URI can be provided to a document that contains a map, floorplan or illustration. Applications could use this information to display the relative location. Additional fields allow the map to be oriented and scaled correctly.
</t>
<t>Two formats are included: an XML form that is intended for use in PIDF-LO <xref target="RFC4119"/> and a TLV format for use in other protocols such as those that already convey binary representation of location information defined in <xref target="RFC4776"/>.
</t>
</section>
<section anchor="conventions" title="Conventions used in this document">
<t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in <xref target="RFC2119"/>.
</t>
</section>
<section title="Overview">
<t>This document describes an extension to PIDF-LO <xref target="RFC4119"/> as updated by <xref target="RFC5139"/> and <xref target="RFC5491"/>,
to allow the expression of a location as an offset relative to a reference.</t>
<t>This extension effectively allows the creator of a location object to
include two location values plus an offset. The "baseline" location
that is given outside of the <relative-location> element is what will be
visible to a client that does not understand that extension (i.e., one
that ignores the <relative-location> element). A client that does understand
this extension will interpret the location within the relative element
as a refinement of the baseline location, which gives the reference
location for the relative offset.
</t><t>
Creators of location objects with relative location thus have a choice
of how much information to put into the "baseline" location and how
much to put into the "reference" location. For example, all location
information could be put inside the <relative-location> element, so that
clients that do not understand relative location would receive no
location information at all. Alternatively, the baseline location
value could be precise enough to specify a building that contains the
relative location, and the reference location could specify a point
within the building from which the offset is measured.
</t><t>
The baseline location SHOULD be general
enough to describe both the reference location and the relative
location (reference plus offset). In particular, while it is possible
to put all location information into the "reference" location (leaving
an universally broad "baseline"), location objects SHOULD NOT have all
location information in the baseline location. Doing this would
cause clients that do not understand relative location to incorrectly
interpret the baseline location (i.e., the reference point) as the
actual, precise location of the client.
</t><t>Both the baseline and the reference location are defined either as a <xref target="OGC.GeoShape">geodetic location</xref> or a <xref target="RFC4776">civic address</xref>.
If the baseline location was expressed as a geodetic location, the reference MUST be geodetic. If the baseline location was expressed as a civic address, the reference MUST
be a civic.
</t><t>
Baseline and reference locations MAY also include dynamic location information <xref target="RFC5962"/>.
</t><t>
The relative location can be expressed using a point (2- or 3-dimensional), or a shape that includes uncertainty: circle, sphere,
ellipse, ellipsoid, polygon, prism or arc-band. Descriptions of these shapes can be found in <xref target="RFC5491"/>.
</t>
<t>Optionally, a reference to a 'map' document can be provided. The 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 URI points to is described as a MIME media type. Metadata in the relative location can include the location of the reference point in 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 to be useable by the application receiving the PIDF with the relative location to locate the reference point in the map. This document does not describe any mechanisms for displaying or manipulating the document other than providing the reference location, orientation and scale.
</t>
<t>As an example, consider a relative location expressed as a point, relative to a civic location:</t>
<figure><artwork><![CDATA[
<presence xmlns="urn:ietf:params:xml:ns:pidf"
xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model"
xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10"
xmlns:ca="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr"
xmlns:rel="urn:ietf:params:xml:ns:pidf:geopriv10:relative"
xmlns:gml="http://www.opengis.net/gml"
xmlns:gs="http://www.opengis.net/pidflo/1.0"
entity="pres:relative@example.com">
<dm:device id="relative1">
<gp:geopriv>
<gp:location-info>
<ca:civicAddress xml:lang="en-AU">
<ca:country>AU</ca:country>
<ca:A1>NSW</ca:A1>
<ca:A3>Wollongong</ca:A3>
<ca:A4>North Wollongong</ca:A4>
<ca:RD>Flinders</ca:RD>
<ca:STS>Street</ca:STS>
<ca:HNO>123</ca:HNO>
</ca:civicAddress>
<rel:relative-location>
<rel:reference>
<ca:civicAddress xml:lang="en-AU">
<ca:INT N="Door" R="A">Front</ca:INT>
</ca:civicAddress>
</rel:reference>
<rel:offset>
<gml:Point xmlns:gml="http://www.opengis.net/gml"
srsName="urn:ietf:params:geopriv:relative:2d">
<gml:pos>100 50</gml:pos>
</gml:Point>
</rel:offset>
</rel:relative-location>
</gp:location-info>
<gp:usage-rules/>
<gp:method>GPS</gp:method>
<rel:map>
<rel:url type="image/png">
http://example.com/location/map.png
</rel:url>
<rel:offset>20. 120.</rel:offset>
<rel:orientation>29.</rel:orientation>
<rel:scale>20. -20.</rel:scale>
</rel:map>
</gp:geopriv>
<dm:deviceID>mac:1234567890ab</dm:deviceID>
<dm:timestamp>2007-06-22T20:57:29Z</dm:timestamp>
</dm:device>
</presence>
]]></artwork></figure>
</section>
<section anchor="tlv-relative" title="Relative Location">
<t> Relative location is a shape (point, circle, ellipse…). The shape is defined with a CRS that has a datum defined as the reference (which appears as a civic address or geodetic location in the tuple), and the shape coordinates as meter offsets North/East of the datum measured in meters (with an optional Z offset relative to datum altitude). An optional angle allows the reference CRS be to rotated with respect to North.
</t>
<section title="Relative Coordinate System">
<t>
The relative coordinate reference system uses a coordinate system with two or three axes.
</t><t>
The baseline and reference locations are used to define a relative datum. The reference location defines the origin of the coordinate system. The centroid of the reference location is used when the reference location contains any uncertainty.
</t><t>
The axes in this coordinate system are originally oriented based on the directions of East, North and Up from the reference location: the first (x) axis increases to the East, the second (y) axis points North, and the optional third (z) axis points Up. All axes of the coordinate system use meters as a basic unit.
</t><t>
Any coordinates in the relative shapes use the described Cartesian coordinate system. In the XML form, this uses a URN of “urn:ietf:params:geopriv:relative:2d” for two-dimensional shapes and “urn:ietf:params:geopriv:relative:3d” for three-dimensional shapes. The binary form uses different shape type identifiers for 2D and 3D shapes.
</t><t>
Dynamic location information <xref target="RFC5962"/> in the baseline or reference location alters relative coordinate system. The resulting Cartesian coordinate system axes are rotated so that the ‘y’ axis is oriented along the direction described by the <orientation> element. The coordinate system also moves as described by the <speed> and <heading> elements.</t>
</section>
<section title="Placement of XML Elements">
<t>The baseline of the reference location is represented as <location-info> like a normal PIDF-LO. Relative location adds a new <relative-location> element to <location-info>
Within <relative-location> <reference> and <offset> elements are described. Within <offset> are shape elements described below. This document extends PIDF-LO as described in <xref target="I-D.ietf-geopriv-local-civic"/>.
</t></section>
<section anchor="tlv-top" title="Binary Format">
<t>
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 location.
</t>
<t>A type-length-value encoding is used.
</t>
<figure anchor="tlv-format" title="TLV-tuple format">
<artwork><![CDATA[
+------+------+------+------+------+------+------+
| Type |Length| Value ...
+------+------+------+------+------+------+
| X | N | Value label ...
+------+------+------+------+------+------+------+
]]></artwork>
</figure>
<t>Type field (X) is defined as a single byte. The type codes used are registered an IANA managed 'RLtypes' registry defined by this document, and restricted to not include the values defined by the CAtypes registry. This restriction permits a location reference and offset to be coded with unique TLVs.
</t>
<t>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 length field describes the number of bytes in the Value. Length does not count the bytes used for the Type or Length. </t>
<t> The Value field is defined separately for each type.
</t><t>
Each element of the relative location has a unique TLV
assignment. A relative location encoded in TLV would have the
baseline location TLVs, a reference location TLV
which contains within it the reference refinement TLVs. The
reference TLVs are followed by the relative offset, and optional map
TLDs described in this document.
</t>
</section>
<section title="Distances and Angles">
<t> All distance measures used in shapes are expressed in meters.
</t><t>
All orientation angles used in shapes are expressed in degrees. Orientation angles are measured from WGS84 Northing to Easting with zero at Northing. Orientation angles in the relative coordinate system start from the second coordinate axis (y or Northing) and increase toward the first axis (x or Easting).</t>
</section><section title="Value Encoding">
<t>The binary form uses single-precision floating point values [IEEE754] to represent coordinates, distance and angle measures. Single precision values are 32-bit values with a sign bit, 8 exponent bits and 23 fractional bits.
</t><t>
Binary-encoded coordinate values are considered to be a single value
without uncertainty. When encoding a value that cannot be exactly
represented, the best approximation is chosen according to
<xref target="Clinger1990"/>.</t>
</section><section title="Relative Location Restrictions">
<t>More than one relative shape MUST NOT be included in either a PIDF-LO or TLV encoding of location for a given reference point.
</t><t>Any error in the reference point transfers to the location described by the relative location. Any errors arising from an implementation not supporting or understanding elements of the reference point directly increases the error (or uncertainty) in the resulting location.
</t>
</section><section title="Baseline TLVs">
<t>
Baseline locations is described using the formats defined in <xref target="RFC4776"/> or <xref target="RFC6225"/>.
</t></section>
<section anchor="reference" title="Reference TLV">
<t>When a reference is encoded in binary form, the baseline
and reference locations are combined in a reference TLV. This TLV contains civic address
TLVs (if the baseline was a civic) or geo TLVs (if the
baseline was a geo).
</t>
<figure title="Reference TLV">
<artwork><![CDATA[
+------+------+------+------+------+------+
| 111 |Length| Reference TLVs |
+------+------+------+------+------+------+
]]></artwork>
</figure>
</section>
<section title="Shapes">
<t>Shape data is used to represent regions of uncertainty for the reference and relative locations.
Shape data in the reference location uses a [WGS84] CRS. Shape data in the relative location uses a relative CRS.
</t><t>
The XML form for shapes uses Geography Markup Language (GML) <xref target="OGC.GML-3.1.1"/>,
consistent with the rules in <xref target="RFC5491"/>. Reference locations use the CRS URNs specified in <xref target="RFC5491"/>; relative locations 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.
</t><t>
The binary form of each shape uses a different shape types for 2d and 3d shapes.
</t><t>
Nine shape type codes are defined.
</t>
<section anchor="geo-point" title="Point">
<t>A point "shape" describes a single point with unknown uncertainty. It consists of a single set of coordinates.
</t>
<t>In a two-dimensional CRS, the coordinate includes two values; in a three-dimensional CRS, the coordinate includes three values.
</t>
<section title="XML encoding">
<figure title="GML Point Template">
<preamble>A point is represented in GML using the following template:</preamble>
<artwork><![CDATA[
<gml:Point xmlns:gml="http://www.opengis.net/gml"
srsName="$CRS-URN$">
<gml:pos>$Coordinate-1 $Coordinate-2$ $Coordinate-3$</gml:pos>
</gml:Point>
]]></artwork>
</figure>
<t>Where <spanx style="verb">$CRS-URN$</spanx> is replaced by a urn:ietf:params:geopriv:relative:2d or urn:ietf:params:geopriv:relative:3d and <spanx style="verb">$Coordinate-3$</spanx> is omitted if the CRS is two-dimensional.</t>
</section><section title="TLV encoding">
<t>The point shape is introduced by a TLV of 113 for a 2D point and 114 for a 3D point.
</t>
<figure title="Point Encoding">
<artwork><![CDATA[
+------+------+
| 113/4|Length|
+------+------+------+------+
| Coordinate-1 |
+------+------+------+------+
| Coordinate-2 |
+------+------+------+------+
| (3D-only) Coordinate-3 |
+------+------+------+------+
]]></artwork>
</figure>
</section></section>
<section anchor="geo-circle" title="Circle or Sphere Shape">
<t>A circle or sphere describes a single point with a single uncertainty value in meters.
</t>
<t>In a two-dimensional CRS, the coordinate includes two values and the resulting shape forms a circle. In a three-dimensional CRS, the coordinate includes three values and the resulting shape forms a sphere. </t>
<section title="XML encoding">
<figure title="GML Circle Template">
<preamble>A circle is represented in and converted from GML using the following template:</preamble>
<artwork><![CDATA[
<gs:Circle xmlns:gml="http://www.opengis.net/gml"
xmlns:gs="http://www.opengis.net/pidflo/1.0"
srsName="urn:ietf:params:geopriv:relative:2d">
<gml:pos>$Coordinate-1 $Coordinate-2$</gml:pos>
<gs:radius uom="urn:ogc:def:uom:EPSG::9001">
$Radius$
</gs:radius>
</gs:Circle>
]]></artwork>
</figure>
<figure title="GML Sphere Template">
<preamble>A sphere is represented in and converted from GML using the following template:</preamble>
<artwork><![CDATA[
<gs:Sphere xmlns:gml="http://www.opengis.net/gml"
xmlns:gml="http://www.opengis.net/pidflo/1.0"
srsName="urn:ietf:params:geopriv:relative:3d">
<gml:pos>$Coordinate-1 $Coordinate-2$ $Coordinate-3$</gml:pos>
<gs:radius uom="urn:ogc:def:uom:EPSG::9001">
$Radius$
</gs:radius>
</gs:Sphere>
]]></artwork>
</figure>
</section><section title="TLV encoding">
<t>A circular shape is introduced by a type code of 115. A spherical shape is introduced by a type code of 116.</t>
<figure title="Circle or Sphere Encoding">
<artwork><![CDATA[
+------+------+
| 115/6|Length|
+------+------+------+------+
| Coordinate-1 |
+------+------+------+------+
| Coordinate-2 |
+------+------+------+------+
| (3D-only) Coordinate-3 |
+------+------+------+------+
| Radius |
+------+------+------+------+
]]></artwork>
</figure>
</section></section>
<section anchor="geo-ellipse" title="Ellipse or Ellipsoid Shape">
<t>A ellipse or ellipsoid describes a point with an elliptical or ellipsoidal uncertainty region.
</t>
<t>In a two-dimensional CRS, the coordinate includes two values, plus a semi-major axis, a semi-minor axis, a semi-major axis orientation (clockwise from North). In a three-dimensional CRS, the coordinate includes three values and in addition to the two-dimensional values, an altitude uncertainty (semi-vertical) is added.
</t>
<section title="XML encoding">
<figure title="GML Ellipse Template">
<preamble>An ellipse is represented in and converted from GML using the following template:</preamble>
<artwork><![CDATA[
<gs:Ellipse xmlns:gml="http://www.opengis.net/gml"
xmlns:gs="http://www.opengis.net/pidflo/1.0"
srsName="urn:ietf:params:geopriv:relative:2d">
<gml:pos>$Coordinate-1 $Coordinate-2$</gml:pos>
<gs:semiMajorAxis uom="urn:ogc:def:uom:EPSG::9001">
$Semi-Major$
</gs:semiMajorAxis>
<gs:semiMinorAxis uom="urn:ogc:def:uom:EPSG::9001">
$Semi-Minor$
</gs:semiMinorAxis>
<gs:orientation uom="urn:ogc:def:uom:EPSG::9102">
$Orientation$
</gs:orientation>
</gs:Ellipse>
]]></artwork>
</figure>
<figure title="GML Ellipsoid Template">
<preamble>An ellipsoid is represented in and converted from GML using the following template:</preamble>
<artwork><![CDATA[
<gs:Ellipsoid xmlns:gml="http://www.opengis.net/gml"
xmlns:gs="http://www.opengis.net/pidflo/1.0"
srsName="urn:ietf:params:geopriv:relative:3d">
<gml:pos>$Coordinate-1 $Coordinate-2$ $Coordinate-3$</gml:pos>
<gs:semiMajorAxis uom="urn:ogc:def:uom:EPSG::9001">
$Semi-Major$
</gs:semiMajorAxis>
<gs:semiMinorAxis uom="urn:ogc:def:uom:EPSG::9001">
$Semi-Minor$
</gs:semiMinorAxis>
<gs:verticalAxis uom="urn:ogc:def:uom:EPSG::9001">
$Semi-Vertical$
</gs:verticalAxis>
<gs:orientation uom="urn:ogc:def:uom:EPSG::9102">
$Orientation$
</gs:orientation>
</gs:Ellipsoid>
]]></artwork>
</figure>
</section><section title="TLV encoding">
<t>An ellipse is introduced by a type code of 117 and an ellipsoid is introduced by a type code of 118.</t>
<figure title="Ellipse or Ellipsoid Encoding">
<artwork><![CDATA[
+------+------+
| 117/8|Length|
+------+------+------+------+
| Coordinate-1 |
+------+------+------+------+
| Coordinate-2 |
+------+------+------+------+
| (3D-only) Coordinate-3 |
+------+------+------+------+------+------+------+------+
| Semi-Major Axis | Semi-Minor Axis |
+------+------+------+------+------+------+------+------+
| Orientation | (3D) Semi-Vertical Axis |
+------+------+------+------+------+------+------+------+
]]></artwork>
</figure>
</section></section>
<section anchor="geo-polygon" title="Polygon or Prism Shape">
<t>A polygon or prism include a number of points that describe the outer boundary of an uncertainty region. A prism also includes an altitude for each point and prism height.
</t>
<t>At least 3 points MUST be included in a polygon. In order to interoperate with existing systems, an encoding SHOULD include 15 or fewer points, unless the recipient is known to support larger numbers.
</t>
<section title="XML Encoding">
<figure title="GML Polygon Template">
<preamble>A polygon is represented in and converted from GML using the following template:</preamble>
<artwork><![CDATA[
<gml:Polygon xmlns:gml="http://www.opengis.net/gml"
srsName="urn:ietf:params:geopriv:relative:2d">
<gml:exterior>
<gml:LinearRing>
<gml:posList>
$Coordinate1-1$ $Coordinate1-2$
$Coordinate2-1$ $Coordinate2-2$
$Coordinate3-1$ ...
...
$CoordinateN-1$ $CoordinateN-2$
$Coordinate1-1$ $Coordinate1-2$
</gml:posList>
</gml:LinearRing>
</gml:exterior>
</gml:Polygon>
]]></artwork>
</figure>
<t>Alternatively, a series of <spanx style="verb">pos</spanx> elements can be used in place of the single <spanx style="verb">posList</spanx>. Each <spanx style="verb">pos</spanx> element contains two or three coordinate values.
</t>
<t>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 provided.
</t>
<t>A GML polygon that includes altitude cannot be represented completely in binary. When converting to the binary representation, a two dimensional CRS is used and altitude is removed from each coordinate.
</t>
<figure title="GML Prism Template">
<preamble>A prism is represented in and converted from GML using the following template:</preamble>
<artwork><![CDATA[
<gs:Prism xmlns:gml="http://www.opengis.net/gml"
xmlns:gs="http://www.opengis.net/pidflo/1.0"
srsName="urn:ietf:params:geopriv:relative:3d">
<gs:base>
<gml:Polygon>
<gml:exterior>
<gml:LinearRing>
<gml:posList>
$Coordinate1-1$ $Coordinate1-2$ $Coordinate1-3$
$Coordinate2-1$ $Coordinate2-2$ $Coordinate2-3$
$Coordinate2-1$ ... ...
...
$CoordinateN-1$ $CoordinateN-2$ $CoordinateN-3$
$Coordinate1-1$ $Coordinate1-2$ $Coordinate1-3$
</gml:posList>
</gml:LinearRing>
</gml:exterior>
</gml:Polygon>
</gs:base>
<gs:height uom="urn:ogc:def:uom:EPSG::9001">
$Height$
</gs:height>
</gs:Prism>
]]></artwork>
</figure>
<t>Alternatively, a series of <spanx style="verb">pos</spanx> elements can be used in place of the single <spanx style="verb">posList</spanx>. Each <spanx style="verb">pos</spanx> element contains three coordinate values.
</t>
</section><section title="TLV Encoding">
<t> 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 121.</t>
<figure title="Polygon or Prism Encoding">
<artwork><![CDATA[
+------+------+
|119-21|Length|
+------+------+------+------+------+------+
| Count | (3D-only) Height |
+------+------+------+------+------+------+
| Coordinate1-1 |
+------+------+------+------+
| Coordinate1-2 |
+------+------+------+------+
| (3D-only) Coordinate1-3 |
+------+------+------+------+
| Coordinate2-1 |
+------+------+------+------+
...
+------+------+------+------+
| CoordinateN-1 |
+------+------+------+------+
| CoordinateN-2 |
+------+------+------+------+
| (3D-only) CoordinateN-3 |
+------+------+------+------+
]]></artwork>
</figure>
<t> 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
representation. The duplicated point is removed from the binary form. </t>
</section></section>
<section anchor="geo-arc-band" title="Arc-Band Shape">
<t>A arc-band describes a region constrained by a range of angles and distances from a predetermined point. This shape can only be provided for a two-dimensional CRS.
</t>
<t>Distance and angular measures are defined in meters and degrees respectively. Both are encoded as single precision floating point values.
</t>
<section title="XML encoding">
<figure title="GML Arc-Band Template">
<preamble>An arc-band is represented in and converted from GML using the following template:</preamble>
<artwork><![CDATA[
<gs:ArcBand xmlns:gml="http://www.opengis.net/gml"
xmlns:gs="http://www.opengis.net/pidflo/1.0"
srsName="urn:ietf:params:geopriv:relative:2d">
<gml:pos>$Coordinate-1 $Coordinate-2$</gml:pos>
<gs:innerRadius uom="urn:ogc:def:uom:EPSG::9001">
$Inner-Radius$
</gs:innerRadius>
<gs:outerRadius uom="urn:ogc:def:uom:EPSG::9001">
$Inner-Radius$
</gs:outerRadius>
<gs:startAngle uom="urn:ogc:def:uom:EPSG::9102">
$Start-Angle$
</gs:startAngle>
<gs:openingAngle uom="urn:ogc:def:uom:EPSG::9102">
$Opening-Angle$
</gs:openingAngle>
</gs:Ellipsoid>
]]></artwork>
</figure>
</section><section title="TLV Encoding">
<t>An arc-band is introduced by a type code of 122.</t>
<figure title="Arc-Band Encoding">
<artwork><![CDATA[
+------+------+
| 122 |Length|
+------+------+------+------+
| Coordinate |
+------+------+------+------+
| Coordinate |
+------+------+------+------+------+------+------+------+
| Inner Radius | Outer Radius |
+------+------+------+------+------+------+------+------+
| Start Angle | Opening Angle |
+------+------+------+------+------+------+------+------+
]]></artwork>
</figure>
</section></section>
</section>
<section title="Dynamic Location TLVs">
<t>Dynamic location elements use the definitions in <xref target="RFC5962"/>.</t>
<section title="Orientation">
<t>The orientation of the target is described using one or two angles.</t>
<figure title="Dynamic Orientation TLVs">
<artwork><![CDATA[
+------+------+
| 123 |Length|
+------+------+------+------+
| Angle |
+------+------+------+------+
| (Optional) Angle |
+------+------+------+------+
]]></artwork>
</figure>
</section>
<section title="Speed">
<t>The speed of the target is a scalar value in meters per second.</t>
<figure title="Dynamic Speed TLVs">
<artwork><![CDATA[
+------+------+
| 124 |Length|
+------+------+------+------+
| Length |
+------+------+------+------+
| Speed |
+------+------+------+------+
]]></artwork>
</figure>
</section><section title="Heading">
<t>The heading, or direction of travel, is described using one or two angles.</t>
<figure title="Dynamic Heading TLVs">
<artwork><![CDATA[
+------+------+
| 125 |Length|
+------+------+------+------+
| Angle |
+------+------+------+------+
| (Optional) Angle |
+------+------+------+------+
]]></artwork>
</figure>
</section></section>
<section anchor="map" title="Secondary Map Metadata">
<t>The optional "map" URL can be used to provide a user of relative location with a visual reference for the location information. This document does not describe how the recipient uses the map nor how it locates the reference or offset within the map. Maps can be simple images, vector files, 2-D or 3-D geospatial databases, or any other form of representation understood by both the sender and recipient.
</t>
<section anchor="map-url" title="Map URL"><t>
In XML, the map is a <map> element defined within <relative-location> and contains the URL. The URL is encoded as a UTF-8 encoded string. An <spanx style="verb">http:</spanx> or <spanx style="verb">https:</spanx> URL MUST be used unless the entity creating the PIDF-LO is able to ensure that authorized recipients of this data are able to use other URI schemes. A "type" attribute MUST be present and specifies the kind of map the URL points to. Map types are specified as mime media types as recorded in the IANA Media Types registry. For example <map type="image/png">https://www.example.com/floorplans/123South/floor-2</map>. In binary, the map type is a separate TLV from the map URL:
</t>
<figure title="Map URL TLVs">
<artwork><![CDATA[
+------+------+------+------+------+-- --+------+
| 126 |Length| Map Media Type ...
+------+------+------+------+------+-- --+------+
| 127 |Length| Map Image URL ...
+------+------+------+------+------+-- --+------+
]]></artwork>
</figure>
</section>
<section anchor="map-crs" title="Map Coordinate Reference System">
<t>The CRS used by the map depends on the type of map. For example, a map described by a 3-D geometric model of the building may contain a complete CRS description in it. For some kinds of maps, typically described as images, the CRS used within the map must define the following:
<list style='symbols'>
<t>The CRS origin</t>
<t>The CRS axes used and their orientation</t>
<t>The unit of measure used</t></list></t>
<t>This document provides elements that allow for a mapping between the local coordinate reference system used for the relative location and the coordinate reference system used for the map where they are not the same.
</t>
<section anchor="map-ref" title="Map Reference Point Offset">
<t>This optional element identifies the coordinates of the reference point as it appears in the map. This value is measured in a map-type dependent manner, using the coordinate system of the map.
</t>
<t>For image maps, coordinates start from the upper left corner and coordinates are first counted by column with positive values to the right; then rows are counted with positive values toward the bottom 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 in the image coordinate space.
</t>
<t>The <offset> element contains 2 (or 3) coordinates similar to a GML <spanx style="verb">pos</spanx>, For example:</t>
<figure title="Map Reference Point Example XML">
<artwork><![CDATA[
<offset> 2670.0 1124.0 1022.0</offset>
]]></artwork></figure>
<figure title="Map Reference Point Coordinates TLV">
<artwork><![CDATA[
+------+------+
| 128 |Length|
+------+------+------+------+
| Coordinate-1 |
+------+------+------+------+
| Coordinate-2 |
+------+------+------+------+
| (3D-only) Coordinate-3 |
+------+------+------+------+
]]></artwork>
</figure>
<t>If omitted, a value containing all zeros is assumed. If the coordinates provided contain fewer values than are needed, the first value from the set is applied in place of any missing values.
</t>
</section>
<section anchor="map-orientation" title="Map Orientation">
<t> The map orientation includes the orientation of the map direction
in relation to the Earth. Map orientation is expressed
relative to the orientation of the relative coordinate system. This
means that map orientation with respect to WGS84 North is the sum of
th orientation field, plus any orientation included in a dynamic portion of the reference location. Both values default to zero if no value
is specified.
</t>
<t>This type uses a single precision floating point value of degrees relative to North.
</t>
<t>
In XML, the <orientation> element contains a single floating point value, example <orientation>67.00</orientation>. In TLV form:
</t>
<figure title="Map Orientation TLV">
<artwork><![CDATA[
+------+------+------+------+------+------+
| 129 |Length| Angle |
+------+------+------+------+------+------+
]]></artwork>
</figure>
</section>
<section anchor="map-scale" title="Map Scale">
<t>The optional map scale describes the relationship between the units of measure used in the map, relative to the meters unit used in the relative coordinate system.
</t>
<t>This type uses a sequence of <xref target="IEEE.754">IEEE 754</xref> single precision floating point values to represent scale as a sequence of numeric values. The units of these values is dependent on the type of map, and could
for example be pixels per meter for an image.
</t>
<t>A scaling factor is provided for each axis in the coordinate system. For a two-dimensional coordinate system, two values are included to allow for different scaling along the x and y axes independently. For a three-dimensional coordinate system, three values are specified for the x, y and z axes.
</t>
<t>Alternatively, a single scaling value MAY be used to apply the same scaling factor to all coordinate components.
</t>
<t>Images that use a rows/columns coordinate system often use a left-handed coordinate system. A negative value for the y/rows-axis scaling value can be used to
account for any change in direction between the y-axis used in the relative coordinate system and the rows
axis of the image coordinate system.
</t>
<t>
In XML, the <scale> element may contain the single scale value, or may contain 2 (or 3) values similar to a GML <spanx style="verb">pos</spanx> with separate scale values. In TLV form:
</t>
<figure title="Map Scale TLV">
<artwork><![CDATA[
+------+------+------+------+------+
| 130 |Length| Scales ...
+------+------+------+------+------+
]]></artwork>
</figure>
</section> <!-- map-scale -->
</section> <!-- map-crs -->
<section title="Map Example">
<t>An example of expressing a map is:</t>
<figure title="Map Example">
<artwork><![CDATA[
<rel:map>
<rel:url type="image/jpeg">
http://example.com/map.jpg
</rel:url>
<rel:offset>200 210</rel:offset>
<rel:orientation>68</rel:orientation>
<rel:scale>2.90 -2.90</rel:scale>
</rel:map>
]]></artwork>
</figure>
</section> <!-- map example -->
</section> <!-- map -->
</section>
<section anchor="example" title="Examples">
<section title="Civic PIDF with Polygon Offset">
<figure><artwork><![CDATA[
<presence xmlns="urn:ietf:params:xml:ns:pidf"
xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model"
xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10"
xmlns:ca="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr"
xmlns:rel="urn:ietf:params:xml:ns:pidf:geopriv10:relative"
xmlns:gml="http://www.opengis.net/gml"
xmlns:gs="http://www.opengis.net/pidflo/1.0"
entity="pres:ness@example.com">
<dm:device id="nesspc-1">
<gp:geopriv>
<gp:location-info>
<ca:civicAddress xml:lang="en-AU">
<ca:country>AU</ca:country>
<ca:A1>NSW</ca:A1>
<ca:A3>Wollongong</ca:A3>
<ca:A4>North Wollongong</ca:A4>
<ca:RD>Flinders</ca:RD>
<ca:STS>Street</ca:STS>
<ca:HNO>123</ca:HNO>
</ca:civicAddress>
<rel:relative-location>
<rel:reference>
<ca:civicAddress xml:lang="en-AU">
<ca:INT N="Building">A</ca:INT>
<ca:INT N="Level">I</ca:INT>
<ca:INT N="Suite">113</ca:INT>
<ca:INT N="Door" R="A">Front</ca:INT>
</ca:civicAddress>
</rel:reference>
<rel:offset>
<gml:Polygon xmlns:gml="http://www.opengis.net/gml"
srsName="urn:ietf:params:geopriv:relative:2d">
<gml:exterior>
<gml:LinearRing>
<gml:pos>433.0 -734.0</gml:pos> <!--A-->
<gml:pos>431.0 -733.0</gml:pos> <!--F-->
<gml:pos>431.0 -732.0</gml:pos> <!--E-->
<gml:pos>433.0 -731.0</gml:pos> <!--D-->
<gml:pos>434.0 -732.0</gml:pos> <!--C-->
<gml:pos>434.0 -733.0</gml:pos> <!--B-->
<gml:pos>433.0 -734.0</gml:pos> <!--A-->
</gml:LinearRing>
</gml:exterior>
</gml:Polygon>
<rel:offset>
</rel:relative-location>
</gp:location-info>
<gp:usage-rules/>
<gp:method>GPS</gp:method>
</gp:geopriv>
<dm:deviceID>mac:1234567890ab</dm:deviceID>
<dm:timestamp>2007-06-22T20:57:29Z</dm:timestamp>
</dm:device>
</presence>
]]></artwork></figure>
</section><section title="Geo PIDF with Circle Offset">
<figure><artwork><![CDATA[
<?xml version="1.0" encoding="UTF-8"?>
<presence xmlns="urn:ietf:params:xml:ns:pidf"
xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model"
xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10"
xmlns:rel="urn:ietf:params:xml:ns:pidf:geopriv10:relative"
xmlns:gml="http://www.opengis.net/gml"
entity="pres:point2d@example.com">
<dm:device id="point2d">
<gp:geopriv>
<gp:location-info>
<gml:Circle srsName="urn:ogc:def:crs:EPSG::4326">
<gml:pos>-34.407 150.883</gml:pos>
<gs:radius uom="urn:ogc:def:uom:EPSG::9001">
50.0
</gs:radius>
</gml:Circle>
<rel:relative-location>
<rel:reference>
<gml:Point srsName="urn:ogc:def:crs:EPSG::4326">
<gml:pos>-34.407 150.883</gml:pos>
</gml:Point>
</rel:reference>
<rel:offset>
<gml:Circle xmlns:gml="http://www.opengis.net/gml"
srsName="urn:ietf:params:geopriv:relative:2d">
<gml:pos>500.0 750.0</gml:pos>
<gml:radius uom="urn:ogc:def:uom:EPSG::9001">
5.0
</gml:radius>
</gml:Circle>
</rel:relative-location>
<map:map>
<map:urltype="image/png">
https://www.example.com/flrpln/123South/flr-2</gp:url>
<map:offset> 2670.0 1124.0 1022.0</gp:offset>
<map:orientation>67.00</gp:orientation>
<map:scale>10</gp:scale>
</map:map>
</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>
</status>
<timestamp>2003-06-22T20:57:29Z</timestamp>
</tuple>
</presence>
]]></artwork></figure>
</section><section title="Civic TLV with Point Offset">
<figure><artwork><![CDATA[
+--------+-------------------------------------------------+
| Type | Value |
+--------+-------------------------------------------------+
| 0 | en |
| | |
| 1 | IL |
| | |
| 3 | Chicago |
| | |
| 34 | Wacker |
| | |
| 18 | Drive |
| | |
| 19 | 3400 |
| | |
| 112 | Reference |
| | |
| 40 | BBuilding|A |
| | |
| 40 | AFloor|6th |
| | |
| 40 | BSuite|213 |
| | |
| 40 | ADoor|Front |
| | |
| 115 | 100 70 |
| | |
| 126 | image/png |
| | |
| 127 | http://maps.example.com/3400Wacker/A6 |
| | |
| 128 | 0.0 4120.0 |
| | |
| 129 | 113.0 |
| | |
| 130 | 10.6 |
+--------+-------------------------------------------------+
]]></artwork></figure>
</section></section>
<section anchor="schema" title="Schema Definition">
<figure title="xml schema relative-location">
<artwork><![CDATA[
<?xml version="1.0"?>
<xs:schema
xmlns:rel="urn:ietf:params:xml:ns:pidf:geopriv10:relative"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:gml="http://www.opengis.net/gml"
targetNamespace="urn:ietf:params:xml:ns:pidf:geopriv10:relative"
elementFormDefault="qualified"
attributeFormDefault="unqualified">
<!-- [[NOTE TO RFC-EDITOR: Please replace all instances of the URL
'http://ietf.org/rfc/rfcXXXX.txt' with the URL of published
document and remove this note.]] -->
<xs:annotation>
<xs:appinfo
source="urn:ietf:params:xml:schema:pidf:geopriv10:relative">
Relative Location for PIDF-LO
</xs:appinfo>
<xs:documentation source="http://ietf.org/rfc/rfcXXXX.txt">
This schema defines a location representation that allows for
the description of locations that are relative to another.
An optional map reference is also defined.
</xs:documentation>
</xs:annotation>
<xs:import namespace="http://www.opengis.net/gml"/>
<xs:element name="relative-location" type="rel:relativeType"/>
<xs:complexType name="relativeType">
<xs:complexContent>
<xs:restriction base="xs:anyType">
<xs:sequence>
<xs:element name="reference" type="rel:referenceType"/>
<xs:element name="offset" type="rel:offsetType"/>
<xs:any namespace="##any" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:restriction>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="referenceType">
<xs:complexContent>
<xs:restriction base="xs:anyType">
<xs:sequence>
<xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:restriction>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="offsetType">
<xs:complexContent>
<xs:restriction base="xs:anyType">
<xs:sequence>
<xs:element ref="gml:_Geometry"/>
<xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:restriction>
</xs:complexContent>
</xs:complexType>
<xs:element name="map" type="rel:mapType"/>
<xs:complexType name="mapType">
<xs:complexContent>
<xs:restriction base="xs:anyType">
<xs:sequence>
<xs:element name="url" type="rel:mapUrlType"/>
<xs:element name="offset" type="rel:doubleList"
minOccurs="0"/>
<xs:element name="orientation" type="rel:doubleList"
minOccurs="0"/>
<xs:element name="scale" type="rel:doubleList"
minOccurs="0"/>
</xs:sequence>
</xs:restriction>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="mapUrlType">
<xs:simpleContent>
<xs:extension base="xs:anyURI">
<xs:attribute name="type" type="rel:mimeType"
default="application/octet-stream"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<!-- From draft-ietf-httpbis-p3-payload-09, excluding
the obsolete parts -->
<xs:simpleType name="mimeType">
<xs:restriction base="xs:token">
<xs:pattern value="[!#$%&'\*\+\-\.\dA-Z^_`a-z\|~]+
/[!#$%&'\*\+\-\.\dA-Z^_`a-z\|~]+([\t ]*;([\t ])*[!#$%&
'\*\+\-\.\dA-Z^_`a-z\|~]+=([!#$%&'\*\+\-\.\dA-Z^_`a-z\|~]+|
"([!#-\[\]-~]|[\t ]*|\\[\t !-~])*"))*"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="doubleList">
<xs:list itemType="xs:double"/>
</xs:simpleType>
</xs:schema>
]]></artwork></figure>
</section>
<section anchor="security" title="Security Considerations">
<t>This document describes a data format. To a large extent, security properties of this depend on how this data is used.</t>
<t>Privacy for location data is typically important. Adding relative location may increase the precision of the location, but does not otherwise alter its privacy considerations, which are discussed in <xref target="RFC4119"/>
</t>
<t>[[Not that interesting, but it could be relevant ?]] The fractional bits in <xref target="IEEE.754">IEEE 754</xref> floating point values can be used as a covert channel. For values of either zero or infinity, non-zero fraction bits could be used to convey information. If the presence of covert channels is not desired then the fractional bits MUST be set to zero. There is no need to represent NaN (not a number) in this encoding.
</t>
</section>
<section anchor="iana" title="IANA Considerations">
<section title="Relative Location Registry">
<t>This document creates a new registry called ’Relative Location Parameters’. As defined in <xref target="RFC5226"/>, this registry
operates under "IETF Consensus" rules.</t>
<t>The content of this registry includes:</t>
<t>Relative Location Code: Numeric identifier, assigned by IANA.</t>
<t>Brief description: Short description identifying the meaning of the
element.</t>
<t>Reference to published specification: A stable reference to an RFC
which describes the value in sufficient
detail so that interoperability between independent
implementations is possible.</t>
<t>IANA is requested to not permit values to be assigned into this registry which conflict with values assigned in the CAtypes registry or to permit values to be assigned into the CAtypes registry which conflict with values assigned to to this registry unless the IANA considerations section for the new value explicitly overrides this prohibition, and the document defining the value describes how conflicting TLV codes will be interpreted by implementations</t>
<t>The values defined are:</t>
<figure><artwork>
+--------+----------------------------------------+-----------+
| RLtype | description | Reference |
+--------+-------+--------------------------------+-----------+
| 111 | relative location reference | this RFC |
| 112 | relative location angle | this RFC |
| 113 | relative location shape 2D point | this RFC |
| 114 | relative location shape 3D point | this RFC |
| 115 | relative location shape circular | this RFC |
| 116 | relative location shape spherical | this RFC |
| 117 | relative location shape elliptical | this RFC |
| 118 | relative location shape ellipsoid | this RFC |
| 119 | relative location shape 2D polygon | this RFC |
| 120 | relative location shape 3D polygon | this RFC |
| 121 | relative location shape prism | this RFC |
| 122 | relative location shape arc-band | this RFC |
| 123 | relative location dynamic orientation | this RFC |
| 124 | relative location dynamic speed | this RFC |
| 125 | relative location dynamic heading | this RFC |
| 126 | relative location map type | this RFC |
| 127 | relative location map URI | this RFC |
| 128 | relative location map coordinates | this RFC |
| 129 | relative location map angle | this RFC |
| 130 | relative location map scale | this RFC |
+--------+-------+--------------------------------+-----------+
</artwork></figure>
</section>
<section title="URN Sub-Namespace Registration">
<t>This document registers a new XML namespace, as per the guidelines in <xref target="RFC3688"/>) that has been registered with IANA.</t>
<figure><artwork><![CDATA[
URI: urn:ietf:params:xml:ns:pidf:geopriv10:relative
Registrant Contact: IETF, GEOPRIV working group (geopriv@ietf.org),
Martin Thomson (martin.thomson@andrew.com).
XML:
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</title>
</head>
<body>
<h1>Format for representing relative location in GEOPRIV</h1>
<h2>urn:ietf:params:xml:ns:pidf:geopriv10:relative</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
]]></artwork></figure></section>
<section title="XML Schema Registration">
<t>
This section registers an XML schema as per the procedures in
<xref target="RFC3688"/>.</t>
<figure><artwork><![CDATA[
URI: urn:ietf:params:xml:schema:pidf:geopriv10:relativeLocation
Registrant Contact: IETF, GEOPRIV working group (geopriv@ietf.org),
Martin Thomson (martin.thomson@andrew.com).
The XML for this schema can be found as the entirety of Section 7
of this document.
]]></artwork></figure></section>
<section title="CRS public identifier registration">
<t>This section registers two public identifiers as per the procedures in
<xref target="RFC3688"/>.</t>
<figure><artwork><![CDATA[
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:
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 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
Registrant Contact: IETF, GEOPRIV working group (geopriv@ietf.org),
Martin Thomson (martin.thomson@andrew.com).
XML:
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 3d CRS</title>
</head>
<body>
<h1>Identifier for a 3D CRS in GEOPRIV relative location</h1>
<h2>urn:ietf:params:xml:ns:pidf:geopriv10:relative:3d</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
]]></artwork></figure></section>
<section title="CAtype Registration">
<t>This section adds a new entry to the CAtype registry defined by <xref target="I-D.ietf-geopriv-local-civic"/>.
</t>
<t><list style="hanging">
<t hangText="Namespace URI:">urn:ietf:params:xml:ns:pidf:geopriv10:relative
</t>
<t hangText="Local Name:">REL
</t>
<t hangText="Description:">Relative location from a reference point
</t>
<t hangText="Contact:">The IESG (iesg@ietf.org); the GEOPRIV working group (geopriv@ietf.org).
</t>
<t hangText="Specification:"> RFCXXXX
</t>
<t hangText="Schema:">urn:ietf:params:xml:schema:pidf:geopriv10:relativeLocation
</t>
<t hangText="Type:">A
</t>
</list>
</t>
</section>
</section>
<section title="Acknowledgements">
<t>This is the product of a design team on relative location. Besides the authors, this team included: Marc Linsner, James Polk, and James Winterbottom.
</t>
</section>
</middle>
<back>
<references title="Normative References">
&RFC2119;
&RFC4119;
&RFC4776;
&RFC5139;
&RFC5226;
&RFC5491;
&RFC5962;
&RFC6225;
&draft-ietf-geopriv-local-civic;
<reference anchor="OGC.GML-3.1.1" target="http://portal.opengeospatial.org/files/?artifact_id=4700">
<front>
<title>Geographic information - Geography Markup Language (GML)</title>
<author initials="S" surname="Cox" fullname="Simon Cox">
<organization />
</author>
<author initials="P" surname="Daisey" fullname="Paul Daisey">
<organization />
</author>
<author initials="R" surname="Lake" fullname="Ron Lake">
<organization />
</author>
<author initials="C" surname="Portele" fullname="Clemens Portele">
<organization />
</author>
<author initials="A" surname="Whiteside" fullname="Arliss Whiteside">
<organization />
</author>
<date month="April" day="19" year="2004" />
<abstract>
<t>Geography Markup Language is an XML grammar written in XML Schema for the modelling, transport, and storage of geographic information.
</t>
</abstract>
</front>
<seriesInfo name="OpenGIS" value="03-105r1" />
</reference>
<reference anchor="OGC.GeoShape">
<front>
<title abbrev="GeoShape">GML 3.1.1 PIDF-LO Shape Application Schema for use by the Internet Engineering Task Force (IETF)</title>
<author initials="M." surname="Thomson" fullname="Martin Thomson">
<organization>Andrew Corporation</organization>
</author>
<author initials="C." surname="Reed" fullname="Carl Reed, PhD.">
<organization>Open Geospatial Consortium Inc.</organization>
</author>
<date month="April" day="10" year="2007"/>
</front>
<seriesInfo name="OGC Best Practice"
value="06-142r1, Version: 1.0"/>
</reference>
<reference anchor="IEEE.754">
<front>
<title abbrev="IEEE754">IEEE Standard for Binary Floating-Point Arithmetic</title>
<author>
<organization>IEEE</organization>
</author>
<date month="January" year="2003"/>
</front>
<seriesInfo name="IEEE Standard"
value="754-1985"/>
</reference>
<reference anchor="Clinger1990" target="ftp://ftp.ccs.neu.edu/pub/people/will/howtoread.ps">
<front>
<title abbrev="Float">How to Read Floating Point Numbers Accurately</title>
<author initials="W." surname="Clinger" fullname="William D. Clinger">
<organization></organization>
</author>
<date month="" day="" year="1990"/>
</front>
<seriesInfo name="Proceedings of Conference on Programming Language Design and Implementation"
value="pp. 92-101"/>
</reference>
</references>
<references title="Informative References">
&RFC3688;
&RFC3986;
</references>
</back>
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-23 00:05:37 |