<unitdatestructured> Structured Date of the Unit

<unitdatestructured> is a new element in EAD3 used to create machine-processable forms of the date elements. It takes advantage of the new structured date elements: <daterange>, <dateset>, and <datesingle>.

Attributes

  • @altrender – not required. Use if the content of the element should be displayed or printed differently than the rendering established in a style sheet for other occurrences of the element.
  • @audience – not required. Use to set whether the element’s contents will be visible to external users or to internal ones. Possible values are: “internal” and “external.”
  • @calendar – not required. Default value is “gregorian.”
  • @certainty – not required. May be used to indicate degree of precision used in dating—”circa,” “approximately,” “after,” etc.
  • @datechar – not required. May be used to characterize the nature of the dates, such as “creation” or “modification.”
  • @encodinganalog – not required. May contain information to map this tag to a particular element in another schema.
  • @era – not required. May be used to indicate the era in which the date falls. Default values is “ce” for common or “Christian” era.
  • @id – not required. Creates an ID for element. Can be used for linking.
  • @label – not required. This can be used when a meaningful display label for an element can’t be derived by the stylesheet from its name. It is available in all <did> subelements.
  • @lang – not required. Three-letter code that indicates the language in which the element’s contents were written. It should come from ISO 639-2b.
  • @script – not required. Four-letter code that indicates the script in which the element’s contents were written. It should come from ISO 15924.
  • @unitdatetype – not required. Use to record whether the unit dates are bulk or inclusive. Possible values: bulk, inclusive.

Child Elements

Each <unitdatestructured> element must contain one, and only one, of the following: <daterange>, <dateset>, and <datesingle>.

DACS

Use DACS Section 2.4, Date. Required. (or <unitdate> is) (DACS 2013, pp.24-27)

Example

<unitdatestructured unitdatetype="inclusive">
	<daterange>
		<fromdate notafter="0975">975</fromdate>
		<todate notafter="1050">1050</todate>
	</daterange>
</unitdatestructured>

EAD3 Tag Library Entry

View the official tag library entry for <unitdatestructured>