[OSM-talk] immutable=yes Fwd: DEC Lands

[MP]

> In that case, the data should not be in OSM but should instead be pulled
> in on another level - for example, create transparent tiles to show on
> top of OSM tiles, or make a shapefile and pull that in through Mapnik.

Well, if the data won't be in OSM (neither in dumps or in things
received from API), how would people see them? Slippy map is not all
we have.
Plus, this would make harder to make data derived from it (if appropriate).

>> How do people feel about me importing this data (with all of their
>> metadata), adding an immutable=yes tag, with the intent of tracking
>> their dataset, and deleting --outright-- any changes made by OSM
>> editors.

While the data may be very accurate and usually they shouldn't be
edited, I don't think they should be really immutale - someone may
still want to correct tags or names (even "100% correct" data from
authorities often have at least few mispelling in them). The data
could be watched for changes, but I don't think forbidding any changes
or automatically reverting them without examining the change is the
way to go. Maybe the immutable tag could get some support in editor
that will show some big warning when you (probably accidentally) try
to edit these data (so it would be more of a hint that the data should
not be changed), but I won't forbid it in general.

Martin