[Tagging] remove “rendering” from proposal template

Peter Elderson pelderson at gmail.com
Fri Apr 23 05:52:28 UTC 2021

"Rendering Suggestions" sounds to me that I am supposed to provide examples. That's not the idea, is it? My idea is that the proposer should reflect on the impact of the proposed tagging on rendering (and other data use). This could be very simple e.g. when proposing tagging a new amenity node and suggesting an icon and an overpass query, but it could also be complicated when proposing a change to a long used problematic tagging scheme where all data users have implemented their own interpretation and preferences, and now get yet another tagging scheme on top of that. 
It should answer the question: how is a renderer / data user supposed to make sense of this tagging, given the state of the database.

I see no harm in the proposer just providing rendering examples; then it's up to the RFC participants to ask for further reflection on the impact of the proposal on rendering/data use. E.g. by asking "How is a renderer/data user supposed to interpret this tagging, given that the database now contains.... Could you add that to the section Whateveritscalled?"

Peter Elderson

> Op 23 apr. 2021 om 03:50 heeft stevea <steveaOSM at softworkers.com> het volgende geschreven:
>>>> Let’s remove “Rendering” from the template.
> I think there is a balance to be struck here.  If we leave "Rendering" in the template — I think it is a good idea to do so — it should be emphasized that these are SUGGESTIONS to rendering:  a "weak" section that is wholly independent of being implemented by ANY renderer, should the proposal be Approved.  So perhaps the simple re-titling of the section to "Rendering Suggestions" will convey that these are merely (emphasis on MERELY) "suggestions."  By "weak" I mean  "not strictly tied to the rest of what is being Proposed."
> If we do so, there might also be "stock text" always appearing at the beginning of said "Rendering Suggestions" section.  The text that follows is rather quickly invented, but I'm thinking something like "While proposals can have significant effects on rendering, any actual rendering of this syntax is not the focus of what is being proposed here.  However, should this Proposal become Approved, here are the proposal author's ideas on suggestions on how various aspects of the proposal MIGHT be rendered:"  And then a table or simple text description can show an icon, .png, symbol, fill color, shading, edge, way or line segment that has a particular thickness, hatching and/or color, et cetera.  The text should make it clear that THIS section, THESE suggestions (and they are SUGGESTIONS only), regarding rendering, are wholly independent of being enacted should the proposal become Approved.
> _______________________________________________
> Tagging mailing list
> Tagging at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/tagging

More information about the Tagging mailing list