XML Schema "dictionary.xsd"
Target Namespace:
Version:
3.2.1.2
Defined Components:
elements (4 global), complexTypes (4)
Default Namespace-Qualified Form:
Local Elements: qualified; Local Attributes: unqualified
Schema Location:
http://schemas.opengis.net/gml/3.2.1/dictionary.xsd; see XML source
Includes Schemas (2):
Included in Schemas (3):
Annotation
See ISO/DIS 19136 Clause 16. Many applications require definitions of terms which are used within instance documents as the values of certain properties or as reference information to tie properties to standard information values in some way. Units of measure and descriptions of measurable phenomena are two particular examples. It will often be convenient to use definitions provided by external authorities. These may already be packaged for delivery in various ways, both online and offline. In order that they may be referred to from GML documents it is generally necessary that a URI be available for each definition. Where this is the case then it is usually preferable to refer to these directly. Alternatively, it may be convenient or necessary to capture definitions in XML, either embedded within an instance document containing features or as a separate document. The definitions may be transcriptions from an external source, or may be new definitions for a local purpose. In order to support this case, some simple components are provided in GML in the form of - a generic gml:Definition, which may serve as the basis for more specialized definitions - a generic gml:Dictionary, which allows a set of definitions or references to definitions to be collected These components may be used directly, but also serve as the basis for more specialised definition elements in GML, in particular: coordinate operations, coordinate reference systems, datums, temporal reference systems, and units of measure. Note that the GML definition and dictionary components implement a simple nested hierarchy of definitions with identifiers. The latter provide handles which may be used in the description of more complex relationships between terms. However, the GML dictionary components are not intended to provide direct support for complex taxonomies, ontologies or thesauri. Specialised XML tools are available to satisfy the more sophisticated requirements. GML is an OGC Standard. Copyright (c) 2007,2010 Open Geospatial Consortium. To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ .
All Element Summary
The basic gml:Definition element specifies a definition, which can be included in or referenced by a dictionary.
Type:
Content:
complex, 1 attribute, 6 elements
Subst.Gr:
may substitute for elements: gml:AbstractGML, gml:AbstractObject; may be substituted with 49 elements
Defined:
globally; see XML source
Used:
at 15 locations
Sets of definitions may be collected into dictionaries or collections.
Type:
Content:
complex, 2 attributes, 8 elements
Subst.Gr:
may substitute for elements: gml:Definition, gml:AbstractGML, gml:AbstractObject
Defined:
globally; see XML source
Used:
never
This property element contains or refers to the definitions which are members of a dictionary.
Type:
Content:
complex, 10 attributes, 1 element
Subst.Gr:
may be substituted with 1 element
Defined:
globally; see XML source
Used:
Type:
string
Content:
simple
Defined:
globally; see XML source
Used:
Complex Type Summary
Content:
complex, 1 attribute, 5 elements
Defined:
globally; see XML source
Includes:
definitions of 1 attribute, 5 elements
Used:
Content:
complex, 1 attribute, 6 elements
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
Content:
complex, 10 attributes, 1 element
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
Content:
complex, 2 attributes, 8 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
XML Source
<?xml version="1.0" encoding="UTF-8"?>
<schema elementFormDefault="qualified" targetNamespace="http://www.opengis.net/gml/3.2" version="3.2.1.2" xmlns="http://www.w3.org/2001/XMLSchema" xmlns:gml="http://www.opengis.net/gml/3.2">
<annotation>
<appinfo source="urn:opengis:specification:gml:schema-xsd:dictionary:v3.2.1">dictionary.xsd</appinfo>
<documentation>
See ISO/DIS 19136 Clause 16.
Many applications require definitions of terms which are used within instance documents as the values of certain properties or as reference information to tie properties to standard information values in some way. Units of measure and descriptions of measurable phenomena are two particular examples.
It will often be convenient to use definitions provided by external authorities. These may already be packaged for delivery in various ways, both online and offline. In order that they may be referred to from GML documents it is generally necessary that a URI be available for each definition. Where this is the case then it is usually preferable to refer to these directly.
Alternatively, it may be convenient or necessary to capture definitions in XML, either embedded within an instance document containing features or as a separate document. The definitions may be transcriptions from an external source, or may be new definitions for a local purpose. In order to support this case, some simple components are provided in GML in the form of
- a generic gml:Definition, which may serve as the basis for more specialized definitions
- a generic gml:Dictionary, which allows a set of definitions or references to definitions to be collected
These components may be used directly, but also serve as the basis for more specialised definition elements in GML, in particular: coordinate operations, coordinate reference systems, datums, temporal reference systems, and units of measure.
Note that the GML definition and dictionary components implement a simple nested hierarchy of definitions with identifiers. The latter provide handles which may be used in the description of more complex relationships between terms. However, the GML dictionary components are not intended to provide direct support for complex taxonomies, ontologies or thesauri. Specialised XML tools are available to satisfy the more sophisticated requirements.

