IHO S-100 Framework. The Essence. WP / Task: Date: Author: hansc/dga Version: 0.6. Document name: IHO S-100 Framework-The Essence

Transcription

1 WP / Task: Date: Author: hansc/dga Version: 0.6 Document name: IHO S-100 Framework-The Essence IHO S-100 Framework Version 0.6 The Essence

2 Document information More recent versions of this document may exist ask the author if in any doubt. Project : EfficienSea2 WP4 e-navigation Services Subject Version : 1.0 : Workpackage 4 document Created : by Christoph Schreyer Last edited : by Christoph Schreyer Page count : 20 Edit count : Filename : S-100TheEssencev0.6.doc Version log Version Date Summary of changes Author May 2016 Add smaller additions and made corrections. Ch.Schreyer March 2016 Revised and commended Su Marks February 2016 Add chapter 3. Data Interoperability, smaller additions and made corrections. Ch. Schreyer September 2015 Revised chapter 2.2 and 3.3 Ch. Schreyer September 2015 Revised and commended Su Marks August 2015 Initial Draft Ch. Schreyer Referenced documents Reference Name Side 2 / 20

3 Table of Contents 1. INTRODUCTION Foreword Scope Limitation IHO S-100 AND ISO Introduction Model-Driven Engineering DATA INTEROPERABILITY CONTENT OF S Part 1 Conceptual Schema Language (ISO 19103) Part 2 Management of IHO Geospatial Information Registers (ISO 19135) Part 3 General Feature Model and Rules for Application Schema (ISO 19109) Part 4 Metadata (ISO 19115) Part 5 Feature Catalogue (ISO 19110) Part 6 Coordinate Reference Systems (ISO 19111) Part 7 Spatial Schema (ISO 19107) Part 8 Imagery and Gridded Data (ISO 19129) Part 9 Portrayal (ISO 19117) Part 10 Encoding Formats Part 11 Product Specifications (ISO 19131) Part 12 S-100 Maintenance Procedures ANNEX A - DESIGN OF IHO S-100 COMPLIANT PRODUCT SPECIFICATION ANNEX B - GLOSSARY REFERENCES Side 3 / 20

4 1. Introduction 1.1 Foreword The intention of this document is to provide the information, definitions and examples required to understand and work with the IHO S-100 framework. This document is primarily intended for use by anyone working with hydrographic data or interested in working with hydrographic data. It would be helpful if the reader of this document has a fundamental understanding of data and its modelling, but it is not necessary to be a data model expert. Chapter 4 Content of S-100 is following the structure of the original S-100 document. This fact makes it easier to find the relevant section for additional information. This document is part of the The Essence series, which will facilitate and promote the understanding and application of the IHO S-100 framework. 1.2 Scope In 2010, the International Hydrographic Organisation (IHO) adopted the conceptual S-100 framework. S-100 has been developed by the IHO Transfer Standard Maintenance and Applications Development (TSMAD) Working Group with active participation from hydrographic offices, industry and academia. The IHO S-100 framework is based on the ISO series of Geographic Standards. This means that S-100 is interoperable with other ISO/TC211 based standards which significantly extends the scope of digital hydrographic data. ISO standards are not easy to understand because the standards only provide a framework for creating own standards. This is the reason for the generic nature of the standards. The standards are generic because these make them universally applicable to a wide range of organizations regardless of size or business models. S-100 is a framework for the Universal Hydrographic Data Model. It is a description how to develop amongst other product specification. The main role of S-100 framework is to provide a repeatable data specification development methodology and general provisions for the data specification process, which is valid for all spatial data themes. 1.3 Limitation This document will mostly concentrate on the description of the IHO S-100 framework and how to work with the framework. Other related topics i.e. UML, S-57, S-101, S-102 and other product specifications will be mentioned but not discussed in this document. Side 4 / 20

