instantiationRelationType describes the relation between the instantiation being described and another instantiation.

Best practice: The instantiations may be related in that they are different discrete parts of a single intellectual unit, they may be generationally related, one may be a derivative of another, they may be different versions.

instantiationRelationTypecan only be contained by instantiationRelation.

Usage: required within instantiationRelation, not repeatable.

Attributes

• source – optional. The source attribute provides the name of the authority used to declare the value of the element. Different elements will use the source attribute slightly differently.  For example, identifier source (required) should be the name of the organization, institution, system or namespace that the identifier came from, such as “PBS NOLA Code” or an institutional database identifier.  For other elements, this might be the name of a controlled vocabulary, namespace or authority list, such as Library of Congress Subject Headings.  We recommend a consistent and human readable use.
• ref – optional. The ref attribute is used to supply a source’s URI for the value of the element. Attribute ref can be used to point to a term in a controlled vocabulary, or a URI associated with a source.
• version – optional. The version attribute identifies any version information about the authority or convention used to express data of this element.
• annotation – optional. The annotation attribute includes narrative information intended to clarify the nature of data used in the element. This attribute be used as a notes field to include any additional information about the element or associated attributes

Subelements

instantiationRelationType contains no subelements.

Controlled Vocabularies

PBCore relationType (recommended)
Dublin Core RDF Schema Declaration of Relation Types

Examples

Submit any issues or suggested changes for future schema iterations by creating a ticket in our Github repository.