The SEDRIS Data Representation Model
APPENDIX B - Constraints
Mandatory Metadata

Definition

In the following meta-data classes, the following information shall be provided. In the case of string fields, the strings may not be empty.

CLASS MANDATORY FIELDS
<Access> security's classification shall be a non-empty string
<Browse Media> name shall be a non-empty string

media_urn shall be a non-empty string in the form of a valid URN

<Citation> title shall be a non-empty string
originators shall be a non-empty string
<Description> abstract shall be a non-empty string
<Keywords> keyword_array shall be non-NULL

For each entry in keyword_array, the thesaurus shall be a non-empty string. To indicate that no thesaurus is applicable, the thesaurus field shall have the value "NONE".

For each entry in keyword_array, the keyword_list shall be a non-empty string, where keywords are separated by semicolons.

For any two entries in keyword_array, either the code fields or the thesaurus fields shall have different values.

<Point Of Contact> person_or_position shall be a non-empty string

organization shall be a non-empty string

address shall be a non-empty string

voice_phone shall be a non-empty string

email_address, if provided, shall be a comma-separated list of syntactically valid e-mail addresses

web_site, if specified, shall be a comma-separated list of syntactically valid URLs

<Process> description shall be a non-empty string
<Source> description shall be a non-empty string

Rationale

This is consistent with the [CSDGM] metadata standard which requires these fields and the ISO/DIS 19115 Metadata Standard which allows for these fields.

Example

  1. For <Point Of Contact>, web_site = SE_STRING_DEFAULT is valid, and web_site = { SE_LOCALE_DEFAULT, 21, "http://www.sedris.org" } is valid, but web_site = { SE_LOCALE_DEFAULT, 3, "N/A" } is not.

FAQs

No FAQs supplied.
Prev: LSR Transformation Components. Next: Model Reference Type Constraints. Up:Index.

Last updated: October 1, 2002 Copyright © 2002 SEDRIS™