<div dir="ltr"><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Am Di., 8. März 2022 um 09:17 Uhr schrieb Mateusz Konieczny via Tagging <<a href="mailto:tagging@openstreetmap.org">tagging@openstreetmap.org</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>
<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"></div></div></blockquote><div><br></div></div><div class="gmail_quote"><br></div><div class="gmail_quote">this is (or should be) generally the case for all "...wikipedia" and "...wikidata". <br></div><div class="gmail_quote">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 class="gmail_quote"><br><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div dir="auto">If artwork_subject=sheela-na-gig is used already then adding subject:*<br></div><div dir="auto">repeating this info to every single one seems to be not needed duplicate.<br></div></div></blockquote><div><br></div><div><br></div><div>wikidata integration is generally useful to improve interoperability, but it isn't a replacement for tagging in osm, as a result it will somehow "duplicate" information in a certain sense.<br></div><div><br></div><div></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div dir="auto"></div><div dir="auto"><br></div><div dir="auto">artwork_subject seems likely to be bunch of intersecting categories<br></div><div dir="auto">(and with artwork_subject=figurative already is) <br></div></div></blockquote><div><br></div><div><br></div><div>yes, it is implicit that some tags have overlapping values, as there can be more generic categories and more specific categories, where the latter are completely or partially covered by the generic classes. For example it can be seen in "building" as well (residential vs. apartments, house and detached, etc.), in landuse (farmland vs. vineyard etc.), sculptures, ...<br></div><div>in this sense, artwork_subject=sheela-na-gig is probably a part of artwork_subject=figurative (which is very broad (maybe too broad?) in meaning)<br></div><div><br></div><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">https://taginfo.openstreetmap.org/keys/artwork_subject#values</a></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</div><div><a href="https://wiki.openstreetmap.org/wiki/Key%3Aartwork_subject">https://wiki.openstreetmap.org/wiki/Key%3Aartwork_subject</a></div><div></div><div>From the 5 documented values, figurative, religious, abstract, art_nouveau, genre, the "art nouveau" value seems to be about style and not subject. Some of the more used values are not in English, etc.</div><div>In this context, IMHO artwork_subject=sheela-na-gig is a better fit for the key than most of the already used values.<br></div><div><br></div><div></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div dir="auto"></div><div dir="auto"><br></div><div dir="auto">Maybe artwork:sheela-na-gig=yes would be better?<br></div><div><br></div></div></blockquote><div><br></div><div><br></div><div>IMHO not. It would not provide context unless you knew what "sheela-na-gig" was, better put it in the value.</div><div>If you wanted to use sheela-na-gig as a part of the key, why not sheela-na-gig=yes?</div><div><br></div><div>Cheers,<br></div><div>Martin<br></div><div><br></div><div> </div></div></div>