[Major revision] Updates to date elements

[kerstarno]

Provide a general summary of the issue in the Title above. Delete the part of the issue template that does not apply depending on whether you describe a change to an existing element / attribute or the addition of a new one.

Creator of issue

State your name, organisation and ways to reach you. Name: Kerstin Arnold Organisation: Archives Portal Europe Foundation, Working Group on Standards Email: standards@archivesportaleurope.net GitHub username (if applicable): @kerstarno

Changes to existing element / attribute

Give the current name of the element / attribute. Include the tag name and the full name. Name: <date>, <dateRange>, <fromDate>, <toDate>, <dateSet>

Change in context

List all parent elements to which the element / attribute should be added. Furthermore, list all parent elements from which the element / attribute should be removed.

• <date> as sub-element of <repositorfound> and <repositorsup> will not be available anymore as both these elements will be removed from EAG 3.0; instead, this date information will be encoded in <existDates> (see #125).
• <date> and <dateRange> as sub-elements of <localControl> will not be available anymore as this element will be removed from EAG 3.0 without replacement (see #110).
• One of <date>, <dateRange> or <dateSet> will remain required within <useDates> (see #124), while one of these will remain optional within <holdings> and in <relation> (which replaces <resourceRelation> and <eagRelation>, see #107).
• Furthermore, one of <date>, <dateRange> and <dateSet> will be required within the newly added <existDates> (see #125) and in <chronItem> within <biogHist> (see #126) and one of these will be optional within the new elements <otherRepositoryType> (see #86), <place> (see #123), <function>, <legalStatus>, and <mandate> (see #85).

Change in content model (elements)

List all sub-elements and attributes that should be removed from or added to the element's content model.

date

• <date> can have content and allows for the attributes @audience with the values "external" and "internal" (0), @id (0), @languageOfElement (0) - replaces @xml:lang, @scriptOfElement (0), @target(0), @localType (0), @localTypeDeclarationReference (0), @calendar (0) - data type NMTOKEN, @certainty (0) - data type NMTOKEN, @era (0) - data type NMTOKEN, @notAfter (0), @notBefore (0), @standardDate (0), @conventionDeclarationReference (0), @maintenanceEventReference (0), @sourceReference (0) - replaces @source, @status with the value "unknown" (0), and an option to include attributes from any other namespace.
  • The restriction for the attributes @standardDate, @notBefore, and @notAfter only to include dates before 31 December 9999 (see https://github.com/ArchivesPortalEuropeFoundation/EAG2012/issues/40) is lifted completely. All three attributes have the data type NMTOKEN instead.

    dateRange

• <dateRange> requires either <fromDate> or <toDate> to be present, with <fromDate> required to be mentioned first, if both elements exist. This is a relaxation compared to EAG 2012, where both elements were required. <dateRange> allows for the attributes @audience with the values "external" and "internal" (0), @id (0), @languageOfElement (0), @scriptOfElement (0), @target(0), @localType (0), @localTypeDeclarationReference (0), @conventionDeclarationReference (0), @maintenanceEventReference (0), @sourceReference (0), and an option to include attributes from any other namespace.

  fromDate

• <fromDate> can have content and allows for the attributes @audience with the values "external" and "internal" (0), @id (0), @languageOfElement (0), @scriptOfElement (0), @target(0), @calendar (0) - data type NMTOKEN, @certainty (0) - data type NMTOKEN, @era (0) - data type NMTOKEN, @notAfter (0), @notBefore (0), @standardDate (0), @conventionDeclarationReference (0), @maintenanceEventReference (0), @sourceReference (0) - replaces @source, @status with the value "unknown" (0), and an option to include attributes from any other namespace.
  • The restriction for the attributes @standardDate, @notBefore, and @notAfter only to include dates before 31 December 9999 (see https://github.com/ArchivesPortalEuropeFoundation/EAG2012/issues/40) is lifted completely. All three attributes have the data type NMTOKEN instead.

    toDate

• <toDate> can have content and allows for the attributes @audience with the values "external" and "internal" (0), @id (0), @languageOfElement (0), @scriptOfElement (0), @target(0), @calendar (0) - data type NMTOKEN, @certainty (0) - data type NMTOKEN, @era (0) - data type NMTOKEN, @notAfter (0), @notBefore (0), @standardDate (0), @conventionDeclarationReference (0), @maintenanceEventReference (0), @sourceReference (0) - replaces @source, @status with the value "unknown" and "ongoing" (0), and an option to include attributes from any other namespace.
  • The restriction for the attributes @standardDate, @notBefore, and @notAfter only to include dates before 31 December 9999 (see https://github.com/ArchivesPortalEuropeFoundation/EAG2012/issues/40) is lifted completely. All three attributes have the data type NMTOKEN instead.

    dateSet

• <dateSet> still requires at least two of <date> and/or <dateRange> to be present, i.e. either two <date>-s or two <dateRange>-s or one <date> and one <dateRange> with both sub-elements being repeatable. Furthermore, <dateSet> now allows for the attributes @audience with the values "external" and "internal" (0), @id (0), @languageOfElement (0), @scriptOfElement (0), @target(0), @localType (0), @localTypeDeclarationReference (0), @conventionDeclarationReference (0), @maintenanceEventReference (0), @sourceReference (0), and an option to include attributes from any other namespace.

[kerstarno]

For conversion within the date elements themselves, the main aspects to keep in mind are:

• The value of @xml:lang of <date> in EAG 2012 is moved into @languageOfElement of <date> in EAG 3.0.
• If <date>, <fromDate> or <toDate> have a @source attribute, the value of this attribute is moved into a new <source><reference> within <sources>, a new @id is added to this new <source> element, and a @sourceReference is added to <date>, <fromDate> or <toDate> respectively in order to point to that @id.
• For all other aspects mentioned above, EAG 2012 was more restrictive than EAG 3.0 will be, so that a 1-to-1 conversion will suffice.

E.g. the current encoding:

<useDates>
  <dateSet>
    <date standardDate="1917" notBefore="1915" notAfter="1919" xml:lang="[language for date] localType="[localType for date]" source="[source for date]">1917</date>
    <dateRange localType="[localType of dateRange]">
      <fromDate standardDate="1919" notBefore="1917" notAfter="1921" source="[source for fromDate]">1919</fromDate>
      <toDate standardDate="1945" notBefore="1943" notAfter="1947" source="[source for toDate]">1945</toDate>
    </dateRange>
  </dateSet>
</useDates>

becomes:

<control>
  [...]
  <sources>
    <source id="source1">
      <reference>source for date</reference>
    </source>
    <source id="source2">
      <reference>source for fromDate</reference>
    </source>
    <source id="source3">
      <reference>source for toDate</reference>
    </source>
  </sources>
  [...]
</control>
[...]
<useDates>
  <dateSet>
    <date standardDate="1917" notBefore="1915" notAfter="1919" languageOfElement="[language for date] localType="[localType for date]" sourceReference="#source1">1917</date>
     <dateRange localType="[localType of dateRange]">
       <fromDate standardDate="1919" notBefore="1917" notAfter="1921" sourceReference="#source2">1919</fromDate>
       <toDate standardDate="1945" notBefore="1943" notAfter="1947" sourceReference="#source3">1945</toDate>
     </dateRange>
  </dateSet>
</useDates>