<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Luckily for you that you're not a data consumer because otherwise
you would want the OSM community to actually listen to us which
they don't do at all sadly :(<br>
</p>
<p>We have two options:<br>
1. If we find a way to distinguish between url=*, website=*,
webpage=* which is also reasonable understandable to newbies, then
it can be an improvement. But as I followed the discussion here I
doubt that we find a good definition for each of them.<br>
2. We deprecate url, website, webpage in favor of website or url
or webpage and do an automatic edit to change all occurrences of
the deprecated ones to the approved one. But we don't touch all
the tags for the social media websites because they are special
websites and handled differently by most applications.<br>
</p>
<div class="moz-cite-prefix">On 20.03.21 20:46, Peter Elderson
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAKf=P+thbQ2zOeFnzz+R+hSxXz9k+dwTqONuyWMft1uwMOWOVw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">website, url and webpage are all valid keys, anyone
can use them even if no one else does. Anyone who thinks uri is
a better key for uri's is also right and can use it.
Systematically removing or replacing them is wrong and should
lead to a ban.
<div><br>
</div>
<div>As for unifying this, I think it's not worth the hassle. I
for one have seen valid arguments for all these keys, and even
missed a few for allowing multiple keys so multiple purposes
can be served. I use that e.g. for route relations, where the
website key references an information website about e.g. all
the routes maintained by an operator, and the url references
the page or sub-site of the route. </div>
<div>Same with stolpersteine: website references a site for a
(sub)collection, url gives the page or subpage for one
stolperstein. I have had cases where I could use a webpage key
in addition. <br>
<div><br>
</div>
<div>It's up to the data consumers to decide what to support
for particular use cases. If I were a data user, I would
support them all.</div>
<div><br clear="all">
<div>
<div dir="ltr" class="gmail_signature"
data-smartmail="gmail_signature">Peter Elderson</div>
</div>
<br>
</div>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">Op do 18 mrt. 2021 om 13:33
schreef Paul Allen <<a href="mailto:pla16021@gmail.com"
moz-do-not-send="true">pla16021@gmail.com</a>>:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div>Hi</div>
<div><br>
</div>
<div>Some time ago, as a side-issue to something else, I</div>
<div>mentioned that I preferred using url=* to website=*
when</div>
<div> the item was a single, standalone page in a much
larger website.</div>
<div>Somebody (I forget who) suggested using webpage=*
instead. So</div>
<div> I recently did.</div>
<div><br>
</div>
<div>I added a holiday cottage and used webpage=* for the
single</div>
<div> page on a website dealing with many holiday cottages.
A couple</div>
<div> of hours later I received a changeset comment telling
me not to</div>
<div> use non-standard keys and which changed webpage=* to</div>
<div> website=*.</div>
<div><br>
</div>
<div>I wondered if the person had happened across the
newly-added</div>
<div>holiday cottage by accident or was using some sort of
tool to</div>
<div>catch things like this. So I didn't respond, merely
changed</div>
<div>it back, noting that I had deliberately chosen that
key, please</div>
<div>don't revert, and "any key you like." That way I'd
know if</div>
<div>the person was using a tool to catch these things or
not.</div>
<div>Sure enough, that user changed it back to website.</div>
<div><br>
</div>
<div>I checked the wiki: nothing for webpage=*. Which does
indeed</div>
<div> make it non-standard. But if it showed up in taginfo
I could add</div>
<div>a page with status "in use" or "de facto" (if I can
figure out the</div>
<div>difference between them). It did show up in taginfo.
1 use</div>
<div>(probably mine). But a chronology showing it once had
a</div>
<div>far higher use which ramped up over time and then
dropped</div>
<div>off a cliff. Then later showed some small usage that
then</div>
<div>dropped off a cliff. That has zero usage today.
Unless</div>
<div>somebody knows how to get at the details, as far as</div>
<div>taginfo is concerned it never existed.<br>
</div>
<div><br>
</div>
<div>Then I checked that user's edit history. Quite a lot
of</div>
<div>changesets are about "fixing" things. He or she fixed</div>
<div>wbsite=* in one edit (for which he or she deserves
thanks).</div>
<div>But he or she also waged war upon webpage.</div>
<div><br>
</div>
<div>So a few questions:</div>
<div><br>
</div>
<div>1) Does what this user is doing constitute good
practise or not?</div>
<div>He or she is not fixing errors that he or she finds
when editing</div>
<div>objects but is using a tool to wage war on tags he or
she</div>
<div>considers non-standard. Before you answer this,
remember<br>
</div>
<div>"any tag you like." You might one day roll out limited
usage</div>
<div>of a tag you just invented to get a feel for how it
works, only</div>
<div>to find it has been replaced a few hours later because
it is</div>
<div>non-standard.<br>
</div>
<div><br>
</div>
<div>2) Is there sufficient excuse to document webpage=* as</div>
<div>"in use" (with suggestion to consider using website=*</div>
<div>where appropriate) given that it was, prior to war
being</div>
<div>waged upon it, actually in use? Or is it so
controversial</div>
<div>it would need a proposal and vote? If so, I'll
probably go</div>
<div>back to using url=*.<br>
</div>
<div><br>
</div>
<div>-- <br>
</div>
<div>Paul</div>
<div><br>
</div>
</div>
_______________________________________________<br>
Tagging mailing list<br>
<a href="mailto:Tagging@openstreetmap.org" target="_blank"
moz-do-not-send="true">Tagging@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/tagging"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.openstreetmap.org/listinfo/tagging</a><br>
</blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Tagging mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Tagging@openstreetmap.org">Tagging@openstreetmap.org</a>
<a class="moz-txt-link-freetext" href="https://lists.openstreetmap.org/listinfo/tagging">https://lists.openstreetmap.org/listinfo/tagging</a>
</pre>
</blockquote>
</body>
</html>