5 2. IHO S-100 and ISO Introduction The Technical Committee (TC) 211 of the International Organisation for Standardisation (ISO) worked on geographic information standard specification and provided the ISO series. The ISO is a series of standards for defining, describing, and managing geographic information, i.e. information concerning objects or phenomena that are directly or indirectly associated with a location relative to the Earth. ISO also specifies methods, tools and services for management of information, including the definition, acquisition, analysis, access, presentation, and transfer of such data in digital/electronic form between different users, systems and locations. This series of standards gives the possibility to define profiles in order to facilitate the development of geographic information systems and application systems that will be used for specific purposes. The IHO S- 100 framework is such a profile. This circumstance makes the framework compatible with other ISO profiles and standards e.g. INSPIRE (Infrastructure for Spatial Information in Europa) and DGIWG (Defence Geospatial Information Working Group) and their data specifications. Data specifications are the base for harmonisation and interoperability between cross domain data models. The following diagram shows the relationship between S-100, UHDM and other spatial data. Figure 1: Relationship between S-100, UHDM and other spatial data The S-100 framework contains multiple components that will be aligned with the ISO series of geospatial standards. For each part the relevant ISO standard is cited in brackets after the chapter heading. 2.2 Model-Driven Engineering The ISO series of geographic standards is using the Model-Driven Engineering (MDE) approach for the creation and use of geospatial standards and specifications. Side 5 / 20

6 Three fundamental objectives of MDE: portability, interoperability and reuse The MDE is a technology developed by the Object Management Group (OMG) for modelling conceptual features in order to implement future applications. A model is an abstraction of a real world view. According to the MDE terminology, a system is represented by a model. A meta-model however gives a standard formal specification for a set of features shared by several models. It provides users with a guideline and types to build their own models. These models must confirm to their meta-models. Figure 2 illustrates the four-layer meta-model architecture based from the Object Management Group (OMG) on the ISO concepts. In general, it provides a meta-meta model at the top layer, called the M3 Level. This meta-meta-model is the basis for meta-model definitions. The Meta-Object Facility (MOF) is used to define object-oriented meta-models (as UML for example) as well as non-object-oriented metamodels (e.g. Web Service meta-model). The M2 Level represents these Meta-models and describes the elements of the M1 Level. It conforms to the Level M3 meta-meta-model. These M2-models describe elements of the M1 Level user-model. The last level is the Level M0. It is used to describe real-world objects that are modelled by the M1-Level. In short: A model at one layer is used to specify models in the layer below. Applied to the IHO S-100 standard, this means: The General Feature Model (GFM) from Part 3 (ISO 19109) conforms to the MOF (M3 Level) of the OMG and is the meta-model (M2 Level) for an application model Sector Light (M1 Level). The GFM (M2 Level) describes the elements of the application model (M1 Level) and the application model describes the real world object sector light (M0 Level). ISO is using the UML notation for all elements in the series and for the meta-models. Some key points from the MDE - Complex structures and contexts will be shown in a simple and clear way. - Support code generation and automation - Modelling is independent from the implementation, this means that changes in information requirements are applied to the schema, never directly to the implementation - Common meta-models guarantee the interoperability between systems on different platforms (using various technologies e.g. various operating systems, network standards, programming languages) Side 6 / 20

7 Figure 2: ISO19100 standards integration into the MDE concept 3. Data Interoperability Interoperability of metadata, spatial data and services is one of the core concepts of S-100 and SDI in general but also a main challenge in providing usable spatial data infrastructures to local, national and international stakeholder communities, ranging from nature conservation to infrastructure planning. By definition interoperability means the possibility for spatial datasets to be combined, and for services to interact, without repetitive manual intervention, in such a way that the result is coherent and the added value of the datasets and services is enhanced. There are two ways to overcome the heterogeneity of data structures and systems in the context e.g. with e-navigation: Transformation of spatial data Data will be transformed by specific software to produce a standardised presentation of the data. The transformation can be performed online via web-based services and offline via a download service. In the offline method an interoperable view is generated and stored. Side 7 / 20

