<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <div class="moz-cite-prefix">Am 17.04.2021 um 14:01 schrieb
      Marc_marc
    </div>
    <blockquote type="cite"
      cite="mid:db7c2f3e-62a3-4a2f-5f1b-81516c115d74@mailo.com">
      <blockquote type="cite">
        <pre class="moz-quote-pre" wrap="">No, there is used post_office:type=* - not post_office=*. post_office=*
ist only used nine times in france.
"post_office" are not "post_office:type" (mho)
</pre>
      </blockquote>
      <pre class="moz-quote-pre" wrap="">
in this case why using "post_office:type=post_partner" in
<a class="moz-txt-link-freetext" href="https://wiki.openstreetmap.org/wiki/Proposed_features/shop_as_post-partner#Tagging">https://wiki.openstreetmap.org/wiki/Proposed_features/shop_as_post-partner#Tagging</a>
?

it's really confusing how you would have to map a shop-post-partner
in France, dealing with 2 brands
for "LaPoste", it would be amenity=post_office post_office:type=post_partner
and to map the brand, we used brand :-)
except that your proposal says to use post_office for the brand,
but only if it is not an amenity=post_office... so not for in France.
so whitch key ? the proposal complicates the situation instead of
bringing things closer together on both sides of the border

I feel like it would be much more consistent and simple:
- to remove the obligation "only if it's not amenity=post_office"
in order to leave this criterion to the choice of the local communities
(we had already discussed this in the previous version)</pre>
    </blockquote>
    <p><span class="VIiyi" lang="en"><span class="JLqJ4b ChMk0b"
          data-language-for-alternatives="en"
          data-language-to-translate-into="de" data-phrase-index="0"><span>Well,
            that just depends on whether it is stand-alone
            (shop-in-shop, as it seems to have been solved by LaPoste
            for you) or integrated in the respective shop / amenity.</span></span>
        <span class="JLqJ4b ChMk0b" data-language-for-alternatives="en"
          data-language-to-translate-into="de" data-phrase-index="1"><span>The
            first would be an independent node, because the baker who
            has a branch in the supermarket is tagged individually, but
            the baked goods counter in the supermarket is not.</span></span></span>
    </p>
    <blockquote type="cite"
      cite="mid:db7c2f3e-62a3-4a2f-5f1b-81516c115d74@mailo.com">
      <pre class="moz-quote-pre" wrap="">- use brand if you want to fill in the brand :)
-- either directly brand when the object represents only the postal
service (case in France)
-- or in case of an object mixing 2 things (the brand of the shop and
the brand of the postal service as you seem to want in Germany, the
simplest seems to me to use the namespace post_office:bramd</pre>
    </blockquote>
    <p><span class="VIiyi" lang="en"><span class="JLqJ4b ChMk0b"
          data-language-for-alternatives="en"
          data-language-to-translate-into="de" data-phrase-index="0"><span>Do
            you mean to omit post_office = * and only use post_office:
            type = post_partner to the shop = * and amenity = * (with
            the exception of amenity = post_office) and then
            post_office: brand?</span></span><span class="JLqJ4b"
          data-language-for-alternatives="en"
          data-language-to-translate-into="de" data-phrase-index="1"><span>
          </span></span><span class="JLqJ4b ChMk0b"
          data-language-for-alternatives="en"
          data-language-to-translate-into="de" data-phrase-index="2"><span>Another
            possibility.</span></span> <span class="JLqJ4b ChMk0b"
          data-language-for-alternatives="en"
          data-language-to-translate-into="de" data-phrase-index="3"><span>Was
            just wanted the other way around in the wiki: D</span></span><span
          class="JLqJ4b" data-language-for-alternatives="en"
          data-language-to-translate-into="de" data-phrase-index="4"><span><br>
          </span></span><span class="JLqJ4b ChMk0b"
          data-language-for-alternatives="en"
          data-language-to-translate-into="de" data-phrase-index="5"><span>Or
            should it stay with the previously used post_office = yes?</span></span>
        <span class="JLqJ4b ChMk0b" data-language-for-alternatives="en"
          data-language-to-translate-into="de" data-phrase-index="6"><span>And
            then post_office: brand?</span></span></span> </p>
    <blockquote type="cite"
      cite="mid:db7c2f3e-62a3-4a2f-5f1b-81516c115d74@mailo.com">
      <pre class="moz-quote-pre" wrap="">the order for ref is also strange, it's often ref:<otherkey>=*
and not post_office:ref=* nor post_office:ref:<brand>=*
</pre>
    </blockquote>
    <span class="VIiyi" lang="en"><span class="JLqJ4b ChMk0b"
        data-language-for-alternatives="en"
        data-language-to-translate-into="de" data-phrase-index="0"><span>This
          resulted from the fact that you then have a direct assignment
          of the brand.</span></span> <span class="JLqJ4b ChMk0b"
        data-language-for-alternatives="en"
        data-language-to-translate-into="de" data-phrase-index="1"><span>I
          know a shop that receives from Deutsche Post the ref XY to
          send Mail / parcels there and ref YZ in general for
          identification and from the local postal operator ABC.</span></span>
      <span class="JLqJ4b ChMk0b" data-language-for-alternatives="en"
        data-language-to-translate-into="de" data-phrase-index="2"><span>This
          was also directed to me, because it would be easier for
          dataconsumer (I cannot validate it)</span></span><span
        class="JLqJ4b" data-language-for-alternatives="en"
        data-language-to-translate-into="de" data-phrase-index="3"><span>
        </span></span><span class="JLqJ4b ChMk0b"
        data-language-for-alternatives="en"
        data-language-to-translate-into="de" data-phrase-index="4"><span><br>
          Of course that can also be adjusted ...</span></span></span>
  </body>
</html>