Copyright © 2010 Open Geospatial Consortium, Inc. All Rights Reserved.
9 can be used to determine the compliance level of the application schema.
The following schema fragment shows how this annotation shall be declared in an application schema:
1 xsd:annotation 2 xsd:appinfo source=http:schemas.opengis.netgmlsfProfile2.0gmlsfLevels.xsd
3 gmlsf:ComplianceLevel0|1|2gmlsf:ComplianceLevel 4 xsd:appinfo
5 xsd:annotation
In line 2, the appinfo element is used to contain the compliance level declaration for the application schema. The source attribute shall point to the gmlsfLevels.xsd schema,
where the ComplianceLevel element is declared.
Line 3 uses the gmlsf:ComplianceLevel element to declare the compliance level of an application schema. The contents of the ComplianceLevel element shall be 0 for
schemas that comply with level SF-0, 1 for schemas that comply with level SF-1 and 2 for schemas that comply with level SF-2.
8 Schema coding patterns for compliance level SF-0
8.1 Introduction
This clause describes a rigid coding pattern for GML application schemas that comply with level SF-0 of this profile. The main motivation behind this pattern is to limit the set
of XML-Schema and GML capabilities that can be used to code a GML application schema. This in turn simplifies the task of building clients that can ingest schema
documents that comply with this coding pattern and understand the structure of the feature types defined within.
The schema fragments defined in the following sub-clauses shall be combined to create a complete GML application schema that complies to level SF-0 of this profile. The
schema fragments shall be structurally encoded exactly as presented in the document. This means that all mandatory elements and attributes presented in the fragment shall be
included as shown even if they are optional in XML-Schema. Furthermore, no other optional elements, attributes or facets that might be defined in XML-Schema or GML
may be used unless specified in this document.
Please note that these requirements have absolutely nothing to do with the formatting of the XML fragments or the order in which elements or type definitions are declared. They
are structural and syntactic requirements, not formatting requirements. White spaces can be used freely to format the generated schema documents in any way.
