ICSM ISO19115-1 Metadata Best Practice Guide

Resource Other Constraints ★★★★

The presence (or at times absence) of constraints (other than those of legal of security nature) on a spatial resource is important to document. Potential users need to be informed of rights, restrictions and responsibilities that apply to the use of such resources. These include *use limitations and releasability constraint information.*

   
Element Name resourceConstraints
Parent MD_Metadata.identificationInfo>MD_Identification.resourceConstraints
Class/Type MD_Constraints
Governance Agency
Purpose Resource use
Audience machine resource - ⭑
  general - ⭑ ⭑ ⭑ ⭑ ⭑
  resource manager - ⭑ ⭑ ⭑ ⭑
  specialist - ⭑ ⭑ ⭑
Metadata type administrative
ICSM Level of Agreement ⭑ ⭑ ⭑

Definition -

Rights, restrictions, and responsibilities for the access and use of this cited resource. While these may optionally be of subtypes legal (MD_LegalConstraints) or security (MD_SecurityConstraints) there are other types of constraints to consider that exist under the more general class MD_Constraints including *useLimitations and releasability restrictions*

ISO Obligation

ICSM Best Practice Recommendations

Discussion

Almost all spatial resources carry some rights, restrictions and responsibility regarding their access and use. These may be legal, security or other. These must be recorded and shared with existing and potential users. Each agency needs to develop consistant guidance on the use of such statements and share clear understanding of their meaning. This is often done by reference to a external body that manages the definitions of the constraints applied.

Recommendations

Therefore - for users to understand the administrative constraints applied to a cited resource, the details of these constraints, together with sufficient information and linkages to provide access to further information as to the deeper meaning and implications of such constraints, needs to be capture in the metadata about the resource.

Crosswalk considerations

ISO19139

See guidance provided in MD_Constraints

RIF-CS

Maps to the agregate Rights/@accessRights

Also Consider

Examples

XML

<mdb:MD_Metadata>
....
 <mdb:identificationInfo>
  <mri:MD_DataIdentification>
  ....
    <mri:resourceConstraints>
      <mco:MD_Constraints>
        <mco:useLimitation>
         <gco:CharacterString>Not to be used for measurement</gco:CharacterString>
        </mco:useLimitation>
        <mco:reference>
         <cit:CI_Citation>
           <cit:title>
            <gco:CharacterString>My own list of constraints
            </gco:CharacterString>
           </cit:title>
         </cit:CI_Citation>
        </mco:reference>
        <mco:releasability>
         <mco:MD_Releasability>
           <mco:addressee>
            <cit:CI_Responsibility>
              <cit:role>
               <cit:CI_RoleCode 
               codeList="https://schemas.isotc211.org/19115
               /resources/Codelist/cat/codelists.xml#CI_RoleCode"
               codeListValue="resourceProvider"/>
              </cit:role>
            </cit:CI_Responsibility>
           </mco:addressee>
           <mco:statement>
            <gco:CharacterString>not useful to others
            </gco:CharacterString>
           </mco:statement>
         </mco:MD_Releasability>
        </mco:releasability>
        <mco:responsibleParty>
         <cit:CI_Responsibility>
           <cit:role>
            <cit:CI_RoleCode 
            codeList="https://schemas.isotc211.org/19115/resources
            /Codelist/cat/codelists.xml#CI_RoleCode" 
            codeListValue="publisher"/>
           </cit:role>
           <cit:party>
            <cit:CI_Organisation>
              <cit:name>
               <gco:CharacterString>OpenWork Ltd
               </gco:CharacterString>
              </cit:name>
              <cit:contactInfo>
               <cit:CI_Contact>
                 <cit:address>
                  <cit:CI_Address>
                    <cit:electronicMailAddress>
                     <gco:CharacterString>info@openwork.nz
                     </gco:CharacterString>
                    </cit:electronicMailAddress>
                  </cit:CI_Address>
                 </cit:address>
               </cit:CI_Contact>
              </cit:contactInfo>
            </cit:CI_Organisation>
           </cit:party>
         </cit:CI_Responsibility>
        </mco:responsibleParty>
      </mco:MD_Constraints>
     </mri:resourceConstraints>
   ....
   </mri:MD_DataIdentification>
 </mdb:identificationInfo>
....
</mdb:MD_Metadata>

\pagebreak

UML diagrams

Recommended elements highlighted in yellow

constraints

\pagebreak