8
Copyright © 2010 Open Geospatial Consortium, Inc.
k Enumeration A data type whose instances form a list of alternative literal values. Enumeration means a short list of well-understood potential values within a
class. l CodeList A flexible enumeration for expressing a long list of potential
alternative values. An enumeration is used if the list alternatives are completely known; a code list is used if only likely alternatives are known.
m Interface A definition of a set of operations that is supported by objects having this interface. An Interface class cannot contain any attributes.
n Type A stereotyped class used for specification of a domain of instances objects, together with the operations applicable to the objects. A Type class may
have attributes and associations. o Union A list of alternate attributes where only one of those attributes can be
present at any time.
NOTE All the stereotypes listed above are adapted from Subclauses 6.8.2 and D.8.3 of ISO 19103. Not
all of these stereotypes are used in this document, but all can be used by a document that normatively references this document.
In this document, the following standard data types are used: a CharacterString
– A sequence of characters b Boolean
– A value specifying TRUE or FALSE c URI
– An identifier of a resource that provides more information d URL
– An identifier of an on-line resource that can be electronically accessed e Integer
– An integer number f Double
– A double precision floating point number
5.3 Document terms and definitions
Following the ISOIEC Directives, Part 2, ―Rules for the structure and drafting of
International Standards‖, the following specification terms and definitions are used in this document:
a shall – verb form used to indicate a requirement to be strictly followed to conform to
this specification, from which no deviation is permitted p should
– verb form used to indicate desirable ability or use, without mentioning or excluding other possibilities
q may – verb form used to indicate an action permissible within the limits of this
specification r can
– verb form used for statements of possibility s informative
– a part of a document that is provided for explanation, but is not required
Copyright © 2010 Open Geospatial Consortium, Inc.
9 t normative
– a part of a standards document that is required u annex
– an auxiliary part of a document, called an ―appendix‖ in United States English
v clause – a major part of a document, called a ―section‖ or ―paragraph‖ in United
States English w subclause
– a secondary part of a clause or annex, called a ―subsection‖ in United States English
5.4 Platform-neutral and platform-specific specifications
As specified in Clause 10 of OGC Abstract Specification Topic 12 ―OpenGIS Service Architecture‖ which contains ISO 19119, this document includes both platform-neutral
and platform-specific specifications. ISO 19119 also specifies that platform-neutral models ―shall be described in UML according to the rules and guidelines in ISOTS
19103.‖ Also, ―a service specification shall not be considered complete until it has a platform-neutral model and at least one platform-
specific model‖.
NOTE Clause 10 of ISO 19119 also uses ―Distributed Computing Platform DCP‖ as a synonym for
―platform‖, and uses ―platform independent‖ as a synonym for ―platform neutral‖.
This document first specifies each operation request and response, and each other parameter and data structure, in platform-neutral fashion. This is done using a table for
each data structure, which lists and defines the parameters and other data structures contained. These tables serve as data dictionaries for the UML class diagrams preceding
these tables and for the UML model in Annex C.
EXAMPLES 1 Platform-neutral specifications are contained in Subclauses 7.2.1, 7.3, 7.4.1 through
7.4.7, 8.2 through 8.4, 9.2.1, 9.3, 13.2.1, 13.3.2, 13.4.1, and 13.5.1.
The specified platform-neutral data can be encoded in many alternative ways, each appropriate to one or more specific platforms. This document now specifies encoding
appropriate for use of HTTP GET transfer of operations requests using KVP encoding, and for use of HTTP POST transfer of operations requests using XML or KVP
encoding. However, the same operation requests and responses and other data could be encoded for many other specific platforms, including SOAPWSDL there may be
multiple SOAPWSDL DCPs.
EXAMPLES 2 Platform-specific specifications for KVP encoding are contained in Subclauses 7.2.3,
9.2.2, and 10.2.3. EXAMPLES 3
Platform-specific specifications for XML encoding are contained in Subclauses 7.2.4, 7.4.10, 7.4.11, 8.5, 9.2.3, 10.2.4, 13.2.2, 13.3.3, 13.4.2, and 13.5.2.
For compliance with Clause 10 of OGC Topic 12 and ISO 19119, specific OWS specifications should follow the same pattern as used here. That is, operation requests and
responses should first be specified in platform-neutral fashion, using similar tables that serve as data dictionaries for the UML model included. Each platform-neutral
specification should be followed by one or more platform-specific encodings of this data.
10
Copyright © 2010 Open Geospatial Consortium, Inc.
These platform-specific encodings shall be included for each specific platform supported by that specific OWS specification.
5.5 Data dictionary tables
