SIST-TP CEN/TR 15449-4:2013

Geographic information - Spatial Data Infrastructure - Service centric view

This Technical Report describes a service-centric view of a Spatial Data Infrastructure (SDI). The Service Centric view addresses the concepts of service specifications, the methodology for developing service specifications through the application of the relevant International Standards, and the content of such service specifications described from the perspective of the five Reference Model of Open Distributed Processing (RM-ODP) viewpoints: - the enterprise viewpoint addresses service aspects from an organisational, business and user perspective; - the computational viewpoint addresses service aspects from a system architect perspective; - the information viewpoint addresses service aspects from a geospatial information expert perspective; - the engineering viewpoint addresses service aspects from a system designer perspective; - the technology viewpoint addresses service aspects from a system builder and implementer perspective. The intended readership of this Technical Report is those people who are responsible for creating frameworks for SDI, experts contributing to INSPIRE experts in information and communication technologies and e-government that need to familiarise themselves with geographic information and SDI concepts, and standards developers and writers.

Geoinformation - Geodateninfrastrukturen - Teil 4: Service-zentrierte Sicht

Information Géographique - Infrastructure de données spatiales - Vue centrée services

Geografske informacije - Infrastrukture za prostorske podatke - 4. del: Storitveno usmerjen vidik

To tehnično poročilo opisuje storitveno usmerjen vidik infrastrukture za prostorske podatke (SDI). Storitveno usmerjen vidik obravnava koncepte specifikacij storitev, metodologijo za razvoj specifikacij storitev z uporabo ustreznih mednarodnih standardov in vsebino teh specifikacij storitev, ki je opisana na podlagi petih vidikov referenčnega modela RM-ODP: – vidik podjetja obravnava vidike storitev s stališča organizacije, poslovanja in uporabnika; – računalniški vidik obravnava vidike storitev s stališča sistemskega arhitekta; – informacijski vidik obravnava vidike storitev s stališča strokovnjaka za geoprostorske informacije; – inženirski vidik obravnava vidike storitev s stališča oblikovalca sistema; – tehnološki vidik obravnava vidike storitev s stališča ustvarjalca in izvajalca sistema. To tehnično poročilo je namenjeno ciljnim skupinam ljudi, ki so odgovorni za oblikovanje okvirov infrastrukture za prostorske podatke, strokovnjakom, ki prispevajo k direktivi INSPIRE, strokovnjakom na področju informacijskih in komunikacijskih tehnologij, e-upravi, ki se mora seznaniti s konceptoma geografskih informacij in infrastrukture za prostorske podatke, ter pripravljavcem in avtorjem standardov.

General Information

• Status: Published
• Publication Date: 12-Sep-2013
• ICS: 07.040 - Astronomy. Geodesy. Geography
• ICS: 35.240.70 - IT applications in science
• Technical Committee: GIG - Geographic information
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 31-Jul-2013
• Due Date: 05-Oct-2013
• Completion Date: 13-Sep-2013
• Ref Project: CEN/TR 15449-4:2013 - Geographic information - Spatial Data Infrastructure - Part 4: Service centric view

Standards Content (sample)

SLOVENSKI STANDARD
SIST-TP CEN/TR 15449-4:2013
01-oktober-2013

Geografske informacije - Infrastrukture za prostorske podatke - 4. del: Storitveno

usmerjen vidik
Geographic information - Spatial Data Infrastructure - Service centric view
Geoinformation - Geodateninfrastrukturen - Teil 4: Service-zentrierte Sicht

Information Géographique - Infrastructure de données spatiales - Vue centrée services

Ta slovenski standard je istoveten z: CEN/TR 15449-4:2013
ICS:
07.040 Astronomija. Geodezija. Astronomy. Geodesy.
Geografija Geography
35.240.70 Uporabniške rešitve IT v IT applications in science
znanosti
SIST-TP CEN/TR 15449-4:2013 en,fr,de

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------
SIST-TP CEN/TR 15449-4:2013
---------------------- Page: 2 ----------------------
SIST-TP CEN/TR 15449-4:2013
TECHNICAL REPORT
CEN/TR 15449-4
RAPPORT TECHNIQUE
TECHNISCHER BERICHT
July 2013
ICS 35.240.70
English Version
Geographic information - Spatial Data Infrastructure - Service
centric view

