Constraint Documentation

Implementation

Directory Interchange Format (DIF)

Structure

<pre<noinclude> style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;"> <Access_Constraints>/DIF/Access_Constraints</Access_Constraints>

<Use_Constraints>/DIF/Use_Constraints</Use_Constraints>

International Organization for Standardization 19115 (ISO19115)

Structure

A general NOAA Disclaimer: This disclaimer states that NOAA has done everything possible to make sure that this resource is accurate, but that unforeseen errors or omissions might cause problems in some situations. The resource is freely accessible and use of the data are not restricted, i.e. there are no MD_LegalConstraints.

<gmd:resourceConstraints>
    <gmd:MD_Constraints>
        <gmd:useLimitation>
            <gco:CharacterString>Disclaimer - While every effort has been made to ensure that these data are 
            accurate and reliable within the limits of the current state of the art, NOAA cannot assume liability for any 
            damages caused by any errors or omissions in the data, nor as a result of the failure of the data to 
            function on a particular system. NOAA makes no warranty, expressed or implied, nor does the fact 
            of distribution constitute such a warranty.</gco:CharacterString>
        </gmd:useLimitation>
    </gmd:MD_Constraints>
</gmd:resourceConstraints>

A similar statement for bathymetry data with a link to resources appropriate for navigation:

<gmd:resourceConstraints>
    <gmd:MD_Constraints>
        <gmd:useLimitation>
            <gco:CharacterString>The intent of these data is to make high-resolution bathymetry available to the public for a 
                wide variety of uses such as research and earth science analysis.  These data are not intended to be used for navigation.  
                Nautical charts produced and certified by NOAA should be used for navigational purposes.  For more information on NOAA"s 
                nautical charts go to NOAA"s Office of Coast Survey website at: http://chartmaker.ncd.noaa.gov/.</gco:CharacterString>
        </gmd:useLimitation>
    </gmd:MD_Constraints>
</gmd:resourceConstraints>

The World Meteorological Organization (WMO) uses several sets of codes for classifying data that have implied access and use constraints. For example, 'WMO Essential' data are to be exchanged with WMO members and the public all over the world without charge and with no conditions on use, i.e. with no access or use constraints. Resources in this category could be described minimally as:

<gmd:resourceConstraints>
    <gmd:MD_LegalConstraints>
        <gmd:otherConstraints>
            <gco:CharacterString>WMO Essential</gco:CharacterString>
        </gmd:otherConstraints>
    </gmd:MD_LegalConstraints>
</gmd:resourceConstraints>

and the code associated with a given resource could be identified using the xPath: //gmd:otherConstraints/gco:CharacterString. The code would be found by someone that knew the content was in that specific element. However, it would be missed by a user or application asking the question in a slightly different way (i.e. are their access or use constraints on this resource?) using the xPaths //gmd:resourceConstraints/gmd:MD_LegalConstraints/gmd:accessConstraints/gmd:MD_RestrictionCode or //gmd:resourceConstraints/gmd:MD_LegalConstraints/gmd:useConstraints/gmd:MD_RestrictionCode. This could be avoided using:

<gmd:resourceConstraints>
    <gmd:MD_LegalConstraints>
        <gmd:accessConstraints>
            <gmd:MD_RestrictionCode codeList="http://www.ngdc.noaa.gov/metadata/published/xsd/schema/resources/
            Codelist/gmxCodelists.xml#MD_RestrictionCode" codeListValue="otherRestrictions">otherRestrictions</gmd:MD_RestrictionCode>
        </gmd:accessConstraints>
        <gmd:useConstraints>
            <gmd:MD_RestrictionCode codeList="http://www.ngdc.noaa.gov/metadata/published/xsd/schema/resources/
            Codelist/gmxCodelists.xml#MD_RestrictionCode" codeListValue="otherRestrictions">otherRestrictions</gmd:MD_RestrictionCode>
        </gmd:useConstraints>
        <gmd:otherConstraints>
            <gco:CharacterString>WMO Essential</gco:CharacterString>
        </gmd:otherConstraints>
    </gmd:MD_LegalConstraints>
</gmd:resourceConstraints>

which states that this resource is of type "WMO Essential" and has associated use and access constraints. This approach may also be appropriate for the category "WMO Additional" that is used for meteorological and related data and products on which WMO members place conditions related to their re-export for commercial purposes outside the receiving country (or group of countries forming a single economic group). The code "WMO Additional" indicates that the resource has some special use and access constraints:

