[Requests] OGC 06-141r5 Ordering Services for Earth Observation Products Interface Standard

Marchionni Daniele daniele.marchionni at telespazio.com
Wed Feb 23 07:02:56 EST 2011


The following issues have been noticed during the implementation of the Reference Order Server.

 

 

PART A

 

 

1. Evaluator:

Daniele Marchionni

 

2. Submission: 

OGC 06-141r5 Ordering Services for Earth Observation Products Interface Standard

 

 

PART B

 

 

1. Requirement: [General, #] 

               The Ordering schema files shall minimize as much as possible the references to the external schemas in order to improve the compatibility with XML Data Binding Tools like XMLBEANS, etc.

 

2. Implementation Specification Section number: [General, #]

               Schema Files, WSDL

 

3. Criticality: [Major, Minor, Editorial, etc.]

               Minor

 

4. Comments/justifications for changes: [Comments]

               This specification should allow the implementation through common development tools (e.g. Java, Netbeans) as much as possible.

               In fact during the implementation of the Reference Order Server several issues have been noticed while generating Java code starting from the XSD / WSDL.

 

 

PART B

 

 

1. Requirement: [General, #] 

               The product identifier returned from GetOptionsResponse shall be at "CommonOrderOptions" type level and not at "option" element level. 

In fact the whole block of order options is related to a product identifier and not only the option element.

 

2. Implementation Specification Section number: [General, #]

               Schema Files

 

3. Criticality: [Major, Minor, Editorial, etc.]

               Minor

 

4. Comments/justifications for changes: [Comments]

 

 

PART B

 

 

1. Requirement: [General, #] 

To split the operations in the WSDL in 2 separated port types: one related to the actual operations (e.g. GetCapabilities, GetOptions, ..) and the other one related to the asynchronous operations (i.e. GetQuotationResponse, SubmitResponse, CancelResponse).

 

2. Implementation Specification Section number: [General, #]

               WSDL File

 

3. Criticality: [Major, Minor, Editorial, etc.]

               Minor

 

4. Comments/justifications for changes: [Comments]

Necessary for clarifying which operations must be implemented by the Server and which operations must be implemented from the Client.

 

 

PART B

 

 

1. Requirement: [General, #] 

To update WS-addressing to the latest version. 

In fact the document currently refers to http://schemas.xmlsoap.org/ws/2003/03/addressing/ <http://schemas.xmlsoap.org/ws/2003/03/addressing/role/anonymous>  while http://www.w3.org/2005/08/addressing has to be used.

 

2. Implementation Specification Section number: [General, #]

               Schema Files & document

 

3. Criticality: [Major, Minor, Editorial, etc.]

               Minor

 

4. Comments/justifications for changes: [Comments]

 

 

PART B

 

1. Requirement: [General, #] 

Req.111 is non correct; in fact CancelResponse shall be returned in case of AsyncCancellation requirement class and not for Cancellation requirement class.

 

2. Implementation Specification Section number: [General, #]

               §16.2

 

3. Criticality: [Major, Minor, Editorial, etc.]

               Minor

 

4. Comments/justifications for changes: [Comments]

 

 

 

___________________________________________________________________

Daniele Marchionni

Telespazio S.p.A. - A Finmeccanica / Thales Company
HQ: via Tiburtina 965  -  I-00156 Rome   Italy
http://www.telespazio.com/ <http://www.telespazio.com/> 
mailto:daniele.marchionni at telespazio.com <mailto:nome.cognome at telespazio.com> 

Operating address: via Beniamino Segre 91  -   I-00134 Rome  Italy

Phone: +39.06.5027.4593 (direct) 
   +39.06.5027.4570 (secretary)
Fax:   +39.06.5027.4500

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opengeospatial.org/pipermail/requests/attachments/20110223/1eaf8381/attachment.htm>


More information about the Requests mailing list