[GeoJSON] Integrating GeoJSON with other kinds of data via JDIL

[chris goad]

Hi Allan,


> However, I'd like to see a
> few parallel examples of GeoJSON and GeoJDIL just to better
> understand the implications.

I added a very simple example of GeoJSON to the JDIL doc at 
http://jdil.org/#GeoJSON  . It illustrates the basic point that GeoJSON can 
be mixed into RSS providing, in effect, a JSON alternative to GeoRSS feeds. 
Of course there are plenty of other examples (eg mixing in domain specific 
vocabularies for things such as  weather or geology) that would further 
emphasize the mixing-of-data point.  Do you have recommendations or 
requests?  Once I get GeoJSON support into the Platial feeds, and include 
domain specific content in those feeds (both of which are coming along 
soon), plenty of examples will be available.

-- Chris


----- Original Message ----- 
From: "Allan Doyle" <adoyle at eogeo.org>
To: <geojson at lists.geojson.org>
Sent: Friday, June 01, 2007 8:29 AM
Subject: Re: [GeoJSON] Integrating GeoJSON with other kinds of data via JDIL


> Chris,
>
> I think there would be a willingness to support this if it's really
> as minor as adding the namespaces member. However, I'd like to see a
> few parallel examples of GeoJSON and GeoJDIL just to better
> understand the implications.
>
> Allan
>
> On Jun 1, 2007, at 11:20, chris goad wrote:
>
>> I've been working with JSON for geo for a year or so at Platial. I
>> love the simplicity and conciseness of JSON, but there were things
>> that I missed from earlier work with RDF - not the whole  stack,
>> but basic capabilities for data integration. JDIL  (Jason Data
>> Integration Layer -  http://jdil.org )  , which I formulated
>> earlier this year, was my stab at retrieving what was missing; JDIL
>> has nothing specific to do with geo, but implementing geo inside
>> JDIL makes it play well with other data.
>>
>> Briefly stated, JDIL is a thin encoding on top of JSON  which adds
>> namespaces, and labeling of objects for representing object graphs
>> as well as trees.  Labels may be URIs, which supports merging of
>> property-value assertions from different sources about the same
>> object.   JDIL implements the core of the RDF data model  within
>> JSON,  though RDF need not be mentioned in explanations of JDIL.
>>
>> Minor changes in GeoJSON would make it compliant with JDIL's
>> conventions, and as a consequence would allow  GeoJSON to  mixed
>> with other kinds of data in a wider range of applications. This is
>> an important benefit, since geo applications that involve data of
>> other varieties are the norm rather than the exception.  The
>> changes : 1)  support the namespace construct, and allocate a URI
>> for the GeoJSON namespace, 2) utilize the generic JDIL "@type" name
>> for the type-of concept.
>>
>> In pure geo applications (eg sending feature geometry off to a
>> client for rendering), the overhead is miniscule. A pure GeoJSON
>> file would need only  include  this property in the root object:
>>
>> "@namespaces":  {"":"http://whateverthegeojsonuriturnsouttobe"}
>>
>> This specifies a blank prefix for the GeoJSON namespace, removing
>> the need to prefix GeoJSON properties in the body.
>>
>> Platial supports JDIL in its feeds and api, with GeoRSS properties
>> carrying the geo.  I'd like to add support for GeoJSON as well.
>>
>>
>> -- Chris
>>
>> _______________________________________________
>> geojson mailing list
>> geojson at lists.geojson.org
>> http://lists.geojson.org/listinfo.cgi/geojson-geojson.org
>
> -- 
> Allan Doyle
> +1.781.433.2695
> adoyle at eogeo.org
>
>
>
> _______________________________________________
> geojson mailing list
> geojson at lists.geojson.org
> http://lists.geojson.org/listinfo.cgi/geojson-geojson.org