Re: [dhcwg] Fwd: Working Group Last Call: Location Configuration Information for GEOPRIV
creediii@mindspring.com Thu, 03 July 2003 16:32 UTC
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22382; Thu, 3 Jul 2003 12:32:49 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Y705-0006hU-E5; Thu, 03 Jul 2003 12:32:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Y5jh-0008Ji-6M for dhcwg@optimus.ietf.org; Thu, 03 Jul 2003 11:11:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA14940 for <dhcwg@ietf.org>; Thu, 3 Jul 2003 11:10:57 -0400 (EDT)
From: creediii@mindspring.com
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Y5je-0007l1-00 for dhcwg@ietf.org; Thu, 03 Jul 2003 11:10:58 -0400
Received: from mclean.mail.mindspring.net ([207.69.200.57]) by ietf-mx with esmtp (Exim 4.12) id 19Y5jd-0007kw-00 for dhcwg@ietf.org; Thu, 03 Jul 2003 11:10:57 -0400
Received: from dialup-65.58.59.209.dial1.denver1.level3.net ([65.58.59.209] helo=pavilion) by mclean.mail.mindspring.net with smtp (Exim 3.33 #1) id 19Y5jR-00047y-00; Thu, 03 Jul 2003 11:10:45 -0400
Message-ID: <00da01c34178$1f3bce80$0101a8c0@pavilion>
To: Henning Schulzrinne <hgs@cs.columbia.edu>, Marc Linsner <mlinsner@cisco.com>
Cc: 'Andrew Daviel' <andrew@daviel.org>, dhcwg@ietf.org, geopriv@mail.apps.ietf.org
References: <000501c340ab$46784be0$220d0d0a@mlinsnerzk7abh> <3F03854D.2060608@cs.columbia.edu>
Subject: Re: [dhcwg] Fwd: Working Group Last Call: Location Configuration Information for GEOPRIV
Date: Thu, 03 Jul 2003 08:30:29 -0600
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4807.1700
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Content-Transfer-Encoding: 7bit
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Id: <dhcwg.ietf.org>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
I support Henning on the requirement for a UoM. This is why I referenced the OGC recommendation paper on Units of Measurement. Many geospatial technologies today - in order to make best use of coordinates - need to know the UoM. Regards Carl ----- Original Message ----- From: "Henning Schulzrinne" <hgs@cs.columbia.edu> To: "Marc Linsner" <mlinsner@cisco.com> Cc: "'Andrew Daviel'" <andrew@daviel.org>; <dhcwg@ietf.org>; <geopriv@mail.apps.ietf.org> Sent: Wednesday, July 02, 2003 7:22 PM Subject: Re: [dhcwg] Fwd: Working Group Last Call: Location Configuration Information for GEOPRIV > Marc Linsner wrote: > > > > For those who are struggling with this, it is not our intention to > > (re)define zero altitude. We are simply attempting to provide a > > mechanism for people who understand altitude values to share them > > amongst each other via a standardized mechanism. If one were to receive > > such data, it is assumed that they will understand the definition of > > zero altitude within the jurisdiction/authority from which the data > > originated. Some map datum define zero altitude, some don't. For those > > that don't, we define mean low tide. > > Like the datum, what's wrong with providing an indication of the unit of > the measurement? > > I think it is generally a bad idea to assume that all parties along a > chain of transmission know what the data meant initially. This only adds > a modest number of bits to the format, given that the number of choices > appears to be on the order of two. > _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] Fwd: Working Group Last Call: Location Co… Ralph Droms
- Re: [dhcwg] Fwd: Working Group Last Call: Locatio… Robert Elz
- Re: [dhcwg] Fwd: Working Group Last Call: Locatio… John Schnizlein
- Re: [dhcwg] Fwd: Working Group Last Call: Locatio… Robert Elz
- Re: [dhcwg] Fwd: Working Group Last Call: Locatio… Andrew Daviel
- RE: [dhcwg] Fwd: Working Group Last Call: Locatio… Marc Linsner
- Re: [dhcwg] Fwd: Working Group Last Call: Locatio… Henning Schulzrinne
- Re: [dhcwg] Fwd: Working Group Last Call: Locatio… creediii
- [dhcwg] Unit of Measurement...? James M. Polk
- Re: [dhcwg] Fwd: Working Group Last Call: Locatio… John Schnizlein
- [dhcwg] Re: Unit of Measurement...? James M. Polk
- Re: [dhcwg] Fwd: Working Group Last Call: Locatio… James M. Polk
- RE: [dhcwg] Fwd: Working Group Last Call: Locatio… Marc Linsner
- Re: [dhcwg] Fwd: Working Group Last Call: Locatio… Henning Schulzrinne
- Re: [dhcwg] Fwd: Working Group Last Call: Locatio… Greg Troxel
- [dhcwg] Re: Unit of Measurement...? Henning Schulzrinne
- [dhcwg] Re: Unit of Measurement...? Greg Troxel
- Re: [dhcwg] Fwd: Working Group Last Call: Locatio… Greg Troxel
- Re: [dhcwg] Fwd: Working Group Last Call: Locatio… Greg Troxel
- [dhcwg] Re: Unit of Measurement...? Carl Reed
- Re: [dhcwg] Fwd: Working Group Last Call: Locatio… Dominic Pinto
- Re: [dhcwg] Fwd: Working Group Last Call: Locatio… Carl Reed