[Tagging] remove “rendering” from proposal template

stevea steveaOSM at softworkers.com
Sat Apr 24 19:39:58 UTC 2021

On Apr 24, 2021, at 12:23 PM, Peter Elderson <pelderson at gmail.com> wrote:
> I think it's about renderability and usability of the data, not about prescribing what a particular renderer or data user should do exactly. Many proposals do not consider that enough, which gives the data users an extra headache or just leads to nothing. 
> If the proposer voices her or his thoughts, it gives participants the opportunity to comment on that in a positive way. The ideas may be spot-on, fine. Or they may show misunderstanding of what it takes to render or use the proposed tagging, given the current state of the database. Or there may be an easier or quicker way to accomplish the same result.
> Let's not call this mandatory, just encouragement to think it through. If a proposer  doesn't consider impact, usability, and backward compatibility, chances are the proposal will not make the cut.

Very nice, Peter!

(Spitballing):  "You might leave this 'Suggested Rendering' section blank, you might contribute suggestions here which voice your thoughts. allowing other participants to constructively comment.  Perhaps what emerges are misunderstandings of what it takes to render (this does happen), perhaps there is another (easier or quicker) way a renderer might accomplish this.  "While thoughtful contributions of suggestions and ideas that consider impact, usability and backward compatibility are welcome here, decisions of "how to render this?" are ultimately up to renderer authors."

Let's include, additional associated, more-minor stuff, like "don't-let-this-affect-your-Approve-or-Oppose-vote," important enough to mention as to how consumers of the Proposal should behave with these.  We seem to be sharpening focus.

More information about the Tagging mailing list