On Mon, Jun 7, 2010 at 9:18 AM, John Smith <span dir="ltr"><<a href="mailto:deltafoxtrot256@gmail.com">deltafoxtrot256@gmail.com</a>></span>
wrote:<br>
<div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im">On 7 June 2010 23:12, Anthony <<a href="mailto:osm@inbox.org">osm@inbox.org</a>> wrote:<br>
> The only thing I'm really afraid of is that these tags would
violate what<br>
> some people seem to believe is a rule - the supposed "map only
what's on the<br>
> ground" rule. Do the website=* and wikipedia=* tags violate this
rule?<br>
<br>
</div>Using that logic, source=* from aerial imagery, would need to be<br>
removed,</blockquote><div><br>
Well, I'm sure even the most ardent "map only what's on the ground"
proponents will make exceptions for things which are legally required.
As for source tags that *aren't* legally required, I'd actually argue
myself that as metatags they should be on the changeset, not the
element.<br>
<br>
Either way, I could see someone going around removing uuid=* tags from
places where they couldn't find the QR code in the store window.<br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">although
if wikipedia starts linking to OSM objects do we<br>
need to also link to wikipedia objects?<br>
</blockquote></div><br>
I'd suggest that we should have a single website=* or uuid=* link to an all-inclusive wiki (can't use Wikipedia as that single website because of their notability rules), and that all other linking to any other websites should be done by adding an external link from that wiki page.<br>
<br>So, no.<br><br><div class="gmail_quote">On Mon, Jun 7, 2010 at 9:18 AM, John Smith <span dir="ltr"><<a href="mailto:deltafoxtrot256@gmail.com">deltafoxtrot256@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">While you can embed a UUID in a URL I would suggest it gets it's own<br>
tag since lots of objects already get a website tag.<br></blockquote><div><br>I'd prefer that. But if the "let's try to get consensus for a new tag" process fails, there's always "shove it into an already accepted tag" option. (At which point it'd probably be website:uuid=*, or even website:uuid:building/operator/etc=*)<br>
</div></div>