8 In both cases the original data with their semantics and structure are preserved to fulfil the original user requirements for which they have been created. Harmonisation of spatial data According to the INSPIRE definition data harmonisation is: The process of developing a common set of data product specifications in a way that allows the provision of access to spatial data through spatial data services in a representation that allows for combining it with other harmonised data in a coherent way. The process of harmonisation adjusts the semantics and structure of the data and removes the remaining inconsistencies that cannot be solved by available technology. Both interoperability arrangements and harmonisation requires a wide-ranging standardisation of the data and services. Standards in the geospatial domain are mainly nationally and internationally organised. The Technical Committee (TC) 211 of the ISO and the Open Geospatial Consortium (OGC) define the basis for the creation of coherent geospatial data and information across domains. For general information about standardisation and the relationship between S-100, UHDM and other spatial data, see chapter 2.1 Introduction. The figure below shows all the necessary components to realise cross-sector data interoperability. Figure 3: The main components of Data Interoperability The main components are defined in one of the 12 parts of the IHO S-100 framework with references to the relevant ISO standard. Side 8 / 20

9 For example describe the General Feature Model from part 3 the object types, their properties and relationships and the application model from the same part defines a conceptual model independent of the concrete encoding. The encoding is defined in part 10 and the consistent management and versioning in part 12. To get an introduction about the 12 parts of S-100 and the reference to the relevant ISO standard, see chapter 4. Content of S-100. We lack a common UML registry as a management tool which makes the S-100 data models contained in the data specifications available in different formats and views. Kommentar [SM1]:? Any action on this? 4. Content of S-100 The IHO S-100 framework consists of 12 parts. Not all parts are necessary for you to do your specific work, e.g. design a product specification or a service model. To determine which parts are relevant for you, you need a thorough analysis of the user needs. More information about designing a product specification, see Annex A. The following chapter gives only an overview of the parts of S-100. For further information please read the relevant chapter in the S-100 documentation. The original S-100 document can be found with the following link: Part 1 Conceptual Schema Language (ISO 19103) The IHO defines a combination of UML 2 (Unified Modelling Language) and a set of basic data types as the conceptual schema language for specifications of geographic information. UML offers many types of diagram to design IT systems, but in conjunction with S-100 product specifications, primarily class diagrams and package diagrams are used. A UML class diagram is a static diagram that describes the structure of a data model with the following elements: Element Attributes Basic data types Enumerated types Relationships and Associations Description Attributes must have a unique name within the context of a class. Attributes have a visibility (public, protected, private, derived) Primitive types: Integer, Real, Boolean, CharacterString, Date, Time, DateTime Complex types: UnlimitedInteger, Matrix, S100_Multiplicity, S100_NumericRange, S100_UnitOfMeasure, S100Measure, S100_Length, S100_Angle A list of valid identifiers of mnemonic words. Types of relationships: Association, Generalisation, Dependency, Refinement, Aggregation, Composition Multiplicity: Exactly one, many optional zero or more, optional zero or one, at least one, given number Side 9 / 20

10 Stereotypes Optional, conditional, mandatory Naming and name space Interface, Type, Enumeration, MetaClass, DataType All attributes are per default mandatory. The default multiplicity for associations is 0..*, and for attributes is 1. Use precise and understandable technical names for classes and attributes. All classes shall have unique names. Class names start with an upper case letter. Attributes start with a lower case letter. In the case, if a class diagram represents a real world model, then we speak about a conceptual model. A class is a part of the specification, not of an implementation. A UML package diagram is a container to group sub packages, classes and their associations. A package shall be used to represent a schema. In addition to the diagrams, context tables help to explain the meaning of attributes, associations, operations and constraints. A context table is defined for each class, with following columns: Column Role Name Name Description Multiplicity Data Type Remarks Description Possible properties: Class, Attribute, Association, Enumeration, Literal Name of the property Semantic of the property Number of occurrences of the property in the class. Name of the data type of the property Additional information about the property e.g. constraints, conditions 4.2 Part 2 Management of IHO Geospatial Information Registers (ISO 19135) This part describes the management of geographic registers. This includes roles and responsibilities and description of proposal processing. Furthermore it describes the structure of an IHO Geospatial Information Register. Generally a registry is a managed list, which is easier to maintain as a fixed document. The use of a register improves the ability to manage and extend multiple products and ensure interoperability. A registry can contain a number of registers, of which the Feature Concept Dictionary (FCD) will be the most common because it will be used to develop a feature catalogue. The Feature Concept Dictionary specifies definitions of features, attributes, enumerated values and information types that will be used to describe hydrographic and metadata information. The current S-100 Geospatial Information Registry is accessible via the web site: Part 3 General Feature Model and Rules for Application Schema (ISO 19109) This Part introduces a General Feature Model (GFM) which is a conceptual model for defining Features and Information Types, their characteristics and relationships which shall be used in S-100 products. The GFM is the basis for the structures of feature catalogues. Side 10 / 20

