<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><font face="Verdana">Yep, I was reading them but essentially what
you do is create a many to one or many to many relationship.
This could be possible in a many to one relationships, all the
top level keys apply to all the attribute tags. But how are you
going to manage this when you get multiple ones.</font></p>
<p><font face="Verdana">F.i. you could say
amenity=restaurant;post_office;butcher (and where does this
stop, at <br>
</font></p>
<p><font face="Verdana">Next brand=brand A; brand B; brand C; brand
D;, <br>
</font></p>
<p><font face="Verdana">Operator= operator A; operator B;</font></p>
<p><font face="Verdana">Which relates or is linked to which ?</font></p>
<p><font face="Verdana">To make that clear I would need</font></p>
<p><font face="Verdana">restaurant:brand=brand A; brand D;<br>
post_office:brand= brand C;<br>
restaurant:operator= operator C;<br>
.... this keys list are going to be very long and longer and
longer<br>
<br>
Where in the contrary, if we would allow nodes as being just
data containers and use relations would be much more simple and
powerful. Maybe we should introduce an additional key to
indicate that these data container nodes are not intended to
provide additional spatial information, like data_node=yes ?<br>
In that situation you remain with one spatial node that provides
the primary purpose of the location and many nodes that are just
data containers. The pure existence of these data nodes should
attend a data consumer that he has to look for a relation or a
spatial link to decide how it needs to be precessed or rendered.<br>
Or, if we don't want a specific data_node=yes one could
introduce a way called "data_link", linking all the data nodes
with the single spatial node but not representing any spatial
feature ?</font></p>
<p><font face="Verdana">Greetings,</font></p>
<p><font face="Verdana">Bert Araali<br>
</font></p>
<div class="moz-cite-prefix">On 28/02/2021 14:04, Georg wrote:<br>
</div>
<blockquote type="cite"
cite="mid:1MAwXh-1l50Hi0WuP-00BIo4@mail.gmx.net">
<br>
<br>
Am 2021-02-27 um 23:03 schrieb Bert -Araali- Van Opstal:
<br>
<br>
<blockquote type="cite">- we want to evolve into a model with
millions of unique keys trying to
<br>
define all kinds of combined uses
<br>
</blockquote>
<br>
We do not need millions of keys, nor values - the amount of keys
&
<br>
values won't change much. The main difference would b, e that we
can use
<br>
multiple values for one single node; please see the posts of
Martin
<br>
(2021-02-27 22:08) and me (2021-02-28 11:28)
<br>
<br>
_______________________________________________
<br>
Tagging mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:Tagging@openstreetmap.org">Tagging@openstreetmap.org</a>
<br>
<a class="moz-txt-link-freetext" href="https://lists.openstreetmap.org/listinfo/tagging">https://lists.openstreetmap.org/listinfo/tagging</a>
<br>
</blockquote>
</body>
</html>