Difference between revisions of "MD SecurityConstraints"

From Earth Science Information Partners (ESIP)
 
Line 62: Line 62:
 
<tr>
 
<tr>
 
<td bgcolor="FFFF99">7</td>
 
<td bgcolor="FFFF99">7</td>
<td bgcolor="FFFF99">[[ISO_19115_and_19115-2_CodeList_Dictionaries#MD_ClassificationCode|mco:classification]]</td>
+
<td bgcolor="FFFF99">[[ISO_19115-3_Codelists#MD_ClassificationCode|mco:classification]]</td>
 
<td bgcolor="FFFF99">1</td>
 
<td bgcolor="FFFF99">1</td>
<td bgcolor="FFFF99">[[ISO_19115_and_19115-2_CodeList_Dictionaries#MD_ClassificationCode|mco:MD_ClassificationCode]]</td>
+
<td bgcolor="FFFF99">[[ISO_19115-3_Codelists#MD_ClassificationCode|mco:MD_ClassificationCode]]</td>
 
<td></td>
 
<td></td>
 
<td><i></i></td>
 
<td><i></i></td>

Latest revision as of 08:12, September 12, 2017

mco:MD_SecurityConstraints

MD_Constraints
Elements Domain Definition and Recommended Practice Examples
1 mco:useLimitation 0..* gco:CharacterString limitation affecting the fitness for use of the resource or metadata. Example, "not to be used for navigation"
2 mco:constraintApplicationScope 0..1 mcc:MD_Scope Spatial and temporal extent of the application of the constraint restrictions
3 mco:graphic 0..* mcc:MD_BrowseGraphic graphic / symbol indicating the constraint.
4 mco:reference 0..* cit:CI_Citation citation/URL for the limitation or constraint, e.g. copyright statement, license agreement, etc
5 mco:releasability 0..1 mco:MD_Releasability information concerning the parties to whom the resource can or cannot be released and the party responsible for determining the releasibility
6 mco:responsibleParty 0..* cit:CI_Responsibility party responsible for the resource constraints
7 mco:classification 1 mco:MD_ClassificationCode
8 mco:userNote 0..1 gco:CharacterString
9 mco:classificationSystem 0..1 gco:CharacterString
10 mco:handlingDescription 0..1 gco:CharacterString




ISO Legend

Possible Parent Elements

ESIP-logo-tag sm-H.jpg

Please contribute!