Mandatory Metadata

The SEDRIS Data Representation Model APPENDIX B - Constraints Mandatory Metadata

Definition

The following table lists meta-data classes. When these classes are instanced, at least the designated fields shall be populated.

CLASS	MANDATORY FIELDS
<Access>	The classification portion of the security field shall be a non-empty string. Consider an <Access> instance A. If A's access_constraints is set to SE_RESTR_CODE_OTHER_RESTRICTIONS. A's other_constraints field shall contain a non-empty string specifying what those other restrictions are. If A's use_constraints is set to SE_RESTR_CODE_OTHER_RESTRICTIONS. A's other_constraints field shall contain a non-empty string specifying what those other restrictions are.
<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
<Description>	abstract shall be a non-empty string. A <Description> instance that is a <Transmittal Root> component shall have at least one <Keywords> component and at least one <Responsible Party> component with role = SE_RESP_PTY_RL_CODE_POINT_OF_CONTACT.
<Keywords>	All the <Keywords> components of a given DRM object shall have distinct type codes. Within a given <Keywords> instance, the entries of the keyword_array shall be distinct.
<Lineage>	A <Lineage> instance shall specify at least one of the following: a <Process Step> component, a <Source> component, or a non-empty string within its statement field.
<Process Step>	The description field shall specify a non-empty string. The <Absolute Time> component shall have time_significance = SE_TIME_SIGNIF_OCCURRENCE. If the <Process Step> instance has <Responsible Party> components, each shall specify role = SE_RESP_PTY_RL_CODE_PROCESSOR.
<Responsible Party>	Each entry within contact_information. address. email_address shall specify a syntactically valid email address. contact_information. online_resource. linkage shall specify a syntactically valid URL. The locale of each SE_String field shall be specified using the same country code as that used by the contact_information. address, except that contact_information. address. email_address entries shall be syntactically valid email addresses (with locale values set accordingly). At least one of the following fields shall contain a non-empty string: individual_name, position_name, or organization_name.
<Source>	description shall be a non-empty string

Rationale

This is consistent with ISO 19115.

Example

No example supplied.

FAQs

No FAQs supplied.

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

Last updated: August 23, 2005

Copyright © 2005 SEDRIS™