<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><br>
</p>
<div class="moz-cite-prefix">Am 16.10.2021 um 12:09 schrieb Yves via
Tagging:<br>
</div>
<blockquote type="cite"
cite="mid:58DBA8AF-DA7B-4FE4-B7E5-DB9B6EC4402C@mailbox.org">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
If 06:00-25:00 is supposed to be valid, I think it's worth adding
as an exemple on the wiki as some would find it weird.<br>
</blockquote>
<p>It is literally the correct grammar. <br>
</p>
<p>Now the case to do it this way, is likely due to be able to have
time ranges where the end time is numerically larger than the
start time, so say something like <br>
</p>
<p>22:00-47:00</p>
<p>which is not the same as</p>
<p>22:00-23:00</p>
<p>To further use this example, all ranges starting with 22:00 with
end times up to 21:59<br>
</p>
<p>22:00-21:59 <br>
</p>
<p>can be <span style="color: rgb(32, 33, 36); font-family: arial,
sans-serif; font-size: 14px; font-style: normal;
font-variant-ligatures: normal; font-variant-caps: normal;
font-weight: 400; letter-spacing: normal; orphans: 2;
text-align: start; text-indent: 0px; text-transform: none;
white-space: normal; widows: 2; word-spacing: 0px;
-webkit-text-stroke-width: 0px; background-color: rgb(255, 255,
255); text-decoration-thickness: initial; text-decoration-style:
initial; text-decoration-color: initial; display: inline
!important; float: none;">unambiguously parsed without reverting
to the extended notation.</span></p>
<p><span style="color: rgb(32, 33, 36); font-family: arial,
sans-serif; font-size: 14px; font-style: normal;
font-variant-ligatures: normal; font-variant-caps: normal;
font-weight: 400; letter-spacing: normal; orphans: 2;
text-align: start; text-indent: 0px; text-transform: none;
white-space: normal; widows: 2; word-spacing: 0px;
-webkit-text-stroke-width: 0px; background-color: rgb(255, 255,
255); text-decoration-thickness: initial; text-decoration-style:
initial; text-decoration-color: initial; display: inline
!important; float: none;">I would support changing the
specification to make this a legit part of the grammar, but in a
non-haphazard fashion that allows the previous valid values to
work going forward.</span></p>
<p><span style="color: rgb(32, 33, 36); font-family: arial,
sans-serif; font-size: 14px; font-style: normal;
font-variant-ligatures: normal; font-variant-caps: normal;
font-weight: 400; letter-spacing: normal; orphans: 2;
text-align: start; text-indent: 0px; text-transform: none;
white-space: normal; widows: 2; word-spacing: 0px;
-webkit-text-stroke-width: 0px; background-color: rgb(255, 255,
255); text-decoration-thickness: initial; text-decoration-style:
initial; text-decoration-color: initial; display: inline
!important; float: none;">Simon<br>
</span></p>
<blockquote type="cite"
cite="mid:58DBA8AF-DA7B-4FE4-B7E5-DB9B6EC4402C@mailbox.org">Yves <br>
<br>
<div class="gmail_quote">Le 16 octobre 2021 09:09:16 GMT+02:00,
"Shawn K. Quinn" <a class="moz-txt-link-rfc2396E" href="mailto:skquinn@rushpost.com"><skquinn@rushpost.com></a> a écrit :
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
<pre dir="auto" class="k9mail">So apparently at least two different validators disagree on which is
valid syntax for opening times stretching beyond midnight:
opening_hours=Fr-Sa 06:00-01:00
opening_hours=Fr-Sa 06:00-25:00
opening_hours=Fr 06:00-24:00; Sa 00:00-01:00,06:00-24:00; Su 00:00-01:00
(pretend the third one is all on one line; Thunderbird is being weird
about line wrapping)
JOSM throws a warning for the first but not the second. Apparently
Osmose throws a warning for the second but not the first. The third is
unquestionably valid in any validator but (at least IMHO) needlessly
inefficient and clumsy, and something I'd rather avoid having to resort to.
The second has always made more sense to me and I get the impression
that it's actually the preferred syntax per the formal specification on
the wiki (search for "extended_hour"). Unfortunately none of the
examples use it outside of 24:00 (the midnight on which a day ends, i.e.
Fr 24:00 and Sa 00:00 would be the same time) so there are some who
don't think it's valid syntax. Are there any programs which use OSM data
which have issues with hour values above 24, either choking outright or
which interpret them in a buggy fashion? Should bugs be filed with JOSM
and/or Osmose about this?
<div class="k9mail-signature">--
Shawn K. Quinn <a class="moz-txt-link-rfc2396E" href="mailto:skquinn@rushpost.com"><skquinn@rushpost.com></a>
<a href="http://www.rantroulette.com" moz-do-not-send="true">http://www.rantroulette.com</a>
<a href="http://www.skqrecordquest.com" moz-do-not-send="true">http://www.skqrecordquest.com</a><hr>Tagging mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Tagging@openstreetmap.org">Tagging@openstreetmap.org</a>
<a href="https://lists.openstreetmap.org/listinfo/tagging" moz-do-not-send="true">https://lists.openstreetmap.org/listinfo/tagging</a>
</div></pre>
</blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-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>
</body>
</html>