>
>
>
> Totally and completely agree. The problem as I see it is that to
> achieve both 'Common Usage' _and_ adhere to the spec, we introduce a
> difference in behavior - if 2012 means all of 2012 excluding
> 2013-01-01T00:00:00Z but 2012/2013 means _including_ that first day of
> the new year (as per the spec), then this would bad™. I again submit
> the evidence that in many domains, single increments on a precision
> element (e.g. 1 year, 1 month, etc.) are _not_ standard or common
> usage (think census data, seasonal weather deviations from norm,
> stream gauge-data, weather forecasts, etc.).
>
My reading of ISO8601 is that lists (,) and ranges (/) are extending the
basic time syntax that can have precision by dropping time arguments right
to left. With that, I would read that 2012 and 2013 alone always represent
the entire year and as such 2012/2013 is the entirety of both years (which
to me is a great easy to express syntax).
The big issue here is that I believe to be "correct" any ranges must have
the same precision on both the from and to sides. 2012/2013-01-01 should
not be valid.
With regards to clients never manually using ISO8601 strings, while they
may not be putting them in the url manually, having a text box to enter
ISO8601 strings including ranges and lists as part of a client is really
quite handy. I have an application that does this and it allows much
quicker (particularly with the shortcut of being able to use reduced
precision) ability to do things like look at the first day of every month
or to pull up January from each of the last three years in one step.
David
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
