Re Namespaces: In applications where different varieties of data are
being mingled, namespaces are of course the standard disambiguation
technique. Even if a particular job involves encoding one fixed
formalism where name collisions are not a concern, maybe someone else
will be interested in mingling what's been produced with other content.
Don't get me wrong, I'm a fan of namespaces, and completely understand
their utility. I'd just like to see a consensus of the way to do them
right in JSON. Maybe JDIL will be it, but I feel some serious promotion
needs to be done to get it to be a standard or even pseudo-standard.
That's not a problem I feel a need to work on.
If there's a solution it will be easy for me to implement - all data in
GeoServer requires a namespace (though many still don't understand this
and use the default...)
I'd prefer to get general consensus on
namespacing json from a standards organization.
Me too, but didn't find any. With OGC moving in this direction ... ?
The geo component, however, is, as it's a small enough community to get
a grasp on. I just chatted with Sean about his ideas for approaching
mutli-geometries and holes in polygons (two areas that GeoRSS simple
punts on, since there is GeoRSS GML to handle them) in a js friendly
way. So I'll code those up and post some examples, and maybe between
the group of us we can get some consensus. And Cameron and I can take
it to the OGC, maybe post something on OSGeo as well.
best regards,
Chris
But past that I'd really like to figure out some consensus on how to
encode lines, polygons, and collections of geometries in to JSON.
Indeed - JSON provides an encoding of trees. JDIL is one way of
extending this to graphs with URI-labeled nodes. Encoding various
domain-specific entities as labeled graphs is the next level in this
direction of work. Needless to say, ports of GML encodings is one way
to go.
-- Chris
----- Original Message ----- From: "Chris Holmes" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Tuesday, February 06, 2007 12:58 PM
Subject: Re: [Geowanking] JSON for GEO
As a side note, I think the Chris Holmes has included JSON as an output
format for Geoserver.
Yeah, I've been meaning to blog about it and make it available for
download, as a plug in to GeoServer. But got swamped last month.
I drew inspiration from Sean's stuff, but wasn't sure how to handle
geometry types other than points. I was going to call mine 'Simple
Features for JSON', in line with Simple Features for SQL, which defined
Well Known Text for representing geographic features. It was easiest
for me to do the same - I just used a .toWKT() function to make my
geometry.
But I'm in no way tied to doing things that way, I just wanted to start
a conversation and hopefully work towards standardization.
At first pass jdil.org feels a bit more heavyweight than I was going
for, doing all the namespaces. And it seems to really just focus on
doing the namespaces. I'd prefer to get general consensus on
namespacing json from a standards organization, I've seen a few others
talk about it and do it slightly different ways.
If there's consensus on that it'd be easy to just write GML output as
JSON, with namespaces and all.
But past that I'd really like to figure out some consensus on how to
encode lines, polygons, and collections of geometries in to JSON. Maybe
that just involves me asking Sean to add some more examples on how he
wants to do that in GeoJSON, as I have no strong preference, just want
to standardize on something.
Chris
chris goad wrote:
Hi,
http://jdil.org describes a simple scheme for implementing namespaced
vocabularies (including RDF vocabularies) in JSON. The idea is
general, but the examples (and our own applications here at Platial)
are in the Geo domain.
-- Chris
------------------------------------------------------------------------
_______________________________________________
Geowanking mailing list
[email protected]
http://lists.burri.to/mailman/listinfo/geowanking
--
Chris Holmes
The Open Planning Project
http://topp.openplans.org
_______________________________________________
Geowanking mailing list
[email protected]
http://lists.burri.to/mailman/listinfo/geowanking
!DSPAM:1003,45c8f7df146511410093335!
--
Chris Holmes
The Open Planning Project
http://topp.openplans.org
begin:vcard
fn:Chris Holmes
n:Holmes;Chris
org:The Open Planning Project
adr:;;349 W. 12th Street, #3;New York;NY;10014;USA
email;internet:[EMAIL PROTECTED]
title:Managing Director, Strategic Development
x-mozilla-html:FALSE
url:http://topp.openplans.org
version:2.1
end:vcard
_______________________________________________
Geowanking mailing list
[email protected]
http://lists.burri.to/mailman/listinfo/geowanking
