Introduction Capitalization XML Schema documentation Namespaces

Copyright © 2010 Open Geospatial Consortium, Inc. 87

11.6 XML encoding

11.6.1 Introduction

This subclause specifies the XML encoding of the operation request and response parameters specified in Clauses 7 through 10 and 13.

11.6.2 Capitalization

The capitalization of parameter and operation names when encoded as XML elements and attributes shall be as used in Clauses 7 through 10 of this document. More generally, these name capitalization rules shall be used: a All names of XML elements shall have the first word and any subsequent words in the name capitalized UpperCamelCase. All other letters will be lower case. b All names of XML attributes shall have the first word in lower case and any subsequent word in the name capitalized lowerCamelCase. All other letters shall be lower case. EXAMPLES 1 The GetCapabilities operation request element name shall be GetCapabilities UpperCamelCase. The updateSequence attribute name shall be updateSequence lowerCamelCase. The capitalization of parameter values when encoded as XML strings shall be as used in Clauses 7 through 10 of this document. More generally, all XML string values shall have the first word and any subsequent words in the name capitalized. All other letters will be lower case. EXAMPLE 2 One possible ―request‖ attribute value is ―GetCapabilities‖.

11.6.3 XML Schema documentation

All XML Schemas shall contain documentation of the meaning of each element, attribute, and type. In many cases, a documentation element is included only for the complex or simple types, but is applicable to all the elements or attributes that use that type. All of these documentation elements shall be considered normative, except where labelled ―informative‖. XML encoded operation requests and responses are not required to be fully validated against their respective schemas. However, XML parsing and validation shall follow the normal XML syntax rules, for example regarding XML Namespaces.

11.6.4 Namespaces

Namespaces are used to discriminate XML elements, attributes, and data types defined in application-specific domains from one another [Namespaces In XML]. Multiple normative XML namespaces definitions are thus used in different XML Schemas for an OWS, and shall be suitably implemented by each compliant OWS server. While many of 88 Copyright © 2010 Open Geospatial Consortium, Inc. the examples in this document and OWS interface specifications use a single namespace, multiple namespaces shall be supported by each compliant OWS server.

11.6.5 XML Schema extension and restriction