1 / 4

Civic Address Boundaries

This draft proposes a standard method to define boundaries for location-based services to determine if a location falls "within" a specified boundary based on civic address elements. It aims to address internationalization concerns and provide clear limitations and guidance for implementing rough location and other operations.

kendall
Download Presentation

Civic Address Boundaries

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Civic Address Boundaries draft-thomson-ecrit-civic-boundary

  2. “Within” • LoST maps a location to a service if the location is “within” the associated boundary • Each <serviceBoundary> element describes a set of civic addresses that fall within the service boundary, namely, all addresses that textually match the civic address elements provided, regardless of the value of other address elements. • Definition is a little loose • Especially for addresses with elements in multiple languages

  3. Example

  4. Definitions • Define what it means for one address to be considered “within” another • More rigorously than in RFC 5222 • Deal with address internationalization concerns • Make the limitations clear • Define basic operations useful for implementing rough-loc and other work • Union and intersection • Make limitations clear • Provide guidance to LoST server and location hiding implementers

More Related