Information Géographique - Infrastructure de données Geoinformation - Geodateninfrastrukturen - Teil 4: Service-

spatiales - Vue centrée services zentrierte Sicht

This Technical Report was approved by CEN on 20 November 2012. It has been drawn up by the Technical Committee CEN/TC 287.

CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia,

Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania,

Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and United

Kingdom.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION
EUROPÄISCHES KOMITEE FÜR NORMUNG
Management Centre: Avenue Marnix 17, B-1000 Brussels

© 2013 CEN All rights of exploitation in any form and by any means reserved Ref. No. CEN/TR 15449-4:2013: E

worldwide for CEN national Members.
---------------------- Page: 3 ----------------------
SIST-TP CEN/TR 15449-4:2013
CEN/TR 15449-4:2013 (E)
Contents Page

1 Scope ................................................................................................................................................ 7

2 Normative references ....................................................................................................................... 7

3 Terms and definitions ...................................................................................................................... 7

4 Abbreviated terms ............................................................................................................................ 9

5 Service-centric view on SDI ........................................................................................................... 10

5.1 Introduction .................................................................................................................................... 10

5.2 Use of RM-ODP viewpoints ............................................................................................................ 11

5.2.1 The enterprise viewpoint ............................................................................................................... 11

5.2.2 The computational viewpoint ........................................................................................................ 12

5.2.3 The information viewpoint ............................................................................................................. 12

5.2.4 The engineering viewpoint ............................................................................................................ 12

5.2.5 The technology viewpoint .............................................................................................................. 12

5.3 Relationships between viewpoints ................................................................................................ 12

5.4 Service models, processes and service oriented architectures .................................................. 13

5.5 The model-driven approach ........................................................................................................... 13

5.6 System-of-Systems Engineering ................................................................................................... 13

6 Enterprise viewpoint ...................................................................................................................... 15

6.1 Overview ......................................................................................................................................... 15

6.2 Relevant standards ........................................................................................................................ 16

6.3 Example and tools.......................................................................................................................... 16

7 Computational viewpoint ............................................................................................................... 17

7.1 Overview ......................................................................................................................................... 17

7.2 Relevant standards ........................................................................................................................ 17

7.3 Examples and tools ........................................................................................................................ 18

7.3.1 Service Modeling with SoaML ....................................................................................................... 18

7.3.2 Lifecycle Service Components ...................................................................................................... 18

7.3.3 Value Chain of SDI Knowledge Generation ................................................................................... 19

7.3.4 Overview of Stakeholders .............................................................................................................. 19

7.3.5 Requirements for a next generation of SDI Services ................................................................... 20

7.4 Architecture-based Enabler Classification ................................................................................... 21

8 Information viewpoint .................................................................................................................... 22

8.1 Introduction .................................................................................................................................... 22

8.2 Relevant standards ........................................................................................................................ 24

8.3 Examples and tools ........................................................................................................................ 24

9 Engineering viewpoint ................................................................................................................... 25

9.1 Overview ......................................................................................................................................... 25

9.2 Multi-style SOA ............................................................................................................................... 25

9.3 Relevant standards ........................................................................................................................ 27

9.3.1 Service-Oriented-Architectures ..................................................................................................... 27

9.3.2 Representational State Transfer (REST) ....................................................................................... 28

9.3.3 Web 2.0 ........................................................................................................................................... 28

10 Technology viewpoint .................................................................................................................... 29

10.1 Overview ......................................................................................................................................... 29

10.2 Architectural Classification according to Cloud Computing Service Categories ....................... 30

11 Services and Security .................................................................................................................... 30

11.1 Services - security and rights management ................................................................................. 30

11.2 Managing access and re-use rights .............................................................................................. 31

11.3 Drivers of effective rights management ........................................................................................ 31

---------------------- Page: 4 ----------------------
SIST-TP CEN/TR 15449-4:2013
CEN/TR 15449-4:2013 (E)

