Hi Eckhart.

With a rough scan only - so no details about the content of your wiki page:
Yes, I think it's useful to have this kind of documentation, but IMHO it's not a good replacement, but an addition to the example based one. To understand a technical documentation like that you have to understand everything. To use simple examples it's sufficient to find one that nearly fits and adapt it to the individual needs, most of the time this satisfies opening hours, collecting times and much more tags.

I agree, that a more formal description and documentation is useful, and that this documentation should be the base to check the more human readable documentation (e.g. the example based one) against, but to replace it excludes less technical people from this tag even more than currently, where it's already a slightly complicated one (that's no offense, but a fact IMHO).

regards
Peter

Am 04.11.2012 19:05, schrieb Eckhart Wörner:
Hi everybody,

as you probably know, all condition-related proposals and specifically the 
accepted Conditional Restrictions depend on the opening_hours syntax for time 
domains.
However, the whole page is a huge mess. It tries to define the syntax using 
examples (which is doomed to fail). In consequence, none of the existing 
implementations even get the full set of examples right, and the list of 
deviations is quite long.

Therefore, I've started another approach at time domains, with the following 
objectives:
- has to be implementable
- reuses opening_hours syntax as much as reasonable
- is properly defined
- is reasonably complete
- is reasonably extensible

The result can be seen in 
http://wiki.openstreetmap.org/wiki/Proposed_features/Time_domains

As this is an RFC, comments are of course welcome.

Eckhart

_______________________________________________
Tagging mailing list
[email protected]
http://lists.openstreetmap.org/listinfo/tagging



_______________________________________________
Tagging mailing list
[email protected]
http://lists.openstreetmap.org/listinfo/tagging

Reply via email to