I’m a big fan of education=* . In general, this will really streamline the tagging of education facilities and enable more specificity while increasing usage by simplifying queries.
@InsertUser, you mentioned some really good aspects within the Aviation training sector. Could you come up with a couple more tags that might better capture training in that sector? Like education=training + training=aviation + aviation = maintenance …=ATC …=… . I think this structure actually fits perfectly and would enable folks who are interested in aviation education to expand this concept. It provides flexibility to those with particular interests while providing a natural “home”, without forcing “amenity” to be the generic catch all. I think the failure of some of the previous education efforts were exactly because they were overly prescriptive and some users felt pigeon-holed into something. I certainly am not qualified to think about all of the nuances of aviation education, I think that should be left to that particular OSM userbase. I think this education=* proposal enables a structure that offers users more flexibility and specificity without constraining them.
@woodpeck, and @InsertUser since training=* was rejected. I think you both mention some key points for clarification. Does the addition of training=* take away from sport=* ? Is there a difference in places that have sport only, or also include training? I would argue that education=training + training=fencing implies sport=fencing (and should be tagged as such), and would certainly not replace it but sport=fencing does not imply that instruction is performed. This would also apply to your examples of wrestling, boxing, hapkido, and kickboxing.
Given the previous highly ambitious that were not successful on the basis of being too broad. I think the scope is right for this one. Again, I think it provides a nice option, and a framework which, as @InsertUser demonstrates so clearly, could be applied in a variety of contexts, each of which could be proposed to meet the needs of that specific OSM user base. From a functionality perspective, since this deprecates no tags, there will be no compatibility issues with pre-existing hardware or software, but instead makes an option to streamline queries, just like healthcare=* did.
I look forward to seeing more discussion! (edited because * and the period put everything in italics)