<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<div><br></div><div><br></div><div><br></div><div>Mar 8, 2022, 09:54 by dieterdreist@gmail.com:<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div dir="ltr"><div class=""><div class="" dir="ltr">Am Di., 8. März 2022 um 09:17 Uhr schrieb Mateusz Konieczny via Tagging <<a href="mailto:tagging@openstreetmap.org" rel="noopener noreferrer" target="_blank">tagging@openstreetmap.org</a>>:<br></div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class=""><div><div>Using both <br></div><div dir="auto"><br></div><div dir="auto">artwork_subject=sheela-na-gig<br></div><div dir="auto"><br></div><div dir="auto">and<br></div><div dir="auto"><br></div><div dir="auto">subject:wikidata=Q509424<br></div><div dir="auto">subject:wikipedia=en:Sheela na gig<br></div><div dir="auto"><br></div><div dir="auto">seems to be not needed for me.<br></div><div dir="auto"><br></div></div></blockquote><div><br></div></div><div class=""><br></div><div class="">this is (or should be) generally the case for all "...wikipedia" and "...wikidata". <br></div><div class="">Our data should be self contained (not sure if this is the right term, I mean that the semantics should be clear without having to use another database in order to make sense of it).<br></div></div></blockquote><div dir="auto">species:wikipedia / taxon:wikipedia and its wikidata variant is at least helping<br></div><div dir="auto">with being linked to specific species while species / species:en / species:pl etc<br></div><div dir="auto">are often having massive number of synonyms, variants etc.<br></div><div dir="auto"><br></div><div dir="auto">The same for vehicle:wikipedia/vehicle:wikidata where vehicle type/model<br></div><div dir="auto">is not really appearing in name and parsing description would be a nightmare<br></div><div dir="auto"><br></div><div dir="auto">But in this case it is like linking "Water" page on every single natural=water<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div dir="ltr"><div class=""><div>There doesn't seem to be a conceived system behind the artwork_subject in general <a href="https://taginfo.openstreetmap.org/keys/artwork_subject#values" rel="noopener noreferrer" target="_blank">https://taginfo.openstreetmap.org/keys/artwork_subject#values</a><br></div><div>the second most used value, "religious", has potential overlap with all the other values (and could possibly be expressed with the standard religion=* tag), although with some few it may be less likely (e.g. lgbtq). There are only 3800 objects with this tag, and you cannot see yet where it may evolve to. The documentation is a bunch of referrals to wikipedia, so that they will change by the time without us noticing in the OSM-Wiki<br></div><div><a href="https://wiki.openstreetmap.org/wiki/Key%3Aartwork_subject" rel="noopener noreferrer" target="_blank">https://wiki.openstreetmap.org/wiki/Key%3Aartwork_subject</a><br></div></div></div></blockquote><div dir="auto">I agree, though my conclusion would be "and therefore this tag should be avoided,<br></div><div dir="auto">using some other scheme that will not be very likely to be problematic in future<br></div><div dir="auto">should be preferred"<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div dir="ltr"><div class=""><div>IMHO not. It would not provide context unless you knew what "sheela-na-gig" was, better put it in the value.<br></div><div>If you wanted to use sheela-na-gig as a part of the key, why not sheela-na-gig=yes?<br></div></div></div></blockquote><div dir="auto">It also works for me.<br></div><div dir="auto"><br></div> </body>
</html>