search

SAA-SDT / eac-cpf-schema

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

<event> #225

Closed SJagodzinski closed 2 years ago

SJagodzinski commented 3 years ago

Event

Creator of issue

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

Related issues / documents

EAD3 Reconciliation

May contain: [text], abbr, corpname, date, emph, expan, famname, footnote, foreign, function, genreform, geogname, lb, list, name, num, occupation, persname, ptr, quote, ref, subject, title May occur within: chronitem, chronitemset Attributes: altrender, audience, id, lang, localtype, script - all optional Availability: Within : Optional, not repeatable Within : Required, repeatable

Context

Summary: An element used to encode an event associated with a date and, optionally, a place within a structured chronology. May contain: [text] May occur within: chronItem Attributes: @localType, @xml:id, @xml:lang - all optional Availability: Mandatory, Non-repeatable

Solution documentation: agreed solution for TL and guidelines

May contain: [text], <reference> (0..n), <span> (0..n) May occur within: <chronItem>, <chronItemSet> Attributes: @audience - optional (values limited to: external, internal) @conventationDeclarationReference - optional @id - optional @languageOfElement - optional @localType - optional @localTypeDeclarationReference - optional @maintenanceEventReference - optional @scriptOfElement - optional @sourceReference - optional @valueURI - optional @vocabularySource - optional @vocabularySourceURI - optional Availability: Mandatory, Non-repeatable

Example encoding

<chronItem>
 <dateRange>
  <fromDate>start date for a list item</fromDate>
   <toDate>end date for a list item</toDate>
  </dateRange>
  <event audience="external" conventionDeclarationReference="conventiondeclaration1" id="event1" languageOfElement="en" localType="localevent1" localTypeDeclarationReference="localTypeDeclaration1" maintenanceEventReference="maintenancevent1" scriptOfElement="lat" sourceReference="source1" valueURI="http://eventsvocabulary/event" vocabularySource="EV" vocabularySourceURI="http://eventsvocabulary/">event of this chronology list item</event>
</chronItem>
ailie-s commented 3 years ago

Tag Library Text:

Summary: A child element of <chronItem> or <chronItemSet> that is used to encode an event associated with a date, and optionally a place, within a structured chronology. May contain: [text], reference (0..n), span (0..n) May occur within: chronItem, chronItemSet Attributes: @audience - optional (values limited to: external, internal) @conventationDeclarationReference - optional @id - optional @languageOfElement - optional @localType - optional @localTypeDeclarationReference - optional @maintenanceEventReference - optional @scriptOfElement - optional @sourceReference - optional @valueURI - optional @vocabularySource - optional @vocabularySourceURI - optional @target - optional Description and Usage: <event> contains discursive text identifying the event described by the <chronItem> or <chronItemSet>. <chronItem> must include one of either <event> or <chronItemSet>. <chronItemSet> must include one or more <event>. Every <event> must have date(s) (<date>, <dateRange> or <dateSet>) associated with it. It may also have optional <placeName> element associated with it. Availability: Within <chronItem>: One of <chronItemSet> or <event> required, not repeatable. Within <chronItemSet>: required, repeatable.

fordmadox commented 3 years ago

If we add "reference" here (and "item", etc.), should we also add "span"? In principle, I'd think that span should be available in all of the same mixed-content locations that reference is available.

kerstarno commented 3 years ago

It's not specifically put down in the minutes, but I made this suggestion (adding <span> to <event) as part of my general suggestion of having <reference> with <event>. This is not only to align the same mixed-content locations that make <reference> available within the EAC-CPF context, but will also make alignment with EAD easier in the long run.

fordmadox commented 3 years ago

Wherever "reference" is allowed in mixed content, I should say, then "span" should be allowed too :smile:

SJagodzinski commented 3 years ago

Confirmed, I added <span> together with <reference> in the issue above.

kerstarno commented 3 years ago

Tested as part of the Schema Team's schema testing:

The above applies to both schemas, RNG and XSD.

The element is ready.