Hi Adam,

Thanks for sharing this discussion with the public list. I'll comment 
specifically
below on your suggestions:

On Feb 1, 2012, at 7:57 AM, Adam Estrada wrote:

> FYI
> 
> ---------- Forwarded message ----------
> From: Adam Estrada <[email protected]>
> Date: Tue, Jan 31, 2012 at 1:37 PM
> Subject: Re: Implementing GeoSPARQL
> To: [email protected]
> 
> 
> Mattmann,
> 
> Check out the GeoRSS page for more information on the variants of GeoRSS.
> http://georss.org/Main_Page. I also think that GeoJSON via Jackson has some
> merit as well. Should a middle tier "translation" class be implemented to
> handle real time query responses in different formats?

Yep I think this is definitely something that we could implement in SIS and 
that 
I think fits with the goals of the project.

> I do think that
> GeoSPARQL is cool but there not really that many clients supporting it, are
> there?

That would be something I'd have to defer to an RDF/OWL expert or someone like 
Andy to comment/answer on. I'll ask the Any23 community folks that I'm mentoring
what they think too.

> Could this be a game changer for linked data?

I think it could be. 

> As for data size, I
> would always suggest the Geonames database as a good benchmarking data set.

+1

> http://download.geonames.org/export/dump/allCountries.zip There are lots of
> examples on the web on how to work with these ~9 million points.

Yep, you interested in working with Andy and me on fleshing out some basic use
cases and code for this?

Cheers,
Chris

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: [email protected]
WWW:   http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Reply via email to