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

Sergio Manzi smz at smz.it
Thu Nov 29 16:18:37 UTC 2018


Hi Martin!

On 2018-11-29 17:11, Martin Koppenhoefer wrote:

> payment:sms:WhateverPayApp:contact=<phone number to send>
>
>
> Does not look very sustainable, are we going to mass retag all of these if the number changes? I agree it might be useful to have this information, but it shouldn’t need to be tagged on every instance where you can pay (unless the number is individual and not universal), e.g. it could be entered in the wiki.
>
>
I'm not familiar with the technology. If the phone number to use is always the same for a given app/service, I totally agree with you.


On 2018-11-29 17:11, Martin Koppenhoefer wrote:
>>
>>     payment:sms:WhateverPayApp:ref:payment=<code to send>
>>
>
>
> two times ‘payment’? Maybe payment:sms:ExampleApp:payment_ref=
>
> or ...code_to_send=*

Right! Too many payments! :-) To spare some bytes it could be: payment:sms:ExampleApp:code=<code to send>.  What do you think?

Cheers!

Sergio

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20181129/80d95483/attachment-0001.html>
-------------- 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/80d95483/attachment-0001.bin>


More information about the Tagging mailing list