<div dir="auto">Thanks for answers :)<div dir="auto"><br></div><div dir="auto">I said a lib, but indeed the diversity of projects would be too problematic for implementation and rollouts.</div><div dir="auto">JSON, xml, text are fine</div><div dir="auto"><a href="https://twitter.com/VincentPrivat/status/944923315831033856">https://twitter.com/VincentPrivat/status/944923315831033856</a><br></div><div dir="auto"><br></div><div dir="auto">As Simon said, taginfo is a great tool to extract data from wiki.</div><div dir="auto">Even if it's not perfect, the wiki is the only reference I know and where data consumers go to get information. Then it's relevent to improve it</div><div dir="auto">It would be hard to put all practicies and rules in wiki keys scorecard templates (from where taginfo get most of its input). Should we complete it in taginfo itself ?</div><div dir="auto"><br></div><div dir="auto">All the best</div><div dir="auto"><br></div><div dir="auto">François </div></div><div class="gmail_extra"><br><div class="gmail_quote">Le 24 déc. 2017 1:47 PM, "Simon Poole" <<a href="mailto:simon@poole.ch">simon@poole.ch</a>> a écrit :<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<p>On the one hand lots of the in principle useful information in
the wiki is not really easily extractable and on the other hand it
is prone to manipulation in more than one way (current fad is to
add big warnings about tagging errors what are not).</p>
<p>IMHO addressing the first issue would likely be more helpful and
perhaps allow the generation of at least rudimentary presets
directly from the wiki (potentially with support from taginfo).</p>
<p>Simon<br>
</p>
<p><br>
</p>
<br>
<div class="m_1508402919614463030moz-cite-prefix">On 24.12.2017 12:54, Mateusz Konieczny
wrote:<br>
</div>
<blockquote type="cite">
<div dir="auto">
<div>> <span style="font-family:sans-serif;font-size:12.8px">conform
validation to wiki</span>
<div dir="auto"><span style="font-family:sans-serif;font-size:12.8px"><br>
</span></div>
<div dir="auto"><span style="font-family:sans-serif;font-size:12.8px">Sometimes
wiki is wrong and should be changed. </span></div>
<div dir="auto"><span style="font-family:sans-serif;font-size:12.8px"><br>
</span></div>
<div dir="auto"><span style="font-family:sans-serif;font-size:12.8px">Note also
that authors of different tools have different opinions
how and what should be reported as errors.</span></div>
<div dir="auto"><br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On 24 Dec 2017 11:12 a.m.,
"François Lacombe" <<a href="mailto:fl.infosreseaux@gmail.com" target="_blank">fl.infosreseaux@gmail.com</a>>
wrote:<br type="attribution">
<blockquote class="m_1508402919614463030quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="auto">Hi
<div dir="auto"><br>
</div>
<div dir="auto">Here is an idea I got regarding
tagging validation in editors (iD, JOSM, others).</div>
<div dir="auto">Subsequently to wiki proposal voting
and cleanups, it's currently necessarily to open
issues in each editor repository to ask for new
tagging validation rules. </div>
<div dir="auto"><br>
</div>
<div dir="auto">It can sometimes be time consuming to
develop those new rules and such a work is done
independently by each project maintainer. While each
project have its own specific components, background
logic is the same.</div>
<div dir="auto"><br>
</div>
<div dir="auto">Would a new lib called like
osmtagvalidator or so in charge of doing conform
validation to wiki be useful?</div>
<div dir="auto">It may be shared by any project
involved in osm editing and preserve its resources
for other valuable developments.</div>
<div dir="auto"><br>
</div>
<div dir="auto">For me, validation doesn't prevent
users to use tags they want, but only warn them
about possible mistakes.</div>
<div dir="auto"><br>
</div>
<div dir="auto">How would devs and users feel about
this?</div>
<div dir="auto"><br>
</div>
<div dir="auto">All the best</div>
<font color="#888888">
<div dir="auto"><br>
</div>
<div dir="auto">François</div>
</font></div>
<br>
______________________________<wbr>_________________<br>
talk mailing list<br>
<a href="mailto:talk@openstreetmap.org" target="_blank">talk@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/talk" rel="noreferrer" target="_blank">https://lists.openstreetmap.or<wbr>g/listinfo/talk</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</div>
</div>
<br>
<fieldset class="m_1508402919614463030mimeAttachmentHeader"></fieldset>
<br>
<pre>______________________________<wbr>_________________
talk mailing list
<a class="m_1508402919614463030moz-txt-link-abbreviated" href="mailto:talk@openstreetmap.org" target="_blank">talk@openstreetmap.org</a>
<a class="m_1508402919614463030moz-txt-link-freetext" href="https://lists.openstreetmap.org/listinfo/talk" target="_blank">https://lists.openstreetmap.<wbr>org/listinfo/talk</a>
</pre>
</blockquote>
<br>
</div>
<br>______________________________<wbr>_________________<br>
talk mailing list<br>
<a href="mailto:talk@openstreetmap.org">talk@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/talk" rel="noreferrer" target="_blank">https://lists.openstreetmap.<wbr>org/listinfo/talk</a><br>
<br></blockquote></div></div>