EO PMOS SWG Correct inconsistencies between UML model and tables

All Fields marked with * are mandatory.
Change Request 312
#:
Assigned OGC 13-088
Document #:
Name: *Steven Smolders
Organization: *GIM nv
Email: *steven.smolders@gim.be
Document
Name/Version:

*+-",+/-#('--)+(2%( ,+/-#(',,.+&'-, 

OGC Project
Document:

* 
+

 -"#,#,+/#,#('( )+/#(.,,.&#,,#(''1(."/"'!*.,-.&+then check here:
'-+-"'.&+"+

'-+-"/,#('.&+-"-1(.++/#,#'!"+

Title:
Source:

*

[EO PMOS SWG] Correct inconsistencies between UML model and tables

*

Work item code:

Category:

*

A (corresponds to a correction in an earlier release)

Reason for *

change:

UML Model and derived XML schemas are not fully in correspondance with
the tables in the specification

Summary of *
change:

1/ In the EarthObservationResult class (opt schema), the properties
cloudCoverPercentageQuotationMode and snowCoverPercentageQuotationMode
are both wrongly defined as being of type EarthObservationResult. They
should be of type PercentageCoverQuotationModeValue that specifies the
enumeration AUTOMATIC or MANUAL. The corresponding entries in table 9
are correct.

( 

2/ In the Processing Information class diagram, the enumeration class
CompositeTypeValue should be removed since the type of the
compositeType property has been changed since the preceding

specification (OGC06-080) from an enumeration to a TM_PeriodDuration.
The CompositeTypeValue class is hence not in use anylonger and can be
removed.
3/ In the Processing Information class diagram, the type of the
processingDate property is TM_PeriodDuration. The table specifies that
this should be a datetime. The model is wrong and the type of
processingDate should be changed to DateTime.
4/ Table 6 lists the possible values for the OrbitDirectionValue as
Ascending and Descending. The UML model specifies ASCENDING and
DESCENDING. The model is correct and table 6 should be amended.
5/ Table 9 lists properties cloudCoverPercentageAssessmentPercentage
and snowCoverPercentageAssessmentPercentage. The
opt:EarthObservationResult class diagram has instead the properties
cloudCoverPercentageAssessmentConfidence and
snowCoverPercentageAssessmentConfidence. The UML diagram is correct
and Table 9 should be corrected.
6/ The class diagram for Synthesis and Systematic Products metadata
has a derivedFrom property of type CharacterString. The associated
table 22 specifies that this property should be a link to the EO
Products that were used in the generation of the ssp products. Like

the similar eop:linkedWith and subsetOf properties, the type of the
element should be EarthObservation encoded by reference. The UML model
should be adapted.
7/ The class diagram for Altimetric products has the cardinality of
the property alt:auxiliaryInstrument/alt:instrumentType as 1. The
corresponding table 12 has 0..1 .Table 12 is wrong and should be
updated.
8/ atm:earthObservationResult model contains cloudCover and snowCover
related properties, table does not. Table needs to be extended.
9/ Add HH, HV, VH, VV as value in the enumeration for the
sar:polarisationChannelValues

Consequences if
not approved:

Clauses affected: *
Table 5, 6, 9,12, 22 and corresponding class diagrams.

Additional ('
Documents

affected:
Supporting
Documentation:
Comments:


( 

Status:
Assigned To:
Disposition:

Assigned

EO PMOS SWG

Referred

(