- From: bergi <bergi@axolotlfarm.org>
- Date: Tue, 9 Feb 2016 11:28:23 +0100
- To: Maik Riechert <m.riechert@reading.ac.uk>, public-sdw-comments@w3.org
Yes, the @geometry property is a custom solution. But the current JSON-LD implementations will just ignore it. The value of the @geometry property defines the predicate for the geometry data. The geometry itself will be stored as a literal. The JavaScript code on the HTML page does that mapping. So after running the code the properties object will have a new property. The key is the value of @geometry and the value is the geometry as literal. Best, bergi On 08.02.2016 15:01, Maik Riechert wrote: > Ok that makes more sense, but I still don't understand how the > "@geometry" thing is supposed to work. It's again a custom solution that > would have to be supported by implementations, right? But I guess that's > the point you're making, namely that linked data should be added to > GeoJSON in a defined and constrained way and that a GeoJSON document > should not be forced to suddenly become a full JSON-LD document. It will > be hard to convince everyone that "properties" is the right container > for all linked data, but the more ideas the better. > > Cheers > Maik > > On 08/02/2016 13:36, bergi wrote: >> Hi Maik, >> >> The Leaflet example uses the proposed GeoJSON structure: >> >> https://raw.githubusercontent.com/zazukoians/geojson-ld/gh-pages/us-states.json >> >> >> The info box up right shows the N-Triples of the current state, but >> the example contains only data for Alabama. >> >> But you are right, I should add this to the description page. I was a >> little bit in a hurry, to publish this document in time for the group >> meeting. >> >> Best, >> bergi >> >> On 08.02.2016 13:35, Maik Riechert wrote: >>> Hi, >>> >>> I don't really understand what you're doing there. I think it would help >>> if you could add some actual GeoJSON examples in your description page. >>> >>> Thanks >>> Maik >>> >>>> Dear all, >>>> >>>> We are currently looking for ways to represent spatial data as Linked >>>> Data and at the same time make sure that it's easy to consume in the >>>> web >>>> stack. After some discussions I've come up with a proposal to embed >>>> JSON-LD in GeoJSON and vice versa. >>>> >>>> Seehttp://zazukoians.github.io/geojson-ld/ for description and example >>>> code. If you have any comments post it here or create an issue on >>>> Github:https://github.com/zazukoians/geojson-ld >>>> >>>> Best, >>>> bergi >>> >
Received on Tuesday, 9 February 2016 10:29:09 UTC