ICSM ISO19115-1 Metadata Best Practice Guide

class - MD_Constraints

When constraints are palced on a spatial resource or its metadata, it is important to document these.. Potential users need to be informed of rights, restricutions and responsibilities (or lack thereof) that apply to the use of such resources.

Definition

restrictions on the access and use of a resource or metadata.

ISO Associations (May be found in)

Attributes -

Associated Classes, Codelists and Unions

MD_RestrictionCode - codelist

The name of the handling restrictions on the resource

MD_Scope - class

See MD_Scope

MD_BrowseGraphic - class

Generalisations of MD_Constraints

MD_Constraints may be expressed as:

Discussion

Information about constraints on the access and use of a resource or its metadata is of high importance to document as this information strongly impacts on the usability of the resource to the user. Constraints may be security (MD_SecurityConstraints), legal (MD_LegalConstraints) or other (MD_Constraints).

A restriction may be applicable to a particular aspect of the resource. In this case capture this scope in constraintApplicationScope using a value from MD_Scope

Outstanding Issues

Best Practice examples lacking There is a need to gain greater consensus as to the general use of MD_Constraints across its instances by the MDWG.

Distribution Constraints Currently there are no clear methods to apply different constraints to different distributions. This may be an ISO issue to address. We should develop use cases.

ICSM Best Practice Recommendations

Crosswalk considerations

ISO19139

\pagebreak

UML diagrams

Recommended elements highlighted in yellow

MD_Constraints

\pagebreak