[Tagging] consider website=www.openstreetmap.org to be OK
joseph.eisenberg at gmail.com
Tue Jan 26 16:32:16 UTC 2021
Taginfo shows 0 (zero) uses of the string "gopher://" in values or keys:
This discussion seems to be considering very hypothetical uses rather than
what is practical for mapper and database users.
website=* in practice is only used for normal website addresses like
https:// or http://
I have not bothered to add these prefixes when typing in a web address
since about 1996.
Can someone please show a real-world example where there is a significant
benefit from adding all these extra, hard-to-type characters?
-- Joseph Eisenberg
On Tue, Jan 26, 2021 at 7:03 AM Paul Johnson <baloo at ursamundi.org> wrote:
> On Tue, Jan 26, 2021 at 12:55 AM Mateusz Konieczny via Tagging <
> tagging at openstreetmap.org> wrote:
>> Right now https://wiki.openstreetmap.org/wiki/Key:website has:
>> "include the scheme (http or https) explicitly.
>> not www.openstreetmap.org/"
>> Why this is supposed to be substantially better?
> Website is often generalized to mean "any internet resource that directly
> relates to this object". https and http aren't the only possible methods
> by a long shot. University of Michigan definitely has some things that
> only has a gopher presence (gopher is their baby), so gopher:// would be
> the method part of the URL in that case, and trying to access it with http
> or https *will not* work.
> IETF STD-66 was very thorough for a reason. Let's not break it because
> some browsers make assumptions.
> Tagging mailing list
> Tagging at openstreetmap.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Tagging