- From: Richard Newman <r.newman@reading.ac.uk>
- Date: Wed, 10 Aug 2005 09:33:34 -0700
- To: semantic-web@w3.org
- Message-Id: <C5EF3C53-1D60-4F71-A42A-908ABD8B8B6A@reading.ac.uk>
Dan, all, I've taken a long-running interest in this kind of thing, and it recently came up in an email discussion, so I've got a chunk pre- prepared! These are ones I've found: --- • Discussion of the topic: <http://space.frot.org/ontology.html> --- • Cyc: "This document describes collections, predicates and other Cyc constants that are used to represent spatial objects and relations. See also documents for Groups, Quantities, Movement, Paths & Trajectories, Parts Of Objects, and Geography." <http://www.cyc.com/cycdoc/vocab/spatial-vocab.html> <http://opencyc.sourceforge.net/daml/cyc.daml#> and <http:// www.cyc.com/2004/06/04/cyc#> --- • Geo, one of my favourites for its simplicity. <http://www.w3.org/2003/01/geo/wgs84_pos#> <http://www.schemaweb.info/schema/SchemaDetails.aspx?id=42> --- • GeoURL defines a competing pair of lat/long properties, which is annoying. <http://geourl.org/news/2005/04/26/rssplus.html> --- • Geometry. "RDFGeom2d defines a set of RDF classes and properties for two- dimensional geometry." <http://www.mapbureau.com/rdfgeom2d1.0/index.html> --- • Mindswap geo ontologies. "We've created three ontologies for geoStuff which express a base set of geographic features such as countries and cities, their spatial descriptors such as points and multipolygons, and relationships between these spatial descriptors, as described below." <http://www.mindswap.org/2004/geo/geoOntologies.shtml> <http://www.mindswap.org/2003/owl/geo/geoFeatures20040307.owl#> <http://www.mindswap.org/2003/owl/geo/geoRelations20040307.owl#> --- • Airports: <http://www.daml.org/cgi-bin/airport?> --- • Loc, which describes location roles etc.: <http://www.site.uottawa.ca/~mkhedr/Ontologies/Location#> --- Also of relevance are the whois: and bio: ontologies (specifically bio:place), but I'll let others discuss those. Finally, I have my own "places" vocabulary, in which I have (a) some annotated places, using these vocabularies, and (b) a few vocabulary terms: • placename, to specifically name places • pub, restaurant, etc. -- location roles for the Loc vocabulary. This ontology lives at <http://www.holygoat.co.uk/owl/places/> I hope that lot is of some interest. -R On 10 Aug 2005, at 05:50, Dan Brickley wrote: > > (attachment forwarded from a geo/mapping hackers list.) > > I'm interested to learn of any RDF vocabularies that folk > here have knowledge of (especially backed by running code, > data, community etc...). There is, as some of you will know, > a small lat/long-etc vocab at http://www.w3.org/2003/01/geo/ > that was produced by Interest Group collaborations (mostly in > #rdfig IRC chat sessions a couple years ago). Lately I have been > investigating the uptake of that namespace in the RSS scene, > and looking at Google's KML (formerly Keyhole, now used by > the rather fun http://earth.google.com/ application). > > If you have an RDF vocabulary or dataset that has a mapping, > geographical, lat/long etc component (including place name > databases), do let me know, ideally in this thread of by updating > the public Wiki page at http://esw.w3.org/topic/GeoInfo > > I'm particularly interested in hearing from any W3C Members > on this topic, and in collecting perspectives on how "lightweight" > (RSS-friendly) extensions might relate to more sophisticated standards > such as the OGC's GML work (from which KML seems to draw). Mixing > geographic with other non-geographic data is one of the advantages > we would > expect from using RDF; I'm interested to put that to the test by > building > some demos on top of a SPARQL database. Suggestions welcomed! > > cheers, > > Dan > > From: Mikel Maron <mikel_maron@yahoo.com> > Date: 10 August 2005 05:38:49 GMT-07:00 > To: geowanking@lists.burri.to > Subject: [Geowanking] geoRSS > Reply-To: geowanking@lists.burri.to > > > > Work on standardizing geoRSS, and bridging with OGC standards is very > commendable, if for nothing else than strengthening the support and > use > of the format. However I question whether any increase in complexity > from the current "practices" of geoRSS will be adopted by the 90% > without demonstration of significant new benefits. > > And any new formalizations need to acknowledge and incorporate present > work, mostly based on the w3c Geo vocabularly > [http://www.w3.org/2003/01/geo/] and the large amount of existing data > in this format. geoRSS as is has traction -- can we make > standardization backwards compatible? > > Among the publishers are the USGS > [http://earthquake.usgs.gov/recenteqsww/rss.html] and European > Commission [http://tsunami.jrc.it/model/index.asp], and loads of > individuals and small orgs. Yahoo's new Mapping API > [http://developer.yahoo.net/maps/documentation.html] is based on RSS > 2.0 plus the geo namespace. Hackers are plotting RSS feeds on Google > Maps too [http://blog.bulknews.net/georss-gmaps.cgi]. > > Even lighter weight and dead simple is the geotagging method seen on > flickr and del.icio.us, where coordinates are entered as tags in the > form "geo:lat=*" and "geo:long=*". In a complete abuse, these show up > within the content of <dc:subject> in this rss feed > [http://del.icio.us/rss/tag/geotagged]. But it works, for the users, > and for aggregators and mapping! On flickr there are more than 30k > photos geotagged > [http://geobloggers.blogspot.com/2005/07/rise-of-geotagged-tag.html] > > For worldKit, I've informally extended the geo namespace for lines and > polygons [http://brainoff.com/worldkit/doc/polygon.php]. > > Beyond this, the georss.org spec would give the ability to define a > non-default coordinate reference system, semantics and relationships. > Perhaps polygons with voids. All worthwhile, but crucial to that 90%? > > Don't get me wrong -- I'm happy to see an RSS/GML hybrid and I'd > definitely add parsing support to worldKit for it. Other efforts to > bridge these domains have perked my interest as well > [http://en.wikipedia.org/wiki/GML_FAQ_for_RSS_Geeks_and_others]. But > just as important is putting w3c geoRSS and existing flavors on firm > footing. > > Mikel > > > --- "Josh@oklieb" <josh@oklieb.net> wrote: > > >> Bryce, >> >> A standard which is simple, but extensible in the way you describe is >> >> being developed at http://www.georss.org hosted by EOGEO). We hope to >> >> flesh out the representation and its applications in the next couple >> >> of weeks. >> >> Josh Lieberman >> > > > _______________________________________________ > Geowanking mailing list > Geowanking@lists.burri.to > http://lists.burri.to/mailman/listinfo/geowanking > > Work on standardizing geoRSS, and bridging with OGC standards is very > commendable, if for nothing else than strengthening the support and > use > of the format. However I question whether any increase in complexity > from the current "practices" of geoRSS will be adopted by the 90% > without demonstration of significant new benefits. > > And any new formalizations need to acknowledge and incorporate present > work, mostly based on the w3c Geo vocabularly > [http://www.w3.org/2003/01/geo/] and the large amount of existing data > in this format. geoRSS as is has traction -- can we make > standardization backwards compatible? > > Among the publishers are the USGS > [http://earthquake.usgs.gov/recenteqsww/rss.html] and European > Commission [http://tsunami.jrc.it/model/index.asp], and loads of > individuals and small orgs. Yahoo's new Mapping API > [http://developer.yahoo.net/maps/documentation.html] is based on RSS > 2.0 plus the geo namespace. Hackers are plotting RSS feeds on Google > Maps too [http://blog.bulknews.net/georss-gmaps.cgi]. > > Even lighter weight and dead simple is the geotagging method seen on > flickr and del.icio.us, where coordinates are entered as tags in the > form "geo:lat=*" and "geo:long=*". In a complete abuse, these show up > within the content of <dc:subject> in this rss feed > [http://del.icio.us/rss/tag/geotagged]. But it works, for the users, > and for aggregators and mapping! On flickr there are more than 30k > photos geotagged > [http://geobloggers.blogspot.com/2005/07/rise-of-geotagged-tag.html] > > For worldKit, I've informally extended the geo namespace for lines and > polygons [http://brainoff.com/worldkit/doc/polygon.php]. > > Beyond this, the georss.org spec would give the ability to define a > non-default coordinate reference system, semantics and relationships. > Perhaps polygons with voids. All worthwhile, but crucial to that 90%? > > Don't get me wrong -- I'm happy to see an RSS/GML hybrid and I'd > definitely add parsing support to worldKit for it. Other efforts to > bridge these domains have perked my interest as well > [http://en.wikipedia.org/wiki/GML_FAQ_for_RSS_Geeks_and_others]. But > just as important is putting w3c geoRSS and existing flavors on firm > footing. > > Mikel > > > --- "Josh@oklieb" <josh@oklieb.net> wrote: > > >> Bryce, >> >> A standard which is simple, but extensible in the way you describe is >> >> being developed at http://www.georss.org hosted by EOGEO). We hope to >> >> flesh out the representation and its applications in the next couple >> >> of weeks. >> >> Josh Lieberman >> > > > _______________________________________________ > Geowanking mailing list > Geowanking@lists.burri.to > http://lists.burri.to/mailman/listinfo/geowanking > > >
Received on Wednesday, 10 August 2005 16:33:46 UTC