#6461 closed defect (fixed)
update preset for contact information
Reported by: | flaimo | Owned by: | ce |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | Internal preset | Version: | tested |
Keywords: | Cc: |
Description
according to http://wiki.openstreetmap.org/wiki/Key:contact the keys "phone", "fax", "website" and "email" should be grouped using the "contact:" namespace. the josm preset should be updated so it writes those keys instead the old ones without a namespace.
Attachments (0)
Change History (10)
comment:1 Changed 12 years ago by
comment:2 Changed 12 years ago by
Component: | Core → Internal preset |
---|---|
Owner: | changed from team to ce |
comment:3 Changed 12 years ago by
We could add a preset "Contact (new)"
containing the contact:
tags. Doing so, we can assist the user independently of the tagging scheme being used.
comment:5 Changed 11 years ago by
Note the discussion in the josm-dev
mailing list: http://lists.openstreetmap.org/pipermail/josm-dev/2011-December/005877.html
comment:6 Changed 11 years ago by
Following the discussion in the mailinglist, I'd rename the common/old scheme to "Contact (common schema)" to clarify the relation. Any comments/objections?
comment:7 Changed 11 years ago by
Maybe rename "Contact (new schema)" to "Contact (tagging schema with 'contact:*' prefix)"?
comment:8 Changed 11 years ago by
Both renamings combined would make it very clear:
- Contact (common schema)
- Contact (schema with 'contact:*' prefix)
Although from a data design/computer science perspective the contact:-namespace would definitely be nicer you have to admit that the much more human-readable "phone"-tag is way more established (Taginfo.openstreetmap.org says 89.000 "phone" vs 9.000 "contact:phone"). It's fairly easy to change all instances to "contact:phone" in database preprocessing.
Conclusion: JOSM preset should stick with the established tagging scheme