Re: [Geojson] Requests for comments on GeoJSON Events draft

[Sean Gillies <[e-mail]>]

Hi Erik,

On Wed, Jan 4, 2017 at 5:50 PM, Erik Wilde <[e-mail]> wrote:

> hello sean.
>
> happy new year to you (and everybody), too!
>
> On 2017-01-04 02:32, Sean Gillies wrote:
>
>> * To set an example for other extension projects.
>>
>
> great work with the events draft! one thing that came to my mind when i
> looked at this: we did not do this for the GeoJSON RFC, but it seems that
> maybe we should have thought of a registry where extensions like this can
> be registered? maybe i have become too obsessed with registries lately, but
> it's in cases like this where in the end it might be very helpful to have a
> place where you can see who/how "where" was defined, and that will allow
> this to be defined and discovered in an open and unambiguous way.
>
> https://github.com/dret/GeoJSON-X is where i played around with an idea
> similar to yours (not the events, but the extension model) a little while
> back, but this was different because it was not (just) about top-level
> extensions (and i think this is now specifically disallowed by what ended
> up being the final RFC text).
>
> any thoughts? thanks and cheers,
>
> dret.
>

For an application to find out what "where" means, I think we need either a
registry or JSON-LD (which is sort of like a framework for using the web as
a registry, also entailing a lot of other things). I'm more inclined to a
registry. I think we got the sense that adding a registry to the GeoJSON
I-D was not going to reach consensus and now we need to add it on after the
fact, in a grassroots way. Are there other registries we can piggyback on
or would we need to create a new site for this?

-- 
Sean Gillies