ACTION-43: Review in terms of requirements

Review in terms of requirements

Karl Grossner
Due on:
May 20, 2015
Created on:
May 13, 2015
Associated Product:
Use Cases and Requirements
Related emails:
  1. [Minutes] 2015-05-15 (from on 2015-05-13)

Related notes:

This use case has been linked to 6 requirements dealing with temporality, 3 of which do address the joint or combined representation of spatial and temporal extents (5.22 4D model of space-time, 5.39 Space-time multi-scale, 5.56 Valid time). These in turn percolate up to two deliverables, 2.2 Spatial Data on the Web Best Practices, and 2.3 Time Ontology in OWL.

As it stands, the requirements of spatial and temporal representation remain bifurcated when it comes to deliverables. In 2.2, there is mentioned "an agreed spatial ontology;" in 2.3, the intent to work with the OWL Time Ontology authors on unspecified further development. So the spatial deliverable makes no mention of time and vice versa.

It may be that the work on OWL Time will include spatiality and/or that the emergent spatial ontology will incorporate time, but there is nothing in the expression of deliverables at this point that explicitly directs or even suggests it.

Karl Grossner, 10 Oct 2015, 17:09:13

I have marked this ACTION as Closed because I have made the review, but the review suggests a remaining issue (in my mind).

K. Grossner

Karl Grossner, 10 Oct 2015, 17:11:09

Display change log.

Chair, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <>.
$Id: 43.html,v 1.1 2018/10/09 10:07:34 carine Exp $