<gmd:resourceConstraints>
    <gmd:MD_LegalConstraints>
        <gmd:accessConstraints>
            <gmd:MD_RestrictionCode codeList="http://www.ngdc.noaa.gov/metadata/published/xsd/schema/resources/
            Codelist/gmxCodelists.xml#MD_RestrictionCode" codeListValue="otherRestrictions">otherRestrictions</gmd:MD_RestrictionCode>
        </gmd:accessConstraints>
        <gmd:useConstraints>
            <gmd:MD_RestrictionCode codeList="http://www.ngdc.noaa.gov/metadata/published/xsd/schema/resources/
            Codelist/gmxCodelists.xml#MD_RestrictionCode" codeListValue="otherRestrictions">otherRestrictions</gmd:MD_RestrictionCode>
        </gmd:useConstraints>
        <gmd:otherConstraints>
            <gco:CharacterString>WMO Additional</gco:CharacterString>
        </gmd:otherConstraints>
    </gmd:MD_LegalConstraints>
</gmd:resourceConstraints>

Usage

ISO 19115 supports the description of constraints on resources and metadata using the MD_Constraints object. This object describes limitations on the fitness of use of the resource, use and access constraints, and security classification. Each of these elements have different implications. The definitions are:

useLimitation	limitation affecting the fitness for use of the resource or metadata. Example, “not to be used for navigation"
accessConstraints	access constraints applied to assure the protection of privacy or intellectual property, and any special restrictions or limitations on obtaining the resource or metadata
useConstraints	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
MD_SecurityConstraints	handling restrictions imposed on the resource or metadata for national security or similar security concerns. These elements are straight forward and different than the others and are not discussed further (for security reasons!).

The principle difference between these elements is that useLimitations is related to characteristics of the resource, how it was collected, or how it was processed that might make it inappropriate for some specific use, e.g. navigation. In contrast, the use and access constraints (i.e. the MD_LegalConstraints) are imposed on the resource by organizations that collect or distribute the data.

The useConstraints and accessConstraints elements are codes that can take any of the values in the MD_RestrictionCode code list (copyright, patent, patentPending, trademark, license, intellectualPropertyRights, restricted, otherRestrictions). The MD_Constraints object includes a constraint that states that otherConstraints must be documented if either useConstraints or accessConstraints have the value "otherConstraints". It does not, however, require useConstraints or accessConstraints if otherConstraints is populated.

Crosswalks

Resource and Metadata Constraints

Constraints on the use of the resource and metadata

