RE: AW: [Geopriv] Quickrandomcommentsondraft-ietf-geopriv-pdif-l o-profile-00

RFC3825 provides a mechanism to convey a binary alt value that can represent
a floor.  Since there is no RFC police, it would seem that building
engineers and operators *may* implement the mechanism in 3825 to best match
their local situation.  There may be a case where the ground floor may be 0
and the 22nd floor (missing floor label 13) may well be 22.  I can't imagine
the IETF or anyone else claiming 'your building is out of 3825 compliance'
with this approach.  Ascii floor labels were examined in length during the
3825 process and deemed insigificant wrt the overall intent of the
architecture.  A larger requirement was to maintain a small compact object.

It was never the intent of 3825 to influence the engineering of building
floors and labels as conveyed with, "The values represented by this AT will
be of local significance. Since buildings and floors can vary due to lack of
common control, the values chosen to represent the characteristics of an
individual building will be derived and agreed upon by the operator of the
building and the intended users of the data.  Attempting to standardize this
type of function is beyond the scope this document."

If in fact, you get your desires, and the receiver of the data derived from
the 3825 object actually has a modern GIS system, why can't the 3825 data
simply be used as a db key to lookup the 'human-useful' data?  And as a side
benefit, in the interim, the 3825 LO does convey more data than is available
in the majority of the records of the current ALI system.

-Marc-

> -----Original Message-----
> From: Brian Rosen [mailto:br@brianrosen.net] 
> Sent: Friday, July 15, 2005 10:40 AM
> To: Marc Linsner; James M. Polk; James Winterbottom; Henning 
> Schulzrinne
> Cc: GEOPRIV
> Subject: Re: AW: [Geopriv] 
> Quickrandomcommentsondraft-ietf-geopriv-pdif-l o-profile-00
> 
> Because 3825 counts floors; there would be a 13th floor.
> 
> I think this is hard to deal with.  It's precise, but 
> impossible to use without more data, for which we don't have 
> a practical way to provide.
> 
> Brian

_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www1.ietf.org/mailman/listinfo/geopriv