Le 21. 11. 18 à 16:33, Paul Allen a écrit : > On Wed, Nov 21, 2018 at 3:21 PM marc marc wrote: > > Le 21. 11. 18 à 13:39, Michael Brandtner a écrit : > > it's a ref specific to this parking lot to be entered into an app > or sms. > > payment:sms=yes or payment:sms=<the number to send the sms to> > payment:<appname>=yes > > > ref:payment:app=12345 > > ref:payment:sms=12345 > > ref=12345 look enough, isn't it ? > > No.
I already have trouble imagining that there are mobile apps so badly made that it asks the user to transcribe the parking ref instead of finding it by geolocation but for those apps, it seems more convenient to me to use payment:<appname>=<the number the app need> <about a different ref for each payment method> > ALL of them might be possible might ? of course ! but does this situation exist or it's it's purely fictional ? of course we can put several ref:<target1> ref:<target2> on all parking of the planet just in case another entity would designate this parking lot with another ref... but if the majority of car parks have only one reference, their operator's ref, it seems to me to bring no advantage to use several ref:*=* over using ref=* without suffix and add suffixes only when necessary. In this case, the suffix should be the same between the payment key and the ref key like payment:sms=yes with ref:sms=* not payment:sms=yes with ref:payement-by-sms=* Regards, Marc _______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
