Discovery Monitoring Authentication and Authorisation
6.7.4 Discovery
Meta-information is extensively used for resource discovery and is described in detail in section 6.6.3. The conceptual meta-information model is defined in section 7.6.3. Typical examples of meta-information necessary for the support of the search functionality are keyword-lists, spatial-temporal information and bounding areas. Examples of meta-information for the purpose of navigation are descriptions of the content and structure of catalogue content. The discovery of services requires a specific meta-information model and dedicated query languages to access the meta-information entries. Meta-information may be semantically annotated in order to increase the quality and the recall of the discovery process. Note: For automatic service discovery meta-information based on semantic service descriptions e.g. OWL-S or WSMO could be provided. However, as there is not yet a generally accepted standard, semantic service specifications will not be considered in the scope of the SANY project.6.7.5 Monitoring
According to section 6.6.2 monitoring is ap plied to the manageable components “sensor” and “service”. Meta-information for the purpose of monitoring includes status, actual load, usage statistics e.g. amount, quality, resolution and time span of downloaded data, used processing time, execution traces, etc. This meta-information is especially useful as input for composite services e.g. services resulting from service orchestration that rely on the data provided by other services. Furthermore, accounting applications that audit the usage of resources e.g. as a pre-requisite for billing rely on such monitoring information. Meta-information concerning accounting is a combination of the principal and some measure quota for resource usage.6.7.6 Authentication and Authorisation
Authentication and authorisation rely on meta-information necessary for controlling the access to services and enforcing access control policies see section 6.8.2. Typical meta-information for the purpose of authentication includes the identifier of the principal that uniquely identifies the subject. For the purpose of authorisation, meta-information necessary to enable restriction of the usage of resources on a per-principal basis have to exist. An authorisation process is used to decide whether a principal is allowed to access a certain resource or not. This type of meta- information is directly related to the services implementing the authorisation paradigm and is of minimal or no relevance for anything else. A specific set of meta-information makes up the authorisation context that is used by an authorisation service to decide on the authorisation for a given request before allowing access to the requested service operations. SANY D2.3.4 Specification of the Sensor Service Architecture V3 Doc.V3.1 Copyright © 2007-2009 SANY Consortium Page 90 of 2336.7.7 Quality control and management
Parts
» Specification of the Sensor Service Architecture (SensorSA)
» Executive Summary Specification of the Sensor Service Architecture (SensorSA)
» Intended Audience Abbreviations and acronyms
» General Remark Terms and Definitions
» Architectural Framework Specification of the Sensor Service Architecture (SensorSA)
» Relationship to the ORCHESTRA Architecture
» Requirements of GMES Enterprise Viewpoint
» Requirements of GEOSS Enterprise Viewpoint
» Requirements of Sensor Networks
» Overview Sensor Network User Requirements
» Data and Information User Requirements
» Data Quality Security User Requirements
» Processing and Fusion User Requirements
» Decision Support User Management
» Complex form of a Sensor Sensor System
» Overview Enterprise Viewpoint of a Sensor
» Engineering Viewpoint of a Sensor
» Service Viewpoint of a Sensor
» Information Viewpoint of a Sensor
» Overview Functional Domains Major Concepts of the Sensor Service Architecture
» Overview RequestReply Interaction Model
» Event-based Interaction Model Models of Interaction
» Event Definition Event-based Architectural Style
» Event Properties Event Model
» Event Verbosity Levels Event Model
» Form of Events Roles in Event Relationships
» Overview Event Processing Role Model
» Event Role Interfaces Event-Driven Processing System
» Resources Resources and their Identification
» URN Namespace for SANY Resources
» Naming principles Resources and their Identification
» Resource and Catalogue Types
» Sensor Planning Information Service Planning Functions
» Introduction Data and Service Integration Interpretation
» Discovery Monitoring Authentication and Authorisation
» The measurement process Uncertainty
» Access Control Service Architecture
» t Conceptual Building blocks for “Plug-and-Measure”
» Overview Information Model for Observations Measurements OM
» Information Model of the Sensor Observation Service
» Model for Subject Related Information Profiles and Identities
» SAML Security Assertion Markup Language
» XACML eXtensible Access Control Markup Language
» Event Information Model Information Viewpoint
» Resource representation Resource name
» Resource link Uniform Interface
» Introduction Relationship between Resources, Services and Features
» Overview Meta-information Schema for Discovery
» Meta-information Sections Related to Observation Discovery
» Overview Services of the OGC Sensor Web Enablement
» Sensor Observation Service Services of the OGC Sensor Web Enablement
» Web Notification Service Services of the OGC Sensor Web Enablement
» Overview Profile Management Service
» Policy Enforcement Service Access Control Services
» Overview Services of the Mediation, Processing and Application Domain
» Interfaces of WS-Base Notification Specification
» Properties of a Service Platform
» Specification of the SensorSA W3C Web Services Platform
» Specification of the SensorSA OGC Web Services Platform
» Specification of the SensorSA RESTful Web Services Platform
» Introduction Query Models Resource Discovery Policy
» Discovery of Observations Typical resource discovery policies
» Discovery of Procedures Typical resource discovery policies
» Event-based Harvesting Resource Discovery Policy
» Overview Policies for Sensor and Service Monitoring
» Policies for Sensor Planning
» “Non intrusive” at service level
» Delegate Anonymous Service Chain
» Patterns for Access Control in a Multi-Protocol Environment Usage of SAML
» Attachment of quality information
» Data flow optimization Providing alternative views to data
» Data pre-processing Multi-level sensor data storage
» Processing Chain Service Processing Chains .1 Introduction
» Approach Combining Earth Observation and In-situ data .1 Introduction
» Integration of Mobile Sensors
» Definition and Subscription of Events
» Sensor Plug In Plug-and-measure Support
» Sensor recognition and connection establishment Sensor Adapters
Show more