11 Conceptual modelling should not be confused with other modelling disciplines. Beside the Conceptual Modelling there are two other levels of data modelling, the Logical Modelling and the Physical Modelling. The difference between these three levels is the complexity. The complexity increases from the conceptual to logical and to the physical. The S-100 GFM illustrates the data explicitly at a low complexity level because it helps us to understand our data better. In S-100, the conceptual model is explicitly chosen to make the model independent of design and implementation. This part also describes the rules for developing an application schema which is a basic part of any S-100 based product specification. An application schema is a conceptual schema that defines how a universe of discourse shall be described as data and operations. It defines the sematic of the content and the logical structure of the geographic information. An application schema conforms to the GFM and is described in UML. Figure 4: The relationship between an Application Schema and the GFM and UML The purpose of the application schema is: - correct and common understanding of the content and structure of data within a particular application field - computer readable schema (XML) for applying automated mechanisms for data management The two roles include a stepwise process for creating an application schema: 1) Define the requirements for the view of your scope of application (Universe of Discourse) 2) Identify the feature types, their properties and constraints with concepts defined in the GFM and write it into a conceptual model 3) Describe the elements of the application schema using UML. 4) Integrate the formal application schema with other standardized schemas, (spatial schema, quality schema, etc.) into a complete application schema. 4.4 Part 4 Metadata (ISO 19115) ISO defines almost 300 metadata elements, most of these are listed as "optional". This means, that the standard is often specified for regional or national use or for specific purposes (e.g. bathymetry). This is called profiling and the result is called community profile. Side 11 / 20

12 The S-100 metadata profile provides a specification for describing, validating and exchanging metadata about geographic datasets commonly produced by hydrographic organisations. Its purpose is the creation of metadata records that provide information about the identification, spatial and temporal extent, quality, application schema, spatial reference system and distribution of digital geographic data. The minimum set of core elements answers the following questions: 1. Does a dataset on a specific topic exist (What)? 2. For a specific place (Where)? 3. For a specific date or period (When)? 4. A point of contact to learn more about or order the dataset (Who)? By using the core metadata, a potential user should be able to understand without ambiguity the characteristics of geographic datasets or resources. If you are preparing metadata about an S-100 dataset or series the following categories of core elements are relevant: Categories of core elements Identifying a Resource Classifying Spatial Data Describing Data Quality Relating to Data Usage Relating to Metadata Description A resource is uniquely identified through a title, an abstract, a date, a type, a locator and a language. Spatial data will be classified with a topic category, bounding box, extent, vertical extent information (EPSG), spatial reference system and temporal reference. The quality of data will be described by lineage and spatial resolution. Data usage will be described by limitation on public access, conditions applying for access and use, distribution format and online resource. Metadata on metadata covers file identifier, date, standard name, standard version, language, Point of contact and parent id (link between dataset and series). The metadata elements will be described as follows: Element number Element name Requirement Occurrence Field Type Reference number of the element Name of the element (e.g. Resource title) The element is either: Mandatory (M) - the element must be filled in under all circumstances Conditional (C) - the element must be completed if certain conditions are met e.g. Resource language must be completed if the resource contains textual information Optional (O) - the element may be filled in if desired The number for how often an element occurs in the schema, which will be either one or many? The data allowed in a field: - Free text enter a text in the field - Controlled vocabulary select an option from a list - Date or date time - specify a date or a date and time in the format yyyy-mm-dd for dates and hh:mm:ss for times Side 12 / 20

