From OpenStreetMap Wiki
Jump to: navigation, search
Additional values

Added values: yes. As there must be an opposite to no. And neither no or yes are the default. And members_only as in some locations only members may reserve in advance, other people cannot reserve, but reservation isn't mandatory either.

  • I explicitly avoided yes as a value. Either you cannot make a reservation or you have two options: a) It is required that you make a reservation (i.e. you cannot access an object without a reservation), or b) it is recommended, but optional. If a user would find a yes as a value, she cannot tell if a reservation is optional or required, so it is a useless value for her. Kay D 12:34, 12 April 2012 (BST)
Well for many places it depends on the time, season, and so on whether it would be recommendable or not. Take a restaurant. It's open all day, but only over midday and from 6-8PM it is crowded. Those would be the only times where from an outsider, you might want to reserve. On the other hand the restaurant maybe doesn't like reservations for theese hours. Some other places might say they recommend you to reserve. Recommended isn't good at all from this sense, as we don't know who recommends it (users vs owner) and for which time it makes sense. I do agree that Yes is very generic, but recommendable on the other hand is not giving any more information either--Extremecarver 12:52, 13 April 2012 (BST)
  • members_only is a good information to be added to an object, but how about specifying it in the access key?. Kay D 12:34, 12 April 2012 (BST)
No, member_only means everyone can come/use/do whatever, but only members may reserve in advance. Hence advantage to members, but not related to access at all. --Extremecarver 12:52, 13 April 2012 (BST)