On Fri, Aug 29, 2014 at 9:43 AM, Peter Wendorff
<wendo...@uni-paderborn.de> wrote:
> +0.5, as UIs are decoupled from the data in OSM. You may write your own
> editor with a completely different UI, even one that doesn't know about
> oneway at all, so reasoning on UI preferences may help to get the best
> default, but not to derive rules from.
Agreed.
That was a way to say: if you reset the values in the database to have
no NULLs, and change the semantics of NULL to mean strictly "unknown",
not all is lost regarding convenience of data entry. iD (to put an
example) can still choose to preselect "no" for streets. Nowadays it
has a list of stuff for which "yes" is assumed:
https://github.com/bhousel/iD/blob/master/js/id/core/oneway_tags.js
And you increase certainty. If a UI does not include oneway and
creates streets, then oneway remains unknown for them, fine. The user
said nothing, so fine to write a NULL meaning "don't know".
Nevertheless, all this is a theoretical exercise just for the sake of
thinking about the attribute.
_______________________________________________
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
