RFC 7035: Relative Location Representation
In plain English — editorial summary, not part of the RFC
This document defines an extension to the Presence Information Data Format Location Object (PIDF-LO) (RFC 4119) 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. An alternative binary representation is described. 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.
Document record
- Document ID
- RFC7035
- Published
- October 2013
- Authors
- M. Thomson; B. Rosen; D. Stanley; G. Bajko; A. Thomson
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 39
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7105Using Device-Provided Location-Related Measurements in Location Configuration ProtocolsCurrent
January 2014
- RFC 6848Specifying Civic Address Extensions in the Presence Information Data Format Location Object (PIDF-LO)Current
January 2013
- RFC 6753A Location Dereference Protocol Using HTTP-Enabled Location Delivery (HELD)Current
October 2012
- RFC 6447Filtering Location Notifications in the Session Initiation Protocol (SIP)Current
January 2012
- RFC 5491GEOPRIV Presence Information Data Format Location Object (PIDF-LO) Usage Clarification, Considerations, and RecommendationsUpdated
March 2009
- RFC 5139Revised Civic Location Format for Presence Information Data Format Location Object (PIDF-LO)Current
February 2008
- RFC 6739Synchronizing Service Boundaries and <mapping> Elements Based on the Location-to-Service Translation (LoST) ProtocolUpdated
October 2012
- RFC 6451Location-to-Service Translation (LoST) Protocol ExtensionsCurrent
December 2011
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?