yes and INSEE as well http://prefix.cc/geo
not to conflate issues here but the recommended OGC upgrade path for geosparql jena prjects from jena+spatial would look something like this to index your data in the future if we move away from the current lucene spatial implementation: PREFIX w3cGeo: <http://www.w3.org/2003/01/geo/wgs84_pos#> PREFIX geo: <http://www.opengis.net/#geosparql> SELECT (STRDT(CONCAT("POINT(",?long," ",?lat,")"), geo:wktLiteral) AS ?wktLit) WHERE { ?point w3cGeo:long ?long . ?point w3cGeo:lat ?lat } On Wed, Dec 12, 2018 at 3:45 PM John A. Fereira <[email protected]> wrote: > geo is also used as a namespace prefixe for the U.N. Geopoltical ontology: > http://aims.fao.org/aos/geopolitical.owl# > > > On 12/12/18, 8:43 AM, "Marco Neumann" <[email protected]> wrote: > > geo is currently used in jena spatial for w3c geo predicates. and it > will > be used in the new geosparql module for jena/fuseki as an internal > prefix > for geosparql keywords. this might be our main concern here. I don't > see a > consensus on the web for re-purposing the geo prefix from w3c to ogc > at the > moment besides the adoption of geo for ogc by wikidata. (by the way > this > reassignment of geo might have been an ad hoc decision by a developer > or > group of developers in the wikidata project by simply looking up the > ogc > spec) > > > On Wed, Dec 12, 2018 at 1:33 PM Andy Seaborne <[email protected]> wrote: > > > Hi Marco, > > > > Where is' geo' being used? > > > > Andy > > > > > > On 12/12/2018 12:16, Marco Neumann wrote: > > > What do people on the list think about re-using the namespace > prefix geo? > > > > > > it's currently used for > > > > > > WGS84 Geo Positioning: an RDF vocabulary > > > http://www.w3.org/2003/01/geo/wgs84_pos# > > > > > > but becomes more popular (e.g. see wikidata) as a namespace prefix > for > > > > > > OGC GeoSPARQL 1.0 > > > http://www.opengis.net/ont/geosparql# > > > > > > I would have preferred to see the OGC introduce a new namespace > prefix > > like > > > geosparql but for some reason they settled on replacing geo (W3C ) > with > > > geosparql (OGC) and geof for functions. Technically not a big deal > but > > that > > > said most people would have to change their existing data to refer > to the > > > new URI now to accommodate the change. > > > > > > Alternatively we could just introduce geosparql or ogcgeo as a new > > > namespace prefix in jena projects for OGC gesparql to avoid > confusion. I > > am > > > sure the re-purposing of the geo namespace prefix was a "mistake" > at the > > > time of OGC geosparql (Ed. Matthew Perry and John Herring Oracle) > > > discussions. No need to perpetuate this change into the future > here. > > > > > > What are your thoughts on this? > > > > > > > > > > > > > > -- > > > --- > Marco Neumann > KONA > > > -- --- Marco Neumann KONA
