<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi,<br>
<br>
I'm conducting an offline TEC conversation business with Jo and I'm
impressed.<br>
You will soon be able to confidently buy TEC tickets and use the OSM
transport map ;-)<br>
<br>
I have just two tag remarks.<br>
<br>
For the third time (Julien), if we want to use URLs, we'd better use
URLs.<br>
network=tec-wl.be is not an URL as you can see by <a
href="http://www.openstreetmap.org/node/857875464">not being able
to click on it here</a>.<br>
network=<a href="http://tec-wl.be" rel="nofollow">http://tec-wl.be</a>
is one as you can see by <a
href="http://www.openstreetmap.org/node/1645537259">being able to
click on it here</a>.<br>
<br>
I recommend adding <b>source=survey 2014-06 TEC 2014-04</b><br>
Much like <a href="http://wiki.openstreetmap.org/wiki/Key:source"
title="Key:source">Key:<span class="searchmatch">source</span></a>
indicates and I am presently proposing to amend slightly as shown
below.<br>
<br>
The bulk import scenario was clearly written with in mind the idea
to maintain a remaining-to do TEC file.<br>
<br>
Suppose an *.osm file is built from an imported source. The map
contributors are requested to move/update the map elements to
osm.org after verifications such as coordinates. If the *.osm map
elements contain a survey value such as source=survey
<import-date>, then a program can find out by checking for an
equal or later survey date what map elements have been moved/updated
to osm.org and hence build a remaining.osm file containing what
remains to be done. A FIXME can be added at import time to already
existing osm.org elements to warn about the ongoing import.
<br>
<br>
Cheers,<br>
<br>
<table>
<tbody>
<tr>
<td>André.</td>
</tr>
</tbody>
</table>
<br>
<blockquote type="cite">Following this discussion here is a proposed
clarification to <a
href="http://wiki.openstreetmap.org/wiki/Key:source"
title="Key:source">Key:<span class="searchmatch">source</span></a>.<br>
The goal is to define the word, make date mandatory, use ISO
format, define per source tag meaning.<br>
Is there any objection or suggestion for changes?<br>
<br>
<b>survey</b> yyyy-mm[-dd] (with one blank and an <a
href="http://www.google.be/url?sa=t&rct=j&q=&esrc=s&source=web&cd=3&cad=rja&uact=8&sqi=2&ved=0CDAQFjAC&url=http%3A%2F%2Fwww.iso.org%2Fiso%2Ffr%2Fhome%2Fstandards%2Fiso8601.htm&ei=X3qZU_CEPNHR4QT34YGwCg&usg=AFQjCNHMm5_cA8CzTjEvrWYQc5GZ9K1wLg&sig2=m6xdSXuaBGqt6Qlj0tCfTw&bvm=bv.68911936,d.bGE"
onmousedown="return
rwt(this,'','','','3','AFQjCNHMm5_cA8CzTjEvrWYQc5GZ9K1wLg','m6xdSXuaBGqt6Qlj0tCfTw','0CDAQFjAC','','',event)"
target="_blank"><em>ISO</em> 8601</a> format date) can be used
within the data of any source.KEY=* or source=* tag to indicate
that, on that date, the source(s) of KEY were the most recent and
the data was verified to be correct for that KEY. In source=*,
survey means the same for all possible (required) keys (even those
absent by default), but it can be overridden by survey in some
source.KEY tags. survey helps to avoid making already done
verifications, especially because a source publication date is not
a verification date. survey can contain the date of dateless
sources like visual or knowledge. It can help humanly assisted
bulk imports. Please update the survey date of what you verify (a
substantial time later), even if you don't add survey dates
yourself.<br>
</blockquote>
<br>
</body>
</html>