Advanced ISO Topics

ISO for Data Documentation

Contents• Content Updates

– gmx:Anchor for text– Codelists

• NCEI Component Registry– Resolved Records– Unresolved Records

• Related Standards– ISO 19110– ISO 19111

• Status of Standards

Special Problem:

• I have an element that is a free text domain. How can I restrict this field to a set of defined terms?

gmx:Anchor for text• anchor (gmx:Anchor) can be used as a substitute for

a CharacterString when you want to restrict the free text to a controlled vocabulary.

Ex: <gco:CharacterString>Pearl Harbor, HI</gco:CharacterString>

can be replaced by<gmx:Anchor xlink:href="http://www.rvdata.us/voc/port#101065">Pearl Harbor, HI</gmx:Anchor>

In this implementation example, the gmx:Anchor points to a vocabulary that containing a specific vocabulary entry.

Special Problem: Codelists• I have an element that uses a codeList but the codeList

values do not contain the information I need. How can I extend the codeList or can I use my own?

• Creators can supply your own codeList anywhere in the Standard by pointing to a custom location instead of the standard location. Of course, this could cause interoperability problems, so it should not be done without careful consideration of the implications.

NCEI Component Registry - Docucomp

Example CI_ResponsibleParty

Unresolved Records

Record Services

Sample record

Resolve Records

Ideally, you have a single component with a default role that you can “overwrite”.

When you resolve the component, the specified role will override and replace the default

component role value.

Special Problem:• How do I change the default role value of a

responsible party component?

Example of ‘role’Ex:

<gmd:contact xlink:href="http://www.ngdc.noaa.gov/docucomp/component/7c7d17a0-4d66-11df-9879-0800200c9a66" xlink:title="DOC/NOAA/NESDIS/NODC/NCDDC> National Coastal Data Development Center (pointOfContact)">

<gmd:CI_ResponsibleParty><gmd:role>

<gmd:CI_RoleCode codeList="http://www.isotc211.org/2005/resources/Codelist/gmxCodelists.xml#CI_RoleCode" codeListValue="originator" codeSpace="006">originator</gmd:CI_RoleCode>

</gmd:role></gmd:CI_ResponsibleParty>

</gmd:contact>

Example of ‘role’Ex: The component <gmd:contact

xlink:href="http://www.ngdc.noaa.gov/docucomp/component/7c7d17a0-4d66-11df-9879-0800200c9a66" xlink:title="DOC/NOAA/NESDIS/NODC/NCDDC> National Coastal Data Development Center (pointOfContact)"/>

Has a default role of

pointOfContact

Related Standards -19110• This is a separate document that can be used

to describe the ‘content’ of your dataset,when appropriate.

• It is similar to the CSDGM Section 5 Entity and Attributes

• A “data dictionary”

Content Information

FC_FeatureCatalogue

Future ISO 19110 Feature Catalog use

Related Standards -19111• How do I document the Spatial Referencing?

ISO 19111 Spatial Referencing Use

ISO 19111 Spatial Referencing Use• Use citation and identifier to reference to external 19111• Use components to reference to external registries

– EPSG http://www.epsg-registry.org/– spatialreference.org http://www.spatialreference.org/

Related Standards -19119• How do I use ISO 19119 to document

Services?

ISO 19119 Service Metadata use

ISO 19119 Service Metadata use

Special Problem:• How can I document biological data?• The ISO 19115 and -2 can be used to describe biological data.• Use the metadata extension information provided in the ISO

19115 standard as needed.

• Extended ISO Biological schema available via ftp://ftp.ncddc.noaa.gov/pub/Metadata/NOS_CD/schemas/ISObio/

• See Biological Workbook

http://service.ncddc.noaa.g

ov/rdn/www/metadata-standards/

documents/BIO-Metadata.pdf

Biological Profile Additions

MD_DataIdentification

Dataset Series• How do I build hierarchical relationships using

metadata?

Datasets, Aggregates and their Metadata – Hierarchical Metadata

Datasets, Aggregates and their Metadata – Hierarchical Metadata

Hierarchical Metadata

Subsets

Building Relationships

Platform

Data type/sensor

Cruise 1

Cruise2

Cruise 1

Building Relationships

Program

Platform

Data type/sensor

Status of Standards

Who’s Your community

of practice???

Is 19110 still going to be separate in 19115-2?19139

XML schema implementation

19115-2 Part 2: gridded data and imagery

19115Geographic information – Metadata

19110 19111

MI_

MD_

FC_

19119Services

SV_

QUESTIONSncddcmetadata@noaa.gov