Provides the services (given by service URL and service type) which will be returned upon DescribeResultAccess with sensorID. This information is pure meta information about which services (URLs) of which type will most likely store the information gathered by the sensor. This allows clients to determine in advance whether they are capable of accessing the sensor data or not. Container for information that have to be provided by a sensor. The information will be used to create a SensorProfile for the sensor which can be registered to the PM. Container for information that shall be updated in a specific SensorProfile. The information provided in one of the elements will replace all existing information for that element. E.g. if one or more InputDescriptors are provided those will replace the existing ones. This is the ID used by the SPS framework internally to clearly identify a sensor (plugin) instance. A better remindable name for the sensor ID. Must be unique for each sensor currently registered within the framework and should be of the form PROVIDER:SENSOR_IDENTIFIER, where the syntax of the SENSOR_IDENTIFIER is up to the provider - but should conform to OGC rules. Contains the fully qualified OGC URN for identifying a sensor instance. This URN contains the urn:ogc... prefix followed by the Alias information of the provider. Contains both internal (SensorID) and external (Alias) ID of a sensor instance. Contains information to set a new sensor instance state when it is registered or to restore a sensors state when the service is restarting. The content depends on the actual sensor. Each sensor type defines its own configuration schema. Contains update information for a specific sensor. The content depends on the actual sensor. Each sensor type defines its own configuration update schema. Used to retrieve the current status of a sensor Each target shall provide at least the ID and status of each known task. Contains a report with status information a services sensor. The content depends on the actual sensor. Each sensor type defines its own status information schema. Contains information where the data gathered by a sensor in a certain task can be accessed from. If the DataServices element is omitted then the default data services for that sensor serve the data of the task. This configuration file can be used for storing the basic information a sensor needs in order to be registered. Links to where the SensorML description can be downloaded. Contains the SensorML description directly as XML. We chose to use ##any namespace so that we are independent of the actual SensorML version used.