Skip to content

Spatial ontologies

From TR 103 781:

  • SAREF4ENVI uses the W3C Basic Geo Vocabulary. It copies the definition of geo Point, geo:SpatialThing, and add disjoint axioms to many classes in SAREF. Other ontologies use the OGC GeoSPARQL standard instead. One unique choice should be made for all SAREF.
  • SAREF4BLDG copies the definition of the geo:location from the W3C Basic Geo Vocabulary, but it does not use it. Other ontologies use the OGC GeoSPARQL standard instead. One unique choice should be made for all SAREF.
  • SAREF4CITY:
    • uses the W3C Basic Geo Vocabulary. It declares class geo:SpatialThing, copies the definition of geo:location, geo:lat, geo:long, geo:alt, geo:Point. These concepts are not further used in the ontology and could be deleted. geo:Point is hijacked and defined as a subclass of geosp:Geometry.
    • uses the OGC GeoSPARQL standard. It copies the definition of geosp:hasGeometry, geosp:sfContains, geosp:sfWithin, geosp:Feature, geosp:Geometry, geosp:SpatialObject. Some classes in SAREF4CITY are defined as subclasses of geosp:Feature. Class saref:Device is hijacked and defined as a subclass of geosp:Feature.
  • SAREF4AGRI:
    • SAREF4AGRI uses the W3C Basic Geo Vocabulary, like SAREF4CITY but with a different prefix wgs84:. It declares class geo:SpatialThing, copies the definition of geo:location, geo:lat, geo:long, geo:alt, geo:Point. These concepts are not further used in the ontology and could be deleted. In particular, geo:long is defined as an OP in SAREF4AGRI while it is defined as a DP in SAREF4CITY. Therefore, using these two ontologies together would lead to an inconsistency. geo:Point is hijacked and defined as a subclass of geosp:Geometry.
    • SAREF4AGRI uses the OGC GeoSPARQL standard, like SAREFCITY but with a different prefix geo:. It copies the definition of geosp:hasGeometry, geosp:sfContains, geosp:sfWithin, geosp:Feature, geosp:Geometry, geosp:SpatialObject. Some classes in SAREF4CITY are defined as subclasses of geosp:Feature. Class saref:Device is hijacked and defined as a subclass of geosp:Feature.
  • SAREF4AUTO:
    • uses the W3C Basic Geo Vocabulary, with no prefix. It copies the definition of geo:location, geo:lat, geo:long, geo:alt, geo:Point and geo:SpatialThing. These concepts are used in the ontology in the definition of s4auto:Point and s4auto:AbsolutePosition.
    • uses the OGC GeoSPARQL standard, with prefix geosp:. It copies the definition of geosp:hasGeometry, geosp:Feature, geosp:Geometry, geosp:SpatialObject. These concepts are used in the ontology in the definition of s4auto:Point and s4auto:ParkingSpot.
  • SAREF4WEAR:
    • SAREF4WEAR uses the W3C Basic Geo Vocabulary, with prefix geo:. It copies the definition of geo:location, geo:Point. These concepts are not further used in the ontology and could be deleted. geo:Point is hijacked and defined as a subclass of geosp:Geometry.
    • SAREF4WEAR uses the OGC GeoSPARQL standard with prefix geosp:. It copies the definition of geosp:hasGeometry, geosp:sfContains, geosp:sfWithin, geosp:Feature, geosp:Geometry, geosp:SpatialObject. Some classes in SAREF4WEAR are defined as subclasses of geosp:Feature. Or geosp:SpatialObject.

Proposals:

  • only allow the reuse of OGC GeoSPARQL. with one unique prefix geo:
  • never use W3C Basic Geo.
  • introduce saref:PhysicalObject, allow its instances to also be of type geo:SpatialObject
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information