XML Schema "opm.xsd"
Target Namespace:
Version:
1.0
Default Namespace-Qualified Form:
Local Elements: qualified; Local Attributes: unqualified
Schema Location:
http://schemas.wmo.int/opm/1.0/opm.xsd; see XML source
Imports Schemas (1):
Includes Schemas (1):
Imported by Schemas (2):
Included in Schemas (1):
Annotation
Annotation 1 [src]:
References to WMO and ICAO Technical Regulations within this XML schema shall have no formal status and are for information purposes only. Where there are differences between the Technical Regulations and the schema, the Technical Regulations shall take precedence. Technical Regulations may impose requirements that are not described in this schema.
Annotation 2 [src]:
The 'Observable Property' model enables observed physical properties (also termed "Quantities" within the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) to be aggregated into composite properties and for any qualification or constraint relating to those observed physical properties to be explicitly described. A data publisher may need to use the Observed Property Model to explicitly define any qualification or constraint applied to the observed property, or, where the observation results in the evaluation of multiple properties, to explicitly define each of those individual physical properties. Usage: The Observable Property Model may be used to specify constraint or qualification of a physical quantity (or set of physical quantities) within the context of a specific observation or measurement event; e.g. via OM_Observation/parameter Attribute (from ISO 19156, type Class "NamedValue"): - name: http://def.wmo.int/opm/2013/observable-property#property [1] - parameter: instance of Class "AbstractObservableProperty" or concrete subclass thereof [2] Note that Class "OM_Observation" asserts a constraint such that the value of the parameter/NamedValue/name Attribute shall not occur more than once within a given instance of Class OM_Observation. In situations where multiple physical quantities are observed or measured, the value of the associated parameter/NamedValue/value Attribute may be specified as an instance of Class "CompositeObservableProperty" thus allowing a set of observable properties to be specified. Also note that, whilst Class "OM_Observation" provides Attribute "observedProperty" for specifying the (physical) property observed or measured the cardinality of this Attribute is one (e.g. only a single property can be referenced). Furthermore, this Attribute is implemented "by reference" (serialised as gml:ReferenceType) implying that one cannot define an instance of Class "CompositeObservableProperty" in-line within the data. Whilst it is permissible to make a local reference to an instance of Class "CompositeObservableProperty" defined elsewhere within the data, it is preferable to reference an external definition. The reason for this is that the value of Attribute "observedProperty" is used by the OGC Sensor Observation Service as a key on which data is indexed; use of internal references are likely to inhibit discovery and retrieval of data. Alternatively, if the constraint or qualification of the physical quantity (or set of physical quantities) is consistent within a repeatable procedure, it may be defined within the context of that procedure; e.g. via the Process/parameter Attribute (from "«Application Schema» METCE", type Class "NamedValue"). Note that in the case of Class "Process", there is no constraint on the number of occurences of a given parameter name. However, recommended practice indicates the use of an instance of Class "CompositeObservableProperty" where a set of observable properties are to be specified. [1] Association Role "property" is specified to have type Class "AbstractObservableProperty" [2] Class "AbstractObservableProperty" has concrete sub-classes "ObservableProperty", "QualifiedObservableProperty" and "CompositeObservableProperty".
XML Source
<?xml version="1.0" encoding="UTF-8"?>
<schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://def.wmo.int/opm/2013" version="1.0" xmlns="http://www.w3.org/2001/XMLSchema" xmlns:gml="http://www.opengis.net/gml/3.2" xmlns:opm="http://def.wmo.int/opm/2013">
<annotation>
<documentation>
References to WMO and ICAO Technical Regulations within this XML schema shall have
no formal status and are for information purposes only. Where there are differences
between the Technical Regulations and the schema, the Technical Regulations shall
take precedence. Technical Regulations may impose requirements that are not described
in this schema.
</documentation>
<documentation>
The 'Observable Property' model enables observed physical properties (also termed
"Quantities" within the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf])
to be aggregated into composite properties and for any qualification or constraint
relating to those observed physical properties to be explicitly described. A data
publisher may need to use the Observed Property Model to explicitly define any qualification
or constraint applied to the observed property, or, where the observation results
in the evaluation of multiple properties, to explicitly define each of those individual
physical properties. Usage: The Observable Property Model may be used to specify
constraint or qualification of a physical quantity (or set of physical quantities)
within the context of a specific observation or measurement event; e.g. via OM_Observation/parameter
Attribute (from ISO 19156, type Class "NamedValue"): - name: http://def.wmo.int/opm/2013/observable-property#property
[1] - parameter: instance of Class "AbstractObservableProperty" or concrete subclass
thereof [2] Note that Class "OM_Observation" asserts a constraint such that the value
of the parameter/NamedValue/name Attribute shall not occur more than once within a
given instance of Class OM_Observation. In situations where multiple physical quantities
are observed or measured, the value of the associated parameter/NamedValue/value Attribute
may be specified as an instance of Class "CompositeObservableProperty" thus allowing
a set of observable properties to be specified. Also note that, whilst Class "OM_Observation"
provides Attribute "observedProperty" for specifying the (physical) property observed
or measured the cardinality of this Attribute is one (e.g. only a single property
can be referenced). Furthermore, this Attribute is implemented "by reference" (serialised
as gml:ReferenceType) implying that one cannot define an instance of Class "CompositeObservableProperty"
in-line within the data. Whilst it is permissible to make a local reference to an
instance of Class "CompositeObservableProperty" defined elsewhere within the data,
it is preferable to reference an external definition. The reason for this is that
the value of Attribute "observedProperty" is used by the OGC Sensor Observation Service
as a key on which data is indexed; use of internal references are likely to inhibit
discovery and retrieval of data. Alternatively, if the constraint or qualification
of the physical quantity (or set of physical quantities) is consistent within a repeatable
procedure, it may be defined within the context of that procedure; e.g. via the Process/parameter
Attribute (from "&#171;Application Schema&#187; METCE", type Class "NamedValue"). Note that
in the case of Class "Process", there is no constraint on the number of occurences
of a given parameter name. However, recommended practice indicates the use of an instance
of Class "CompositeObservableProperty" where a set of observable properties are to
be specified. [1] Association Role "property" is specified to have type Class "AbstractObservableProperty"
[2] Class "AbstractObservableProperty" has concrete sub-classes "ObservableProperty",
"QualifiedObservableProperty" and "CompositeObservableProperty".
</documentation>
</annotation>
<include schemaLocation="observable-property.xsd"/>
</schema>