11.4 Challenges of implementing rights management ........................................................................ 32

11.5 Securing OGC Web Services ........................................................................................................ 32

11.6 Security Requirements .................................................................................................................. 33

Annex A (informative) RM-ODP viewpoints and the Parts of CEN/TR 15449 ........................................... 35

Annex B (informative) Example – Use case based methodology ............................................................. 36

Annex C (informative) Example – Use case template ............................................................................... 39

Annex D (informative) Service Modeling - SoaML ..................................................................................... 42

---------------------- Page: 5 ----------------------
SIST-TP CEN/TR 15449-4:2013
CEN/TR 15449-4:2013 (E)
Foreword

This document (CEN/TR 15449-4:2013) has been prepared by Technical Committee CEN/TC 287 “Geographic

information”, the secretariat of which is held by BSI.

Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights.

CEN [and/or CENELEC] shall not be held responsible for identifying any or all such patent rights.

CEN/TR 15449, Geographic information - Spatial data infrastructures, consists of the following parts:

 Part 1: Reference model
 Part 2: Best practices
 Part 3: Data centric view
 Part 4: Service centric view.
---------------------- Page: 6 ----------------------
SIST-TP CEN/TR 15449-4:2013
CEN/TR 15449-4:2013 (E)
Introduction

Spatial Data Infrastructure (SDI) is a general term for the computerised environment for handling data that relates to a

position on or near the surface of the earth. It may be defined in a range of ways, in different circumstances, from the

local up to the global level.

This Technical Report focuses on the technical aspects of SDIs, thereby limiting the term SDI to mean an

implementation neutral technological infrastructure for geospatial data and services, based upon standards and

specifications. It does not consider an SDI as a carefully designed and dedicated information system; rather, it is

viewed as a collaborative framework of disparate information systems that contain resources that stakeholders desire

to share. The common denominator of SDI resources, which can be data or services, is their spatial nature. It is

understood that the framework is in constant evolution, and that therefore the requirements for standards and

specifications supporting SDI implementations evolve continuously.

SDIs are becoming more linked and integrated with systems developed in the context of e-Government. Important

drivers for this evolution are the Digital Agenda for Europe, and related policies . By sharing emerging requirements

at an early stage with the standardization bodies, users of SDIs can help influence the revision of existing or the

conception of new standards. A number of recommendations are made within the Eye on Earth White Paper [1] which

provides additional context and background to the service centric view.

The users of an SDI are considered to be those individuals or organisations that, in the context of their business

processes, need to share and access geo-resources in a meaningful and sustainable way. Based on platform- and

vendor-neutral standards and specifications, an SDI aims at assisting organisations and individuals in publishing,

finding, delivering, and eventually, using geographic information and services over the internet across borders of

information communities in a more cost-effective manner.

Existing material about SDIs abounds. The following reports have been taken into account in the preparation of this

Technical Report:
• legal texts and guidelines produced in the context of INSPIRE;
• documents produced by ISO/TC 211 (and co-published by CEN);

• documents produced by the Open Geospatial Consortium (OGC), including the OpenGIS Reference Model

(ORM) [2];
• the European Interoperability Framework and related documents;

• deliverables from European Union-funded projects (e.g. ORCHESTRA, GIGAS, SANY, ENVISION, ENVIROFI,

EO2HEAVEN) .

Considering the complexity of the subject and the need to capture and formalise different conceptual and modelling

views, CEN/TR 15449 is comprised of multiple parts:

• Part 1: Reference model: This part provides a general context model for the other Parts, applying general IT

architecture standards;

• Part 2: Best Practice: This part provides best practices guidance for implementing SDI, through the evaluation of

the projects in the frame of the European Union funding programmes;
1) As described in Part 1 of this Technical Report.
2) A list of EU Funded projects is given in Part 2 of this Technical Report.
---------------------- Page: 7 ----------------------
SIST-TP CEN/TR 15449-4:2013
CEN/TR 15449-4:2013 (E)

• Part 3: Data centric view: This part addresses concerns related to the data, which includes application schemas

