Properties of a Service Platform

SANY D2.3.4 Specification of the Sensor Service Architecture V3 Doc.V3.1 Copyright © 2007-2009 SANY Consortium Page 164 of 233

9. Technology Viewpoint

The Technology Viewpoint of the SensorSA specifies the technological choices of the concrete service platform and its operational issues. To accommodate the requirements of Sensor Networks as introduced in section 4.5 the SensorSA refines the guidelines and requirements for platform specifications as defined in the Technology Viewpoint of the ORCHESTRA Reference Model RM-OA, 2007. These guidelines comprise: - a general approach for how to specify a service platform see section 9.1, - the specification of the SANY service platform - a description of how access control mechanisms are being implemented section 9.3.1, - an agreement on data formats see section 9.3.2, and - optionally a set of restrictions to be observed for a particular platform.

9.1. Properties of a Service Platform

As a general guideline, the specification of a service platform shall be conformant to the OASIS Reference Model for Service Oriented Architecture 1.0 SOA-RM, 2006. This implies that the platform is being described according to the SOA-RM by the following predefined platform properties: - Platform Name Name of the platform and if applicable the exact version number of the platform specification. In the case of a standard platform, a reference shall be provided. - Reference Model If the platform specification is based on a specific reference model, the name and the exact version number of the reference model shall be provided. - Interface Language Specification of the formal machine-processable language used to define SOA-RM Service Interfaces. In the case of a standard language, a reference shall be provided. - Execution Context Specification of the SOA-RM Execution Context. The Execution context is an agreement between service providers and consumers. It contains information that can include preferred protocols, semantics, policies and other conditions and assumptions that describe how a service can and may be used. This includes, for example, the specification of the transport and the security layer, the format of the messages exchanged between service providers and consumers, etc. In the case of a standard SOA-RM Execution Context, a reference shall be provided. SANY D2.3.4 Specification of the Sensor Service Architecture V3 Doc.V3.1 Copyright © 2007-2009 SANY Consortium Page 165 of 233 - Schema Language Specification of the schema language used to define SOA-RM Information Models. - Schema Mapping Specification of how to map the abstract level UML to the schema language used for this particular platform. - Information Model Constraints Specification of the constraints on the SOA-RM Information Model, especially the constraints on the message format which is required to accomplish the SOA-RM Action model.

9.2. The SensorSA Service Platform