Abbreviated terms OGC® Sensor Planning Service Implementation Standard

8 Copyright © 2011 Open Geospatial Consortium

5.2 UML notation

Diagrams that appear in this standard are presented using the Unified Modeling Language UML static structure diagram, as described in Subclause 5.2 of [OGC 06-121r3]. NOTE Packages and data types from foreign namespaces or data types from packages other than the one under consideration are shown with grey background unless they are given only as types of attributes from classes in the model defined in this specification. Interfaces are shown with light turquoise background.

5.3 Platform-neutral and platform-specific standards

For compliance with Clause 10 of OGC Topic 12 and ISO 19119, this standard follows the pattern defined in subclause 5.4 of [OGC 06-121r3]. That is, model elements are specified in platform-neutral fashion first, using tables that serve as data dictionaries for the UML model see clause 5.4 of this document. Platform-specific encodings of these model elements are provided in separate clauses or documents. The XML Schema encoding has automatically been generated using the rules defined in clause 24 of [OGC 09-001]. This document specifies platform-specific encodings appropriate for a SOAPWSDL operation binding. However, the model as well as its XML Schema encoding and other data can be used by other bindings as well, like RESTful or POX Plain Old XML over HTTP using XML or KVP encoding.

5.4 Data dictionary tables

The UML model data dictionary is specified herein in a series of tables. The contents of the columns in these tables are described in table 1 of [OGC 06-121r3]. The contents of these data dictionary tables are normative, including any table footnotes.

5.5 Classes imported from other specifications with predefined XML encoding

This specification uses an automatic mapping approach from the UML model to the XML Schema encoding. The approach is described in chapter 24 of [OGC 09-001]. As shown in Figure 13, this standard uses types defined by other standards. For the mapping to XML Schema, the implementation instructions listed in table D.2 of [OGC 07-036] are used together with the instructions listed in Table 2, Table 3 and Table 4 in this standard and Table 4 from [OGC 09-001]. For an explanation of the table columns, see clause D.2.1 in OGC 07-036. Copyright © 2011 Open Geospatial Consortium 9 Table 2 — Implementation of types from OWS Common [OGC 06-121r3] UML class object element type property type AbstractMetadata ows:AbstractMetaData - - GetCapabilities - ows:GetCapabilitiesType - LanguageString - ows:LanguageStringType - OWSServiceMetadata - ows:CapabilitiesBaseType - ReferenceGroup ows:ReferenceGroup ows:ReferenceGroupType - Table 3 — Implementation of types from SWE Common Data Model [OGC 08-094] UML class object element type property type AbstractDataCom ponent swe:AbstractDataCo mponent swe:AbstractDataCompo nentType swe:AbstractDataComponentP ropertyType AbstractEncoding swe:AbstractEncodin g swe:AbstractEncodingTy pe swe:AbstractEncodingPropert yType Table 4 — Implementation of types from SWE Service Model [OGC 09-001] UML class object element type property type AbstractContents swes:AbstractContent s swes:AbstractContentsTy pe swes:AbstractContentsProper tyType AbstractOffering swes:AbstractOffering swes:AbstractOfferingTy pe swes:AbstractOfferingProper tyType ExtensibleRequest swes:ExtensibleReque st swes:ExtensibleRequestT ype swes:ExtensibleRequestProp ertyType ExtensibleRespons e swes:ExtensibleRespo nse swes:ExtensibleResponse Type swes:ExtensibleResponsePro pertyType NotificationProduc erMetadata swes:NotificationProd ucerMetadata swes:NotificationProduce rMetadataType swes:NotificationProducerM etadataPropertyType