<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 2018-11-18 13:47, Jo wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAJ6DwMB_ruC5rqLMb=MBdeLv0EZ5yP4hBRhX0a6-fUUurR_FjA@mail.gmail.com">
<div dir="ltr">Frank,
<div><br>
</div>
<div>url wasn't used yet on the bus stops, so no conflict there.</div>
</div>
</blockquote>
Jakka's point is not that "url" is used but that it could be wanted
and that this usage would prevent it.<br>
To prevent the "first jumping on it owns it" practice, the good move
would be to consider that anything:url is <b>officially</b> an URL.<br>
"being officially" meaning principally that listings make it a
clickable link.<br>
Even though any URL can be recognized inside any text and made
clickable.<br>
But I've had problems suggesting to make multiple tags containing
URLs clickable.<br>
The answer was: "the URL tag exists already" <span
class="moz-smiley-s3"><span>;-)</span></span><br>
<br>
All the best,
<br>
<br>
<table>
<tbody>
<tr>
<td>André.</td>
</tr>
</tbody>
</table>
<br>
<blockquote type="cite"
cite="mid:CAJ6DwMB_ruC5rqLMb=MBdeLv0EZ5yP4hBRhX0a6-fUUurR_FjA@mail.gmail.com">
<div dir="ltr">
<div>Pieter, good to hear De Lijn plans such deep links. I think
it will be good to have them on our route_master relations.
The route relations are for the longest variations in
itinerary, not sure if they fit there.</div>
<div><br>
</div>
<div>For the stops, I tend to like the <a
href="http://mijnlijn.be/" moz-do-not-send="true">mijnlijn.be/</a>
form, as that is the information printed on each of the paper
schedules on the stops. So if De Lijn is not planning to
abolish those in the medium term, I'd prefer to use them. I'll
hold off with preparing the data and launching the Project of
the Month though.</div>
<div><br>
</div>
<div>Pieter, is De Lijn planning to introduce uic identifiers we
could put in uic_ref?</div>
<div><br>
</div>
<div>We don't have anything that corresponds to the zones in
OSM. I'm curious to find out what will be behind those urls. I
painstakinglly added the zone information on the stops, but
now that a ticket has a time limitation instead of a zone
dependent one, they became less relevant.</div>
<div><br>
</div>
<div>Marc, we can leave the ref:De_Lijn tags. I'm not strongly
against keeping them, but I doubt anyone uses them (except me
in my integraton scripts). If anyone wants to use them, it's
trivial to extract the identifiers from the url tag values.</div>
<div><br>
</div>
<div>There is another tag I'd like to introduce. While reviewing
the import of bus stops around Finland, they added a direction
tag.</div>
<div><br>
</div>
<div>My first reflex was to remove it after reviewing the stop,
but now I start to see value in knowing in which direction the
bus will leave. I plan to add functionality to PT_Assistant to
calculate it automatically based on the segment of the way the
stop is adjacent to. And in a second stage a validator rule
that checks whether the stop is (still) on the correct side of
the road (right or left, depending on the side of the road
vehicles drive on)</div>
<div><br>
</div>
<div>Polyglot</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div> </div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr">El dom., 18 nov. 2018 a las 11:19, Pieter
Colpaert (<<a href="mailto:pieter@openknowledge.be"
moz-do-not-send="true">pieter@openknowledge.be</a>>)
escribió:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Polyglot,<br>
<br>
We are in a Linked Data project with De Lijn and we’re going
to have <br>
official persistent identifiers (HTTP URIs) soon for stops
(but also for <br>
things like the routes and zones). It might be interesting to
integrate <br>
these in OSM rather than the <a href="http://mijnlijn.be"
rel="noreferrer" target="_blank" moz-do-not-send="true">mijnlijn.be</a>
one?<br>
<br>
From the moment we have an official URI strategy, I will get
back to <br>
this list in each case.<br>
<br>
Kind regards,<br>
<br>
Pieter<br>
<br>
On 18/11/18 11:10, Jakka wrote:<br>
> Using key as "url=" not comming in conflict with already
other keys <br>
> that use short key url ?<br>
><br>
> Op 18/11/2018 om 10:51 schreef Jo:<br>
>> Our bus stops in Flanders have unique identifiers
visible to the public<br>
>> on the flags of the stop poles.<br>
>><br>
>> I started by entering those in the ref tag, then
later decided to use<br>
>> ref:De_Lijn=y0yyyy, as some of those stops are served
by other operators<br>
>> as well.<br>
>><br>
>> For several years now itt's possible to obtain
real-time information<br>
>> about the buses on a url+identifier, so I want to add
that to those<br>
>> stops. As i don't like to duplicate information I'd
prefer to drop the<br>
>> ref:De_Lijn though.<br>
>><br>
>> So all of those stops would have:<br>
>> url=<a href="http://mijnlijn.be/303079"
rel="noreferrer" target="_blank" moz-do-not-send="true">http://mijnlijn.be/303079</a>
(<- you can test this, the url is<br>
>> expanded/translated to a url on <a
href="http://www.delijn.be" rel="noreferrer" target="_blank"
moz-do-not-send="true">www.delijn.be</a> <<a
href="http://www.delijn.be" rel="noreferrer" target="_blank"
moz-do-not-send="true">http://www.delijn.be</a>>)<br>
>><br>
>> For the conversion, I'd like to launch a Belgian
"Project of the month",<br>
>> so the position of the stops can be verified once
more by locals, but<br>
>> also shelters and bus_bays can be added and if cycle
ways split off to<br>
>> go around those bus bays, that detail can be added as
well.<br>
>><br>
>> I know that that is what we have been doing for the
past 5+ years, but<br>
>> now it would get some more dedicated focus.<br>
>><br>
>> For several years I thought having the identifier n a
dedicated ref:X<br>
>> tag and then telling everyone about how to turn it
into such a url was<br>
>> the way to go,. That doesn't actually work though.
Nobody knows how to<br>
>> get from the identifer to the url. Giving potential
passengers a url<br>
>> they can simply click through on, seems to be the
better way of doing<br>
>> this for this use case.<br>
>><br>
>> Polyglot<br>
>><br>
>><br>
>> _______________________________________________<br>
>> Talk-be mailing list<br>
>> <a href="mailto:Talk-be@openstreetmap.org"
target="_blank" moz-do-not-send="true">Talk-be@openstreetmap.org</a><br>
>> <a
href="https://lists.openstreetmap.org/listinfo/talk-be"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.openstreetmap.org/listinfo/talk-be</a><br>
>><br>
><br>
><br>
><br>
> _______________________________________________<br>
> Talk-be mailing list<br>
> <a href="mailto:Talk-be@openstreetmap.org"
target="_blank" moz-do-not-send="true">Talk-be@openstreetmap.org</a><br>
> <a
href="https://lists.openstreetmap.org/listinfo/talk-be"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.openstreetmap.org/listinfo/talk-be</a><br>
<br>
-- <br>
+32486747122<br>
<br>
<br>
_______________________________________________<br>
Talk-be mailing list<br>
<a href="mailto:Talk-be@openstreetmap.org" target="_blank"
moz-do-not-send="true">Talk-be@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/talk-be"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.openstreetmap.org/listinfo/talk-be</a><br>
</blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Talk-be mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Talk-be@openstreetmap.org">Talk-be@openstreetmap.org</a>
<a class="moz-txt-link-freetext" href="https://lists.openstreetmap.org/listinfo/talk-be">https://lists.openstreetmap.org/listinfo/talk-be</a>
</pre>
</blockquote>
<br>
</body>
</html>