[OSM-dev] Opening hours

Thomas Meller thomas.meller at gmx.net
Thu May 6 18:30:49 BST 2010

Complicated, yes.
You cannot avoid complexity if you want to cover all cases.

You could instead invent a language to put in the value in whole.
Or you can decide to not be able to cover complex opening hours.

A linked list at least leaves the option to define simple opening hours in a slim format instead of using the complicated scheme, without a syntactic effort in the OSM db.

If it were only for an online service, the solution could be hidden from the apps. But OSM isn't an online service.

pity (?)

-------- Original-Nachricht --------
> Datum: Fri, 7 May 2010 03:16:30 +1000
> Von: John Smith <deltafoxtrot256 at gmail.com>
> An: OpenStreetMap Developers <dev at openstreetmap.org>
> Betreff: Re: [OSM-dev] Opening hours

> On 7 May 2010 03:00, Thomas Meller <thomas.meller at gmx.net> wrote:
> > I have spent some thought on a simple linked list like in this template:
> >
> > tag:next_tag=expression
> > next_tag:third_tag=expression
> > third_tag:following_tag=expression
> > following_tag=[validity|AND|OR|XOR] *which may be followed by even more
> tags
> Is there a good reason to make things increasingly complex?
> Things are already complex enough at present, to the point people
> don't often tag this kind of information...
> > validity={restriction enabled|disabled} *always last in chain
> I've already applied this sort of thinking to school zones, during
> certain times of the day the speed limit will be lowered.
> http://wiki.openstreetmap.org/wiki/Proposed_features/Tag:restriction%3Dschool_zone
> However I can't think of any examples when the restriction happens the
> majority of the time so I'm not sure what the advantage of making
> things overly complicated in this case.
> _______________________________________________
> dev mailing list
> dev at openstreetmap.org
> http://lists.openstreetmap.org/listinfo/dev


GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

More information about the dev mailing list