GML is an OGC Standard.
Copyright (c) 2007,2010 Open Geospatial Consortium.
To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ .
</documentation>
</annotation>
<include schemaLocation="gml.xsd"/>
<include schemaLocation="gmlBase.xsd"/>
<element name="Definition" substitutionGroup="gml:AbstractGML" type="gml:DefinitionType">
<annotation>
<documentation>
The basic gml:Definition element specifies a definition, which can be included in or referenced by a dictionary.
The content model for a generic definition is a derivation from gml:AbstractGMLType.
The gml:description property element shall hold the definition if this can be captured in a simple text string, or the gml:descriptionReference property element may carry a link to a description elsewhere.
The gml:identifier element shall provide one identifier identifying this definition. The identifier shall be unique within the dictionaries using this definition.
The gml:name elements shall provide zero or more terms and synonyms for which this is the definition.
The gml:remarks element shall be used to hold additional textual information that is not conceptually part of the definition but is useful in understanding the definition.
</documentation>
</annotation>
</element>
<complexType name="DefinitionBaseType">
<complexContent>
<restriction base="gml:AbstractGMLType">
<sequence>
<element maxOccurs="unbounded" minOccurs="0" ref="gml:metaDataProperty"/>
<element minOccurs="0" ref="gml:description"/>
<element minOccurs="0" ref="gml:descriptionReference"/>
<element ref="gml:identifier"/>
<element maxOccurs="unbounded" minOccurs="0" ref="gml:name"/>
</sequence>
<attribute ref="gml:id" use="required"/>
</restriction>
</complexContent>
</complexType>
<complexType name="DefinitionType">
<complexContent>
<extension base="gml:DefinitionBaseType">
<sequence>
<element minOccurs="0" ref="gml:remarks"/>
</sequence>
</extension>
</complexContent>
</complexType>
<element name="remarks" type="string"/>
<element name="Dictionary" substitutionGroup="gml:Definition" type="gml:DictionaryType">
<annotation>
<documentation>
Sets of definitions may be collected into dictionaries or collections.
A gml:Dictionary is a non-abstract collection of definitions.
The gml:Dictionary content model adds a list of gml:dictionaryEntry properties that contain or reference gml:Definition objects. A database handle (gml:id attribute) is required, in order that this collection may be referred to. The standard gml:identifier, gml:description, gml:descriptionReference and gml:name properties are available to reference or contain more information about this dictionary. The gml:description and gml:descriptionReference property elements may be used for a description of this dictionary. The derived gml:name element may be used for the name(s) of this dictionary. for remote definiton references gml:dictionaryEntry shall be used. If a Definition object contained within a Dictionary uses the descriptionReference property to refer to a remote definition, then this enables the inclusion of a remote definition in a local dictionary, giving a handle and identifier in the context of the local dictionary.
</documentation>
</annotation>
</element>
<complexType name="DictionaryType">
<complexContent>
<extension base="gml:DefinitionType">
<choice maxOccurs="unbounded" minOccurs="0">
<element ref="gml:dictionaryEntry"/>
<element ref="gml:indirectEntry"/>
</choice>
<attributeGroup ref="gml:AggregationAttributeGroup"/>
</extension>
</complexContent>
</complexType>
<annotation>
<documentation>
This property element contains or refers to the definitions which are members of a dictionary.
The content model follows the standard GML property pattern, so a gml:dictionaryEntry may either contain or refer to a single gml:Definition. Since gml:Dictionary is substitutable for gml:Definition, the content of an entry may itself be a lower level dictionary.
Note that if the value is provided by reference, this definition does not carry a handle (gml:id) in this context, so does not allow external references to this specific definition in this context. When used in this way the referenced definition will usually be in a dictionary in the same XML document.
</documentation>
</annotation>
</element>
<complexType name="DictionaryEntryType">
<complexContent>
<extension base="gml:AbstractMemberType">
<sequence minOccurs="0">
<element ref="gml:Definition"/>
</sequence>
<attributeGroup ref="gml:AssociationAttributeGroup"/>
</extension>
</complexContent>
</complexType>
</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/