SPS 2.0, Implementation Cycle 1

Roadmap

• Interface development for SPS Core Profile (with doing some pre-work for non-core interfaces)
• Maven Project Setup
• Web Application structure making several HTTP bindings possible
  • Choose POST XML as first implemented binding
  • Consider loose coupling of components for ease configuration of new (e.g. optional SPS) components
• Implement basic service metadata logic
  • static capabilities information
  • dynamic capabilities information this requires an SPS admin interface to avoid static configuration of sensors
• SPS Admin interface
  • create admin interface to add new SensorOfferings or SensorPlugin instances respectively each sensor instance can offer one or more SensorOfferings (with different observedProperties)
  • let insert logic differentiate between both create a new instance and add a SensorOffering to an existing instance
• Implement task submission
  • develop task creation and management logic
  • check syntax and validate parameters
  • create scheduling logic
    • Task scheduling is (for now) not done by the SPS and has to be done by the sensor plugin itself
• Create a CITE test plugin
  • Define SensorPlugin interface
  • Plugin is similar to the CITE Plugin used in OWS-5 (SPS version 1.0)
  • simulate task execution
  • create ResultAccess
• Database
  • Create data storage in memory at first and use them in tests
  • Make storage implementation exchangable
  • Create DAO interfaces
  • Provide database implementation for persisted storage (done by hibernate)

Metadata

• Topic created by: HenningBredel
• Topic created on: 2012-05-23