and metadata;
• Part 4: Service centric view: This current document.
Further parts may be created in the future.
---------------------- Page: 8 ----------------------
SIST-TP CEN/TR 15449-4:2013
CEN/TR 15449-4:2013 (E)
1 Scope

This Technical Report describes a service-centric view of a Spatial Data Infrastructure (SDI).

The Service Centric view addresses the concepts of service specifications, the methodology for developing service

specifications through the application of the relevant International Standards, and the content of such service

specifications described from the perspective of the five Reference Model of Open Distributed Processing (RM-ODP)

viewpoints:

• the enterprise viewpoint addresses service aspects from an organisational, business and user perspective;

• the computational viewpoint addresses service aspects from a system architect perspective;

• the information viewpoint addresses service aspects from a geospatial information expert perspective;

• the engineering viewpoint addresses service aspects from a system designer perspective;

• the technology viewpoint addresses service aspects from a system builder and implementer perspective.

The intended readership of this Technical Report is those people who are responsible for creating frameworks for SDI,

experts contributing to INSPIRE experts in information and communication technologies and e-government that need

to familiarise themselves with geographic information and SDI concepts, and standards developers and writers.

2 Normative references
Not applicable.
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
3.1
architecture

fundamental organisation of a system embodied in its components, their relationship to each other and the

environment, and the principles guiding its design and evolution
[SOURCE: IEEE 1471-2000].
3.2
architectural style

co-ordinated set of architectural constraints that restricts the roles/characteristics of architectural elements and the

allowed relationships among those elements within an architecture that conforms to that style

[SOURCE: [3], modified]
3.3
conceptual formalism
set of modelling concepts used to describe a conceptual model
[SOURCE: EN ISO 19101:2005]
EXAMPLE UML meta model, EXPRESS meta model.

Note 1 to entry One conceptual formalism can be expressed in several conceptual schema languages.

---------------------- Page: 9 ----------------------
SIST-TP CEN/TR 15449-4:2013
CEN/TR 15449-4:2013 (E)
3.4
conceptual model
model that defines concepts of a universe of discourse
[SOURCE: EN ISO 19101:2005]
3.5
conceptual schema
formal description of a conceptual model
[SOURCE: EN ISO 19101:2005]
3.6
conceptual schema language

formal language based on a conceptual formalism for the purpose of representing conceptual schemas

[SOURCE: EN ISO 19101:2005]
EXAMPLE UML, EXPRESS, IDEF1X.

Note 1 to entry: A conceptual schema language may be lexical or graphical. Several conceptual schema languages can be

based on the same conceptual formalism.
3.7
conformance
fulfilment of specified requirements
[SOURCE: EN ISO 19113:2005]
3.8
component

physical, replaceable part of a system that packages implementation and provides the realisation of a set of interfaces

[ISO/TS 19103:2005]
3.9
identifier

linguistically independent sequence of characters capable of uniquely and permanently identifying that with which it is

associated
[SOURCE: ISO/IEC 11179-3:2003]
3.10
interface
named set of operations that characterise the behaviour of an entity
[SOURCE: ISO 19119:2005]
3.11
interoperability

capability to communicate, execute programs, or transfer data among various functional units in a manner that

requires the user to have little or no knowledge of the unique characteristics of those units

[SOURCE: ISO/IEC 2382-1:1993]
3.12
reference frame
aggregation of the data needed by different components of an information system
---------------------- Page: 10 ----------------------
SIST-TP CEN/TR 15449-4:2013
CEN/TR 15449-4:2013 (E)
3.13
resource
asset or means that fulfils a requirement
[SOURCE: EN ISO 19115:2005]
3.14
Service
delivery of value to another party, enabled by one or more capabilities
[SOURCE: OMG SoaML]
3.15
use case

specification of a sequence of actions, including variants, that a system (or other entity) can perform, interacting with

