[GeoJSON] Future plans for GeoJSON

[Sean Gillies]

Hi Stefan,

I remain interested in submitting a draft to the IETF and would love help.
In fact, it's clear that I need help. I've been squatting on the idea of
doing it for some time and am embarrassed to have done nothing much about
it. I don't know if you've been through the process before, but I have some
friends and mentors that have and am sure of getting good advice.

One thing I'd like to consider, either before or during the process, would
be to strip out the CRS parts of the specification that get very little
use. Specifically, the linked and named CRS types. I've only seen
non-long/lat GeoJSON in the wild a couple times (City of Chicago's open
data is one) and the producers aren't following the specification with
regards to CRS. This suggests to me that those parts of the spec are either
broken or superfluous.



On Fri, Apr 26, 2013 at 9:19 AM, Stefan Drees <stefan at drees.name> wrote:

> On 26.04.13 16:51, Jerry Sievert wrote:
>
>> I for one, would be very sad to see GeoJSON go the way of OAuth:
>>
>> http://hueniverse.com/2012/07/**oauth-2-0-and-the-road-to-**hell/<http://hueniverse.com/2012/07/oauth-2-0-and-the-road-to-hell/>
>>
>
> thanks for the pointer. Lots of interesting comments also.
> With respect to the suggested submission target IETF, I'd assume it to be
> more like the person claiming to be "Julian Reschke" commented: "[...] it
> is unfair to say that what happened here is what happens throughout the
> IETF. I’ve seen all kinds of Working Groups, some dysfunctional, some
> working great but slowly (ahem), some working just right [...]".
>
>
>  GeoJSON is clean, flexible, and easy to implement and work with (we use
>> it as the base commonality in Terraformer -
>> https://github.com/esri/**Terraformer<https://github.com/esri/Terraformer>),
>> and I would hate to see a
>> standards body destroy that.
>>
>
> cool project. Esp. the AMD capability working with loaders like dojo (I
> often use) and RequireJS. Another thing to try out ;-)
>
> I assume, that this pragmatic  and clean (through constraints)
> specification, will remain intact after submission.
>
>  Just my 2 cents.
>>
>>
> That is the clear target and I read this intention (in keeping it this
> way) as the "declared will of the authors" also in the mails of most
> members of this community.
>
>
> Stefan.
>
>>
>> On Fri, Apr 26, 2013 at 7:07 AM, Stefan Drees <stefan at drees.name
>> <mailto:stefan at drees.name>> wrote:
>>
>>     On 26.04.13 15:51, Howard Butler wrote:
>>
>>         ...
>>
>>         I think an IETF submission is a nice-to-have rather than a
>>         have-to-have for the GeoJSON community. IIRC, at the time there
>>         was some
>>         discussion about bringing it forward, and it's clear that the IETF
>>         process and format inspired the specification document itself
>>         (this came
>>         from Sean, IIRC). I personally see no problem with it, but I
>>         also don't
>>         have the bandwidth to make it happen. Someone with a strong
>>         desire and
>>         time to shepherd it through the process would need to do that.
>>         It sounds
>>         like you have a strong desire to do so...
>>
>>
>>     indeed the GeoJSON community would probably already had undertaken
>>     these steps, if it had been a MUST. I am happy, that you personally
>>     see no problem with submitting to IETF, as I think it would be a
>>     good place for this pragmatic spec.
>>
>>     I already offered my support in shepherding and hereby add to it,
>>     that I'd really like to make it happen as long it is clear, that I
>>     a) do not expect my name to be added as (if I had been) one of the
>>     editors and claimed any credit I do not want to claim, and b) it is
>>     ok for the authors, that I actually do start the submittal process.
>>
>>     So what do the others in the community think and how shall I proceed?
>>
>>     Stefan.
>>
>
> ______________________________**_________________
> GeoJSON mailing list
> GeoJSON at lists.geojson.org
> http://lists.geojson.org/**listinfo.cgi/geojson-geojson.**org<http://lists.geojson.org/listinfo.cgi/geojson-geojson.org>
>



-- 
Sean Gillies
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.geojson.org/pipermail/geojson-geojson.org/attachments/20130426/2f9cec27/attachment.htm>