MI Requirement
From Earth Science Information Partners (ESIP)
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
| Elements | Definition and Recommended Practice | Examples | ||
|---|---|---|---|---|
| 1 | citation | 0..* | Description: identification of reference or guidance material for the requirement shortName: reqRef | See CI_Citation |
| 2 | identifier | 1 | Description: unique name, or code, for the requirement shortName: reqId | See MD_Identifier |
| 3 | requestor | 1..* | Description: origin of requirement shortName: requestor | See CI_Responsibility |
| 4 | recipient | 1..* | Description: person(s), or body(ies), to recieve results of requirement shortName: recipient | See CI_Responsibility |
| 5 | priority | 1 | Description: relative ordered importance, or urgency, of the requirement shortName: reqPri | See ISO_19115_and_19115-2_CodeList_Dictionaries#MI_PriorityCode |
| 6 | requestedDate | 1 | Description: required or preferred acquisition date and time shortName: reqDate | See MI_RequestedDate |
| 7 | expiryDate | 1 | Description: date and time after which collection is no longer valid shortName: reqExpire | See DateTime |
| 8 | satisifiedPlan | 0..* | plan that identifies solution to satisfy the requirement | See MI_Plan |
