<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 28/01/2016 8:51 PM, Martin
Koppenhoefer wrote:<br>
</div>
<blockquote
cite="mid:CABPTjTDwwFekov=sAnyYRBS=3tGeNa+5MGGKubcJkeZYemXdYA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra"><br>
<div class="gmail_quote">2016-01-27 18:00 GMT+01:00 moltonel
3x Combo <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:moltonel@gmail.com" target="_blank">moltonel@gmail.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div id=":1gp" class="a3s" style="overflow:hidden">You
barely broach the subject of how MV and namespaces
combine. For<br>
example if an object has multiple refs with sources, it
should be<br>
clear wether an MV tag corresponds to "multiple sources
for all the<br>
refs" or to "source for the 2nd ref". In suffix syntax,
this could be<br>
distriinguished by "ref_1=x ref_2=y source_1:ref=a
source_2:ref=b" vs<br>
"ref_1=x ref_2=y source:ref_1=a source:ref_2=b", even
though this is<br>
becoming hairy.</div>
</blockquote>
</div>
<br>
</div>
</div>
</blockquote>
Errr I would rather see <br>
<br>
ref_1=x<br>
source:ref_1=y<br>
<br>
Keep the value the same from the first key to the delimited referrer
= makes it easier for all to recognise and sort. <br>
<blockquote
cite="mid:CABPTjTDwwFekov=sAnyYRBS=3tGeNa+5MGGKubcJkeZYemXdYA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra"><br>
<br clear="all">
</div>
<div class="gmail_extra">I believe we should restructure the way
we use metadata aside with data in the particular tags source
and maybe note and fixme (but not description). We are trying
to convince people to add source tags on the changesets, but
putting them on individual objects still has strong advocates,
so we will likely have to live with it. </div>
</div>
</blockquote>
<br>
Some of my change sets have more than one source, I document to
discriminate the sources as well as I can. But it is a good deal
clear to me if I put it on the way/node/relationship. <br>
<blockquote
cite="mid:CABPTjTDwwFekov=sAnyYRBS=3tGeNa+5MGGKubcJkeZYemXdYA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">As an idea, the source information
could become a subtag of another tag, i.e. rather than being
attached to an object it would be attached to a tag (or to the
position). This could also become more refined with several,
optional formalized source tags, e.g. for the source date, a
source link, a source license(?), etc.<br>
</div>
</div>
</blockquote>
<br>
name:source= ? Rather than source:name=... humm That would make
people think about the source being part of some characteristic of
the object. <br>
<blockquote
cite="mid:CABPTjTDwwFekov=sAnyYRBS=3tGeNa+5MGGKubcJkeZYemXdYA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">cheers,<br>
</div>
<div class="gmail_extra">Martin<br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Tagging mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Tagging@openstreetmap.org">Tagging@openstreetmap.org</a>
<a class="moz-txt-link-freetext" href="https://lists.openstreetmap.org/listinfo/tagging">https://lists.openstreetmap.org/listinfo/tagging</a>
</pre>
</blockquote>
<br>
</body>
</html>