This XML schema documentation has been generated with DocFlex/XML 1.11 using DocFlex/XML XSDDoc 2.8.3 template set.
DocFlex/XML is a tool for programming and running highly sophisticated documentation and reports generators by the data obtained from any kind of XML files. The actual doc-generators are implemented in the form of special templates that are designed visually using a high-quality Template Designer GUI basing on the XML schema (or DTD) files describing the data source XML.
DocFlex/XML XSDDoc is a commercial template application of DocFlex/XML that implements a high-quality XML Schema documentation generator with simultaneous support of framed multi-file HTML, single-file HTML and RTF output formats. (More formats are planned in the future).
A commercial license for "DocFlex/XML XSDDoc" will allow you:
  • To configure the generated documentation so much as you want. Thanks to our template technology, it was possible to support > 400 template parameters, which work the same as "options" of ordinary doc-generators. The parameters are organized in nested groups, which form a parameter tree. Most of them have their default values calculated dynamically from a few primary parameters. So, you'll never need to specify all of them. That will give you swift and effective control over the generated content!
  • To use certain features disabled in the free mode (such as the full documenting of substitution groups).
  • To select only the initial, imported, included, redefined XML schemas to be documented or only those directly specified by name.
  • To include only XML schema components specified by name.
  • To document local element components both globally and locally (similar to attributes).
  • To allow/suppress unification of local elements by type.
  • To enable/disable reproducing of namespace prefixes.
  • To use PlainDoc.tpl main template to generate all the XML schema documentation in a signle-file form as both HTML and incredible quality RTF output.
  • To format your annotations with XHTML tags and reproduce that formatting both in HTML and RTF output.
  • To insert images in your annotations using XHTML <img> tags (supported both in HTML and RTF output).
  • To remove this very advertisement text!
Once having only such a license, you will be able to run the fully-featured XML schema documentation generator both with DocFlex/XML (Full Edition) and with DocFlex/XML RE, which is a reduced free edition containing only the template interpretor / output generator. No other licenses will be required!
But this is not all. In addition to it, a commercial license for "DocFlex/XML SDK" will allow you to modify the XSDDoc templates themselves as much as you want. You will be able to achieve whatever was impossible to do with the template parameters only. And, of course, you could develop any template applications by your own!
Please note that by purchasing a license for this software, you not only acquire a useful tool, you will also make an important investment in its future development, the results of which you could enjoy later by yourself. Every single your purchase matters and makes a difference for us!
To purchase a license, please follow this link: http://www.filigris.com/shop/