actors of the system
[SOURCE: OMG UML Specification]
4 Abbreviated terms
API Application Programming Interface
AJAX Asynchronous JavaScript and XML
BPMN Business Process Model and Notation
BMM Business Motivation Metamodel
INSPIRE Infrastructure for Spatial Information in Europe
GIGAS GEOSS, INSPIRE and GMES an Action in Support
GEOSS Global Earth Observation System of Systems
GMES Global Monitoring for Environment and Security
GML Geography Markup Language
HTTP Hyper-text Transfer Protocol
IaaS Infrastructure as a Service
IT Information Technology
JSON Javascript Object Notation
OASIS Organisation for the Advancement of Structured Information Standards
ORCHESTRA Open Architecture and Spatial Data Infrastructure for Risk Management
ODP Open Distributed Processing
OGC Open Geospatial Consortium
OMG Object Management Group
ORM OpenGIS Reference Model
---------------------- Page: 11 ----------------------
SIST-TP CEN/TR 15449-4:2013
CEN/TR 15449-4:2013 (E)
PaaS Platform as a Service
REST Representational State Transfer
RM-ODP Reference Model of Open Distributed Processing
RPC Remote Procedure Call
SANY Sensors Anywhere
SaaS Software as a Service
SDI Spatial Data Infrastructure
SEIS Shared Environmental Information System
SOA Service Oriented Architecture
SoaML Service oriented architecture Modeling Language
SOAP Simple Object Access Protocol
SoS System of Systems
UDDI Universal Description, Discovery and Integration
UML Unified Modelling Language
USDL Universal Service Description Language
WSDL Web Service Description Language
W3C World Wide Web Consortium
XHTML eXtensible HyperText Markup Language
XML eXtensible Markup Language
5 Service-centric view on SDI
5.1 Introduction

Spatial Data Infrastructures can be regarded as a set of interconnected, distributed, information systems. Their

complexity calls for a structured approach to address properly the many facets. ISO/IEC 10746-1, Information

technology - Open Distributed Processing - Reference Model: Overview provides an overall conceptual framework for

building open distributed processing systems in an incremental manner. The viewpoints of the RM-ODP standards

have been widely adopted: they constitute the conceptual basis for the ISO 19100 series of geomatics standards, and

they also have been employed in the OMG object management architecture [5].

This part of CEN/TR 15449 addresses the concepts of service specifications and the methodology for developing

service specifications through the application of the relevant International Standards based on RM-ODP. The

architecture is a set of components, connections and topologies defined through a series of viewpoints. The spatial

data infrastructure of interest for this Technical Report will have multiple users, developers, operators and reviewers.

Each group will view the system from their own perspective. The purpose of the architecture is to provide a description

of the system from multiple viewpoints. The architecture helps to ensure that each viewpoint will be consistent with the

requirements and with the other viewpoints.
3) Original meaning of the acronym SOAP, however, its use has been deprecated.
---------------------- Page: 12 ----------------------
SIST-TP CEN/TR 15449-4:2013
CEN/TR 15449-4:2013 (E)

According to RM-ODP, the content of such service specifications is described from the perspective of the five

viewpoints, which enable the separation of concerns:

 The enterprise viewpoint - service aspects from an organisational, business and user perspective.

 The computational viewpoint - service aspect from a system architect perspective.

 The information viewpoint - service aspects from a geospatial information expert perspective.

 The engineering viewpoint - service aspects from a system designer perspective.

 The technology viewpoint - service aspects from a system builder and implementer perspective.

This Technical Report focuses on platform independent descriptions of services, from the viewpoints of different

stakeholders and concerns. References are given to relevant standards that can be used further for this, both for

platform-independent and platform-dependent descriptions related to services. Figure 1 (adopted from [5]) illustrates

the main focus of each of the five RM-ODP viewpoints, and the main question that each viewpoint addresses.

Figure 1 — ISO RM-ODP viewpoints
5.2 Use of RM-ODP viewpoints
5.2.1 The enterprise viewpoint

The enterprise viewpoint is concerned with the purpose, scope and policies of an enterprise or business and how they

relate to the specified system or service. An enterprise specification of a service is a model of that service and the

environment with which the service interacts. It covers the role of the service in the business and the human-user

roles and business policies related to the service. In the context of the service centric view there is a particular focus

on the use cases and external functionally related to the particular services.
---------------------- Page: 13 ----------------------
SIST-TP CEN/TR 15449-4:2013
CEN/TR 15449-4:2013 (E)
5.2.2 The computational viewpoint

