About metadata

Metadata have been used for a long time, since people started making lists of objects, inventories and phenomena for the purpose of their systematic records and getting an overview of them, resulting in lists, inventories, content catalogues etc. In using spatial data, such as maps in raster or vector format in GIS environment, spatial databases, or when downloading data through a web-service, we often don't know or are not sure who collected the data and when they did it, what the quality of the data is, what coordinate reference system the data are in, what version the data format is or other information on data that allow to be used and interpreted.

Such data and their application (e.g. products and services based on them) have a lower value. To avoid these problems, metadata are collected. Metadata are integral part of data and together they make single units. Metadata need to be collected during the collection of data and they need to be updated when data are changed. In other words, important actions related to data have to be documented through metadata. 

The word metadata consists of the words 'meta' and 'data'. The prefix 'meta' was used in ancient Greek, meaning 'after' and 'with'. With time, 'meta' came to be used to signify transcendent or supernatural. The Latin word 'data' refers to pieces of information or a set of mutually different objects. Today, the most general definition of metadata is that they are data about data.

Since 1990s, metadata have been understood as machine-readable description. With the development of computers, metadata started to be used systematically, with each data file containing accompanying information about the amount of memory it takes, date of creation, user rights etc. Metadata thus became a general term referring to anything from interests to collections of stamps and sports events during a year.

However, describing different types of resources requires different types of metadata and different metadata thematic norms. Inventarisation of everything (knowledge), made possible by metadata, is supported by computers and the amount of information computer systems can store and process, while the development of IT technologies made data sharing an everyday necessity. To be able to use shared data, different groups of users need to know the format of data, their coordinate reference system and other information that can be obtained through metadata catalogues.

There is a clear trend of developing systematic metadata cataloguing (e.g. INSPIRE and national metadata catalogues). To connect different metadata systems, there needs to be some structural link between metadata. INSPIRE was created under a strong influence of ISO metadata standardization, while Croatian NSDI metadata, except national needs, meet the INSPIRE requirements, as well. Each Croatian NSDI metadata element is compared with ISO and INSPIRE metadata, which allows metadata exchange and interoperability.

Harvesting, as an operation allowing downloading metadata from a metadata catalogue, enables linking between catalogues and linking several catalogues with applications, like internet search engines do. The Dublin Core Metadata Initiative (DCMI), as a respectable international not profit organization involved in metadata standardization for various professional, thematic and business needs, differentiates between Dublin Core Metadata Initiative:
  • Shared term definitions define metadata interoperability based on shared natural-language definitions. Within an application environment such as an intranet, library system, or repository, participants agree what terms to use for their metadata and how those terms are defined. Most existing metadata applications currently operate at this level of operability.
  • Formal semantic interoperability defines metadata interoperability based on the shared formal model provided by Resource Description Framework (RDF), which is developed to support linked data that are exposed, shared, and connecting pieces of data, information, and knowledge on the Semantic Web using URI and RDF. Over the past two years, big amounts of commercial and public-sector data have been added to a growing linked data cloud. Search engines such as Yahoo have implemented this level of interoperability. Due to a rapid development of data clouding, this level of metadata interoperability is undergoing a boost.
  • Description Set syntactic interoperability defines metadata interoperability through applications compatible with the linked data model and, in addition, share an abstract syntax for validatable metadata records, the "description set".
  • Description Set Profile interoperability defines metadata interoperability as a process whereby records are exchanged among metadata-using applications following, in addition, a common set of constraints, use the same vocabularies, and reflect a shared model of the world. Levels 3 and 4 are more in the domain of research and development.

Besides the basic role of metadata to describe data, those in the system of INfrastructure for SPatial Information (INSPIRE) or National Spatial Data Infrastructure (NSDI) also meet a certain functionality, i.e. business model. ISO defines metadata as data on data, which is a general definition. INSPIRE defines metadata as information describing spatial datasets and spatial data services allowing their finding and use. This definition sets the goals for the business model that metadata must achieve (i.e. describe spatial data and find and use spatial data). 

ISO metadata packages

Metadata packages and relations between entities

Metadata for geographic data are represented by means of UML packages. Each package contains one or more entities (UML classes) that can be specified or generalised. Entities contain elements (UML class attributes) that identify discrete metadata elements. Entities can be aggregated and repeated as needed. Figure shows the general overview of a package. Metadata are specified by a UML model diagram and data dictionary for each package

Relationship between metadata packages and metadata entities are shown in Table 6.1. Metadata packages are shown in column 'Package' and aggregated metadata entities contained within a package are shown in column 'Entity'. Each package includes sub-classes.

Relationship between metadatapackages and metadata entities

Package Entity
Metadata entity set information MD_Metadata
Identification information MD_Identification
Constraint information MD_Constraints
Data quality information DQ_DataQuality
Maintenance information MD_MaintenanceInformation
Spatial representation information MD_SpatialRepresentation
Reference system information MD_ReferenceSystem
Content information MD_ContentInformation
Portrayal catalogue information MD_PortrayalCatalogueReference
Distribution information MD_Distribution
Metadata extension information MD_MetadataExtensionInformation
Application schema information MD_ApplicationSchemaInformation
Extent information EX_Extent
Citation and responsible party information CI_Citation CI_ResponsibleParty

Package abbreviations

Two-letter abbreviations are used to denote the package that contains a class. Those abbreviations precede class names, connected by a "_".

List of Abbreviations:

CC Changing Coordinates (ISO 19111)
CI Citation (ISO 19115)
CV   Coverages (ISO 19123)
DQ Data quality (ISO 19115)
DS Dataset (ISO 19115)
EX   Extent (ISO 19115)
FC Feature Catalogue (ISO 19110)
FE Feature (ISO 19109)
FT Feature Topology (ISO 19107)
GF General Feature (ISO 19109)
GM Geometry (ISO 19107)
GR Graph (ISO 19107)
LI Lineage (ISO 19115)
MD Metadata (ISO 19115)
PF Feature Portrayal (ISO 19117)
PS Positioning Services (ISO 19116)
RS Reference System (ISO 19115)
SC Spatial Coordinates (ISO 19111)
SI Spatial Identification (ISO 19112)
SV Services (ISO 19119)
TM Temporal (ISO 19108)
TP Topology (ISO 19107)
TS Simple Topology (ISO 19107)

Metadata UML model

Metadata for describing geographic data is defined using an abstract object UML model. Each diagram of the subclass defines a metadata section (UML package) of related entities, data types and code lists.  Entities may have mandatory and/or optional elements and associations. In some cases, optional elements may have mandatory elements. 

More informations about ISO UML Diagrams:

ISO UML Diagrams Metadata package 
ISO UML Diagram for identification information
ISO UML Diagram Constraint information
ISO UML Diagram for data quality information
ISO UML Diagram for maintenance information
ISO UML Diagram for spatial representation information
ISO UML Diagram for reference system information
ISO UML Diagram for content information
ISO UML Diagram for portrayal catalogue information
ISO UML diagram for distribution information
ISO UML diagram for metadata extension information
ISO UML diagram for application schema information
ISO UML diagram for extent information
ISO UML diagram for citation and responsible party information