[Tagging] remove “rendering” from proposal template

[Peter Elderson]

Proposals should consider the impact on rendering, so a section for that has its place. Maybe call it Impact on rendering.

Mvg Peter Elderson

> Op 22 apr. 2021 om 16:01 heeft Brian M. Sperlongano <zelonewolf at gmail.com> het volgende geschreven:
> 
> 
> I 100% agree with this suggestion.  Proposals should discuss tagging and modeling while rendering decisions belong to the various renderers.  While proposals should consider the impact on rendering (especially when modifying tags that render today), it seems that authors are interpreting this section as a place to invent new Carto style features. 
> 
>> On Thu, Apr 22, 2021, 9:42 AM Martin Koppenhoefer <dieterdreist at gmail.com> wrote:
>> The proposal template adds a Rendering section, but it doesn’t make sense. There is some point of having such a section for tag definition pages (in case there is a representation on the “standard” map(s?)), but for a proposal I believe this only creates false expectations. Tag proposals are about the way we describe the world, if and when the tags will have an effect for a map rendering is a completely different question, one that is not influenced by tagging proposals.
>> 
>> Let’s remove “Rendering” from the template.
>> 
>> Cheers Martin 
>> 
>> sent from a phone
>> _______________________________________________
>> Tagging mailing list
>> Tagging at openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/tagging
> _______________________________________________
> Tagging mailing list
> Tagging at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/tagging
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20210422/8e607b96/attachment.htm>