Talk:Key:max age

Target age

Should this tag be used for public playgrounds? Many parks in the USA are designed with targeted age groups due to different developmental abilities and goals-- I'm wondering if min_age and max_age would be a suitable way to indicate these ranges, or if they are strictly about minimums and maximums that are somehow enforced.--TinyMapper (talk) 05:18, 11 December 2023 (UTC)

I suggested min_age:advisory=* Talk:Key:min age#Should this be used for *suggested* minimum ages? , that could go with max_age:advisory=* . The concept should be interchangeable.
Rigorously, it may be argued this is not exactly the same if *:advisory=* in terms of maxspeed:advisory=* is about safety, instead of design intent. For comparison, there are also some maxspeed:suggested=* and maxspeed:recommended=* , although they are more likely mistakes. For fee=donation , there is no proper charge:*=* equivalent yet, except a fee:suggested=* and deprecated fee:amount:suggested=* .
—— Kovposch (talk) 04:29, 12 December 2023 (UTC)

Keep it simple! Who is going to evaluate different sub-tagging of how deeply enforced a particular age-limit is? Who makes the decision if the playground signage is being enforced or not? If an age-range is signposted, I map it with min_age and max_age, absolutely fine for me. --Polarbear w (talk) 16:10, 15 December 2023 (UTC)