Geocoding and Reverse-geocoding Using Location-to-Service Translation
draft-polk-ecrit-lost-geocoding-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | James Polk | ||
Last updated | 2009-07-06 | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document creates new service URNs for geocoding and reverse geocoding location formats to be used by location-to-service translation protocol (LoST) to convert location values into a format of choice. 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 RFC 2119 [RFC 2119].
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)