I step back from my proposal https://wiki.openstreetmap.org/wiki/Proposed_features/Subkey:changing_table:location which is totally fine because of less work. The webapp "Babykarte" by the way supports semicolons as seperators so I do not have problems of having semicolons in values.
Cheers Sören Reinecke alias Valor Naram -----Original Message----- From: Sören Reinecke via Tagging <tagging@openstreetmap.org> Reply-To: "Tag discussion, strategy and related tools" < tagging@openstreetmap.org> To: Tagging@openstreetmap.org Cc: Sören Reinecke <tilmanreine...@yahoo.de> Subject: [Tagging] Feature Proposal - RFC - (changing_table:location) Date: Thu, 05 Dec 2019 14:39:27 +0100 Hey all, A new but small proposal to change the specification for subkey `changing_table:location` because of a discussion yesterday about using seperators in values. I totally agree that we should avoid using seperators when possible. Proposal: https://wiki.openstreetmap.org/wiki/Proposed_features/Subkey:changing_table:location Definition: Tagging of the location of the nappy changing facility in a POI Reason: Someone pointed to the wikipage Semi-colon value separator as part of a discussion of using semicolons as seperator of key values. In my previous successful proposal the subkey `changing_table:location' allows to seperate the values by a semicolon. While the support of a semicolon as seperator for this subkey falls under the three exceptions ( https://wiki.openstreetmap.org/wiki/Semi-colon_value_separator ), I want to give here the chance to change that because the subkey changing_table:location is still not in widespread use. Cheers Sören Reinecke alias Valor Naram _______________________________________________Tagging mailing listtagg...@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
_______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
