[Tagging] Suggestion: ref:mobile_payment for amenity=parking

Sergio Manzi smz at smz.it
Thu Nov 29 16:25:00 UTC 2018


I mean, today maybe you have just one service/clearinghouse and a simple ref: could do, but then tomorrow a new service/clearinghouse requiring a different code is added.

Then you must "namespace" the second code, but the first...  stay un-namespaced?

Languages must be extensible...

Sergio


On 2018-11-29 17:20, Sergio Manzi wrote:
> On 2018-11-29 17:17, Martin Koppenhoefer wrote:
>> maybe just “ref”, unless it is different? We are using ref for example for bus stops where you can use this code to dynamically query an api for bus arrival times. As long as it is just one reference number, there’s no need to declare 5 levels of nested structures ;-)
>>
> Different services/clearinghouses could require different codes... or not? :-/
>
>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3675 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20181129/306b6896/attachment.bin>


More information about the Tagging mailing list