Re: [Geopriv] "House Number" misnamed?
Brian Rosen <br@brianrosen.net> Wed, 04 November 2009 22:05 UTC
Return-Path: <br@brianrosen.net>
X-Original-To: geopriv@core3.amsl.com
Delivered-To: geopriv@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 891013A6A0B for <geopriv@core3.amsl.com>; Wed, 4 Nov 2009 14:05:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.297
X-Spam-Level:
X-Spam-Status: No, score=-2.297 tagged_above=-999 required=5 tests=[AWL=0.302, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M4kFFOQJNnOV for <geopriv@core3.amsl.com>; Wed, 4 Nov 2009 14:05:22 -0800 (PST)
Received: from ebru.winwebhosting.com (ebru.winwebhosting.com [74.55.202.130]) by core3.amsl.com (Postfix) with ESMTP id 9F2973A6898 for <geopriv@ietf.org>; Wed, 4 Nov 2009 14:05:22 -0800 (PST)
Received: from neustargw.va.neustar.com ([209.173.53.233] helo=[192.168.128.96]) by ebru.winwebhosting.com with esmtpa (Exim 4.69) (envelope-from <br@brianrosen.net>) id 1N5nys-0001MZ-99; Wed, 04 Nov 2009 16:05:30 -0600
User-Agent: Microsoft-Entourage/12.20.0.090605
Date: Wed, 04 Nov 2009 17:05:32 -0400
From: Brian Rosen <br@brianrosen.net>
To: "Thomson, Martin" <Martin.Thomson@andrew.com>, Brian Rosen <brian.rosen@neustar.biz>, "geopriv@ietf.org" <geopriv@ietf.org>
Message-ID: <C71764DC.1EF31%br@brianrosen.net>
Thread-Topic: [Geopriv] "House Number" misnamed?
Thread-Index: AcpWVW+3xG5n60b2lE+NtczXoqNVkgAQBSvQAcFaNg4=
In-Reply-To: <8B0A9FCBB9832F43971E38010638454F0F1EA6D5@SISPE7MB1.commscope.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - ebru.winwebhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - brianrosen.net
X-Source:
X-Source-Args:
X-Source-Dir:
Subject: Re: [Geopriv] "House Number" misnamed?
X-BeenThere: geopriv@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Geographic Location/Privacy <geopriv.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/geopriv>, <mailto:geopriv-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/geopriv>
List-Post: <mailto:geopriv@ietf.org>
List-Help: <mailto:geopriv-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/geopriv>, <mailto:geopriv-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Nov 2009 22:05:23 -0000
In further discussion with NENA, we think a separate field is necessary. There are just too many cases where there is both a milepost and an address (house) number. The field has to be decimal (tenths of a mile/km are common). Brian On 10/26/09 7:44 PM, "Thomson, Martin" <Martin.Thomson@andrew.com> wrote: > Misnamed as it may be, the actual label does not need to change if we want to > extend its semantics. The only problem comes about when you attempt to > constrain semantics. I see no problem with what you propose. > > It's a simple enough change to note that HNO can refer to milestones or > whatever. The only question that arises is whether this is the right thing to > do. There was that proposal to add support for a separate "post number", > which seemed to indicate that such things were commonplace, but orthogonal to > house numbering. > > I've always thought that all the suffix fields were largely redundant and just > a source of extra complexity. As it stands, any document author can choose to > use the suffix, or just roll the two identifiers into the base element. The > Austrian mappings in the RFC-to-be use the latter approach consistently. > > --Martin > >> -----Original Message----- >> From: geopriv-bounces@ietf.org [mailto:geopriv-bounces@ietf.org] On >> Behalf Of Rosen, Brian >> Sent: Tuesday, 27 October 2009 3:00 AM >> To: geopriv@ietf.org >> Subject: [Geopriv] "House Number" misnamed? >> >> In the original PIDF-LO definition in RFC4119, we have a field called >> "House >> Number" (and a "House Number Suffix"). Is this field misnamed? >> >> Suppose you had a "milepost" on a road, or on a railroad, or even a >> hiking >> trail. Would you expect the marker number (which is usually miles or >> kilometers as measured from an end of the road/railroad/trail) to >> appear in >> the "HNO" field? >> >> I think yes, which means that the field is misnamed. I would suspect >> that >> the appetite of the work group to actually change the name of the field >> would be low, although I would probably like to do something that would >> generalize the use of the field. >> >> A more subtle question. In 4119, under HNO, it says "numeric part >> only". >> If the post marker was "125.5" is that numeric enough, or would we have >> to >> use the suffix? >> >> Brian >> >> _______________________________________________ >> Geopriv mailing list >> Geopriv@ietf.org >> https://www.ietf.org/mailman/listinfo/geopriv > > _______________________________________________ > Geopriv mailing list > Geopriv@ietf.org > https://www.ietf.org/mailman/listinfo/geopriv
- Re: [Geopriv] "House Number" misnamed? Rosen, Brian
- [Geopriv] "House Number" misnamed? Rosen, Brian
- Re: [Geopriv] "House Number" misnamed? James M. Polk
- Re: [Geopriv] "House Number" misnamed? James M. Polk
- Re: [Geopriv] "House Number" misnamed? Rosen, Brian
- Re: [Geopriv] "House Number" misnamed? James M. Polk
- Re: [Geopriv] "House Number" misnamed? Brian Rosen
- Re: [Geopriv] "House Number" misnamed? Thomson, Martin
- Re: [Geopriv] "House Number" misnamed? James M. Polk
- Re: [Geopriv] "House Number" misnamed? Brian Rosen
- Re: [Geopriv] "House Number" misnamed? Brian Rosen