The QoSE DWG is working on a draft OGC Best Practice (possibly split into more than one document) on declaring expected Quality of Service information within the OWS capabilities documents (http://external.opengeospatial.org/twiki_public/QualityOfService/QoSMetadataBestPractice). This QoS metadata will include things like expected service availability percentage, expected minimum performance & capacity of specified operations, known downtime, limitations in operating hours and operational status.
Testbed 14 should include tasks for
developing a capability for a OWS server admin to declare the QoS metadata elements as extended capabilities using the draft QoS metadata XML Schemas. Ideally this should be demonstrated using more than one existing OGC Web Service server product.
developing capability to automatically ingest the QoS metadata of a remote service and start/modify automatic monitoring of the declared metrics, including the declared downtime and/or operating hours, and reporting the monitoring results to the users. Ideally this should be demonstrated using more than one existing OGC Web Service monitoring product or tool.
The implementation and use experience would be fed back to the QoSE DWG drafting process for the final Best Practice document(s).
The QoSE DWG is working on a draft OGC Best Practice (possibly split into more than one document) on declaring expected Quality of Service information within the OWS capabilities documents (http://external.opengeospatial.org/twiki_public/QualityOfService/QoSMetadataBestPractice). This QoS metadata will include things like expected service availability percentage, expected minimum performance & capacity of specified operations, known downtime, limitations in operating hours and operational status.
Testbed 14 should include tasks for
The implementation and use experience would be fed back to the QoSE DWG drafting process for the final Best Practice document(s).
Relates to #6