Re: [Tagging] Feature Proposal - RFC - Top_up (fifth revision)
sent from a phone > On 11. May 2019, at 18:44, Philip Barnes wrote: > > I would assume that the key public_transport_cards will indicate that I can > top-up the local operators cards, here in The Shire I would expect it to mean > I can top up an Arriva bus card, I would expect a very glazed look if I tried > to top-up (my now obsolete) Oyster card in the local shop. IMHO it can make sense to be specific, you cannot expect every top up place to offer every kind of local public transport payment system, there may be several of them. Cheers, Martin ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Feature Proposal - RFC - Top_up (fifth revision)
On Sun, 2019-05-12 at 00:10 +0900, 石野貴之 wrote: > Hello. > > > 2019年5月11日(土) 5:30 bkil : > > I've read in the previous rejection comments that many opposed to > > > > putting brand details in keys. What do you think about this > > version: > > > > prepaid_top_up:mobile=yes/. The reason is that around here, > > > > you could top up your mobile phone either at the given carrier, > > kiosks > > > > over generic online charging or at given supermarket chains > > > > (supporting fixed subsets of carriers). We could easily map such > > > > detail when importing the given supermarket chain's data. We have > > > > already raised this question during previous imports before this > > > > proposal was started. > > > > > > I'm in favor for your idea of putting brand details. The reason is > mainly because: > > 【There should be consistency between prepaid_top_up tag and payment > tag.】 > > https://wiki.openstreetmap.org/wiki/Key:payment > > For example, there are many kinds of public_transport cards in the > world and payment:* tag supports them. (icsf cards like Suica in > Japan, Oyster card in the UK, T-money card in Korea and so on.) A tag > like prepaid_top_up:public_transport=yes is insufficient, We cannot > use Oyster card in Japan! Where you can use Suica, there should be > top_up machines for it. You can't use an Oyster card in most of the UK either, and I assume you cannot top one up outside London either. I would assume that the key public_transport_cards will indicate that I can top-up the local operators cards, here in The Shire I would expect it to mean I can top up an Arriva bus card, I would expect a very glazed look if I tried to top-up (my now obsolete) Oyster card in the local shop. Phil (trigpoint) ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Feature Proposal - RFC - Top_up (fifth revision)
Hello. 2019年5月11日(土) 5:30 bkil : > I've read in the previous rejection comments that many opposed to > putting brand details in keys. What do you think about this version: > prepaid_top_up:mobile=yes/. The reason is that around here, > you could top up your mobile phone either at the given carrier, kiosks > over generic online charging or at given supermarket chains > (supporting fixed subsets of carriers). We could easily map such > detail when importing the given supermarket chain's data. We have > already raised this question during previous imports before this > proposal was started. > > I'm in favor for your idea of putting brand details. The reason is mainly because: *【There should be consistency between prepaid_top_up tag and payment tag.】* https://wiki.openstreetmap.org/wiki/Key:payment For example, there are many kinds of public_transport cards in the world and payment:* tag supports them. (icsf cards like Suica in Japan, Oyster card in the UK, T-money card in Korea and so on.) A tag like prepaid_top_up:public_transport=yes is insufficient, We cannot use Oyster card in Japan! Where you can use Suica, there should be top_up machines for it. Other types of rechargeable cards or mobile phone applications may be more limited in use. I proposed using prepaid_top_up:gaming=yes in the discussion page, but more specific tags like prepaid_top_up:gaming=paseli sound better for me. Paseli is operated by Konami, so it cannot be used in games by other companies(Sega, Taito,...). Thank you. Takayuki Ishino yumean1...@gmail.com > ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Feature Proposal - RFC - Top_up (fifth revision)
I've read in the previous rejection comments that many opposed to putting brand details in keys. What do you think about this version: prepaid_top_up:mobile=yes/. The reason is that around here, you could top up your mobile phone either at the given carrier, kiosks over generic online charging or at given supermarket chains (supporting fixed subsets of carriers). We could easily map such detail when importing the given supermarket chain's data. We have already raised this question during previous imports before this proposal was started. > > I suggest we leave this out because it is too much to maintain IMO.--PangoSE > (talk) 16:15, 10 May 2019 (UTC) > > > Le 08.05.19 à 18:25, egil a écrit : > > > https://wiki.openstreetmap.org/wiki/Proposed_features/Top_up ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Feature Proposal - RFC - Top_up (fifth revision)
1. If I want to find a place where I can have some ice cream, searching for cuisine="*ice_cream*" is a simple solution. Listing each individual product is difficult to maintain due to changes in time, but I usually add general categories that define the shop and for which people would realistically want to search for. 2. There already exists such a thread: "Values in namespaces/prefixes/suffixes Considered Harmful - Or: Stop over-namespacing and prefix-fooling" https://lists.openstreetmap.org/pipermail/tagging/2018-December/041650.html https://wiki.openstreetmap.org/wiki/Talk:Namespace#Over-namespacing_and_Prefix-fooling The verdict up until now seems to be that you shouldn't tag in such a way that values creep into the key side of tags, especially if the right side is always yes/no, but do share your view over that thread if you think otherwise. The version with semicolons is also easier to type. On Wed, May 8, 2019 at 7:10 PM marc marc wrote: > > Le 08.05.19 à 18:25, egil a écrit : > > https://wiki.openstreetmap.org/wiki/Proposed_features/Top_up > > your proposal seems to be affected by a community division on 2 topics: > > - osm should it contain everything that a store sells ? probably not, > but the limit is difficult to establish (we add the type of fuel sell at > petrol stations) > > - how to fill in a yes/no list. in recent proposals, we see some who > refuse a collection of value in one tag and promote several tags with > yes/no and some others who refuse a tag list with yes/no and want to use > one key with a lot of ";" but for which no schema is currently provided > to list a no (on the namespace page, some have mentioned the prefixes > "un" (like unmarked) the -, the no- ! but there is a general logic > missing... this is perhaps an opportunity to launch a discussion on this > subject to avoid that many proposals are polluted by the same problem. > > ___ > Tagging mailing list > Tagging@openstreetmap.org > https://lists.openstreetmap.org/listinfo/tagging ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Feature Proposal - RFC - Top_up (fifth revision)
Le 08.05.19 à 18:25, egil a écrit : > https://wiki.openstreetmap.org/wiki/Proposed_features/Top_up your proposal seems to be affected by a community division on 2 topics: - osm should it contain everything that a store sells ? probably not, but the limit is difficult to establish (we add the type of fuel sell at petrol stations) - how to fill in a yes/no list. in recent proposals, we see some who refuse a collection of value in one tag and promote several tags with yes/no and some others who refuse a tag list with yes/no and want to use one key with a lot of ";" but for which no schema is currently provided to list a no (on the namespace page, some have mentioned the prefixes "un" (like unmarked) the -, the no- ! but there is a general logic missing... this is perhaps an opportunity to launch a discussion on this subject to avoid that many proposals are polluted by the same problem. ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
[Tagging] Feature Proposal - RFC - Top_up (fifth revision)
https://wiki.openstreetmap.org/wiki/Proposed_features/Top_up Cheers pangoSE ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