13 Description Example XML Fragment - Numeric - enter only numbers into this field. - URL - specify a full web address A description of the data, with links to the code list used or websites where the controlled vocabularies can be found. A textual example of the element. A fragment of an xml output from an ISO compliant schema. 4.5 Part 5 Feature Catalogue (ISO 19110) A Feature Catalogue classifies and organises feature types. The definitions of features and attributes come from the Feature Concept Dictionary (FCD) which is part of a Geospatial Information Register. A feature catalogue shall be available in electronic form (e.g. XML, HTML) for any set of geographic data that contains features. Each product specification contains a feature catalogue. Generally a feature catalogue consists of a list of named types (features), a list of properties for named types and the information on how both are linked together. The named types will be extended by the information types and complex attributes. The feature catalogue gives an informative overview of the feature types and information types defined in the product specifications. A feature catalogue shall be available in both machine readable and human readable forms. 4.6 Part 6 Coordinate Reference Systems (ISO 19111) The location of a real world object is defined by coordinates. Those coordinates relate a feature to a position. This Part describes the relevant elements which are required to define 1-, 2- and 3-dimensional spatial coordinate references. The elements for referencing spatial objects by use of coordinates are described in five UML packages: Package name Prefix Description Identified Objects IO All packages depend on this package which describes the mechanism of linking elements to external definitions. Coordinate Reference Systems SC Describes the base class used for all coordinate reference systems (CRS) and all derived subclasses supported by this component. The following CRS are supported by S-100: - Geodetic CRS - Projected CRS - Vertical CRS - Image CRS Coordinate Systems CS Describes the coordinate systems by their coordinate axes, their number of dimensions, their direction, the value range and the unit of measure. Datums CD A datum is a parameter or set of parameters that defines the position of the origin, the scale, and the orientation of a coordinate system. Side 13 / 20

14 Three types of datum are described by S-100: - Geodetic datum - Vertical datum - Image datum Coordinate Operations CC Describes the operations for coordinate conversion. The following coordinate operations are defined by S-100: - Coordinate Transformation - Coordinate Conversion - Pass Through Operation - Concatenated Coordinate Operation The result of this part is a conceptual XML schema. The UML identifiers are used as element names. Further information on Coordinate Reference Systems is available from the EPSG website: Part 7 Spatial Schema (ISO 19107) This Part defines the information necessary for describing and manipulating the spatial characteristics of features. This profile contains a subset of ISO which is the minimum required to support 0, 1, 2 and 2.5 dimensional spatial schemas, as the spatial requirements of S-100 are less comprehensive than the requirements of ISO This version of the IHO Spatial Schema Profile only contains geometry and no topology. If there is a future requirement for topology then this Part will be extended to meet these requirements. This profile consists of simple geometry based on the following three criteria: - two levels of complexity: 1) Geometric Primitives 2) Geometric Complexes, - four levels of dimensionality: 1) 0-dimensional objects 2) 0- and 1-dimensional objects 3) 0-, 1- and 2-dimensional objects 4) 0-, 1-, 2- and 2.5 -dimensional objects - one level of functional complexity: 1) Data types only (operations are not included). S-100 only permits the use of DirectPosition. A DirectPosition holds the coordinates for a position within a particular coordinate reference system. 4.8 Part 8 Imagery and Gridded Data (ISO 19129) This part identifies the content model for coverage data for use in hydrographic applications, including imagery as a type of gridded data. It describes the organization, type of grid or other coverage structure and associated metadata and spatial referencing for georeferenced data. Side 14 / 20

