Namespace Conventions OpenGIS® SWE Service Model Implementation Standard

10 Copyright © 2011 Open Geospatial Consortium. exception that ScopedName is encoded as xs:anyURI, which is explained in clause 16.3.1 - together with the instructions listed in the following tables. For an explanation of the table columns, see clause D.2.1 in [OGC 07-036]. Table 2 — Implementation of types from ISO 19156 UML class object element type property type GFI_Feature gml:AbstractFeature gml:AbstractFeatureType gml:FeaturePropertyType Table 3 — Implementation of types from Web Services Addressing UML class object element type property type EndpointReference wsa:EndpointReference wsa:EndpointReferenceType - Table 4 — Implementation of types from WS-Topics UML class object element type property type TopicNamespace wstop:TopicNamespace wstop:TopicNamespaceType - Topicset wstop:TopicSet wstop:TopicSetType - Table 5 — Implementation of additional types used in this standard UML class object element type property type Any - xs:anyType xs:anyType

5.6 Namespace Conventions

This standard uses a number of namespace prefixes throughout; they are listed in Table 6. Note that the choice of any namespace prefix is arbitrary and not semantically significant. Copyright © 2011 Open Geospatial Consortium. 11 Table 6 — Prefixes and Namespaces used in this standard Prefix Namespace gml http:www.opengis.netgml3.2 ows http:www.opengis.netows1.1 soap11 http:schemas.xmlsoap.orgsoap soap12 envelopehttp:www.w3.org200305soap-envelope swes http:www.opengis.netswes2.0 wsa http:www.w3.org200508addressing wsn-b http:docs.oasis-open.orgwsnb-2 xs http:www.w3.org2001XMLSchema 12 Copyright © 2011 Open Geospatial Consortium. 6 SWE Service Model Overview This standard currently defines eight packages with data types for common use across SWE services. Five of these packages define operation request and response types. The packages are: a Contents – This package defines data types that can be used in specific services that provide access to sensors. b Notification – This package defines the data types that support provision of metadata about the notification capabilities of a service as well as the definition and encoding of SWES events. c Common – This package defines data types common to other packages. d Common Codes – This package defines commonly used lists of codes with special semantics. e DescribeSensor – This package defines the request and response types of an operation used to retrieve metadata about a given sensor. f UpdateSensorDescription – This package defines the request and response types of an operation used to modify the description of a given sensor. g InsertSensor – This package defines the request and response types of an operation used to insert a new sensor instance at a service. NOTE: insertion metadata required by a certain SWE service type shall be defined in the according implementation specification leveraging this operation h DeleteSensor – This package defines the request and response types of an operation used to remove a sensor from a service. NOTE: the semantic of deleting a sensor shall be defined by each implementation specification leveraging this operation These packages use data types specified in other standards. Those data types are normatively referenced herein, instead of being repeated in this standard. Figure 2 shows a UML diagram summarizing the external dependencies of the SWE Service Model. Cop Figure 2 — SWE Service Model external dependencies Figure 3 shows a UML diagram summarizing the package dependencies of the SWE Service Model. Figure 3 — SWE Service Model package dependencies Each of the eight packages is described in the following clauses. ht © 2011 Open Geospatial Consortium. 13 yrig 14 Copyright © 2011 Open Geospatial Consortium. 7 Contents

7.1 Introduction