[OSM-dev] [Fwd: Re: Chopped of ways. New flag for OSM XML?]

Rogier Wolff R.E.Wolff at BitWizard.nl
Fri Aug 15 16:12:39 BST 2008

On Fri, Aug 15, 2008 at 07:59:07AM -0700, Karl Newman wrote:
> > Making some parameter negative to mean "this object is incomplete"
> > sounds like a hack to me. It's something that you might do in an
> > internal database, or in an in-memory datastructure, but it should not
> > be in an API. Not ever. It's a cludge.

> I was thinking more of the general case--"this object should not be
> uploaded because it's been manipulated in some way that invalidates
> the data".  Setting the version of an entity as negative would
> easily prevent that, using the (proposed) server api. This "hack" is
> intended for offline files, not the main API.

Of course it's not the "main API", but if you use this method in one
instance, it will be seen as an example. People will copy it. And
before you know it, data will be passed along from app to app with this
advice taken to heart. And then you have it in an API. 

You're saying the main API will ignore such uploads. Great. Now the
fact that these are ignored has become part of the API!


** R.E.Wolff at BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2600998 **
**    Delftechpark 26 2628 XH  Delft, The Netherlands. KVK: 27239233    **
*-- BitWizard writes Linux device drivers for any device you may have! --*
Q: It doesn't work. A: Look buddy, doesn't work is an ambiguous statement. 
Does it sit on the couch all day? Is it unemployed? Please be specific! 
Define 'it' and what it isn't doing. --------- Adapted from lxrbot FAQ

More information about the dev mailing list