15 The encoding level is independent from the content level. Hydrographic soundings are by their nature a set of measured data points. These data points can be represented in a grid structure in several different ways, including elevation models using a regular grid spacing, and irregular grids with variable size cells. They can also be represented as Triangular Irregular Networks (TIN triangles) or as point sets. Images are also of great importance for hydrographic data. This includes images from sensors such as aerial photography or LIDAR, photographs that can be associated with vector based feature oriented data and products based on scanned paper charts, commonly known as Raster Charts. Presently, S-100 only addresses grid based coverages, point set coverages, and TIN coverages. Only a subset of the framework defined in ISO is required in S-100. The framework as described in ISO can support both georeferenced and georeferenceable data, however S-100 is currently limited to georeferenced data. 4.9 Part 9 Portrayal (ISO 19117) This part defines the models, structures and formats for a machine readable Portrayal Catalogue. The actual contents of a Portrayal Catalogue need to be defined as part of a Product Specification. The intent is for a Portrayal Catalogue to be delivered separately from product datasets so that it can be imported and interpreted to map Feature objects defined according to the GFM into Drawing Instructions and symbolization. This concept is known as the portrayal mechanism and allows the same content to be displayed in different ways and allows maintenance of the mapping rules without modifying all the content data. The portrayal mechanism is feature-centered and function-based to create drawing instructions for a dataset containing geographic data. The drawing instructions are intermediate data and together with the symbol definitions produce the portrayal output. The symbol definitions contain the detail of all graphical elements used for the portrayal. Part of the Portrayal Process Portrayal Functions Drawing Instructions Symbol Definition Portrayal Output Description Portrayal Functions portray feature instances using geometry and attribute information. The relationship between feature instances, attributes and the underlying spatial geometry is specified in a product specification. Drawing Instructions contains information about the portrayal of geographic data. Drawing instructions include e.g. references to symbol definitions, priority and filter information. Drawing instructions are created by specific portrayal functions. The Symbol Definition contains the details of all graphical elements used for the portrayal. The portrayal output will be created from the rendering engine using the symbol definitions. Side 15 / 20

16 The portrayal process is based on standard XML/XSL languages and an XSLT 1.0 processor to transform Feature data (XML input) into drawing instructions (XML output) used by the rendering engine to process the machine readable XSL files and produce equivalent output. Figure 5 below illustrates the general portrayal model and process. Kommentar [SM2]: Consider adding (from machine readable XSL files) under Portrayal Output Kommentar [SM3]: Consider amending User Parameter to read Context (User parameters) Figure 5: The general portrayal model and process The portrayal mechanism makes it possible to portray the same dataset in different ways without altering the dataset itself. This part only includes mechanisms for portrayal of 2D vector data according to the GFM and Coverage data Part 10 Encoding Formats This part covers the encoding formats. S-100 does not mandate a particular encoding format. It is rather left to the developer of a product specification to decide which encoding standard matches the requirement of the use case best and which content, defined in the feature catalogue, and which structure, defined in the application schema, the dataset has. The following table gives an incomplete overview, over the available encoding standards from which new schemas can be developed. Encoding Name Description ISO/IEC 8211 The encoding standard currently used to encode S-57 ENC data. (see ) GML Geography Markup Language (see ) XML GeoTIFF Extensible Markup Language Extension of the TIFF specification to allow the storage of geo-referencing Side 16 / 20

17 information. HDF-5 Hierarchical Data Format version 5 JPEG2000 Joint Photographic Experts Group - Commonly used method for the compression of photographic images Part 10a ISO/IEC 8211 Encoding The ISO/IEC 8211 specifies an interchange format to facilitate the moving of files or parts of files containing data records between computer systems. The objectives of the standard are: - support interchange of data structures varying significantly in complexity and size - any medium such as a communication line, a magnetic tape, a disk pack, a flexible disk etc., should be able to be used for the physical interchange - all information necessary to successfully recreate the structure in the target system should be contained within the information transported on the medium The IHO S-57standard uses the ISO/IEC 8211 standard to define the actual encapsulation mechanism Part 10b GML Data Format(ISO 19136) GML as an OpenGIS encoding standard stands for Geography Markup Language and is an XML grammar for expressing geographical features. This Part describes an S-100 GML profile with all core GML components that shall be used as a basis for the development of GML application schemas for S-100 data products. The GML application schema defines a file format for the machine-to-machine exchange of information structured in accordance with the application schema from the product specification Part 11 Product Specifications (ISO 19131) A product specification (synonym with data product specification) is a detailed technical description of a geospatial data product. It describes all features, attributes and relationships of a given application and their dataset and includes all necessary information about data identification, data content and structure, reference system, data quality, data capture maintenance, delivery and metadata. This part shall help to develop product specifications with a clear and similar structure and correspond with other standards that have been developed within the IHO S-100 Geospatial Standard for Hydrographic data. Side 17 / 20

