CEN/TR 15449-2:2012
(Main)Geographic information - Spatial data infrastructures - Part 2: Best practices
Geographic information - Spatial data infrastructures - Part 2: Best practices
This part of the Technical Report provides best practices regarding Spatial Data Infrastructures (SDIs), referencing to the outcomes of the projects in the frame of the European Union funding programmes. It summarises the deliverables of projects, structured according to the reference model defined in Part 1 of this Technical Report, to be made available in an on-line repository where the relevant outcomes are collected and classified in order to provide a structured sets of recommendations for implementing SDIs at the European, national and sub-national levels.
This collection refers mainly to the projects funded by the European Union funding programmes: this choice is driven by the wide vision and analysis which such kind of projects can provide and the wide numbers of stakeholders which have been involved.
The outcomes delivered by these relevant practices are collected into a document registry available through the CEN/TC 287 web site. This part of the Technical Report defines the processes and the content of these projects and documents registries, which will help making them more accessible and re-usable. It provides the relevant project deliverables addressing the main SDI issues as described in the other parts of this Technical Report.
The intended readership of this Technical Report are 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 2: Best practices
Dieser Teil des Technischen Berichts enthält Informationen zu den besten Verfahrensweisen (Best Practices) im Zusammenhang mit Geodateninfrastrukturen (GDI), wobei Bezug genommen wird auf Projekte, die im Rahmen von EU Förderprogrammen durchgeführt wurden. Die Ergebnisse dieser Projekte werden zusammenfassend vorgestellt, und zwar strukturiert entsprechend dem in Teil 1 dieses Technischen Berichts definierten Referenzmodell; sie sollen später in einem Online Archiv, in dem relevante Ergebnisse gesammelt und klassifiziert werden, zur Verfügung gestellt werden, um so einen strukturierten Satz von Empfehlungen hinsichtlich der Implementierung von GDI auf europäischer, nationaler und regionaler Ebene zu bieten.
Diese Sammlung bezieht sich in erster Linie auf Projekte, die im Rahmen der EU Förderprogramme finanziert wurden. Diese Auswahl gründet sich auf die langfristigen Perspektiven und Analysen, die mit derartigen Projekten möglich sind und die große Anzahl der beteiligten interessierten Kreise.
Die Ergebnisse der jeweiligen Verfahrensweisen werden in einer Registry für Dokumente gesammelt, die über die Website des CEN/TC 287 zugänglich ist. Der vorliegende Teil dieses Technischen Berichts definiert die Prozesse und den Inhalt dieser Projekte und Registries, wodurch diese leichter zugänglich und wieder verwendbar werden. Bereitgestellt werden die entsprechenden Ergebnisse der Projekte unter Bezugnahme auf die wesentlichen Aspekte einer GDI, die in den übrigen Teilen dieses Technischen Berichts beschrieben sind.
Der vorliegende Technische Bericht wendet sich an die Entwickler von GDI Architekturen, an die an der Erarbeitung der INSPIRE Richtlinie beteiligten Fachleute, Experten auf dem Gebiet der Informations und Kommunikationstechnologie und des E Governments, die sich mit Geoinformations und GDI Konzepten vertraut machen müssen, sowie an die Entwickler und Autoren von Normen und Standards.
Information géographique - Infrastructures de données spatiales - Partie 2: Bonnes pratiques
Geografske informacije - Infrastrukture za prostorske podatke - 2. del: Dobre prakse
Ta del tehničnega poročila zagotavlja dobre prakse v zvezi z infrastrukturami za prostorske podatke (SDI), pri čemer se sklicuje na rezultate projektov v okviru programov Evropske unije za financiranje. Vsebuje povzetek izsledkov projektov, strukturiranih v skladu z referenčnim modelom iz 1. dela tega tehničnega poročila, ki se objavijo v spletni zbirki, v okviru katere se zbirajo in razvrščajo ustrezni rezultati, da se zagotovijo strukturirani sklopi priporočil za izvajanje infrastruktur za prostorske podatke na evropski, nacionalni in področni ravni. Ta zbirka se sklicuje predvsem na projekte, ki jih financirajo programi Evropske unije za financiranje. Razlog za to izbiro so široka vizija in analize, ki jih lahko zagotavljajo tovrstni projekti, ter veliko število sodelujočih zainteresiranih strani. Rezultati navedenih ustreznih praks se zberejo v registru dokumentov, ki je na voljo prek spletne strani odbora CEN/TC 287. Ta del tehničnega poročila določa postopke in vsebino navedenih registrov projektov in dokumentov, kar zagotavlja njihovo večjo dostopnost ter ponovno uporabnost. Zagotavlja ustrezne izsledke projektov, ki obravnavajo glavna vprašanja infrastruktur za prostorske podatke, opisane v drugih delih tega tehničnega poročila. To tehnično poročilo je namenjeno ciljnim skupinam ljudi, ki so odgovorni za oblikovanje okvirov infrastruktur 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
Relations
Standards Content (Sample)
SLOVENSKI STANDARD
01-januar-2013
1DGRPHãþD
SIST-TP CEN/TR 15449:2011
Geografske informacije - Infrastrukture za prostorske podatke - 2. del: Dobre
prakse
Geographic information - Spatial data infrastructures - Part 2: Best practices
Geoinformation - Geodateninfrastrukturen - Teil 2: Best practice
Information géographique - Infrastructures de données spatiales - Partie 2 : Bonnes
pratiques
Ta slovenski standard je istoveten z: CEN/TR 15449-2:2012
ICS:
07.040 Astronomija. Geodezija. Astronomy. Geodesy.
Geografija Geography
35.240.70 Uporabniške rešitve IT v IT applications in science
znanosti
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
TECHNICAL REPORT
CEN/TR 15449-2
RAPPORT TECHNIQUE
TECHNISCHER BERICHT
October 2012
ICS 07.040; 35.240.70 Supersedes CEN/TR 15449:2011
English Version
Geographic information - Spatial data infrastructures - Part 2:
Best practices
Information géographique - Infrastructures de données Geoinformation - Geodateninfrastrukturen - Teil 2: Best
spatiales - Partie 2 : Bonnes pratiques practice
This Technical Report was approved by CEN on 27 May 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
© 2012 CEN All rights of exploitation in any form and by any means reserved Ref. No. CEN/TR 15449-2:2012: E
worldwide for CEN national Members.
Contents Page
Foreword .4
Introduction .5
1 Scope .6
2 Normative references .6
3 Terms and definitions .6
4 Abbreviated terms .7
5 Overview .7
5.1 Introduction .7
5.2 Categories of contribution .8
5.2.1 Content classification .8
5.2.2 SDI reference model components .9
5.2.3 Architectural reference model services .9
5.2.4 Phases of an SDI .9
5.2.5 Project document types .9
6 Processes and procedures . 10
6.1 Requirements from a content provider perspective . 10
6.2 Inclusion of projects in this part Technical Report . 11
6.2.1 Permanent call for contributions . 11
6.2.2 Role definitions . 11
6.2.3 Criteria for inclusion of projects and deliverables . 12
6.2.4 Analysis and revision of contributions . 13
6.3 CEN/TC 287 document registry . 13
6.3.1 Submission procedure . 13
6.3.2 Register user functionalities . 15
6.3.3 Relation to other registries . 15
6.4 Structure and content of the repository . 15
7 Description of project deliverables . 15
7.1 Requirements from a consumer perspective . 15
7.2 Structure of the best practices repository . 16
7.3 Description of the project register . 17
7.4 Description of the best practice outcomes . 18
8 Best practices overview . 21
8.1 General . 21
8.2 SDI reference model components . 22
8.2.1 General . 22
8.2.2 Data . 22
8.2.3 Register . 22
8.2.4 Discovery . 22
8.2.5 View . 22
8.2.6 Invoke . 22
8.2.7 Download . 22
8.2.8 GeoRM . 23
8.2.9 Orchestration and composition . 23
8.3 Phases of an SDI . 23
8.3.1 General . 23
8.3.2 Concept design . 23
8.3.3 Implementation . 23
8.3.4 Validation. 23
8.4 Project document type . 24
8.4.1 Standards . 24
8.4.2 Specifications . 24
8.4.3 Technical reports . 24
8.4.4 Guidelines . 24
Annex A Projects relevant to Standards development organisations . 25
Annex B SDI components and project outcomes . 31
Annex C Project summaries . 33
Foreword
This document (CEN/TR 15449-2:2012) 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.
This document supersedes CEN/TR 15449:2011.
The present standard comprises the following parts:
CEN/TR 15449-1, Geographic information — Spatial data infrastructures — Part 1: Reference model;
CEN/TR 15449-2, Geographic information — Spatial data infrastructures — Part 2: Best practices (the
present part);
CEN/TR 15449-3, Geographic information — Spatial data infrastructures — Part 3: Data centric view;
CEN/TR 15449-4, Geographic information — Spatial Data Infrastructure (SDI) — Part 4: Service centric
view.
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 and 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. This
Technical Report takes these developments into account. 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.
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.
Considering the complexity of the subject and the need to capture and formalize different conceptual and
modelling views, CEN/TR 15449 is comprised of multiple parts:
• Part 1: Reference model: this provides a general context model for the other Parts, applying general IT
architecture standards;
• Part 2: Best practices: this provides best practices guidance for implementing SDI, through the evaluation
of the projects in the frame of the European Union funding programmes;
• Part 3: Data centric view: this addresses concerns related to the data, which includes application schemas
and metadata;
• Part 4: Service centric view (in preparation): this includes the taxonomy of services, concepts of
interoperability, service architecture, service catalogue, and the underlying IT standards.
Further parts may be created in the future.
1 Scope
This part of the Technical Report provides best practices regarding Spatial Data Infrastructures (SDIs),
referencing to the outcomes of the projects in the frame of the European Union funding programmes. It
summarises the deliverables of projects, structured according to the reference model defined in Part 1 of this
Technical Report, to be made available in an on-line repository where the relevant outcomes are collected and
classified in order to provide a structured sets of recommendations for implementing SDIs at the European,
national and sub-national levels.
This collection refers mainly to the projects funded by the European Union funding programmes: this choice is
driven by the wide vision and analysis which such kind of projects can provide and the wide numbers of
stakeholders which have been involved.
The outcomes delivered by these relevant practices are collected into a document registry available through
the CEN/TC 287 web site. This part of the Technical Report defines the processes and the content of these
projects and documents registries, which will help making them more accessible and re-usable. It provides the
relevant project deliverables addressing the main SDI issues as described in the other parts of this Technical
Report.
The intended readership of this Technical Report are 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 familiarize themselves with geographic information and SDI concepts, and
standards developers and writers.
2 Normative references
The following documents, in whole or in part, are normatively referenced in this document and are
indispensable for its application. For dated references, only the edition cited applies. For undated references,
the latest edition of the referenced document (including any amendments) applies.
EN ISO 19115, Geographic information Metadata (ISO 19115)
EN ISO 19135:2007, Geographic information Procedures for item registration (ISO 19135:2005)
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
3.1
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.2
register
set of files containing identifiers assigned to items with descriptions of the associated items
[SOURCE: EN ISO 19135:2007]
3.3
registry
information system on which a register is maintained
[SOURCE: EN ISO 19135:2007]
3.4
spatial data infrastructure
policies, standards and procedures under which organizations and technologies interact to foster more
efficient use, management and production of geo-spatial data
[SOURCE: United Nations SDI initiative (UNSDI)]
4 Abbreviated terms
CB Control body
CB-PoC Point of contact of the Control Body
ESDI European Spatial Data Infrastructure
GEO Group on Earth Observations
GEOSS Global Earth Observation System of Systems
GI geographic information
GIGAS GEOSS, INSPIRE and GMES, an Action in Support
GMES Global Monitoring for Environment and Security
INSPIRE Infrastructure for Spatial Information in Europe
ICT information and communications technology
ISO International Organization for Standardization
IT information technology
OGC Open Geospatial Consortium
OMG Object Management Group
RM Register manager
SDI Spatial Data Infrastructure
SOA Service Oriented Architecture
UML Unified Modelling Language
5 Overview
5.1 Introduction
This clause describes the various roles that projects can assume in relation to the standardisation processes.
It will describe the categories of contributions that projects give, directly or indirectly, to standards
development, evaluation, support to the implementation, and education of standards for geographic
information. In addition there are projects that help linking standards development to the implementation of
legal acts and policies.
In particular for the outcomes and best practices of projects that are not directly involved in the standards
development processes, it is paramount that their efforts be captured and made sustainable beyond the
lifetime of the projects.
1) 2) 3)
With INSPIRE , GEOSS and GMES now well established, numerous projects and activities that are
(co-)funded by EU programmes are being asked to use or build upon standards and specifications in the
domain of geographic information. Design methodologies, reference models, good practices in UML data
model design and data model transformation, as well as standards for various services are examples of topics
that are being or that have been addressed by dozens of European Union-funded projects. The paymasters
and the consortia that developed these products have made investments that should be protected.
4)
The GIGAS project (GEOSS, INSPIRE and GMES, an Action in Support), financed by the Directorate
General Information Society of the European Commission, has made concrete recommendations on how this
could be done. In particular, a role is proposed for CEN/TC 287 Geographic Information to maintain relevant
deliverables or parts thereof, not only of the GIGAS project, but also of other EU-funded projects. This is to
lead to a formal EU-level repository of reference material on interoperability, where future projects can find
state-of-the-art information on interoperability. At the same token, these projects could then add new
reference material as they progress in their work programmes.
This part of the Technical Report, along with the CEN/TC 287 document registry, constitutes the backbone for
making the outcomes and best practices of projects sustainable.
5.2 Categories of contribution
5.2.1 Content classification
The general issue is knowledge management related to standardization processes in projects funded by the
European Union programmes. More specifically, the proposed relevant practices should support the analysis
of project outcomes, which in the majority of the case are documents, but it can be also IT tools, infrastructure
and datasets. The core goal of this repository is strictly limited in the setup of a document registry related to
the relevant outcomes of European Union funded projects. Additional extension of this registry to manage
references to outcomes different from the documents will be taken into account in the future release.
The content managed by this registry can be categorized according to different aspects, applying a faceted
classification. A faceted classification allows the assignments of multiple classifications to a document,
enabling the classifications to be ordered in multiple ways, rather than in a single, predetermined order. A
facet comprises “clearly defined, mutually exclusive, and collectively exhaustive aspects, properties or
characteristics of a class or specific subject. According to this concept, the outcomes of projects related to SDI
can be categorized according to different facets which are listed below. According to this approach, each
document register will be classified under these different facets and the implemented registry permits to
address the registers according to this combined facets. The collected documents registers refers to best
practices about implementing SDI.
The following subsections provide the classification of the project outcomes in terms of the reference model
components, architectural reference services, and the phase(s) of an SDI, to which a project outcome is
applicable.
1) Infrastructure for Spatial Information in the European Community (INSPIRE), http://inspire.jrc.ec.europa.eu.
2) Global Earth Observation System of Systems, http://earthobservations.org/ .
3) Global Monitoring for Environment and Sustainability, http:///www.gmes.info .
4) GEOSS, INSPIRE and GMES an Action in Support (GIGAS) http://www.thegigasforum.eu/project/project.html .
5.2.2 SDI reference model components
A project outcome addresses one or more of the following SDI components:
• Data;
• Register;
• Discovery;
• View;
• Invoke;
• Download;
• GeoRM;
• Orchestration and Composition.
5.2.3 Architectural reference model services
A project outcome is characterized by one or more of the following type of services:
• Human Interaction Services;
• Model Management Services;
• Workflow/Task Services;
• System Management Services;
• Processing Services;
• Communication Services.
5.2.4 Phases of an SDI
A project outcome can focus mainly on one of the following different phases related to the SDI implementation
process:
Concept and design: including analyses, methodologies, reference models, state of play related to the
main SDI areas;
Implementation: including development methodologies, development implementation, deployment,
management and maintenance;
Validation: including monitoring, testing and reference standards compliance.
5.2.5 Project document types
Given the current way of delivering project results by submitting documents, this overarching goal implies
taking documents pertinent to the issue required to implement an SDI, and in particular:
1) Standards: the reference standards analysis, applicability, implementation, testing, refinements and
validation. This information must be applied.
2) Specifications: related to the standards or legally binding documents containing detailed description
of the requirements, recommendations and where relevant open issues. Specifications provide more
flexible level of documentation supporting more fixed binding documents. Specifications usually
remain on more conceptual level of reality abstraction.
3) Technical reports: often representing overall or partial outputs of the projects. Technical reports
often stands on more logical level of reality abstraction.
4) Guidelines: the technical documentation and guidelines related to the issues described above.
Guidelines can contain practical examples, best practices of the specific SDI components
implementations.
5) Software tool: the software component (either OSS than COTS tools) including products, API,
development environment, etc.
6 Processes and procedures
6.1 Requirements from a content provider perspective
This clause defines the processes and procedures for the inclusion and update of the outcomes and best
practices of projects. These processes and procedures has been determined by the analysis of the registry
requirements according to a project perspective.
From a project perspective, it is expected to have a simple system to populate and to upload the register
related to the best practice document. This entails:
a) being able to register the project through a wizard approach: a step-by-step process where the best
practice provider enters:
1) project details,
2) executive abstract,
3) contact details, etc.,
4) link to other "persistent" Web 2.0-like information available (e.g. YouTube channel, etc.),
5) PR material (official brochure / flyer as PDF),
6) link to official website,
7) project duration,
8) gantt chart and deliverables (incl. delivery dates),
9) other (e.g. funding programme),
At any time the document provider should be able to "save" and continue later, and should see the
remaining information needed to complete the process.
b) when uploading information minimise re-structuring of deliverables which would be time consuming and
discouraging;
c) ideally the document provider would like to upload a series of pdfs and tag them through a pre-defined
structure. An option could be to have online forms where to copy and paste (with all the problems this
may cause) the various sections of the deliverable (like Wikipedia but it should be much more usable);
d) have facilities to access the software code by the provision of a URL or software code page or repository.
6.2 Inclusion of projects in this part Technical Report
6.2.1 Permanent call for contributions
The contributions collected and referred to in this technical report are related to the date of publication of this
version of document. However, the collection of the best practice documents related to the outcomes of the
European Union funded projects will continue and a permanent call for contribution will be maintained and
open by the CEN/TC 287 secretariat. The upcoming requests for inclusion in the registry of new best practices
references will be processed according to the procedure defined in the following paragraph, and they will be
stored into the online registry managed by the CEN/TC 287 secretariat. It will be evaluated when it will be
opportune to publish an updated version of this part of this technical report, including the updated reference
documents and best practices collected into the on-line registry.
6.2.2 Role definitions
Regarding item registration in general, EN ISO 19135 identifies six diverse roles:
Register Owner: an organization establishing the register and has the primary responsibility for the
management, dissemination and intellectual content of the register.
Register Manager: manages the register(s) of items.
Submitting Organizations: a qualified organization to propose changes to the content of a register, or
an appeal if the proposals are not accepted.
Control Body: a group of technical / thematic domain experts deciding on the acceptability of the
proposals and changes to the content of a register. The control body shall accept proposals from the
register manager and renders a decision regarding each proposal.
Registry Manager: a person or an organization responsible for the day-to-day management of a registry
(an information system on which a register is maintained). The registry manager ensures the integrity of
any register held in the registry and provides means of electronic access to the registry for register
managers, control body(ies) and register users.
Register Users: access a registry in order to use one or more of the registers. They may include any
person or organization interested in accessing or influencing the content of a register. They may have a
variety of requirements and therefore present different categories of users (for example developers of
standards and specifications, data producers, data users, system developers). A register owner may set
terms and conditions for different levels of access to the register to satisfy the requirements of different
categories of users.
Multiple parties my play each of these roles and a single entity may play more than one role. These roles are
summarised in Table 1.
Table 1 Registry roles
EN ISO 19135 role Role about best practice registry
Register Owner CEN, OGC, ISO or the European Commission
Register Manager CEN, OGC, ISO or the European Commission
Submitting organization Content provider (the owner/generator of the reference
document, mainly the reference project but also CEN, OGC,
ISO or the European Commission)
Control body CEN/TC 287 secretariat
Registry manager CEN/TC 287 secretariat
Register Users any person or organization interested in accessing or
influencing the content of a register
6.2.3 Criteria for inclusion of projects and deliverables
The qualification process for the best practices providers as well as register owners in order to set-up a
qualified list of enabled best practices providers is shown in Figure 1.
Figure 1 Qualification process
The main steps are as follows:
1) CEN/TC 287 provide a standard form to submit a request to be qualified as a best practice provider.
This form is made available both on-line and off-line. The off-line version has to be sent via email to
the CEN/TC 287 secretariat.
2) The potential content provider (The project contact point, mainly the project coordinator, CEN, OGC,
ISO, EC) will apply to be accepted as a submitting organisation.
3) The potential content provider is qualified (and notified) to submit project reference documents by
Control Body; or
4) The request of the project contact point is refused and notified to him with the motivation of the
Control Body.
An initial set of reference projects and related documents has been selected by CEN secretary jointly with the
European Commission. It refers the major projects in the frame of the different funding programme (FP6, FP7,
eContentplus, ICT-PSP, etc). This initial set of information is available in the on-line repository (registry) set-up
by CEN secretary. This repository will be progressively increased and updated according to the future
outcomes from the European Commission funding programmes.
The request for the inclusion of new upcoming reference project and/or reference document can be received
by:
the project contact point (usually the project coordinator);
the European Commission;
the CEN/TC 287 Secretariat;
any other stakeholder authorised by the Control body.
6.2.4 Analysis and revision of contributions
The document candidate to be labelled as best practice and to be enclosed into the registry has to be
analysed and revised by a Control Body committed to perform this action. The Control Body is designed by
the CEN/TC287 WG5.
If a new release of the document has been delivered by the reference project, the Control Body will revise and
validate the updated version, updating the related registered item or suggesting the creation of a new one,
maintaining in this way the different versions of the document. The different version will be referred by
different registers, due to the fact that these documents continue to maintain the status of “best practice” even
with the presence of new updated versions.
If the new version completely updates the previous one, the old version will keep the status of “updated” and
the register will refer to the new one.
6.3 CEN/TC 287 document registry
6.3.1 Submission procedure
The process for document submission is shown in Figure 2.
Figure 2 Document submission process
The main steps in this process are as follows:
a) CEN/TC 287 provide a standard form to submit a best practice document reference. This standard form is
put at disposal in on-line and off-line version. The off-line version have to be sent via email to the CEN/TC
287 secretariat.
b) The content provider (submitting organisation) create a new instance of register item filling the predefined
form (web/excel). The submitting organisation can exploit the online form or submit the new register using
the off-line form. Using the on-line form, the submitting organisation have at disposal a simple content
management system in which he can manage his own register items. This tool can put at disposal to the
submitting organisation the following simple commands:
1) Insert a new register item (when a new register item is generated, this is set-up in “submission”
status);
2) Modify an existing register item (only if it is in “submission” or “revision” status);
3) Remove an existing register item (only if it is in “submission” status);
4) Duplicate a register item;
5) Submit a register item for the evaluation step (only if it is in “submission” or “revision” status). When a
register item is submitted for evaluation, this moves in “evaluation” status.
c) The register manager fills the full mandatory fields and submit the register item to the Control Body (CB).
The register item is moved in “Evaluation” status and a notification is sent to the CEN/TC287 secretariat
which is the point of contact of CB (CB-PoC). If the form is submitted in off-line way, the CB-PoC have to
insert/update the register item on the on-line database and submitting the new register item in place of
submitting organisation. The submitting organisation will be notified of this submission.
d) The Control Body are responsible for the evaluation of the submitted register items which are in
“submission” status. The result of the evaluation can have three results: accepted, refused, revision. In
any case, a notification is sent to the submitting organisation.
1) Accepted: In this case, the register item is setup in “valid” status. In this case the register item is
available to the register users.
2) Refused: in this case the register item is setup in “refused” status and it will be frozen and it will be
not more accessible by submitting organisation and register users. The Control Body have to provide
the motivation of his decision to the submitting organisation.
3) Revised: The register item is requested to be revised by the register owner. The Control Body
provide a list of comments/suggestions which have to be receipted by the Register Owner. The
register item is setup to “revision” and the submitting organisation is notified to updated the register
item and the referenced documents in order to submit again for the acceptance and publication.
6.3.2 Register user functionalities
The best practice registry is available for public view. The information can be search and analysed by the user
through the entry point published on CEN/TC 287 web site. The registry interface permits to access to the
registers:
by listing the registered items;
by a search form based on the categories described above.
A user may be required to be qualified to provide their comments on the registry content and/or propose
additional entries to the Control Body. This is provided by a discussion forum moderated by the CEN/TC287
secretariat. Any users may provide comments and suggestions to the CEN/TC287 secretariat.
6.3.3 Relation to other registries
For each project and for each document, a set of categories has been defined to classify the registered items
into this repository. In addition to these categories, free keywords can be used to additionally classify the
documents. A reference to the INSPIRE glossary registry may be used in order to have a harmonised
understanding of the free keywords used to classify the best practice reference outcomes.
6.4 Structure and content of the repository
Include a brief description of the on-line repository functionalities.
7 Description of project deliverables
7.1 Requirements from a consumer perspective
As a user (accessing information) it would be useful to be able to gather information of relevance on:
a) reference material relating to a specific topic;
b) a specific project [through a list of "indexed project"] - this requires having the possibility to identify a
project and then search:
1) executive abstract;
2) all relevant documents;
3) software/tools available;
4) list of participants (companies/institution & people);
c) specific documents through:
1) free keywords;
2) list of pre-defined list of topics (as defined in the above clause);
d) specific pieces of code/tools (relevant for software deliverables) by pointing to other source code
repositories (e.g. SourceForge).
For each of the above it should be indicated if the information is "public" (and therefore to be able to download
it) or if "private" (accessible only to consortium members). In the latter case in fact it would be important to
know that the piece of information I am looking for exists somewhere.
In all cases there should be:
1) a link to a contact person (including reference to relevant social networks e.g. LinkedIn);
2) company/institution details.
The personal details should be automatically associated to each document according to the log-in account
used for the upload. This way, if the contact person moves to another company, at least one could contact the
organization to get some additional insight.
7.2 Structure of the best practices repository
The best practice repository is based on the outcomes of the European Union funded projects. The registry is
setup in order to manage the information related to the project of reference, to the set of outcomes of the
project maintaining also a set of information related to the involved project stakeholders (including project
partners, advisory institutions, interested partners, etc).
The repository collects two types of registers:
Reference Project: the EU funded project addressing some key aspect classified as best practice in
implementation of an SDI;
Projects outcomes: the specific project outcomes which have been classified relevant to make the project
as a reference best practice.
For example, the project Nature-SDIplus has been considered a relevant project due by the following main
best practice outcomes:
Design of a thesaurus framework to harmonise the metadata content and provide semantic search
facilities (deliverable D3.1);
Operational methodology and guidelines for data harmonisation (deliverable D3.3)
Set-up of a data model validation methodology and implementation of a validation briefcase (deliverable
D5.1).
In the best practice repository, it will be registered the project Nature-SDIplus and the three main outcomes,
i.e. the deliverables D3.1, D3.3 and D5.1. Then for each project it can be one or more reference outcomes.
Based on the concept of maintaining the information mainly on their original producer, the essential
information related to the project and the referred documents are stored in the register metadata while the
more detailed information are provided as linked information.
In this document the most relevant information has been collected and provided, while for more additional
details, it has been provided the project/document link (like the project web site and the projects documents
links).
7.3 Description of the project register
For each project that has been identified for being relevant for the implementation of SDI in Europe the major
scopes, components and implementations are described. Components and implementations are structured
according to the relevance regarding possible solutions for the implementation of the INSPIRE Implementing
Rules. This covers:
• Metadata including multilingual approaches, EN ISO 19115 Metadata profiles and data collection tools.
• Network services including all kind of web services that are able to search, view and download geographic
information.
• Data specifications including data models, feature concept dictionaries, codelist dictionaries, application
schemas, data harmonization and information about the INSPIRE themes that are covered.
• Data sharing including licencing issues as well as pricing models.
• Possible additional approaches that could be relevant for supporting the implementation of SDI are also
described.
According to the above listed requirements, the project register has been designed including the following
information:
• Project ID, acronym and full name: the project ID refer to the ID assigned by the European Institution and
specified in the document of work.
• URL of the project website.
• The scope of the project (executive abstract) including a brief description of the main relevance of the
project which make it as a best practice of reference.
• The start and the end dates of the project.
• The main list of category which fit with the project qualification as a best practice in the SDI
implementation process.
• The list of the main outcomes which have been qualified as best practices in the process of implementing
an SDI.
• The details about the main contact person of the project (usually the project coordinator).
• The details about the EU project officer.
According to the above listed requirements, some information is not included into this metadata set (for
example, the project partners). This are assumed to be enclosed into the project website without the need to
replicate this information already collected into the project website and/or the enclosed information of the
European Union funding programmes websites.
Table 2 represent the template which has been used to collect the information related to the reference
projects listed in Annex A.
Table 2 Template used to collect project information
Project ID
Project acronym
Project full title
Project website
EU funding Programme
programme
Start Date End Date
Relevant classification SDI reference model Data
c
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...