Namespace: |
|
Type: |
|
Content: |
|
Subst.Gr: |
may substitute for elements: gml:AbstractFeature, gml:AbstractGML, gml:AbstractObject; may be substituted with 1 element |
Defined: |
globally in procedure.xsd; see XML source |
Used: |
at 2 locations |
XML Representation Summary |
||||||
<metce:Process |
||||||
|
||||||
> |
||||||
|
||||||
</metce:Process> |
<annotation>
<documentation>
</annotation>
Class 'OM_Process' (related to OM_Observation via the 'Procedure' Association) is
</documentation>
used to define the process(es) involved in generating an observation. An instance of OM_Process is often an instrument or sensor (perhaps even a sensor in a given calibrated state), but it may be a human observer executing a set of instructions, a simulator or process algorithm. The 'Procedure' should provide sufficient information to interpret the result of an observation; thus if a sensor is recalibrated or its height above local ground is changed, a new instance of OM_Process should be created and associated with subsequent observations from that sensor (at least until the sensor is changed again). Predominantly we expect the Process instance to be externally published / defined and 'static' (e.g. perhaps changing less often than once per month due to amendments to operational protocols etc.). The class 'Process' provides a concrete implementation of OM_Process (from ISO 19156). The implementation is intended to support the following requirements: 1) reference to supporting documentation (documentationRef); e.g. online documentation describing the procedure in detail; 2) specification of parameters that remain fixed within a particular configuration of the procedure (Configuration); a soft-typed approach is used here following the pattern adopted for OM_Observation/parameter; 3) specification of the resolution [1] with which each observed physical phenomenon is measured; and 4) specification of the measuring interval [2] of the instrument or sensor for each observed physical phenomenon. [1] Resolution: smallest change in a quantity being measured that causes a perceptible change in the corresponding indication (from the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) [2] Measuring interval: set of values of quantities of the same kind that can be measured by a given measuring instrument or measuring system with specified instrumental uncertainty, under defined conditions (from the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) </element>
|
Type: |
ID, predefined
|
Use: |
required |
Defined: |
by reference within gml:AbstractGMLType complexType |
Type: |
gml:BoundingShapeType, complex content
|
Nillable: |
(can be declared as nil using xsi:nil attribute in instance XML documents) |
Defined: |
by reference within gml:AbstractFeatureType complexType |
Type: |
gml:StringOrRefType, simple content
|
Defined: |
by reference within gml:StandardObjectProperties group |
Type: |
gml:ReferenceType, empty content
|
Defined: |
by reference within gml:StandardObjectProperties group |
Type: |
gml:CodeWithAuthorityType, simple content
|
Defined: |
by reference within gml:StandardObjectProperties group |
Type: |
gml:LocationPropertyType, complex content
|
Subst.Gr: |
may be substituted with 1 element |
Defined: |
by reference within gml:AbstractFeatureType complexType |
Type: |
gml:MetaDataPropertyType, complex content
|
Defined: |
by reference within gml:StandardObjectProperties group |
Type: |
gml:CodeType, simple content
|
Defined: |
by reference within gml:StandardObjectProperties group |
Type: |
metce:MeasurementContextPropertyType, complex content |
Defined: |
locally within metce:ProcessType complexType |
<element maxOccurs="unbounded" minOccurs="0" name="context" type="metce:MeasurementContextPropertyType">
<annotation>
<documentation>
</annotation>
The association role 'context' references an instance of MeasurementContext class
</documentation>
that defines resolution and measuring interval for a specific measurand. </element>
|
Type: |
gml:ReferenceType, empty content |
Defined: |
locally within metce:ProcessType complexType |
<annotation>
<documentation>
</annotation>
Reference to an external process definition providing information about relevant documentation
</documentation>
that describes the associated Process. </element>
|
Type: |
om:NamedValuePropertyType, complex content |
Defined: |
locally within metce:ProcessType complexType |
<annotation>
<documentation>
</annotation>
The association role 'parameter' references an instance of NamedValue that specifies
</documentation>
parameters associated with a particular configuration of the procedure (Configuration) </element>
|
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:
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/
|