XML Schema Document file versions XML Schema Document locations

Copyright © 2010 Open Geospatial Consortium, Inc. 93

12.2 XML Schema Document file names

Each normative XML Schema Document used to specify the contents of XML documents should be recorded in a separate computer file. The names of these XML Schema Document files should utilize these naming patterns: a The version number is not included in the XML Schema Document name, since this information is in the namespace of the schema and in the ―version‖ attribute in the XML Schema Document. b Each XML Schema Document name begins with the specific OWS abbreviation in lower case letters, such as wfsUnits.xsd c The name of the operation is the remainder of the file name excluding the .xsd suffix, when a XML Schema Document includes the top level elements for one operation request and response, such as wmsGetMap.xsd d The name of the top level element is the remainder of the XML Schema Document file name, when the document contains only one top level element expected to be referenced outside that schema. If the name of a top level element includes the specific OWS abbreviation, it should not be repeated. Therefore, the file name should be wmsGetMapRequest.xsd and not wmsWmsGetMapRequest.xsd.

12.3 XML Schema Document file versions

The version of each XML Schema Document file should be specified in a ―version‖ attribute in the header of each file in accordance with OGC practice. All OWS specifications should follow the OGC versioning conventions. This version should not be incremented when the text in documentation elements is changed to correct typographical errors, or when a small schema error is fixed. This version should be incremented when any more significant change is made. However, the version of all the XML Schemas used by one OWS should be increased at the same time.

12.4 XML Schema Document locations

The normative XML Schema Documents used by a specific OWS specification should be normatively referenced in that specification. This may be done by including a normative annex similar to Annex B below. These normative XML Schema Documents should be bundled in a zip file with the proposed OWS specification, and the contents of those files should not be repeated in the OWS specification. After approval of version 1.0 and higher of OWS specifications, these normative XML Schema Document files should be posted online in a subdirectory under the directory URL http:schemas.opengis.net . In the event of a discrepancy between the bundled and online versions of these XML Schema files, the ONLINE files should be considered authoritative. Errors in the ONLINE files should be reported to the OGC. 94 Copyright © 2010 Open Geospatial Consortium, Inc. Under the directory URL http:schemas.opengis.net , lower level directories should be used for each specific OWS. Under the directory for each specific OWS, lower level directories should be used to contain the schemas for each specific version of that OWS. EXAMPLES http:schemas.opengis.netwms1.3.0capabilities.xsd http:schemas.opengis.netwcs1.0.1wcsCapabilities.xsd A server may reference an exact copy of these schemas located elsewhere, as long as they are readily accessible by clients. For example, it may be desirable to place the referenced schemas on the same network server as the OWS server, since that decreases the number of points of possible network failure. Such local copies of schemas should be organized into directories similar to http:schemas.opengis.net . The server owner should insure that any such local copies are kept up-to-date with respect to the authoritative files at http:schemas.opengis.net .

12.5 Base URL references resource describing server