Re: DHCP options for civil locations

Two other standards documents that deal with "address" that might be of
interest.

[1] Federal Geographic Data Committee, "Address Data Content Standard -
Public Review Draft", December 2000. This has actually gone through a formal
review process and has moved beyond the draft stage.
[2] ISO/TC 204 N34, "GDF - Geographic Data Files - V4.0", August 23rd 2000.

Regards

Carl Reed, PhD
OpenGIS Consortium

----- Original Message -----
From: Rohan Mahy <rohan@cisco.com>
To: Henning Schulzrinne <hgs@cs.columbia.edu>
Cc: <geopriv@mail.apps.ietf.org>
Sent: Friday, December 06, 2002 3:13 PM
Subject: Re: DHCP options for civil locations

> Hi Henning,
>
> This is a fairly US centric. For example, it woud be very difficult to
> represent a Japanese address using this system. I'd suggest adding ISO
> top level location (country), and changing state to "second-level
> location" (state, province, region, but well-defined worldwide). you
> could also remove county and district and add third/fourth/fifth level
> administrative regions (county, township, and probably district in the
> US). Likewise, you may want to add a hierarchy of community name.
>
> For example: Japan has an address hierarchy. I have probably butchered
> it, but this should get the point across
>
> to/fu or ken/do metropolis or prefecture (these are ISO level 2
> regions)
> shi or gun city or rural area
> ku ward (only within a "to" or "shi")
> chou or mura town or village
> chome district
> ban block
>
> I originally researched this from a set of books that I no longer have,
> but I found a short description at:
> http://www.csse.monash.edu.au/~jwb/afaq/addresses.html
>
> ---------
>
> i once proposed a hierarchical format for civil names name incorporated
> this general idea.
>
> administrative regions
> a1 = top level (country)
> a2 = second level (state, province, region)
> a3 = county, shi, gun
> a4 = township, chou?, mura?
> a5 = smaller administrative division
> ...
>
> habitated area
> h1 = metropolitan area
> h2 = city or town
> h3 = ward, major town division, ku
> h4 = district, chome
> h5 = subdistrict, block, ban
>
> road or way (by way of example)
> r1 = primary, major road, multiple lanes, sealed
> r2 = secondary major road
> r3 = business thoroughfare
> r4 = residential artery
> r5 = residential feeder
> r6 = other residential road or track
> r6 = private or minor road or track
> r7 = etc..
>
> my house would be:
> <a1>us</a1>
> <a2>ca</a2>
> <a3>santa cruz county</a3>
> <h1>greater santa cruz</h1>
> <h2>city of santa cruz</h2>
> <h3>westside</h3>
> <h4>linda vista district</h4>
> <r6>ladera drive</r6>
>
> You can represent a Japanese address, and even an address like this one
> (yes this is their real postal address sans postal code):
>
> The Gibsons
> Barmby on the Marsh
> Near Goole
> North Humberside
> UK
>
> hope this helps.
> thanks,
> -rohan
>
>
> On Thursday, December 5, 2002, at 10:32 AM, Henning Schulzrinne wrote:
>
> > Inspired by the Polk/Linsner/Schnizlein draft on using DHCP for
> > conveying geospatial location information to client, I wrote up a
> > complementary draft on civil locations:
> >
> > draft-schulzrinne-geopriv-dhcp-civil-00
> >
> > Until it appears in the archives, you can find it at
> > http://www.cs.columbia.edu/~hgs/sip/drafts/draft-schulzrinne-geopriv-
> > dhcp-civil-00.txt
> >
> > Usage would be similar and complementary to the DHCP-geo draft, i.e.,
> > it would allow clients to determine their current (approximate)
> > location at boot or network join time.
> >
> > This is still very immature work; I would appreciate feedback.
> >
> > Henning
> >
>
Received on Sun Dec 8 20:13:31 2002