search

SAA-SDT / eac-cpf-schema

https://eac.staatsbibliothek-berlin.de/
10 stars 4 forks source link

@dateEncoding #124

Closed SJagodzinski closed 2 years ago

SJagodzinski commented 4 years ago

Date Encoding

Add optional attribute @dateEncoding with closed lists of predefined values to <control>.

Availability: optional Values: iso8601, otherDateEncoding May occur within: <control>

Creator of issue

  1. Silke Jagodzinski
  2. TS-EAS: EAC-CPF subgroup
  3. silkejagodzinski@gmail.com

Related issues / documents

20200128_SharedSchemaOverview <control> #81

EAD3 Reconciliation

Decision from EAC-EAD-Schema joint meeting, 28 Jan 2020, due to alignment of in both standards.

Summary: The authoritative source or rules for values provided in normal in <date> and <unitdate>. If the value "otherdateencoding" is selected an alternate code list should be specified in <conventiondeclaration>.

Values: iso8601, otherdateencoding

Context

EAD3 specific attribute.

Solution documentation

Summary: The authoritative source or rules for values provided in @standardDate in <date>, <fromDate> and <toDate>. If the value "otherDateEncoding" is selected an alternate code list should be specified in <conventionDeclaration>.

Values: iso8601, otherDateEncoding

May occur within: <control>

Example encoding

<eac>
<control audience="external" countryEncoding="iso3166-1" dateEncoding="iso8601" id="control1" languageEncoding="iso639-1" languageOfElement="en" repositoryEncoding="iso15511" scriptEncoding="iso15924" scriptOfElement="lat">
  <recordId>records identifier</recordId>
  <maintenanceStatus value="new"/>
  <maintenanceAgency>[...]</maintenanceAgency>
  <maintenanceHistory>[...] >/maintenanceHistory>
 </control>
</eac>
kerstarno commented 3 years ago

Tested as part of Schema Team's schema testing:

The above applies for both schemas, RNG and XSD.

The attribute is ready.

kerstarno commented 3 years ago

@fordmadox With regard to Schematron: I'm assuming, the EAD3 Schematron currently only includes checks for ISO 8601, as we wouldn't know what other date encoding people might want to use instead of this. But I was wondering, if Schematron documentation could include something about what to do when using "otherDateEncoding" as the value here? Not necessarily for Schematron only, but also in terms of e.g. a recommendation as to where to define such other date codes (e.g. <localControl>?) next to mentioning the standard itself in <conventionDeclaration>.

fordmadox commented 3 years ago

Just a note that I do not think that "iso8601" is sufficient as a controlled value option. Version 2019 of ISO-8601 is very different from version 2014, etc.

karinbredenberg commented 3 years ago

In the EAC-CPF meeting on the (2021-08-06) we concluded that this fall into the Design principles (principle 7) an suggest that the principle gets an addition of links to the used versions and with this hands this over to the Schema team, @fordmadox .