<div dir="auto"><div dir="auto">Already handled by ISO8601:<div dir="auto"><br></div><div dir="auto"><a href="https://en.m.wikipedia.org/wiki/ISO_8601#Durations" target="_blank" rel="noreferrer">https://en.m.wikipedia.org/wiki/ISO_8601#Durations</a><div dir="auto"><br></div><div dir="auto">I think any discussion of dates and times should start by asking if we could apply ISO8601 to the problem at hand. For example the other thread about start date variants.</div><div dir="auto"><br></div><div dir="auto"> Andrew</div></div></div><br><div class="gmail_quote"><div dir="ltr">On Wed, Feb 20, 2019, 12:48 Warin <<a href="mailto:61sundowner@gmail.com" target="_blank" rel="noreferrer">61sundowner@gmail.com</a> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<div class="m_-7721283856072217843m_3609795190658731651moz-cite-prefix">On 20/02/19 10:32, Paul Allen wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div dir="ltr">On Tue, 19 Feb 2019 at 23:16, Warin <<a href="mailto:61sundowner@gmail.com" rel="noreferrer noreferrer" target="_blank">61sundowner@gmail.com</a>>
wrote:<br>
</div>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
<div class="m_-7721283856072217843m_3609795190658731651gmail-m_4677918196867709093moz-cite-prefix">On
19/02/19 22:03, Paul Allen wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div dir="ltr">On Tue, 19 Feb 2019 at 03:48, Warin
<<a href="mailto:61sundowner@gmail.com" rel="noreferrer noreferrer" target="_blank">61sundowner@gmail.com</a>>
wrote:<br>
</div>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Nothing I could
see on the wiki for this. So some guidance would
be good.<br>
<br>
Units.<br>
</blockquote>
<div><br>
</div>
<div>I added a maxstay a few weeks ago and I found
info about units at</div>
<div> <a href="https://wiki.openstreetmap.org/wiki/Key:maxstay" rel="noreferrer noreferrer" target="_blank">https://wiki.openstreetmap.org/wiki/Key:maxstay</a></div>
<div><br>
</div>
<div>Units are not explicitly defined, but there are
several examples. Units in those examples</div>
<div> are minutes, hours, and days. I expect that
weeks, months and years would also be</div>
<div>acceptable for long-stay parking. Maybe even
decades and centuries, should they be</div>
<div> needed. Seconds are too small to be
practicable.<br>
</div>
<div><br>
</div>
</div>
</div>
</blockquote>
No information on default units. <br>
</div>
</blockquote>
<div><br>
</div>
<div>True. But the examples show which units are permissible
and how they should be</div>
<div>specified.</div>
<div><br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF"> There are some numerical values in
the data base without units ... from those values I would
guess hours, but they could be days.<br>
</div>
</blockquote>
<div><br>
</div>
<div>Or minutes, depending on actual value. One place near me
says waiting is limited to 90 minutes.</div>
<div>But 90 days is close to 3 months. Could be either if
units aren't given.<br>
</div>
<div> <br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF"> As there is no documentation 'we'
could make a decision. <br>
<br>
No information on abbreviations.<br>
</div>
</blockquote>
<div><br>
</div>
<div>From the examples, unit names are spelled out in full.</div>
<div><br>
</div>
<div>So the choice is between:</div>
<div><br>
</div>
<div> 1) Spelling units in full (as per the examples) and
specifying which unit is the default.</div>
<div><br>
</div>
<div> 2) Coming up with abbreviations and specifying which
unit is the default.</div>
<div><br>
</div>
<div>I'd go with 1). Firstly, somebody (like me) may have
specified units that way already.</div>
<div>Secondly, different languages may have different names
for those units of time. We can</div>
<div>agree to (mostly) use SI units for mass and length
because those are applicable in much</div>
<div>of the world and have standard abbreviations. Common
time units like minute, hour and</div>
<div>month probably have different abbreviations in different
parts of the world. Less error</div>
<div>prone if an editor drop-down has minutes/hours/days than
m/h/d if "d" is the abbreviation</div>
<div>for a period of 3600 seconds in some language. Thirdly,
minutes and months (m and m).<br>
</div>
<div><br>
</div>
</div>
</div>
</blockquote>
Looks good to me. See what others think. <br>
<br>
On default units .. <br>
Possibly specify the smallest unit as that will cause the least
amount of harm with already entered values? <br>
By that I mean a value of '60' if taken as days would be more
harmful to the user (fines, tow away) than if taken as minutes. <br>
Not convinced on this, but it is a thought. <br>
<br>
</div>
_______________________________________________<br>
Tagging mailing list<br>
<a href="mailto:Tagging@openstreetmap.org" rel="noreferrer noreferrer" target="_blank">Tagging@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/tagging" rel="noreferrer noreferrer noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/tagging</a><br>
</blockquote></div></div>