search

SAA-SDT / eac-cpf-schema

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

@standardDateTime #241

Closed SJagodzinski closed 2 years ago

SJagodzinski commented 3 years ago

Standard Date and Time

Creator of issue

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

Related issues / documents

@standardDate, @standardDateTime: remove regex pattern #33

EAD3 Reconciliation

Summary: An ISO 8601-compliant form of the date or date and time of a specific maintenance event expressed in <eventdatetime>. For example, 2009-12-31, 2009, 2009-12, 2009-12-31T23:59:59. Available only in <eventdatetime>.

Data Type: Constrained to the following patterns: YYYY-MM-DD, YYYY-MM, YYYY, or YYYY-MM-DDThh:mm:ss [with optional timezone offset from UTC in the form of [+|-][hh:mm], or "Z" to indicate the dateTime is UTC. No timezone implies the dateTime is UTC.]

Context

Summary: The date or date and time represented in a standard form for computer processing.

Description and Usage: The standardDateTime may occur on <eventDateTime>. The value of standardDateTime provides a standard form of the date or date and time expressed in the <eventDateTime> that can be used in computer processing. For example, using both the value in <eventType> and standardDateTime, all EAC-CPF instances "revised" on a particular date can be identified.

Data Type: Union of the XML Schema Datatypes date, gYear, gYearMonth, and dateTime. The following are all valid patterns: 2009-12-31, 2009, 2009-12, 2009-12-31T23:59:59.

Solution documentation:

Rephrasing Summary and Description and Usage needed

May occur within: <eventDateTime> Data Type: Constrained to the following patterns: YYYY-MM-DD, YYYY-MM, YYYY, or YYYY-MM-DDThh:mm:ss [with optional timezone offset from UTC in the form of [+|-][hh:mm], or "Z" to indicate the dateTime is UTC. No timezone implies the dateTime is UTC.]

Example encoding

ailie-s commented 3 years ago

Tag Library Text:

Summary: An ISO 8601-compliant form of the date or date and time of a specific maintenance event expressed in <eventDateTime>. For example, 2009-12-31, 2009, 2009-12, 2009-12-31T23:59:59. Available only in <eventDateTime> Data Type: Constrained to the following patterns: YYYY-MM-DD, YYYY-MM, YYYY, or YYYY-MM-DDThh:mm:ss [with optional timezone offset from UTC in the form of [+|-][hh:mm], or "Z" to indicate the dateTime is UTC. No timezone implies the dateTime is UTC.]

kerstarno commented 3 years ago

Tested as part of Schema Team's schema testing:

The above applies to both schemas, RNG and XSD.

kerstarno commented 3 years ago

Reviewing elements that are currently mandatory in order to create a minimal EAC-CPF instance, the Schema Team suggested to make @standardDateTime mandatory along with restricting <eventDateTime> from having text (see #93). This decision is currently pending.

SJagodzinski commented 3 years ago

No, this solution forces users for automatic creation of EAC-CPF files or at least of the @standardDateTime value. This produces new hurdles which we want to avoid by simplifying the schema.

kerstarno commented 3 years ago

With the decision on <eventDateTime> (#93) with regard to keeping the element mandatory and allowing for text, but leaving the attribute optional, the attribute @standardDateTime is ready.