element <metce:Process> (global)

Namespace:	http://def.wmo.int/metce/2013
Type:	metce:ProcessType
Content:	complex, 1 attribute, 10 elements
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

gml:id

Content:

gml:metaDataProperty*, gml:description?, gml:descriptionReference?, gml:identifier?, gml:name*, gml:boundedBy?, gml:location?, metce:documentationRef?, metce:parameter*, metce:context*

</metce:Process>

Content model elements (10):

gml:boundedBy, gml:description, gml:descriptionReference, gml:identifier, gml:location, gml:metaDataProperty, gml:name, metce:context (type metce:MeasurementContextPropertyType), metce:documentationRef (type gml:ReferenceType), metce:parameter (type om:NamedValuePropertyType)

Known Usage Locations

Within global complexTypes (1):

metce:ProcessPropertyType [ref]
As head element of substitution group affiliations (1):

wmdr:Process

Annotation

Class 'OM_Process' (related to OM_Observation via the 'Procedure' Association) is 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])

XML Source (see within schema source)

Class 'OM_Process' (related to OM_Observation via the 'Procedure' Association) is
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])

</documentation>

</annotation>

</element>

Attribute Detail (all declarations; 1/1)

gml:id

Type:	ID, predefined
Use:	required
Defined:	by reference within gml:AbstractGMLType complexType

XML Source (see within schema source)

Content Element Detail (all declarations; 10/10)

gml:boundedBy

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

XML Source (see within schema source)

gml:description

Type:	gml:StringOrRefType, simple content
Defined:	by reference within gml:StandardObjectProperties group

XML Source (see within schema source)

gml:descriptionReference

Type:	gml:ReferenceType, empty content
Defined:	by reference within gml:StandardObjectProperties group

XML Source (see within schema source)

gml:identifier

Type:	gml:CodeWithAuthorityType, simple content
Defined:	by reference within gml:StandardObjectProperties group

XML Source (see within schema source)

gml:location

Type:	gml:LocationPropertyType, complex content
Subst.Gr:	may be substituted with 1 element
Defined:	by reference within gml:AbstractFeatureType complexType

XML Source (see within schema source)

gml:metaDataProperty

Type:	gml:MetaDataPropertyType, complex content
Defined:	by reference within gml:StandardObjectProperties group

XML Source (see within schema source)

gml:name

Type:	gml:CodeType, simple content
Defined:	by reference within gml:StandardObjectProperties group

XML Source (see within schema source)

metce:context

Type:	metce:MeasurementContextPropertyType, complex content
Defined:	locally within metce:ProcessType complexType

The association role 'context' references an instance of MeasurementContext class that defines resolution and measuring interval for a specific measurand.

XML Source (see within schema source)

The association role 'context' references an instance of MeasurementContext class
that defines resolution and measuring interval for a specific measurand.

</documentation>

</annotation>

</element>

metce:documentationRef

Type:	gml:ReferenceType, empty content
Defined:	locally within metce:ProcessType complexType

Reference to an external process definition providing information about relevant documentation that describes the associated Process.

XML Source (see within schema source)

Reference to an external process definition providing information about relevant documentation
that describes the associated Process.

</documentation>

</annotation>

</element>

metce:parameter

Type:	om:NamedValuePropertyType, complex content
Defined:	locally within metce:ProcessType complexType

The association role 'parameter' references an instance of NamedValue that specifies parameters associated with a particular configuration of the procedure (Configuration)

XML Source (see within schema source)

The association role 'parameter' references an instance of NamedValue that specifies
parameters associated with a particular configuration of the procedure (Configuration)

</documentation>

</annotation>

</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:

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/