Copyright © 2007 Open Geospatial Consortium, Inc. All Rights Reserved.
3 such as way that the offering is “dense” in the sense that requests for observations that are
within the specified parameters should be unlikely to result in an empty set.
4.5 Phenomenon
Characteristic of one or more feature types, the value for which must be estimated by application of some procedure in an observation. [OGC 07-022r1]
4.6 Procedure
Method, algorithm or instrument. [OGC 07-022r1]
4.7 Result
An estimate of the value of some property generated by a known procedure. [OGC 07- 022r1]
4.8 Sensor
An entity capable of observing a phenomenon and returning an observed value. [OGC 07-000]
4.9 Sensor Platform
An entity to which can be attached sensors or other platforms. A platform has an associated local coordinate frame that can be referenced to an external coordinate
reference frame and to which the frames of attached sensors and platforms can be referenced. [OGC 07-000]
5 Conventions
5.1 Symbols and abbreviated terms
API Application Programming
Interface DCP Distributed
Computing Platform
CS-W Catalog Service Web
GML Geography Markup Language
ISO International Organization for Standardization
OGC Open Geospatial Consortium
OWS OGC Web
Services OM
Observations and Measurements SensorML
Sensor Model Language
4
Copyright © 2007 Open Geospatial Consortium, Inc. All Rights Reserved.
SAS Sensor Alert Service
SOS Sensor Observation Service [formerly Sensor Collection Service, SCS]
SOS-T Sensor Observation Service – transactional profile
SPS Sensor Planning Service
SWE Sensor Web
Enablement TML Transducer
Markup Language
UML Unified Modeling Language
WNS Web Notification Service
XML eXtensible Markup
Language
5.2 UML Notation
Some diagrams that appear in this specification are presented using the Unified Modeling Language UML static structure diagram, as described in Subclause 5.2 of [OGC 06-
121r3].
5.3 XML schema notation
Most diagrams that appear in this specification are presented using an XML schema notation defined by the XMLSpy
1
product and described in this subclause. XML schema diagrams are for informative use only, though they shall reflect the accompanied UML
and schema perfectly. The following sub-clauses provide an overview of the most commonly appearing
elements of XML Spy diagrams. For a complete description, see http:www.altova.commanual2007XMLSpySpyEnterpriseindex.html?schemadesignvi
ew.htm .
5.3.1 Element
A named rectangle representing the most basic part of the XML Schema notation. Each represents an XML “Element” token. Each Element symbol can be elaborated with extra
information as shown in the examples below.
1
XML Spy: http:www.altova.com
Copyright © 2007 Open Geospatial Consortium, Inc. All Rights Reserved.
5
Figure 5-1. Simple XML Spy element
This is a mandatory simple element. Note the upper left corner of the rectangle indicates that data is contained in this element.
5.3.2 Optional Element
Optional non mandatory elements are specified with dashed lines used to frame the rectangle.
Figure 5-2. Optional XML Spy element
5.3.3 Recurring Element
This element and its child elements if it has any can occur multiple times.
Figure 5-3. Recurring XML Spy element
This example shows a recurring element that must occur at least once but can occur an unlimited number of times. The upper bound here is shown with the infinity symbol.
5.3.4 Sequence Connector
The connection box, called a sequence indicator, indicates that the “SequenceElement” data is made up of three elements in a fixed order. In this example, the first two elements
are mandatory and the third element is optional.
6
Copyright © 2007 Open Geospatial Consortium, Inc. All Rights Reserved.
Figure 5-4. Sequence Connector in XML Spy
5.3.5 Choice Connector
The connection box here is a “choice” indicator, indicating that there is always going to be exactly one of the child elements listed on the right.
Figure 5-5. Choice Connector in XML Spy
5.3.6 Definition with Complex Type
This diagram illustrates the use of a complex type i.e., “ex:AbstractElementType” in the declaration of an XML element e.g., “AbstractElement”.
Copyright © 2007 Open Geospatial Consortium, Inc. All Rights Reserved.
7
Figure 5-6. Definition with Complex Element in XML Spy 5.3.7
Complex Type
This diagram illustrates the definition of a complex type i.e., “AbstractElementType”, extending another complex type i.e.,“ex:BaseElementType” with three additional
elements. Complex types describe a content model, and can be reused to specify that different elements have the same content model.
Figure 5-7. Complex Type in XML Spy
8
Copyright © 2007 Open Geospatial Consortium, Inc. All Rights Reserved.
6 SOS Overview
6.1 General Approach
