<dateset> Date Set

<dateset> is a new element in EAD3 used to as a wrapper to encode complex dates that can’t be put in a <datesingle> or <daterange>. It may encode multiple instances of either or both of them. It may be used within <chronitem>, <relation>, and <unitdatestructured>.


  • @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.”
  • @id – not required. Creates an ID for element. Can be used for linking.
  • @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.
  • @localtype – not required. This attribute may be used within a number of elements. Its use and values are not defined by the schema and may be defined locally. It may be used in this case to create a more specific characterization of the date set.
  • @script – not required. Four-letter code that indicates the script in which the element’s contents were written. It should come from ISO 15924.

Child Elements

<dateset> may contain <datesingle> and <daterange> to designate the variety of dates represented. It must contain at least two child elements, otherwise either the <datesingle> or <daterange> element should be used instead. It may not contain any text.


<unitdatestructured unitdatetype="inclusive">
      <fromdate standarddate="1978">1978</fromdate>
      <todate standarddate="1982">1983</todate>
    <datesingle standarddate="1985">1985</datesingle>
      <fromdate standarddate="1987">1987</fromdate>
      <todate standarddate="2020">2020</todate>

EAD3 Tag Library Entry

View the official tag library entry for <dateset>