RFC 5139: Revised Civic Location Format for Presence Information Data Format Location Object (PIDF-LO)
In plain English — editorial summary, not part of the RFC
This document defines an XML format for the representation of civic location. This format is designed for use with Presence Information Data Format Location Object (PIDF-LO) documents and replaces the civic location format in RFC 4119. The format is based on the civic address definition in PIDF-LO, but adds several new elements based on the civic types defined for Dynamic Host Configuration Protocol (DHCP), and adds a hierarchy to address complex road identity schemes. The format also includes support for the xml:lang language tag and restricts the types of elements where appropriate. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5139
- Published
- February 2008
- Authors
- M. Thomson; J. Winterbottom
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 14
- Also known as
- —
- Updates:
- RFC 4119
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5491GEOPRIV Presence Information Data Format Location Object (PIDF-LO) Usage Clarification, Considerations, and RecommendationsUpdated
March 2009
- RFC 5962Dynamic Extensions to the Presence Information Data Format Location Object (PIDF-LO)Current
September 2010
- RFC 5964Specifying Holes in Location-to-Service Translation (LoST) Service BoundariesCurrent
August 2010
- RFC 5606Implications of 'retransmission-allowed' for SIP Location ConveyanceCurrent
August 2009
- RFC 6447Filtering Location Notifications in the Session Initiation Protocol (SIP)Current
January 2012
- RFC 6753A Location Dereference Protocol Using HTTP-Enabled Location Delivery (HELD)Current
October 2012
- RFC 6848Specifying Civic Address Extensions in the Presence Information Data Format Location Object (PIDF-LO)Current
January 2013
- RFC 7035Relative Location RepresentationCurrent
October 2013
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?