The computational viewpoint is concerned with the interaction patterns between the components (services) of the

system, described through their interfaces. A computational specification of a service is a model of the service

interface seen from a client, and the potential set of other services that this service requires to have available, with the

interacting services described as sources and sinks of information.
5.2.3 The information viewpoint

The information viewpoint is concerned with the semantics of information and information processing. An information

specification of an ODP system is a model of the information that it holds and of the information processing that it

carries out. In the context of the service centric view there is a particular focus on the information being used and

provided by the particular services.
5.2.4 The engineering viewpoint

The engineering viewpoint is concerned with the design of distribution-oriented aspects, i.e. the infrastructure required

to support distribution. An engineering specification of an ODP system defines a networked computing infrastructure

that supports the system structure defined in the computational specification and provides the distribution

transparencies that it defines. ODP defines the following distribution transparencies: access, failure, location,

migration, relocation, replication, persistence and transaction. Security may also be a mechanism.

5.2.5 The technology viewpoint

The technology viewpoint describes the implementation of the ODP system in terms of a configuration of technology

objects representing the hardware and software components of the implementation. It is constrained by cost and

availability of technology objects (hardware and software products) that would satisfy this specification. These may

conform to platform-specific standards that are effectively templates for technology objects.

5.3 Relationships between viewpoints

There are important relationships between the viewpoints. In particular, for the service-centric view on SDIs, it is

important to see the relationship to the use of services from the enterprise viewpoint, the information being provided

as input and output to services from the information viewpoint, the logical service architecture itself from the

computation viewpoint, the different mechanisms and architectural patterns used for distribution and different

architectural styles around services in the engineering viewpoint, and the actual technologies being used in the

technology viewpoint. For this reason, this part of the Technical Report is structured according to the various ODP

viewpoints – and describes the relevant service-centric aspects within each of the viewpoints.

Each Part of this Technical Report has an emphasis anchored in one of the RM-ODP viewpoints. These are illustrated

in Annex A. Figure 2 shows how the following clauses are dedicated to describing the service-centric for SDIs from

the various ODP viewpoints.
---------------------- Page: 14 ----------------------
SIST-TP CEN/TR 15449-4:2013
CEN/TR 15449-4:2013 (E)
Clause 6
Enterprise
Viewpoint
Computational Information
Viewpoint Viewpoint
Engineering Technology
Viewpoint Viewpoint
Implementation
Figure 2 — Clauses and corresponding RM-ODP viewpoints
5.4 Service models, processes and service oriented architectures

The spatial data in an SDI provides a model of the real world. On top of the data, services can be built to make the

data accessible through the web and to use it in an information system by e.g. viewing, downloading, or processing

them. A Service Oriented Architecture (SOA) enables new and existing enterprise systems to share services,

information and data across technical platforms, departments and ultimately across organisational and regional

boundaries. In current systems, services are also used as an integration approach for multiple architectural styles,

including both document styles and synchronous RPC (Remote Procedure Call) styles of services, and also include

integration with event management and an event driven architectural styles as well as support for interaction with

sensors through services. Process support as with process management and workflow systems, including service

composition, orchestration and choreography, can be viewed as the sequencing of behaviour in the implementation of

services.
5.5 The model-driven approach

A model driven approach has been established in both ISO/TC211 and OGC in particular for the data-centric view, but

is now also emerging from services. Recent work in international standards such as SoaML (from OMG) and current

activities such as USDL (from W3C), provides new facilities for the modelling and specification also of services in a

platform neutral way.

The further description of approaches for service modelling is further described in the sections about SoaML and

USDL under the computational viewpoint.
5.6 System-of-Systems Engineering

The notion of “System of Systems” (SoS) and “System of Systems Engineering” (SoSE) emerged in many fields of

applications, to address the common problem of integrating many independent, autonomous systems, frequently of

large dimensions, in order to satisfy a global goal while keeping them autonomous. A System of Systems is defined as

a large-scale integrated system that is heterogeneous and consists of sub-systems that are independently operable,

but are networked together for a common goal.
In spite of
...