[Requests] Comments to SPS 2.0

Robin, Alexandre Alexandre.Robin at spotimage.fr
Thu Mar 25 12:51:38 EDT 2010


1. Evaluator: Alexandre Robin, Spot Image S.A. (OGC member)

2. Submission: OGC 09-000, OGC(r) Sensor Planning Service Implementation
Specification


COMMENT #1
----------

1. Requirement: General

2. Implementation Specification Section number: 7

3. Criticality: Major
   
4. Comments/justifications for changes: It is necessary to add a section
documenting the XML schema implementation of the models. Otherwise no
requirements can be expressed in terms of the XML implementation but
only on the UML. The abstract test suite is thus not aligned with the
content of the document since it is defined relative to the XML
implementation and thus addresses a different standardization target.


COMMENT #2
----------

1. Requirement: General

2. Implementation Specification Section number: 7.3.5

3. Criticality: Major
   
4. Comments/justifications for changes: An additional and optional
SubmitById operation would be useful in order to allow submitting a task
using an existing feasibility ID. This could also be handled as an SPS
extension but seems common to a lot of applications.


COMMENT #3
----------

1. Requirement: General

2. Implementation Specification Section number: 7

3. Criticality: Major
   
4. Comments/justifications for changes: Convert schemas to reference OWS
Common 1.2 schemas.


COMMENT #4
----------

1. Requirement: General

2. Implementation Specification Section number: Annex A

3. Criticality: Major
   
4. Comments/justifications for changes: ATS should reference the SWE
Common Data Model ATS to test the validity of tasking parameters in
Submit, Update, Reserve, GetFeasibility requests relative to the
structure defined in DescribeTasking.


COMMENT #5
----------

1. Requirement: General

2. Implementation Specification Section number: 7.3.3

3. Criticality: Major
   
4. Comments/justifications for changes: It seems we are missing an
indication of how long the task status information is retained (so that
it is available for subsequent GetStatus requests) by the server after a
task is completed. Such an indication could be added to the capabilities
content section in the form of a "MaxStatusTime" property or equivalent.


COMMENT #6
----------

1. Requirement: General

2. Implementation Specification Section number: Annex A

3. Criticality: Major
   
4. Comments/justifications for changes: The ATS should contain tests for
the state machine described in annex C. Such tests are important to
check the correct asynchronous behavior of an SPS server (and client).


COMMENT #7
----------

1. Requirement: General

2. Implementation Specification Section number: 7.3.1.5

3. Criticality: Minor
   
4. Comments/justifications for changes: Adding an optional
"percentCompletion" attribute to the StatusReport class could be useful
since it is a very common way of expressing a task advancement.


COMMENT #8
----------

1. Requirement: General

2. Implementation Specification Section number: 7.3.3.5

3. Criticality: Minor
   
4. Comments/justifications for changes: Is gml:PolygonPatch the right
XSD type to implement GM_Polygon? Shouldn't gml:Polygon be used instead?


-------------------------------------------------
Alexandre Robin
Spot Image, Web and E-Business
Tel: +33 (0)5 62 19 43 62
Fax: +33 (0)5 62 19 43 43
http://www.spotimage.com
Before printing, think about the environment





More information about the Requests mailing list