Geoscience Australia Community Metadata Profile of ISO … · C.3 Hierarchy Guidelines .....44 ....

Record 2013/17 | GeoCat 76066

Geoscience Australia Community Metadata Profile of ISO 19115:2005Version 1.0, May 2013

Bastrakova, I.V., Ardlie, N., Regan, J.

APPLYING GEOSCIENCE TO AUSTRALIA’S MOST IMPORTANT CHALLENGES www.ga.gov.au

http://www.ga.gov.au

Geoscience Australia Community Metadata Profile of ISO 19115:2005 VERSION 1.0 MAY 2013

Bastrakova, I.V., Ardlie, N., Regan, J.

Department of Resources, Energy and Tourism Minister for Resources and Energy: The Hon Gary Gray AO MP Secretary: Mr Blair Comley, PSM

Geoscience Australia Chief Executive Officer: Dr Chris Pigram This paper is published with the permission of the CEO, Geoscience Australia

© Commonwealth of Australia (Geoscience Australia) 2013

With the exception of the Commonwealth Coat of Arms and where otherwise noted, all material in this publication is provided under a Creative Commons Attribution 3.0 Australia Licence. (http://www.creativecommons.org/licenses/by/3.0/au/deed.en)

Geoscience Australia has tried to make the information in this product as accurate as possible. However, it does not guarantee that the information is totally accurate or complete. Therefore, you should not solely rely on this information when making a commercial decision.

Geoscience Australia is committed to providing web accessible content wherever possible. If you are having difficulties with accessing this document please contact [email protected].

ISSN 2201-702X (PDF)

ISBN 978-1-922201-42-3 (PDF)

GeoCat 76066

Bibliographic reference: Bastrakova, I. V., Ardlie, N., Regan, J., 2013. Geoscience Australia Community Metadata Profile of ISO 19115:2005. Version 1.0. Record 2013/17. Geoscience Australia, Canberra.

Version: 1305-02.

mailto:[email protected].

http://www.creativecommons.org/licenses/by/3.0/au/deed.en

Geoscience Australia Community Metadata Profile of ISO 19115:2005 iii

Contents

Revision History ........................................................................................................................................ 1

1 Overview ................................................................................................................................................ 2 1.1 Contact Details ................................................................................................................................. 2 1.2 References ....................................................................................................................................... 2

2 GA Community Metadata Profile Extension to ISO 19115 .................................................................... 3 2.1 Introduction ...................................................................................................................................... 3 2.2 Metadata for geographic data .......................................................................................................... 3 2.3 Metadata packages .......................................................................................................................... 3 2.4 Package descriptions ....................................................................................................................... 4

2.4.1 Metadata entity set information (MD_Metadata) ........................................................................ 4 2.4.1.1 Identification information (MD_Identification) ....................................................................... 5 2.4.1.2 Constraint information (MD_Constraints) ............................................................................. 5 2.4.1.3 Data quality information (DQ_DataQuality) .......................................................................... 6 2.4.1.4 Lineage information (LI_Lineage) ......................................................................................... 6 2.4.1.5 Distribution information (MD_Distribution) ............................................................................ 7

2.5 Core metadata for geographic resources ........................................................................................ 8 2.5.1 Unified Modelling Language (UML) diagrams ............................................................................ 9

2.6 Data dictionary ...............................................................................................................................10 2.7 Metadata extension information .....................................................................................................10

2.7.1.1 MD_ExtendedElementInformation properties for “fileIdentifier” .........................................11 2.7.1.2 MD_ExtendedElementInformation properties for “parentIdentifier” ....................................11 2.7.1.3 MD_ExtendedElementInformation properties for “dataSetURI” .........................................12 2.7.1.4 MD_ExtendedElementInformation properties for “referenceSystemInfo” ..........................12 2.7.1.5 MD_ExtendedElementInformation properties for “dataQualityInfo”....................................13 2.7.1.6 MD_ExtendedElementInformation properties for “metadataConstraints” ..........................14 2.7.1.7 MD_ExtendedElementInformation properties for “pointOfContact” ....................................14 2.7.1.8 MD_ExtendedElementInformation properties for “resourceMaintenance” .........................15 2.7.1.9 MD_ExtendedElementInformation properties for “resourceFormat” ..................................15 2.7.1.10 MD_ExtendedElementInformation properties for “resourceConstraints” .........................16 2.7.1.11 MD_ExtendedElementInformation properties for “topicCategory”....................................17 2.7.1.12 MD_ExtendedElementInformation properties for “extent” ................................................17 2.7.1.13 MD_ExtendedElementInformation properties for “accessConstraints” ............................18 2.7.1.14 MD_ExtendedElementInformation properties for “useConstraints” ..................................19 2.7.1.15 MD_ExtendedElementInformation properties for “lineage” ..............................................19 2.7.1.16 MD_ExtendedElementInformation properties for “statement” ..........................................20 2.7.1.17 MD_ExtendedElementInformation properties for “source” ...............................................20 2.7.1.18 MD_ExtendedElementInformation properties for “description” ........................................21 2.7.1.19 MD_ExtendedElementInformation properties for “distributionFormat” .............................21

GA Profile Metadata Schemas (UML) ................................................................................23 Appendix AA.1 Metadata UML models ..................................................................................................................23 A.2 Metadata package UML diagrams ................................................................................................24

A.2.1 Metadata entity set information ................................................................................................24 A.2.2 Identification information ..........................................................................................................25 A.2.3 Constraint information ..............................................................................................................26 A.2.4 Data quality information ...........................................................................................................27 A.2.5 Lineage information .................................................................................................................28 A.2.6 Distribution information ............................................................................................................29

GA Profile Data Dictionary ..................................................................................................30 Appendix BB.1 Data Dictionary Overview ..............................................................................................................30

B.1.1 Introduction ..............................................................................................................................30 B.1.2 Name/role name ......................................................................................................................30 B.1.3 Short name and ISO reference ................................................................................................31 B.1.4 Definition ..................................................................................................................................31 B.1.5 Obligation/Condition .................................................................................................................31

B.1.5.1 General ...............................................................................................................................31 B.1.5.2 Mandatory...........................................................................................................................31 B.1.5.3 Conditional..........................................................................................................................31 B.1.5.4 Optional ..............................................................................................................................31 B.1.5.5 Maximum occurrence .........................................................................................................32

B.2 Metadata package data dictionaries ..............................................................................................33 B.2.1 Metadata entity set information ................................................................................................33

B.3 Identification information ................................................................................................................35 B.3.1 General ....................................................................................................................................35 B.3.2 Constraint information ..............................................................................................................37 B.3.3 Data quality information ...........................................................................................................39

B.3.3.1 General ...............................................................................................................................39 B.3.3.2 Lineage information ............................................................................................................39

B.3.3.2.1 General .........................................................................................................................39 B.3.3.2.2 Source Information .......................................................................................................40

B.3.4 Distribution information ............................................................................................................41 B.3.4.1 General ...............................................................................................................................41

B.4 CodeLists and Enumerations ........................................................................................................42 A Use of Metadata Hierarchy (informative) ........................................................................43 Appendix C

C.1 Background ...................................................................................................................................43 C.1.1 Definition by exception .............................................................................................................43 C.1.2 Relational data stores and metadata hierarchy .......................................................................44 C.1.3 Catalog implementations, CSW and ISO19139 ......................................................................44

C.2 Example of GA profile hierarchy ...................................................................................................44 C.3 Hierarchy Guidelines .....................................................................................................................44

Geoscience Australia Community Metadata Profile of ISO 19115:2005 1

Revision History

Date Version Author Description

2011-12-12 0.1 J. Regan First draft

2012-02-29 0.2 I. Bastrakova Review

2012-03-06 0.3 I. Bastrakova, J. Regan

Review

2012-03-16 0.4 J. Hockaday, J. Regan, I. Bastrakova

Review

2012-04-02 0.5 I. Bastrakova Review

2012-04-10 0.6 J. Regan Review

2012-06-20 0.7 N. Ardlie General revision: Revision of extended elements (Removed distributionInfo and dataQuality which are sufficiently constrained by other extension elements – added parentIdentifier and extent) Removed content from Annexes A and B for entities that remain unchanged from ISO19115 Addition of Annex C on use of Metadata Hierarchy

2012-06-25 0.8 N. Ardlie Recreated UML diagrams for Annex A in Enterprise Architect

2012-07-11 0.9 N. Ardlie Made the LI_Source.description property mandatory

2012-07-16 1.0 I. Bastrakova Updated version number to 1.0 for release

2013-05-22 1.0 I. Bastrakova Final review and update before publication. Minor update to the Core Metadata Elements in Table 2 to make consistent with UML diagrams Update of text in the chapters 1.2, 1.5, 1.6

1 Overview

The purpose of this document is to define a Geoscience Australia Metadata Profile version 1.0 Extension to ANZLIC, ISO 19115:2005, referred to as the GA Profile, and to identify the metadata required to accurately describe GA resources. The GA Profile is designed to support the documentation and discovery of GA datasets and other resources, recognising the data management and sharing requirements within the agency. The GA Profile has been developed in accordance with the rules established by Geoscience Australia Programme Darwin. The GA Profile is a subset of the international standard and includes all ANZLIC ISO 19115 core metadata elements. The GA Profile will facilitate interoperability between the GA datasets and make it easier to find, use and share GA data and other resources.

1.1 Contact Details The GA Profile is maintained by the Information Management Section, Geoscience Australia.

1.2 References The following normative documents contain important requisite references for the application of this profile.

• AS/NZS ISO 19115:2005, Geographic information – Metadata

• ISO 19115:2003, Geographic information – Metadata

• ISO/CD TS 19139, Geographic information – Metadata – XML schema implementation

• ISO 19106:2004, Geographic Information - Profiles

• ISO/IEC 19501:2005, Information technology – Open Distributed Processing – Unified Modelling Language (UML) Version 1.4.2


2 GA Community Metadata Profile Extension to ISO 19115

2.1 Introduction The International Standard ISO 19115 (Geographic information – Metadata) defines almost 300 metadata elements, with most of these being listed as “optional”. The ISO standard states that individual communities may develop a “profile” of the International Standard. A select set of metadata elements may be established as mandatory for a set of users. A community may also want to establish additional metadata elements that are not in the International Standard. A profile should establish field sizes and domains for all metadata elements. The rules for creating profiles are described in the International Standard Geographic Information – Profiles (ISO 19106:2004).

ISO 19106 stipulates particular terminology that must be used when any variation is made to a Standard, namely referring to changes as an Extension. For example, ANZLIC has changed the obligation level of one element, and this is referred to as an extension to ISO 19115.

It should be noted that there are no ‘new’ elements in the GA Profile. Obligation levels of 18 elements from ISO 19115 and 1 element from ANZLIC have been changed, and according to ISO 19106, they form an ‘extension’ to ISO 19115.

This profile document highlights all mandatory and conditional packages/entities from ANZLIC (hence ISO 19115), necessary to fulfil GA business requirements. All other entities and packages in ISO 19115 remain available and can be used as required to describe GA products and datasets. The other entities and packages have to be used as defined by ISO 19115 and ANZLIC.

2.2 Metadata for geographic data ISO 19115 identifies the metadata required to describe digital geographic data. Metadata is applicable to independent datasets, aggregations of datasets, individual geographic features, and the various classes of objects that compose a feature. Metadata shall be provided for geographic datasets and may, optionally, be provided for aggregations of datasets, features, and attributes of features.

2.3 Metadata packages ISO 19115 presents metadata for geographic information in UML Packages. Each package contains one or more entities (UML Classes), which can be specialised (subclassed) or generalised (superclassed). Entities contain elements (UML class attributes) which identify the discrete properties of metadata. Entities may be related to one or more other entities. Entities can be aggregated and repeated as necessary to meet: (1) the mandatory requirements stated in this Standard; (2) additional user requirements.

This document provides UML diagrams only for the packages containing variations to the ISO 19115. The elements of the GA Metadata Profile are specified in the UML model diagrams and data dictionary for each package, which can be found in Annex A and Annex B respectively. If a discrepancy between the two annexes exists, Annex A shall be considered authoritative. The relationship between metadata packages and metadata entities is shown in the Table 1.

Table 1: Relationship between packages of metadata and metadata entities

Package Entity UML Diagram Data Dictionary

Metadata entity set information MD_Metadata A.2.1 B.2.1

Identification information MD_Identification A.2.2 B.2.2

Constraint information MD_Constraints A.2.3 B.2.3

Data quality information DQ_DataQuality A.2.4 B.2.4

Lineage LI_Lineage A.2.5 B.2.4.2

Distribution information MD_Distribution A.2.6 B.2.5

2.4 Package descriptions This subsection provides an overview of the packages containing properties whose constraints have been changed by this profile. Complete details of the changes can be found in section 1.10, Annex A and Annex B of this profile.

Metadata entity set information (MD_Metadata) 2.4.1

Metadata entity set information consists of the entity (UML class) MD_Metadata, which is mandatory. The MD_Metadata entity contains both mandatory and optional metadata elements (UML attributes).

The following properties of the MD_Metadata entity have been changed by this profile:

Name Definition Change from the ISO 19115

fileIdentifier unique identifier for this metadata file Optional Mandatory

parentIdentifier file identifier of the metadata to which this metadata is a subset (child)

Conditional Conditional (changed condition)

dataSetURI Uniform Resource Identifier (URI) of the dataset to which the metadata applies

Optional Conditional

referenceSystemInfo description of the spatial and temporal reference systems used in the dataset


dataQualityInfo provides overall assessment of quality of a resource(s)

Optional Mandatory

metadataConstraints provides restrictions on the access and use of metadata

Optional Mandatory


Identification information (MD_Identification) 2.4.2

Identification information contains information to uniquely identify the resource. It includes information about the citation for the resource, an abstract, the purpose, credits, status of the resource and points of contact. The MD_Identification entity is mandatory. The MD_Identification entity MUST be specialised (subclassed) as MD_DataIdentification when used to identify resources other than services1.

The following properties of the MD_Identification entity have been changed by this profile:


pointOfContact identification of, and means of communication with, person(s) and organization(s) associated with the resource(s)

Optional Mandatory

resourceMaintenance provides information about the frequency of resource updates, and the scope of those updates

Optional Mandatory

resourceFormat provides a description of the format of the resource(s)

Optional Mandatory

resourceConstraints provides information about constraints which apply to the resource(s)

Optional Mandatory

The following properties of the MD_DataIdentification (subclass) entity have been changed by this profile:


topicCategory main theme(s) of the dataset Conditional Mandatory

extent extent information including the bounding box, bounding polygon, vertical, and temporal extent of the dataset


Constraint information (MD_Constraints) 2.4.3

Constraint information contains information concerning the restrictions placed on data and metadata. The MD_Constraints entity is mandatory for both resource and metadata. Metadata constraints must be specified as MD_SecurityConstrants. Resource constraints must be specified as MD_SecurityConstraints and MD_LegalConstraints.

The following properties of the MD_LegalConstraints entity have been changed by this profile:


accessConstraints access constraints applied to assure the Optional Conditional

1 For further information about “services” metadata refer to ISO 19119


protection of privacy or intellectual property, and any special restrictions or limitations on obtaining the resource

useConstraints constraints applied to assure the protection of privacy or intellectual property, and any special restrictions or limitations or warnings on using the resource


The following properties of the MD_SecurityConstraints entity have been changed by this profile:


MD_SecurityConstraints handling restrictions imposed on the resource or metadata for national security or similar security concerns

Optional Mandatory

Data quality information (DQ_DataQuality) 2.4.4

The data quality information contains a general assessment of the quality of the dataset. The DQ_DataQuality entity is mandatory and contains the scope of the quality assessment.

The following properties of the DQ_DataQuality entity have been changed by this profile:


lineage non-quantitative quality information about the lineage of the data specified by the scope

Conditional Mandatory

Lineage information (LI_Lineage) 2.4.5

The LI_Lineage entity is mandatory and contains a statement about the lineage and source information. The “statement” element is mandatory. Source information is mandatory if scope level of the resource is “dataset” or “series” and should provide description of the source data used to create a dataset or series. Descriptions should be provided for each data source.

The following properties of the LI_Lineage entity have been changed by this profile:


statement general explanation of the data producer’s knowledge about the lineage of a dataset


source information about the source data used in creating the data specified by the scope


The following properties of the LI_Source entity have been changed by this profile:


description detailed description of the source of the data Conditional Mandatory


Distribution information (MD_Distribution) 2.4.6

The distribution information package contains the distributor of, and options for obtaining, a resource. It contains the conditional MD_Distribution entity. The “distributionFormat” role of MD_Distribution is mandatory if the entity is used.

The following properties of the MD_Distribution entity have been changed by this profile:


distributionFormat provides a description of the format of the data to be distributed


2.5 Core metadata for geographic resources ISO 19115 defines an extensive set of metadata elements. The GA Metadata Profile prescribes only a subset of these elements, representing the minimum set of metadata elements required to describe a GA resource. These metadata elements are required to identify a resource, typically for catalogue purposes. The resulting catalogue of records enable us to answer the following types of questions: “Does a dataset on a specific topic exist?” (‘what’), “For a specific place?” (‘where’), “For a specific date or period?” (‘when’) and “A point of contact to learn more about or order the dataset?” (‘who’). Using the recommended optional elements in addition to the mandatory elements will increase interoperability, allowing users to understand without ambiguity the data and the related metadata provided by either the producer or the distributor. The GA Profile includes the core metadata elements defined in ISO 19115. Table 2 lists mandatory and conditional elements required for a geographic dataset.

Table 2: Core metadata for GA Community geographic datasets

Name ISO19115 Obligation Path 2Ref Num

File Identifier 2 M MD_Metadata.fileIdentifier

Language 3 C MD_Metadata.language

Character Set 4 C MD_Metadata.characterSet > MD_CharacterSetCode

Metadata 5 C MD_Metadata.parentIdentifier Parent Identifier

Metadata 6 C MD_Metadata.hierarchyLevel Hierarchy Level

Metadata 7 C MD_Metadata.hierarchyLevelName Hierarchy Level Name

Metadata 8 M MD_Metadata.contact > CI_ResponsibleParty Point of Contact

Date Stamp 9 M MD_Metadata.dateStamp

Metadata 10 M MD_Metadata.metadataStandardName Standard Name

Metadata 11 M MD_Metadata.metadataStandardVersion Standard Version

Dataset URI 11.1 C MD_Metadata.datasetURI

Metadata 20 M MD_Metadata.metadataConstraints > MD_Constraints

2 This refers to the number used in the leading column of the definition tables within Section B.2 of the ANZLIC ISO19115:2005 standard


Name ISO19115 Ref Num2

Obligation Path

Constraints

Resource Title

360 M MD_Metadata.identificationInfo > MD_DataIdentification.citation > CI_Citation.title

Resource Date

362 M MD_Metadata.identificationInfo > MD_DataIdentification.citation > CI_Citation.date

Resource Abstract

25 M MD_Metadata.identificationInfo > MD_DataIdentification.abstract

Resource Point of Contact

29 M MD_Metadata.identificationInfo > MD_DataIdentification.pointOfContact > CI_ResponsibleParty

Resource Maintenance

30 M MD_Metadata.identificationInfo > MD_DataIdentification.resourceMaintenance> MD_MaintenanceInformation

Resource Constraints

35 M MD_Metadata.identificationInfo > MD_DataIdentification.resourceConstraints > MD_Constraints

Resource Language

39 M MD_Metadata.identificationInfo > MD_DataIdentification.language

Character Set 40 C MD_Metadata.identificationInfo > MD_DataIdentification.characterSet > MD_CharacterSetCode

Data Lineage 81 M MD_Metadata.dataQualityInfo > DQ_DataQuality.lineage > LI_Lineage

Topic Category

41 M MD_Metadata.identificationInfo > MD_DataIdentification.topicCategory > MD_TopicCategoryCode

Data Quality 85 M MD_Metadata.dataQualityInfo > DQ_DataQuality.lineage > LI_Lineage.source > LI_Source

Reference System

(13), 187 C MD_Metadata.referenceSystemInfo > MD_ReferenceSystem.referenceSystemIdentifier > RS_Identifier

Geographic Extent

96 C MD_Metadata.identificationInfo > MD_DataIdentification.extent > EX_Extent.geographicElement > EX_GeographicBoundingBox

Temporal Extent

186 C MD_Metadata.identificationInfo > MD_DataIdentification.extent > EX_Extent.temporalElement > EX_TemporalExtent

Distribution Format

271 Ma MD_Metadata.distributionInfo > MD_Distribution.distributionFormat > MD_Format

Resource Format

32 M MD_Metadata.identificationInfo > MD_DataIdentification.resourceFormat > MD_Format

a distributionFormat: documented if the resource is intended for distribution and the MD_Distribution element is present

Unified Modelling Language (UML) diagrams 2.5.1

Annex A provides the metadata schemas in the form of Unified Modelling Language (UML) diagrams. These diagrams, in conjunction with the data dictionary presented in Annex B, serve to fully define the total abstract model for metadata.

2.6 Data dictionary Annex B contains the element and entity definitions for the metadata schemas. This dictionary, in conjunction with the diagrams presented in Annex A, serve to fully define the total abstract model for metadata.

2.7 Metadata extension information The tables in this subsection describe the GA Community Profile extensions to ISO 19115. Each table identifies the ISO 19115 element name and number for the element being extended, along with the associated properties of the MD_ExtendedElementInformation class.

Without exception, the extensions defined in this profile are based on changes to the obligation level of an existing ANZLIC ISO 19115 element. No new elements have been created by this profile. In all cases these changes have been made to further constrain rather than relax an obligation. In other words a change has been made from “optional” to “mandatory” or “conditional”.

Content in the “Additional Information” section serves only as an informative addition and does not constitute part of the extended element information model.

By way of reference the following table identifies the subsections defining the MD_ExtendedElementInformation properties for each extended element.

Table 3: Listing of subsections for extended elements

Subsection Extended Element Name ISO 19115 Ref

1.10.1 fileIdentifier 2

1.10.2 parentIdentifier 5

1.10.3 dataSetURI 11.1

1.10.4 referenceSystemInfo 13

1.10.5 dataQualityInfo 18

1.10.6 metadataConstraints 20

1.10.7 pointOfContact 29

1.10.8 resourceMaintenance 30

1.10.9 resourceFormat 32

1.10.10 resourceConstraints 35

1.10.11 topicCategory 41

1.10.12 extent 45

1.10.13 accessConstraints 70

1.10.14 useConstraints 71

1.10.15 lineage 81

1.10.16 statement 83

1.10.17 source 85


Subsection Extended Element Name ISO 19115 Ref

1.10.18 description 93

1.10.19 distributionFormat 271

2.7.1 MD_ExtendedElementInformation properties for “fileIdentifier”

Property Name Property Value

name fileIdentifier

shortName mdFileID

definition Existing ISO 19115 element (2)

obligation mandatory

condition

dataType CharacterString

maximumOccurrence 1

domainValue Free text

parentEntity MD_Metadata

rule Changed obligation from optional to mandatory

rationale To ensure a file identifier is always provided

source/organisationName Geoscience Australia

source/role owner

Additional Information

Meaning & Purpose The metadata file identifier permanently and uniquely identifies a metadata record. The fileIdentifier for a metadata record should never change, irrespective of where or how the metadata record is stored. (see ANZLIC for further details)

2.7.2 MD_ExtendedElementInformation properties for “parentIdentifier”


name parentIdentifier

shortName mdParentID


obligation conditonal

condition Mandatory if hierarchy level is one of “feature”, “featureType”, “attribute” or “attributeType”


maximumOccurrence 1




rule Changed condition

rationale To ensure parent identifiers are provided for all lower level hierarchy records


source/role owner


Meaning & Purpose The file identifier of the parent metadata record

MD_ExtendedElementInformation properties for “dataSetURI” 2.7.3


name dataSetURI

shortName dataSetURI

definition Existing ISO 19115 element (11.1)

obligation conditional

condition Mandatory if hierarchy level is “dataset” or “series”


maximumOccurrence 1



rule Changed obligation from optional to conditional

rationale To ensure a dataset URI is always provided for “dataset” and “series” records


source/role owner


Meaning & Purpose This element allows the user to directly access datasets that are available online, either as public or restricted access. A Uniform Resource Identifier (URI) is a short string that identifies a resource on the web or network: documents, images, downloadable files, services, electronic mailboxes, and other resources. A URI can make resources available under a variety of naming schemes and access methods such as HTTP, FTP, and Internet mail addressable in the same simple way.

MD_ExtendedElementInformation properties for 2.7.4“referenceSystemInfo”


name referenceSystemInfo



shortName refSysInfo



condition Mandatory if hierarchy level is “dataset” or “series”

dataType Association

maximumOccurrence N

domainValue MD_ReferenceSystem



rationale To ensure a reference system is always provided for “dataset” and “series” records


source/role owner


Meaning & Purpose The reference system information is used to align the dataset in time and space

MD_ExtendedElementInformation properties for “dataQualityInfo” 2.7.5


name dataQualityInfo

shortName dqInfo



condition


maximumOccurrence N

domainValue DQ_DataQuality



rationale To ensure data quality information is always provided at the metadata record level


source/role owner


Meaning & Purpose To describe the history resource. It can also include a textual explanation of the processing steps and other defining quality statements.

2.7.6 MD_ExtendedElementInformation properties for “metadataConstraints”


name

shortName

definition

obligation

condition

dataType

maximumOccurrence

domainValue

parentEntity

rule

rationale

source/organisationName

source/role


Meaning & Purpose

metadataConstraints

mdConst

Existing ISO 19115 element (20)

mandatory

Association

N

MD_Constraints

MD_Metadata

Changed obligation from optional to mandatory and to enforce at least one instance of the MD_SecurityConstraints child

To ensure constraints are always provided at the metadata record level. This supports mandatory provision of security constraints for GA metadata records.

Geoscience Australia

owner

This element has been made mandatory in order to support mandatory provision of security constraints for GA metadata records. Security constraints are required at the metadata record level specifically to provide the security classification level of the record.

2.7.7 MD_ExtendedElementInformation properties for “pointOfContact”


name pointOfContact

shortName idPoC



condition

dataType Class

maximumOccurrence N

domainValue CI_ResponsibleParty

parentEntity MD_Identification




rationale To ensure point of contact information is always provided


source/role owner


Meaning & Purpose The identification point of contact contains details about the organisation and/or position associated with the resource(s); it facilitates further enquiries about the resource(s)

MD_ExtendedElementInformation properties for 2.7.8“resourceMaintenance”


name resourceMaintenance

shortName resMaint



condition


maximumOccurrence N

domainValue MD_MaintenanceInformation


rule Changed obligation from optional to mandatory and to enforce at least one instance of an MD_MaintenanceFrequencyCode descendant

rationale To ensure resource maintenance information is always provided. This supports mandatory provision of update frequency information for the resource(s).


source/role owner


Meaning & Purpose Information about the update frequency of the resource(s)

MD_ExtendedElementInformation properties for “resourceFormat” 2.7.9


name resourceFormat

shortName dsFormat




condition


maximumOccurrence N

domainValue MD_Format



rationale To ensure format information is always provided for the resource(s)


source/role owner


Meaning & Purpose Format information about a resource allows users to identify resources in formats they are capable of consuming

MD_ExtendedElementInformation properties for 2.7.10“resourceConstraints”


name resourceConstraints

shortName resConst



condition


maximumOccurrence N

domainValue MD_Constraints


rule Changed obligation from optional to mandatory and to enforce at least one instance of each of the MD_LegalConstraints and MD_SecurityConstraints subclass, which themselves must have at least one instance of each of the accessContraints and useConstraints properties (as enforced by extensions 1.10.13 and 1.10.14)

rationale To ensure that access and use constraints for a resource are provided


source/role owner




Meaning & Purpose Provision of access and use constraints assists us to manage the legal and technical restrictions imposed by a resource or its provider

MD_ExtendedElementInformation properties for “topicCategory” 2.7.11


name topicCategory

shortName tpCat



condition

dataType Class

maximumOccurrence N

domainValue MD_TopicCategoryCode



rationale To ensure that a topic category is always provided


source/role owner


Meaning & Purpose Topic categories represent the main theme(s) of the dataset or resource. Enforcing their provision allows a search to be restricted to resources pertaining to a particular theme or topic. For example "find all data resources to do with the environment". As topic category is an important element for searching, careful consideration and consistent use of the enumerated terms should be applied. Especially when documenting a “dataset” or “series”.

MD_ExtendedElementInformation properties for “extent” 2.7.12


name extent

shortName dataExt



condition Mandatory if hierarchy level is equal to ”dataset” or “series”

dataType Class


maximumOccurrence N

domainValue EX_Extent


rule Changed condition

rationale To ensure that extent is provided for dataset and data series records


source/role owner


Meaning & Purpose Extent information including the bounding box, bounding polygon, vertical, and temporal extent of the dataset. The EX_Extent entity requires that at least one of “description“ or “geographicElement“ or “temporalElement“ or “verticalElement“ is provided.

MD_ExtendedElementInformation properties for 2.7.13“accessConstraints”


name accessConstraints

shortName accessConsts



condition Optional at the level of the metadata record. Mandatory at the level of the resource (specified within the record).

dataType Class

maximumOccurrence N

domainValue MD_RestrictionCode

parentEntity MD_Constraints


rationale To ensure that access constraints are always provided at the resource level


source/role owner


Meaning & Purpose Assures the protection of privacy and intellectual property of a resource managed by GA. (Refer to section 1.10.10)


MD_ExtendedElementInformation properties for “useConstraints” 2.7.14


name useConstraints

shortName useConsts



condition Optional at the level of the metadata record. Mandatory at the level of the resource (specified within the record).

dataType Class

maximumOccurrence N

domainValue MD_RestrictionCode

parentEntity MD_Constraints


rationale To ensure that use constraints are always provided at the resource level


source/role owner


Meaning & Purpose Assures the protection of privacy and intellectual property of a resource managed by GA. (Refer to section 1.10.10)

MD_ExtendedElementInformation properties for “lineage” 2.7.15


name lineage

shortName dataLineage



condition


maximumOccurrence 1

domainValue LI_Lineage

parentEntity DQ_DataQuality

rule Changed obligation from conditional to mandatory

rationale To ensure that lineage information is always provided


source/role owner



Meaning & Purpose The lineage element provides the structure that can contain a lineage statement, and source

MD_ExtendedElementInformation properties for “statement” 2.7.16


name statement

shortName statement



condition


maximumOccurrence 1


parentEntity LI_Lineage


rationale To ensure that lineage statement information is always provided


source/role owner


Meaning & Purpose This element provides a statement of the history of the resource. It can also include a textual explanation of the processing steps and source of the resource, although these attributes may be better described in their specific elements.

MD_ExtendedElementInformation properties for “source” 2.7.17


name source

shortName dataSource



condition Mandatory if scope level is a “dataset” or “series”


maximumOccurrence N

domainValue LI_Source

parentEntity LI_Lineage



rule Left obligation as conditional but changed the condition

rationale To ensure that source information is always provided when scope is “dataset” or “series”


source/role owner


Meaning & Purpose Information about the source data used in creating the data specified by the scope

MD_ExtendedElementInformation properties for “description” 2.7.18


name description

shortName srcDesc



condition


maximumOccurrence 1


parentEntity LI_Source


rationale To ensure that a description of the source of the data is always provided


source/role owner


Meaning & Purpose Detailed description of the source of the data

MD_ExtendedElementInformation properties for 2.7.19“distributionFormat”


name distributionFormat

shortName distFormat



condition



maximumOccurrence N

domainValue MD_Format

parentEntity MD_Distribution

rule Changed obligation from conditional to mandatory (in cases where a resource is intended for distribution and hence specifies distribution information)

rationale To ensure that distribution format information is always provided for appropriate resources


source/role owner


Meaning & Purpose Provides a description of the format of the resource to be distributed. If the resource is intended for distribution then the MD_Distribution element will be present. This rule ensures that MD_Distribution elements contain a non-empty value for the ‘distributionFormat’ child element.


GA Profile Metadata Schemas (UML) Annex A

A.1 Metadata UML models Metadata for describing geographic data is defined using an abstract object model in the Unified Modelling Language (UML). The following diagrams provide “views,” which are portions of the total abstract model for metadata. Each diagram defines a metadata section (UML package) of related entities, elements, data types, and code lists. Related entities, which are defined in another diagram, are shown with elements suppressed and the defining package specified under the entity name in parenthesis. Throughout the following models, entities may have mandatory and/or optional elements and associations. In some cases, optional entities may have mandatory elements; those elements become mandatory only if the optional element is used.

The data dictionary for the UML class diagrams is listed in Annex B.

A.2 Metadata package UML diagrams

A.2.1 Metadata entity set information

The MD_Metadata class shows containment relationships with the other metadata classes which define metadata for geospatial data. Refer to B.2.1 for the data dictionary for this diagram.

Figure 1: Metadata entity set information

class Metadata entity set information

MD_Metadata

+ fi leIdentifier :CharacterString+ language :CharacterString [0..1]+ characterSet :MD_CharacterSetCode [0..1] = "utf8"+ parentIdentifier :CharacterString [0..1]+ hierarchyLevel :MD_ScopeCode [0..*] = "dataset"+ hierarchyLevelName :CharacterString [0..*]+ contact :CI_ResponsibleParty [1..*]+ dateStamp :Date+ metadataStandardName :CharacterString+ metadataStandardVersion :CharacterString+ dataSetURI :CharacterString [0..1]

«abstract»Spatial representation

information::MD_SpatialRepresentation

Metadata extension information::MD_MetadataExtensionInformation

«abstract»Content information::

MD_ContentInformation

Distribution information::

MD_Distribution

Data quality information::

DQ_DataQuality

Constraint information::MD_Constraints

+ useLimitation :CharacterString [0..1]

Portrayal catalogue information::MD_PortrayalCatalogueReference

Application schema information::MD_ApplicationSchemaInformation

Maintenance information::MD_MaintenanceInformation

Conditional statements:language: documented if not defined by the encodingstandardcharacterSet: documented if ISO 10646-1 not used andnot defined by the encoding standardparentIdentifier: documented if hierarchyLevel is one of “feature”, “featureType”, “attribute” or “attributeType” hierarchyLevel: documented if hierarchyLevel not = "dataset"hierarchyLevelName: documented if hierarchyLevel not = "dataset"dataSetURI: documented if hierarchyLevel = "dataset"referenceSystemInfo: documented if hierarchyLevel = "dataset"

Reference system information::

MD_ReferenceSystem

«abstract»Identification information::MD_Identification

metadataStandardName: default value = "GA Metadata Profile: A Geoscience Australia Profile of AS/NZS ISO 19115:2005, Geographic information - Metadata"

metadataStandardVersion: default value = "1.0"

+portrayalCatalogueInfo 0..*

+contentInfo0..*

+distributionInfo

0..1

+dataQualityInfo

1..*

+spatialRepresentationInfo 0..*

+metadataConstraints

1..*

+metadataMaintenance0..1

+metadataExtensionInfo 0..*+referenceSystemInfo 0..*

+resourceConstraints

1..*

+resourceMaintenance1..*

+identificationInfo

1..*

+applicationSchemaInfo0..*


A.2.2 Identification information

The UML for identification information defines the metadata classes required to identify a resource. It also defines separate specialisation sub-classes for identifying data and services. Refer to B.2.2 for the data dictionary for this diagram.

Figure 2: Identification information

class Identification information

Metadata entity set information::MD_Metadata

«abstract»MD_Identification

+ citation :CI_Citation+ abstract :CharacterString+ purpose :CharacterString [0..1]+ credit :CharacterString [0..*]+ status :MD_ProgressCode [0..*]+ pointOfContact :CI_ResponsibleParty [1..*]

Maintenance information::MD_MaintenanceInformation

Constraint information::MD_Constraints

Distribution information::MD_Format

MD_BrowseGraphic

+ fi leName :CharacterString+ fi leDescription :CharacterString [0..1]+ fi leType :CharacterString [0..1]

MD_Usage

+ specificUsage :CharacterString+ usageDateTime :DateTime [0..1]+ userDeterminedLimitations :CharacterString [0..1]+ userContactInfo :CI_ResponsibleParty [1..*]

MD_AggregateInformation

+ aggregateDataSetName :CI_Citation [0..1]+ aggregateDataSetIdentifier :MD_Identifier [0..1]+ associationType :DS_AssociationTypeCode+ initiativeType :DS_InitiativeTypeCode [0..1]

MD_Keywords

+ keyword :CharacterString [1..*]+ type :MD_KeywordTypeCode [0..1]+ thesaurusName :CI_Citation [0..1]

MD_Serv iceIdentificationMD_DataIdentification

+ spatialRepresentationType :MD_SpatialRepresentationTypeCode [0..*]+ spatialResolution :MD_Resolution [0..*]+ language :CharacterString [1..*]+ characterSet :MD_CharacterSetCode [0..*] = "utf8"+ topicCategory :MD_TopicCategoryCode [1..*]+ environmentDescription :CharacterString [0..1]+ extent :EX_Extent [0..*]+ supplementalInformation :CharacterString [0..1]

characterSet: documented if ISO 10646-1 is not usedresourceFormat: documented if hierarchyLevel = "dataset"

{MD_Metadata.hierarchyLevel = "dataset" or "series" implies count(extent.geographicElement.EX_GeographicBoundingBox) + count(extent.geographicElement.EX_GeographicDescription) >=1}

Either"aggregateDataSetName" or"aggregateDataSetIdentifier"must be documented

«union»MD_Resolution

+ equivalentScale :MD_RepresentativeFraction+ distance :Distance

«CodeList»MD_Initiativ eTypeCode

+ campaign+ collection+ exercise+ experiment+ investigation+ mission+ sensor+ operation+ platform+ process+ program+ project+ study+ task+ trial

«CodeList»DS_AssociationTypeCode

+ crossReference+ largerWorkCitation+ partOfSeamlessDatabase+ source+ stereoMate

«enumeration»MD_TopicCategoryCode

farming biota boundaries climatologyMeteorologyAtmosphere economy elevation environment geoscientificInformation health imageryBaseMapsEarthCover intell igenceMilitary inlandWaters location oceans planningCadastre society structure transportation util i tiesCommunication

«CodeList»MD_CharacterSetCode

+ ucs2+ ucs4+ utf7+ utf8+ utf16+ 8859part1+ 8859part2+ 8859part3+ 8859part4+ 8859part5+ 8859part6+ 8859part7+ 8859part8+ 8859part9+ 8859part10+ 8859part11+ (reserved for future use)+ 8859part13+ 8859part14+ 8859part15+ 8859part16+ jis+ shiftJIS+ eucJP+ usAscii+ ebcdic+ eucKR+ big5+ GB2312

«CodeList»MD_SpatialRepresentationTypeCode

+ vector+ grid+ textTable+ tin+ stereoModel+ video

«CodeList»MD_ProgressCode

+ completed+ historicalArchive+ obsolete+ onGoing+ planned+ required+ underDevelopment

«DataType»MD_Representativ eFraction

+ denominator :Integer

+aggregationInfo

0..*

+descriptiveKeywords

0..*

+graphicOverview

0..*

+resourceSpecificUsage0..*

+resourceFormat

0..*

+resourceConstraints

1..*

+resourceMaintenance1..*

+identificationInfo 1..*

A.2.3 Constraint information

The UML class diagram for constraint information defines the metadata required for managing rights to information including restrictions on access and use. Refer to B.2.3 for the data dictionary for this diagram.

Figure 3: Constraint information

class Constraint information

MD_Constraints

+ useLimitation :CharacterString [0..1]

Metadata entity set information::MD_Metadata«abstract»Identification information::MD_Identification

MD_LegalConstraints

+ accessConstraints :MD_RestrictionCode [0..*]+ useConstraints :MD_RestrictionCode [0..*]+ otherConstraints :CharacterString [0..*]

MD_SecurityConstraints

+ classification :MD_ClassificationCode+ userNote :CharacterString [0..1]+ classificationSystem :CharacterString [0..1]+ handlingDescription :CharacterString [0..1]

«CodeList»MD_ClassificationCode

+ unclassified+ restricted+ confidential+ secret+ topSecret

«CodeList»MD_RestrictionCode

+ copyright+ patent+ patentPending+ trademark+ license+ intellectualPropertyRights+ restricted+ otherRestrictions

accessConstraints: documented if descendant of resourceConstraintsuseConstraints: documented if descendant of resourceConstraintsotherConstraints: documented if accessConstraints oruseConstraints = "otherRestrictions"

+metadataConstraints1..*+resourceConstraints 1..*


A.2.4 Data quality information

The UML class diagram for data quality information defines the metadata required to give a general assessment of the quality of a resource. Refer to B.2.4 for the data dictionary for this diagram.

class Data quality information

DQ_DataQuality + scope :DQ_Scope

Metadata entity set information::MD_Metadata

LI_Linag

+ statement

«abstract» DQ_Element

+ nameOfMeasure :CharacterString [0..*] + measureIdentification :MD_Identifier [0..1] + measureDescription :CharacterString [0..1] + evaluationMethodType :DQ_EvaluationMethodTypeCode [0..1] + evaluationMethodDescription :CharacterString [0..1] + evaluationProcedure :CI_Citation [0..1] + dateTime :DateTime [0..*] + result :DQ_Result [1..2]

«abstract» DQ_Result

«DataType» DQ_Scope

+ level :MD_ScopeCode + extent :EX_Extent [0..1] + levelDescription :MD_ScopeDescription [0..*]

«CodeList» MD_EvaluationMethodTypeCode + directInternal + directExternal + indirect

DQ_ConformanceResult + specification :CI_Citation + explanation :CharacterString + pass :Boolean

DQ_QuantitativeResult + valueType :RecordType [0..1] + valueUnit :UnitOfMeasure + errorStatistic :CharacterString [0..1] + value :Record [1..*]

"levelDescription" is mandatory if "level" notEqual 'dataset' or 'series'

"report" or "linage" role mandatory if

scope.DQ_Scope.level 'dataset'

+dataQualityInfo 1..* +linage

+report 0..*

Figure 4 Data quality information

A.2.5 Lineage information

This UML class diagram for lineage supports the provision of metadata concerning the sources and production processes used in producing a resource. Refer to B.2.4.2 for the data dictionary for this diagram.

Figure 5: Lineage information


A.2.6 Distribution information

The UML class diagram for distribution information defines the metadata required for accessing a resource. Refer to B.2.5 for the data dictionary for this diagram.

Figure 6: Distribution information

class Distribution information

MD_Distribution

MD_Format

+ name :CharacterString+ version :CharacterString+ amendmentNumber :CharacterString [0..1]+ specification :CharacterString [0..1]+ fi leDecompressionTechnique :CharacterString [0..1]

Metadata entity set information::MD_Metadatacount (distributionFormat + distributorFormat) > 0

MD_DigitalTransferOptions

+ unitsOfDistribution :CharacterString [0..1]+ transferSize :Real [0..1]+ onLine :CI_OnlineResource [0..*]+ offLine :MD_Medium [0..1]

MD_Distributor

+ distributorContact :CI_ResponsibleParty

«CodeList»MD_MediumFormatCode

+ cpio+ tar+ highSierra+ iso9660+ iso9660RockRidge+ iso9660AppleHFS

«CodeList»MD_MediumNameCode

+ cdRom+ dvd+ dvdRom+ 3halfInchFloppy+ 5quarterInchFloppy+ 7trackTape+ 9trackTape+ 3480Cartridge+ 3490Cartridge+ 3580Cartridge+ 4mmCartridgeTape+ 8mmCartridgeTape+ 1quarterInchCartridgeTape+ digitalLinearTape+ onLine+ satell ite+ telephoneLink+ hardcopy

MD_StandardOrderProcess

+ fees :CharacterString [0..1]+ plannedAvailableDateTime :DateTime [0..1]+ orderingInstructions :CharacterString [0..1]+ turnaround :CharacterString [0..1]

«DataType»MD_Medium

+ name :MD_MediumNameCode [0..1]+ density :Real [0..*]+ densityUnits :CharacterString [0..1]+ volumes :Integer [0..1]+ mediumFormat :MD_MediumFormatCode [0..*]+ mediumName :CharacterString [0..1]

"densityUnits" is mandatory if "density" is provided

+distributionInfo 0..1+distributionFormat

+transferOptions 0..* +distributor0..*

+FormatDistributor0..*

+distributorFormat0..*

+distributionOrderProcess 0..*

+distributorTransferOptions

0..*

GA Profile Data Dictionary Annex B

B.1 Data Dictionary Overview

B.1.1 Introduction

This data dictionary describes the characteristics of the metadata defined by the UML model in Annex A.

The dictionary is categorised into sections by UML model package diagram: Metadata Entity Set, Identification, Constraints, Data Quality, Lineage and Distribution. The clause titles of several of the tables have been expanded to reflect class specification within the respective diagram. Each model diagram from Annex A has a section within the data dictionary. In keeping with Annex A, this section only represents those entities whose content models have been changed by the GA profile. Entities not represented in this section remain unchanged from their definitions provided in ANZLIC ISO 19115:2005.

Each UML model class equates to a data dictionary entity. Each UML model class attribute equates to a data dictionary element. The shaded rows define entities. The reference to the ISO 9115 entities and elements are shown as a number within brackets, e.g. (334). The symbol † is used to identify the attributes whose constraints have been modified by this profile.

In case of ambiguity between the data dictionary definitions and the UML class diagrams, the UML class diagrams should be treated as the authoritative source.

The term “dataset,” when used as part of a definition, is synonymous with all types of geographic data resources (aggregations of datasets, individual features and the various classes that compose a feature).

B.1.2 Name/role name

A label assigned to a metadata entity or to a metadata element. Metadata entity names start with an upper case letter. Spaces do not appear in a metadata entity name. Instead, multiple words are concatenated, with each new word starting with a capital letter (e.g. ExampleName). Metadata entity names are unique within the entire data dictionary of this standard. Metadata element names are unique within a metadata entity, not the entire data dictionary of this standard. Metadata element names are made unique, within an application, by the combination of the metadata entity and metadata element names (e.g. MD_Metadata.characterSet). Role names are used to identify metadata abstract model associations and are preceded by “Role name:” to distinguish them from other metadata elements. Names and role names may be in a language other than that used in this standard.


B.1.3 Short name and ISO reference

Those classes that are not CodeList or Enumeration stereotypes are provided with a Short Name for each element. A naming convention similar to that used to create the longer entity and element names was used to create the short names. The number in brackets after the short name is a reference to the ISO 19115 metadata entity or metadata element.

B.1.4 Definition

The metadata entity/element description

B.1.5 Obligation/Condition

B.1.5.1 General

This is a descriptor indicating whether a metadata entity or metadata element shall always be documented in the metadata or sometimes be documented (i.e. contains value(s)). This descriptor may have the following values: mandatory (M), conditional (C), or optional (O).

B.1.5.2 Mandatory

An indication that the metadata entity or metadata element must be documented

B.1.5.3 Conditional

Specifies an electronically manageable condition under which at least one metadata entity or a metadata element is mandatory. Conditional is used for one of the three following possibilities:

• Expressing a choice between two or more options. At least one option is mandatory and must be documented.

• Documenting a metadata entity or a metadata element if another element has been documented.

• Documenting a metadata element if a specific value for another metadata element has been documented. To facilitate reading by humans, the specific value is used in plain text (e.g. table in Section B.2.1, row 3 “conditional / not defined by encoding”).

If the answer to the condition is positive, then the metadata entity or the metadata element shall be mandatory.

B.1.5.4 Optional

The metadata entity or the metadata element may be documented or may not be documented. Optional metadata entities and optional metadata elements have been defined to provide a guide to those looking to fully document their data. (Use of this common set of defined elements will help promote interoperability among geographic data users and producers world-wide.) If an optional entity is not used, the elements contained within that entity (including mandatory elements) will also not be used. Optional entities may have mandatory elements; those elements only become mandatory if the optional entity is used.

B.1.5.5 Maximum occurrence

Specifies the maximum number of instances the metadata entity or the metadata element may have. Single occurrences are shown by “1”; repeating occurrences are represented by “N”.


B.2 Metadata package data dictionaries

B.2.1 Metadata entity set information

Name / Role name Short name Definition Obligation / Condition

Maximum occurrence

Data type Domain

1 MD_Metadata Metadata root entity which defines metadata about a resource or resources

M 1 Class

2 fileIdentifier† mdFileID unique identifier for this metadata file M 1 CharacterString Free text 3 language mdLang language used for documenting

metadata C / not defined by encoding?

1 CharacterString ISO 639-2, other parts may be used

4 characterSet mdChar full name of character coding standard used for the metadata set

C / ISO/IEC 10646-1 not used and not defined by encoding?

1 Class MD_CharacterSetCode; Default value = “utf8”

5 parentIdentifier† mdParentID file identifier of the metadata to which this metadata is a subset (child)

C / hierarchyLevel is one of “feature”, “featureType”, “attribute”, “attributeType” ?

1 CharacterString Free text

6 hierarchyLevel mdHrLv scope to which the metadata applies (see ANZLIC ISO19115 Annex H for more information about metadata hierarchy levels)

C / hierarchyLevel is not equal to ”dataset”?

N Class MD_ScopeCode

7 hierarchyLevelName mdHrLvName name of the hierarchy levels for which the metadata is provided

C / hierarchyLevel is not equal to ”dataset”?

N CharacterString Free text

8 contact mdContact party responsible for the metadata M N Class CI_ResponsibleParty 9 dateStamp mdDateSt date that the metadata was created M 1 Class Date 10 metadataStandardName† mdStanName name of the metadata standard

(including profile name) used M 1 CharacterString Free text; Default value =

“GA Metadata Profile: A Geoscience Australia Profile of AS/NZS ISO 19115:2005, Geographic information - Metadata”

11 metadataStandardVersion† mdStanVer version (profile) of the metadata standard used

M 1 CharacterString Free text; Default value = “1.0”

34 Geoscience Australia Community Metadata Profile of ISO 19115:2005


Maximum occurrence

Data type Domain

11.1 dataSetURI† dataSetURI Uniformed Resource Identifier (URI) of the dataset to which the metadata applies

C / hierarchyLevel is equal to ”dataset”?

1 CharacterString Free text

12 Role name: spatialRepresentationInfo

spatRepInfo digital representation of spatial information in the dataset

O N Association MD_SpatialRepresentation

13 Role name: referenceSystemInfo†

refSysInfo description of the spatial and temporal reference systems used in the dataset


N Association MD_ReferenceSystem

14 Role name: metadataExtensionInfo

mdExtInfo information describing metadata extensions

O N Association MD_MetadataExtensionInformation

15 Role name: identificationInfo

dataIdInfo basic information about the resource(s) to which the metadata applies

M N Association MD_Identification

16 Role name: contentInfo

contInfo provides information about the feature catalogue and describes the coverage and image data characteristics

O N Association MD_ContentInformation

17 Role name: distributionInfo

distInfo provides information about the distributor of and options for obtaining the resource(s)

O 1 Association MD_Distribution

18 Role name: dataQualityInfo†

dqInfo provides overall assessment of quality of a resource(s)

M N Association DQ_DataQuality

19 Role name: portrayalCatalogueInfo

porCatInfo provides information about the catalogue of rules defined for the portrayal of a resource(s)

O N Association MD_PortrayalCatalogueReference

20 Role name: metadataConstraints†

mdConst provides restrictions on the access and use of metadata

M N Association MD_Constraints

21 Role name: applicationSchemaInfo

appSchInfo provides information about the conceptual schema of a dataset

O N Association MD_ApplicationSchemaInformation

22 Role name: metadataMaintenance

mdMaint provides information about the frequency of metadata updates, and the scope of those updates

O 1 Association MD_MaintenanceInformation


B.2.2 Identification information

B.2.2.1 General


Maximum occurrence

Data type Domain

23 MD_Identification Ident basic information required to uniquely identify a resource or resources

Use obligation from referencing object

Use maximum occurrence from referencing object

Aggregated Class (MD_Metadata) <<Abstract>>

24 citation idCitation citation data for the resource(s) M 1 Class CI_Citation 25 abstract idAbs brief narrative summary of the

content of the resource(s) M 1 CharacterString Free text

26 purpose idPurp summary of the intentions with which the resource(s) was developed

O 1 CharacterString Free text

27 credit idCredit recognition of those who contributed to the resource(s)

O N CharacterString Free text

28 status idStatus status of the resource(s) O N Class MD_ProgressCode 29 pointOfContact† idPoC identification of, and means of

communication with, person(s) and organization(s) associated with the resource(s)

M N Class CI_ResponsibleParty

30 Role name: resourceMaintenance†

resMaint provides information about the frequency of resource updates, and the scope of those updates

M N Association MD_MaintenanceInformation

31 Role name: graphicOverview

graphOver provides a graphic that illustrates the resource(s) (should include a legend for the graphic)

O N Association MD_BrowseGraphic

32 Role name: resourceFormat†

dsFormat provides a description of the format of the resource(s)


N Association MD_Format

33 Role name: descriptiveKeywords

descKeys provides category keywords, their type, and reference source

O N Association MD_Keywords

34 Role name: resourceSpecificUsage

idSpecUse provides basic information about specific application(s) for which the resource(s) has/have been or is being used by different users

O N Association MD_Usage



Maximum occurrence

Data type Domain

35 Role name: resourceConstraints†

resConst provides information about constraints which apply to the resource(s)

M N Association MD_Constraints

35.1 Role name: aggregationInfo

aggrInfo provides aggregate dataset information

O N Association MD_AggregateInformation

36 MD_DataIdentification DataIdent information required to identify a dataset



Specialised Class (MD_Identification)

37 spatialRepresentationType spatRpType method used to spatially represent geographic information

O N Class MD_SpatialRepresentationTypeCode

38 spatialResolution dataScale factor which provides a general understanding of the density of spatial data in the dataset

O N Class MD_Resolution

39 language dataLang language(s) used within the dataset M N CharacterString ISO 639-2, other parts may be used

40 characterSet dataChar full name of the character coding standard used for the dataset

C / ISO/IEC 10646-1 not used?

N Class MD_CharacterSetCode

41 topicCategory† tpCat main theme(s) of the dataset M N Class MD_TopicCategoryCode; Default value = “geoscientificInformation”

42 intentionally left blank 43 intentionally left blank 44 environmentDescription envirDesc description of the dataset in the

producer’s processing environment, including items such as the software, the computer operating system, file name, and the dataset size




Maximum occurrence

Data type Domain

45 extent† dataExt extent information including the bounding box, bounding polygon, vertical, and temporal extent of the dataset

C / hierarchyLevel is equal to ”dataset” or “series”? either extent.geographic Element.EX_ GeographicBounding Box or extent.geographic Element.EX_ Geographic Description is required

N Class EX_Extent

46 supplementalInformation suppInfo any other descriptive information about the dataset


B.2.3 Constraint information


Maximum occurrence

Data type Domain

67 MD_Constraints Consts restrictions on the access and use of a resource or metadata



Aggregated Class (MD_Metadata and MD_Identification)

68 useLimitation useLimit limitation affecting the fitness for use of the resource or metadata. Example: “The quality of the data is not good enough to be used as input observation data in climatological models”.

O N CharacterString Free text

69 MD_LegalConstraints LegConsts restrictions and legal prerequisites for accessing and using the resource or metadata



Specialised Class (MD_Constraints)



Maximum occurrence

Data type Domain

70 accessConstraints† accessConsts access constraints applied to assure the protection of privacy or intellectual property, and any special restrictions or limitations on obtaining the resource or metadata

C / descendant of resourceConstraints?

N Class MD_RestrictionCode

71 useConstraints† useConsts constraints applied to assure the protection of privacy or intellectual property, and any special restrictions or limitations or warnings on using the resource or metadata

C / descendant of resourceConstraints?

N Class MD_RestrictionCode

72 otherConstraints othConsts other restrictions and legal prerequisites for accessing and using the resource or metadata

C / accessConstraints or useConstraints equal “otherRestrictions”?

N CharacterString Free text

73 MD_SecurityConstraints SecConsts handling restrictions imposed on the resource or metadata for national security or similar security concerns



Specialised Class (MD_Constraints)

74 classification class name of the handling restrictions on the resource or metadata

M 1 Class MD_ClassificationCode

75 userNote userNote explanation of the application of the legal constraints or other restrictions and legal prerequisites for obtaining and using the resource or metadata

O 1 Class Free text

76 classificationSystem classSys name of the classification system O 1 Class Free text 77 handlingDescription handDesc additional information about the

restrictions on handling the resource or metadata

O 1 Class Free text


B.2.4 Data quality information

B.2.4.1 General


Maximum occurrence

Data type Domain

78 DQ_DataQuality DataQual quality information for the data specified by a data quality scope



Aggregated Class (MD_Metadata)

79 scope dqScope the specific data to which the data quality information applies

M 1 Class DQ_Scope

80 Role name: report

dqReport quantitative quality information for the data specified by the scope

C / lineage not provided?

N Association DQ_Element

81 Role name: lineage†

dataLineage non-quantitative quality information about the lineage of the data specified by the scope

M 1 Association LI_Lineage

B.2.4.2 Lineage information

B.2.4.2.1 General


Maximum occurrence

Data type Domain

82 LI_Lineage Lineage information about the events or source data used in constructing the data specified by the scope or lack of knowledge about lineage



Aggregated Class (DQ_DataQuality)

83 statement† statement general explanation of the data producer’s knowledge about the lineage of a dataset

M 1 CharacterString Free text

84 Role name: processStep

prcStep information about events in the life of a dataset specified by the scope

C / mandatory if statement and source not provided?

N Association LI_ProcessStep



Maximum occurrence

Data type Domain

85 Role name: source†

dataSource information about the source data used in creating the data specified by the scope

C / (DQ_DataQuality.scope.DQ_Scope.level = “dataset”)?

N Association LI_Source

B.2.4.2.2 Source Information


Maximum occurrence

Data type Domain

92 LI_Source Source information about the source data used in creating the data specified by the scope



Aggregated Class (LI_Lineage and LI_ProcessStep)

93 description† srcDesc detailed description of the source of the data

M 1 CharacterString Free text

94 scaleDenominator srcScale denominator of the representative fraction on a source map

O 1 Class MD_RepresentativeFraction

95 sourceReferenceSystem srcRefSys spatial reference system used by the source data

O 1 Class MD_ReferenceSystem

96 sourceCitation srcCitatn recommended reference to be used for the source data

O 1 Class CI_Citation

97 sourceExtent srcExt information about the spatial, vertical and temporal extent of the source data

C / description not provided3?

N Class EX_Extent

98 Role name: sourceStep

srcStep information about an event in the creation process for the source data

O N Association LI_ProcessStep

3 In effect this property is now “Optional” following the addition of a mandatory obligation on the “description” property. However the obligation text remains unchanged in this profile as it is not permissible to formally relax constraints in a profile of ISO19115.


B.2.5 Distribution information

B.2.5.1 General


Maximum occurrence

Data type Domain

270 MD_Distribution Lineage information about the events or source data used in constructing the data specified by the scope or lack of knowledge about lineage



Aggregated Class (DQ_DataQuality)

271 Role name: distributionFormat†

distFormat provides a description of the format of the data to be distributed

M N Association MD_Format

272 Role name: distributor

distributor provides information about the distributor

O N Association MD_Distributor


B.3 CodeLists and Enumerations The GA profile does not currently require any additional or extended code lists or enumerations. Hence it relies solely on those defined in ANZLIC ISO 19115:2005.


A Use of Metadata Hierarchy Annex C(informative)

C.1 Background Annex G of ANZLIC ISO 19115:2005 provides information about the granularity of metadata entities and the potential use of hierarchy in metadata collections.

This hierarchy of metadata can be graphically represented as shown in Figure 7.

Figure 7: Proposed Metadata Hierarchy Model for GA

class GA Metadata Hierarchy Model

Data series

Dataset

Feature instance Attribute instanceFeature type Attribute type

Note that whilst attributes are conceptually the children of features, ISO19115 suggests that dataset parents be aggregates of features and attributes (both types and instances).

In practice this allows for ISO 19139 catalogue implementations to more easily answer questions about metadata relating to a specific dataset (at the cost of making it more difficult to query attributes types associated with a given feature).

Variations on the proposed aggregation or content model are possible as the normative content of ISO19115 imposes very few constraints on hierarchy level and the associated information model. The proposed structure in Figure 7 will be used as a starting point within GA, and may evolve subject to its ability to meet our business requirements.

C.1.1 Definition by exception

The metadata hierarchy level of ISO 19115 is designed to use the concept of “inheritance” associated with Object Oriented class modelling. Each child object inherits information from it parent and has the


option to add or override individual fields. In other words classes lower down in a hierarchy need only define content by exception.

Whilst a feature instance or attribute instance record might only define a small number of fields it is important to recognise it is the fully inherited content model that forms the basis of the record that aims to comply with the constraints of this profile.

C.1.2 Relational data stores and metadata hierarchy

The concept of “definition by exception” as described in the previous subsection is similar to the use of normalised form in relational data modelling.

It is anticipated that the “source of truth” location for most GA profile metadata records will be in corporate Oracle databases. Where possible these databases should use normalised form to represent the GA profile metadata model.

C.1.3 Catalog implementations, CSW and ISO19139

Whilst the source of truth for most GA profile metadata records is likely to be in Oracle databases, catalog implementations that collectively represent those records will most likely not be.

Catalog implementations are required within GA to provide search services over collections of GA profile metadata records (and potentially other record types). They provide an OGC Catalog Services for the Web (CSW) service interface allowing other applications to query the underlying metadata collections. Importantly they represent the underlying ISO 19115 records in XML format (ISO 19139).

Most CSW implementations, like GeoNetwork, require that metadata hierarchy be represented in denormalised form. In other words the catalog represents a collection of XML documents, each with its inherited hierarchy information duplicated into the individual record. The requirement for denormalised form in these catalogs does not imply a requirement for denormalisation in the source data tables or structures.

Catalog databases (like those used by GeoNetwork) are typically inadequate for the purposes of long-term persistent storage and should not be considered the source location for the underlying metadata record data.

C.2 Example of GA profile hierarchy TODO – examples of one or two hierarchy models that might be used in GA with this profile.

C.3 Hierarchy Guidelines Refer to the “GA Profile User Guide” for guidelines on the appropriate use of metadata hierarchy with the GA profile.

Geoscience Australia Community Metadata Profile of ISO … · C.3 Hierarchy Guidelines .....44 ....

Documents

Transcript of Geoscience Australia Community Metadata Profile of ISO … · C.3 Hierarchy Guidelines .....44 ....