18 Figure 6: Relationship between the parts of an S-100 Production Specification In detail, a product specification shall contain the following sections adopted from ISO 19131: Section Overview Specification scopes Data product identification Data content and structure Description (and Clause in S-100) The overview section shall include general information about the data product like a title, an abstract and a content, and metadata to uniquely identify the product specification and creation and maintenance of the data product specification (see Clause 11-4) The scope of a specification is the area in which a part is valid. Some parts, amongst others then coordinate reference system is valid for the whole data product (general or root scope), whereas the maintenance regime is different for navigational features and context features. In other words navigation information that changes rapidly and is essential for safety of navigation and those that provide background reference information. (see Clause 11-5) Gives information about how to identify a data set that conforms to the specification. This will be done via a title, abstract category purpose and so on. (see Clause 11-6) For feature-based data, the product specification shall contain an application schema and an associated feature catalogue. For coverage-based or imagery data, the product specification shall identify each coverage and image type and a narrative description of each (see Part 7). (see Clause 11-7) Kommentar [SM4]:? Kommentar [SM5]:? Side 18 / 20

19 Reference systems Data quality Data capture and classification Data product format (encoding) Data product delivery Metadata Data maintenance Portrayal Additional information This section shall include information about the reference system used in the data product (see Part 6). (see Clause ) This section shall identify and describe the data quality requirements for each scope and list all data quality elements and sub-elements (see Part 3). (see Clause 11-8) This section shall provide information about data collection for each identified scope and can information about their data sources. See NOTE - encoding guide (see Clause 11-9) This section describes the file structure (encoding) and format. A file structure can e.g. be described by GML (ISO 19136) or encoded binary (ISO/IEC 8211). (see Clause 11-12) This section defines the delivery medium for each scope. This section is an optional section. (see Clause 11-13) The core metadata elements shall be included with the data product specification. Additional metadata items shall be defined using ISO and ISO and documented in the data product specification (see Part 3). (see Clause 11-15) The data maintenance section describes for each identified scope, how the data is maintained, which principles and criteria are applied and how often updates are carried out. (see Clause 11-10) This optional section describes how the data is to be presented as graphical output. The feature catalogue dictionary supports the portrayal with classes and attributes e.g. for scale min/max and layout for the textual information. The portrayal section is an optional section. (see Clause 11-11) The additional information section gives the possibility to include any other aspects of the data product specification not provided elsewhere in the specification. This section is an optional section. (see Clause 11-14) Kommentar [SM6]:? Kommentar [SM7]:? Kommentar [SM8]:? Kommentar [SM9]:? Kommentar [SM10]:? Kommentar [SM11]: Duplication, last sentence states this Part 12 S-100 Maintenance Procedures The maintenance part describes how to update, maintain and publish the various parts of S-100 in a uniform manner. It excludes the maintenance of the S-100 registry and product specification (which include their own maintenance section). In Appendix 12-A, this part provides you with a change proposal form. 5. Annex A - Design of IHO S-100 Compliant Product Specification This annex describes the S-100 framework for development of data specifications. The main reason for creating a product specification is to define the characteristics of a newly developed data product. Side 19 / 20

20 6. Annex B - Glossary This annex gives an overview and complementary information on the terminology and terms used in the ISO and IHO-S-100 documents and sets them in context to each other. 7. References 1. IHO S-100-Universal Hydrographic Data Model (Edition June 2015); 2. A Conceptual Model for Developing Interoperability Specifications in Spatial Data Infrastructures (European Commission, Joint Research Centre Institute for Environment and Sustainability, 2012); 3. Reference Information Specifications for Europe (RISE) Side 20 / 20