[Requests] SOS 2.0 request: remove/clarify observation in multiple offerings

I-Lin Kuo ilinkuo at usgs.gov
Tue Nov 30 17:27:48 EST 2010


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


PART A


1. Evaluator:
        I-Lin Kuo                       <ilinkuo at usgs.gov>

2. Submission: OGC 10-037 SOS 2.0 Candidate standard



PART B


1. Requirement: Incorrect relationship between observation, procedure and 
offering

In Section 8.1.2.2,

        "The Contents type lists all ObservationOfferings of an SOS 
server. An ObservationOffering groups collections of observations produced 
by one sensor system . The ObservationOffering lists the basic metadata 
for the associated observations including the procedure which made the 
observations. An observation may belong to more than one 
ObservationOffering.

        To summarize: there is a 1:n relationship between procedures and 
ObservationOfferings; there is a n:m relationship between observations 
created by these procedures and ObservationOfferings."
 
Note that there is also a restriction that an Offering has at most one 
procedure. Note also in Table 18 where "procedure" is defined to be a 
sensor system. When these three restrictions are combined, then the only 
way an observation can belong to more than one ObservationOffering is if 
those two ObservationOfferings come from the same sensor system.

Please either correct this or clarify by providing a use case, because I 
cannot in my wildest imagination come up with a situation where this is 
true or desirable.


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



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

        Major

4. Comments/justifications for changes: [Comments]


I-Lin Kuo
IT Specialist, Center for Data Analytics (CIDA)
USGS WI Water Science Center
Phone: 608-821-3895
http://cida.usgs.gov/professional-pages/kuo.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opengeospatial.org/pipermail/requests/attachments/20101130/e87d5129/attachment-0001.htm>


More information about the Requests mailing list