| Latest Newsletter | ||||
|
||||
Abstract
The description of the geographical information in DC should be done as mapping from ISO 19115 standard. This article describes issues in this context, which are still open.
Geographical information: mapping between ISO 19115 and DC
The Dublin Core has become an important part of the emerging infrastructure of the Internet. Many communities are eager to adopt a common core of semantics for resource description, and the Dublin Core has attracted broad ranging international and interdisciplinary support for this purpose. The description of the geographical information should be done as mapping from ISO 19115 standards. There are still open issues in this context.
DC elements with no ISO Core correspondence
There are four elements from Dublin Core that have no correspondence with any element of the Core version of the ISO DIS 19115. These four elements are "CONTRIBUTOR", "RELATION", "RIGHTS" and "AUDIENCE". Nevertheless, all of them have a correspondence with one or more elements of the full ISO standard.
|
CONTRIBUTOR |
MD_Metadata.identificationInfo > MD_DataIdentification.credit |
|
|
RELATION |
isVersionOf, replaces, isPartOf, references, isFormatOf, <otherwise> |
MD_Metadata.identificationInfo > MD_DataIdentification.aggregationInfo > MD_AggregateInfo |
|
RELATION |
isPartOf |
MD_Metadata.identificationInfo > MD_DataIdentification.citation > CI_Citation.series > CI_Series.name |
|
RIGHTS |
<none> |
MD_Metadata.identificationInfo > MD_DataIdentification.resourceConstraints > MD_LegalConstraints |
|
RIGHTS |
accessRights |
MD_Metadata.identificationInfo > MD_DataIdentification.resourceConstraints >MD_LegalConstraints.accessConstraints > MD_RestrictionCode |
|
AUDIENCE |
<none>,educationLevel |
MD_Metadata.identificationInfo > MD_DataIdentification.purpose |
|
AUDIENCE |
mediator |
MD_Metadata.distributionInformation >MD_Distribution.distributor > MD_Distributor.distributorContact > CI_ResponsibleParty (when role=distributor) |
This Core restriction could justify the expansion of the ISO Core Metadata for Geographic Data Sets in order to fulfil the mapping to Dublin Core. The aim of Dublin Core is to compile the minimum elements that describe a resource and thus ISO Core should include at least these DC elements to be really "Core".
ISO Core elements with no DC correspondence
There are some elements from the Core version of the ISO DIS 19115 that have no direct correspondence with elements from Dublin Core. Following table presents these elements and offers a solution for their mapping (if it exists).
|
ISO-CORE element |
Comment |
|
Dataset character set (C) (MD_Metadata.identificationInfo > MD_DataIdentification.characterSet) |
This is the full name of the character coding standard used for the dataset. The mapping between DC and ISO can be implemented as a refinement of the "FORMAT" Dublin Core element. |
|
Spatial resolution of the dataset (O) (MD_Metadata.identificationInfo > MD_DataIdentification.spatialResolution > MD_Resolution.equivalentScale or MD_Resolution.distance) |
This is the factor which provides a general understanding of the density of spatial data in the dataset. The mapping between DC and ISO cannot be implemented because this is a specific geographic feature of the resource. The draft spatial application profile proposes its use as main element. |
|
Reference system (O) (MD_Metadata.referenceSystemInfo > MD_ReferenceSystem) |
This term provides information about the reference system The mapping between DC and ISO cannot be implemented directly because this is a specific geographic feature of the resource. The draft spatial application profile propose its use as main element. |
|
Metadata file identifier (O) (MD_Metadata.fileIdentifier) |
This element represents the unique identifier for this metadata file. A possible mapping of this ISO element could be its definition as a refinement of the "IDENTIFIER" Dublin Core element. However, it may result complex to generate a unique identifier for metadata descriptions, particularly if data and metadata are delivered separately. |
|
Metadata standard name (O) (MD_Metadata.metadataStandardName) |
This term stores the name of the metadata standard (including profile name). There is not a mapping between ISO and DC. However, the standard name could be autogenerated for a mapping DC->ISO. The objective is precisely to obtain metadata compliant with ISO 19115, i.e. metadata using ISO 19115 as standard name. On the other hand, regarding DC metadata descriptions, the encoding itself should reference the document defining the Dublin Core elements. |
|
Metadata standard version (O) (MD_Metadata.metadataStandardVersion) |
This term stores the version (profile) of the metadata standard used There is not a mapping between ISO and DC. However, the standard name could be autogenerated for a mapping DC->ISO. The objective is precisely to obtain metadata compliant with ISO 19115 and a specific version. On the other hand, regarding DC metadata descriptions, the encoding itself should reference the document and version that defines the Dublin Core elements. |
|
Metadata language (C) (MD_Metadata.language) |
This term keeps the language used for documenting metadata. The mapping between DC and ISO can be implemented as a refinement of the "LANGUAGE" Dublin Core element. |
|
Metadata character set (C) (MD_Metadata.characterSet) |
This element represents the full name of the character coding standard used for the metadata set The mapping between DC and ISO can be implemented as a refinement of the "FORMAT" Dublin Core element. |
Reference: CEN WORKSHOP AGREEMENT CWA 14857 November 2003.
Impressum |
|
|
| Newsletters |
|
Webmaster
|