[RFC] Feature Proposal – Sensory

General talk Tagging general discussion
,
6
  • sensory= : First of all, sensory=yes has no meaning. What would be the reason for it to replace that voted in playground= ? sensory:*=yes provides no further info than sensory=* to justify.
  • Examples: They are almost all defaults that shouldn’t be added. It’s known usually a =library is =quiet , =cinema is =dim but has =flash , and =casino or =amusement_arcade has sensory:visual=yes (what’s the ambience here anyway?). playground=musical_instrument should already imply sensory=audible now.
  • =dim , =quiet , =normal , =loud , =bright , etc: all very subjective and low verifiability in other situations. At least it needs to be relatable, eg discomfort, can’t stare or listen to prolonged time, able to talk to others softly.
  • =protection : Is counterintuitive. It doesn’t mean the sense is protected, but that hearing protection is needed. Personal protective equipment requirements should be a general topic that doesn’t fall into this aspect.
  • sensory:friendly_hours: As I have commented on quiet_hours= before, inventing a *_hours= / *_times= for every purpose is not scalable. It should be attempted to fit into existing methods first, eg service_times:sensory_sensitivity= . Indeed, sensory_sensitivity= may better for showing whether a feature has been designed for them. similar to wheelchair= for physical accessibility. Eg sensory_sensitivity:conditional=designated @ (Mo-Fr 08:00-10:00) , and sensory_sensitivty=designated on “quiet room” / “calm space” (=shelter ?).
  • sensory:friendly_hours:source= : As much as I personally prefer *:source= as found in OHM, source:*= is used in OSM. Furthermore, what you want is *:signed= , as source= is freeform text. For the other options, adding *:url= as in opening_hours:url= is more straightforward and useful.
1 Like