Concept	Description	Dialect (Fit) Paths
Resource Access Constraints	Information about any constraints for accessing the data set. This includes any special restrictions, legal prerequisites, limitations and/or warnings on obtaining the data set. Some words that may be used in this field include: Public, In-house, Limited, Additional detailed instructions on how to access the data can be entered in this field.	DIF /DIF/Access_Constraints DCAT /dct:accessLevel DCAT dct:accessLevelComment ECHO /*/echo:RestrictionFlag ECHO /*/echo:RestrictionComment ECHO /*/echo:Visible ECS /*/ecs:AccessConstraints CSDGM /metadata/idinfo/accconst ISO /*/gmd:identificationInfo/*/gmd:resourceConstraints/gmd:MD_LegalConstraints/gmd:accessConstraints/gco:CharacterString ISO /*/gmd:identificationInfo/*/gmd:resourceConstraints/gmd:MD_LegalConstraints/gmd:otherConstraints/gco:CharacterString ISO-1 /mdb:MD_Metadata/mdb:identificationInfo/*/mri:resourceConstraints/mco:MD_LegalConstraints/mco:accessConstraints/gco:CharacterString ISO-1 /mdb:MD_Metadata/mdb:identificationInfo/*/mri:resourceConstraints/mco:MD_LegalConstraints/mco:otherConstraints/gco:CharacterString SERF /serf:DIF/serf:Access_Constraints THREDDS /thredds:catalog/thredds:dataset/thredds:documentation[@type="rights"] THREDDS /thredds:catalog/thredds:metadata/thredds:documentation[@type="rights"] netCDF /nc:netcdf/nc:variable/nc:attribute[@nc:name=license]/@nc:value
Resource Use Constraints	Information about how the data may or may not be used after access is granted to assure the protection of privacy or intellectual property. This includes any special restrictions, legal prerequisites, terms and conditions, and/or limitations on using the data set. Data providers may request acknowledgement of the data from users and claim no responsibility for quality and completeness of data.	DIF /DIF/Use_Constraints DCAT /dct:dataQuality ECHO /*/echo:RestrictionFlag ECHO /*/echo:RestrictionComment CSDGM /metadata/idinfo/useconst ISO /*/gmd:identificationInfo/*/gmd:resourceConstraints/gmd:MD_Constraints/gmd:useLimitation/gco:CharacterString ISO /*/gmd:identificationInfo/*/gmd:resourceConstraints/gmd:MD_LegalConstraints/gmd:useConstraints/gmd:MD_RestrictionCode ISO /*/gmd:identificationInfo/*/gmd:resourceConstraints/gmd:MD_LegalConstraints/gmd:otherConstraints/gco:CharacterString ISO-1 /mdb:MD_Metadata/mdb:identificationInfo/*/mri:resourceConstraints/mco:MD_Constraints/mco:useLimitation/gco:CharacterString ISO-1 /mdb:MD_Metadata/mdb:identificationInfo/*/mri:resourceConstraints/mco:MD_LegalConstraints/mco:useConstraints/mco:MD_RestrictionCode ISO-1 /mdb:MD_Metadata/mdb:identificationInfo/*/mri:resourceConstraints/mco:MD_LegalConstraints/mco:otherConstraints/gco:CharacterString SERF /serf:DIF/serf:Use_Constraints THREDDS /thredds:catalog/thredds:dataset/thredds:documentation[@type="rights"] THREDDS /thredds:catalog/thredds:metadata/thredds:documentation[@type="rights"] netCDF /nc:netcdf/nc:variable/nc:attribute[@nc:name=license]/@nc:value
Metadata Access Constraints	Information about any constraints for accessing the data set. This includes any special restrictions, legal prerequisites, limitations and/or warnings on obtaining the data set. Some words that may be used in this field include: Public, In-house, Limited, Additional detailed instructions on how to access the data can be entered in this field.	ISO /*/gmd:metadataConstraints/gmd:MD_LegalConstraints/gmd:legalConstraints/gmd:MD_RestrictionCode ISO /*/gmd:metadataConstraints/gmd:MD_LegalConstraints/gmd:otherConstraints/gco:CharacterString ISO-1 /mdb:MD_Metadata/mdb:metadataConstraints/mco:MD_LegalConstraints ISO-1 /mdb:MD_Metadata/mdb:metadataConstraints/mco:MD_SecurityConstraints
Metadata Use Constraints	Information about how the data may or may not be used after access is granted to assure the protection of privacy or intellectual property. This includes any special restrictions, legal prerequisites, terms and conditions, and/or limitations on using the data set. Data providers may request acknowledgement of the data from users and claim no responsibility for quality and completeness of data.	ISO /*/gmd:metadataConstraints/gmd:MD_Constraints/gmd:useLimitation/gco:CharacterString ISO /*/gmd:metadataConstraints/gmd:MD_LegalConstraints/gmd:useConstraints/gmd:MD_RestrictionCode ISO-1 /mdb:MD_Metadata/mdb:metadataConstraints/mco:MD_Constraints/mco:useLimitation/gco:CharacterString ISO-1 /mdb:MD_Metadata/mdb:metadataConstraints/mco:MD_LegalConstraints/mco:useConstraints/mco:MD_RestrictionCode
Security Constraints	Handling restrictions imposed on the resource or metadata for national security or similar security concerns.	DIF /DIF/Access_Constraints DIF /DIF/Use_Constraints CSDGM /metadata/idinfo/secinfo ISO /*/gmd:identificationInfo//*/gmd:resourceConstraints/gmd:MD_SecurityConstraints ISO-1 /mdb:MD_Metadata/mdb:identificationInfo/*/mri:resourceConstraints/mco:MD_SecurityConstraints
Security Constraints	Handling restrictions imposed on the resource or metadata for national security or similar security concerns.	DIF /DIF/Access_Constraints DIF /DIF/Use_Constraints CSDGM /metadata/idinfo/secinfo ISO /*/gmd:identificationInfo//*/gmd:resourceConstraints/gmd:MD_SecurityConstraints ISO-1 /mdb:MD_Metadata/mdb:identificationInfo/*/mri:resourceConstraints/mco:MD_SecurityConstraints
Release Constraints	Information about resource release constraints.	ISO-1 /mdb:MD_Metadata/mdb:identificationInfo/mri:MD_DataIdentification/mri:resourceConstraints/mco:MD_Constraints/mco:releasability/mco:MD_Releasability
Release Constraints	Information about resource release constraints.	ISO-1 /mdb:MD_Metadata/mdb:identificationInfo/mri:MD_DataIdentification/mri:resourceConstraints/mco:MD_Constraints/mco:releasability/mco:MD_Releasability

xPath Note: The xPaths included in this table use several wildcards. // means any path, so //gmd:CI_ResponsibleParty indicates a gmd:CI_ResponsibleParty anywhere in an XML file. /*/ indicates a single level with several possible elements. This usually indicates one of several concrete realizations of an abstract object. For example /*/gmd:identificationInfo could be gmd:MD_Metadata/gmd:identificationInfo or gmi:MI_Metadata/gmd:identificationInfo and gmd:identificationInfo//*/gmd:descriptiveKeywords could be gmd:identificationInfo/gmd:MD_DataIdentification/gmd:descriptiveKeywords or gmd:identificationInfo/srv:SV_ServiceIdentification/gmd:descriptiveKeywords. Fit: The fit of the dialect path with the concept is estimated on a scale of 1 = excellent two-way fit, 2 = one-way fit or some other problem, 3 - extension required.

Metadata Implementation