[Requests] Comment to SOS 2.0 (OGC 10-037) from SWIE

Stefan Fuest Stefan.Fuest at kisters.de
Tue Nov 30 11:16:49 EST 2010


Part A to be completed once.  Iterate Part B as needed.


PART A


1. Evaluator:
        Stefan Fuest
        KISTERS AG - Charlottenburger Allee 5 - 52068 Aachen - Germany
        Tel.: +49 241 9671 -176 | E-Mail: Stefan.Fuest at kisters.de | WWW: 
http://www.kisters.de

2. Submission: 
        OGC® SOS 2.0 Interface Standard, OGC 10-037, 2010-09-02



PART B


1. Requirement: General


2. Implementation Specification Section number: General


3. Criticality: Major


4. Comments/justifications for changes: [Comments]

The FOI is not mandatory in important functions; this is allowing requests 
like getObservation(WaterLevel) which would need to be answered with all 
existing WaterLevel Measurements; currently seen implementation have 4 
ways to answer this 
(1) don?t return anything, 
(2) return any single station but not all, 
(3) return all waterlevel but just the most current value for each, and 
(4) return all waterlevel but stop at a certain amount of time/value 
pairs. 
None of the 4 options match the original request and the client has no 
chance to know what the response really is.

Therefore we suggest enhance the specification to force service providers 
to implement the following:

getObservation requests should answer according to the real request; 
if the service provider wants to restrict data downloads this should be 
done via the defined exception documents with meaningful message like
1.      please specify time-range to obtain information via getObservation 
(if service provider does not want to answer unfiltered requests)
2.      please specify a list of feature of interest to obtain information 
via getObservation (if the service provider wants this as a filter)
3.      ?. Anything that properly describes why the request is answering 
in a specific way which is not matching the requests
Clients could then take advantage of this information and provide 
Information to users.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opengeospatial.org/pipermail/requests/attachments/20101130/7f2024a3/attachment.htm>


More information about the Requests mailing list