Roy Wallace wrote:
> You don't need "all maxspeeds" to be in a single value. Nor would it
> break existing applications. Maxspeed=* is still maxspeed=*. You would
> be adding additional keys such as maxspeed:time, or maxspeed:vehicle,
> or maxspeed:weather, etc.
That seems to be superior to other
On Sat, Aug 8, 2009 at 10:49 AM, Tobias Knerr wrote:
> Roy Wallace wrote:
>> You don't need "all maxspeeds" to be in a single value. Nor would it
>> break existing applications. Maxspeed=* is still maxspeed=*. You would
>> be adding additional keys such as maxspeed:time, or maxspeed:vehicle,
>> or
2009/8/8 Roy Wallace :
>
> maxspeed:vehicle:weather = hgv;wet;|motorcycle;wet;
>
> Actually that's quite readable...
>
We already use the : format for translations, so why don't use it for
time periods and the weather. Make sence to me.
Very useful for parking restrictions as well.
I'm guessing
Martin Koppenhoefer wrote
> I can't really see the point of not putting values in keys
> actually. Aren't we already doing this in many tags?
>
> why is this a value in the key:
> maxspeed:wet=40
> couldn't you interpret "maxspeed:wet" as a key? The maxspeed in wet
> condition? Could you explain t
On Sat, Aug 8, 2009 at 8:14 AM, Tobias Knerr wrote:
> - conditions in values:
>
> Also possible, but means all information of the same category (e.g. all
> maxspeeds) will be in a single value, which will result in rather long
> tags. It will also break existing applications unless you redundantly
5 matches
Mail list logo
