[GeoJSON] GeoJSON Digest, Vol 64, Issue 3

[Jeff Yutzler]

Howard,
> strong case about why it is in scope for GeoJSON
Some stuff changes its geometry over time and I want a
consistent/interoperable way to encode that.

> to place the burden of it on all implementors of GeoJSON
I don't want to burden anyone either which is why I support a
core/extensions model. If you guys aren't willing to entertain that then
this is probably the wrong forum.

> already done, widely accepted, and frequently implemented and say "use
that"
I am not aware of anything that does for "when" what GeoJSON does for
"where" nor am I aware of any initiative that is on the right path to doing
so.
-Jeff






On Thu, Apr 3, 2014 at 2:00 PM, Howard Butler <howard at hobu.co> wrote:

>
> On Apr 3, 2014, at 12:41 PM, Jeff Yutzler <jeffy at imagemattersllc.com>
> wrote:
>
> > I would be interested in hearing from the other GeoJSON contributors. If
> temporal support is in fact a non-starter for GeoJSON, perhaps a separate
> initiative should be established for the purpose. It would be disappointing
> for time to be considered "out of scope" for this group but IMHO the
> Wild-West status quo is worse.
>
> I have no strong opinion either way, but I would ask those clamoring for
> time support in GeoJSON to make a strong case about why it is in scope for
> GeoJSON. The problem of encoding time in JSON would seem to exist in a
> plethora of domains other than Geo. What makes it the mixing of time in
> GeoJSON compelling enough to place the burden of it on all implementors of
> GeoJSON?
>
> My inner lazy ass would like to just point people at something that's
> already done, widely accepted, and frequently implemented and say "use
> that". Why can't that scenario be true today? Will it be true in some
> future tomorrow?
>
> Howard




-- 
Jeff Yutzler
Image Matters LLC
Mobile: (703) 981-8753
Office: (703) 428-6731
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.geojson.org/pipermail/geojson-geojson.org/attachments/20140403/39bfc626/attachment.htm>