Review the use of the new element <formattingExtension> also for EAC-CPF; here: encoding of chronological lists

kerstarno commented 1 year ago

Creator of issue

Kerstin Arnold
EAD team lead, TS-EAS
@kerstarno
kerstin.arnold@archivesportaleurope.net

The issue relates to

[ ] EAC-CPF schema issue
[ ] EAC-CPF Tag Library issue
[x] EAD schema issue
[x] EAD Tag Library issue
[ ] Schema issue
[ ] Tag Library issue
[ ] Suggestions for all schemas
[ ] Suggestions for all Tag Libraries
[ ] Other

Wanted change/feature

Text: The encoding of chronological lists needs to be aligned again across both EAS.

Note for working on and testing this issue: When the schema changes are done in development branch, please mark the tasks on the highest levels of the list (printed in bold) by ticking the box. When the changes have been tested successfully, please mark the tasks on the lowest level of the list.

[x] <chronList>
- [ ] Apply camelCase spelling to <chronList> and its required and repeatable sub-element <chronItem>
- [ ] Remove <head> and <listhead>
- [ ] Adapt @audience
- [ ] Add @target
- [ ] Rename @lang and @script to @languageOfElement and @scriptOfElement respectively
- [ ] Apply camelCase spelling to @localType>
- [ ] Add @localTypeDeclarationReference
- [ ] Add @conventionDeclarationReference, @mainetancenEventReference, and @sourceReference
- [ ] Add an option to include attributes from any other namespace
[x] <chronItem>
- [ ] Apply camelCase spelling also to sub-elements <dateRange>, <dateSet>, and <chronItemSet>
- [ ] Replace <datesingle> with <date> (see #4)
- [ ] Replace <geogname> with <place> (optional, not repeatable, see #42) and put it after <event>
- [ ] Add <reference> as optional and repeatable (see #40)
- [ ] Adapt @audience
- [ ] Add @target
- [ ] Rename @lang and @script to @languageOfElement and @scriptOfElement respectively
- [ ] Apply camelCase spelling to @localType>
- [ ] Add @localTypeDeclarationReference
- [ ] Add @conventionDeclarationReference, @mainetancenEventReference, and @sourceReference
- [ ] Add an option to include attributes from any other namespace
[x] <event>
- [ ] Rename <ref> to <reference>
- [ ] Add <span> (as optional and repeatable)
- [ ] Adapt @audience
- [ ] Add @target
- [ ] Rename @lang and @scriptto @languageOfElement and @scriptOfElement respectively
- [ ] Add @conventionDeclarationReference, @maintenanceEventReference, and @sourceReference
- [ ] Add @localTypeDeclarationReference
- [ ] Add @valueURI, @vocabularySource, and @vocabularySourceURI
- [ ] Add an option to include attributes from any other namespace
[x] <chronItemSet>
- [ ] Replace <geogname> with <place> (optional, repeatable, see #42) and put it after <event>
- [ ] Add <reference> as optional and repeatable (see #40)
- [ ] Adapt @audience
- [ ] Add @target
- [ ] Rename @lang and @script to @languageOfElement and @scriptOfElement respectively
- [ ] Add @conventionDeclarationReference, @mainetancenEventReference, and @sourceReference
- [ ] Add an option to include attributes from any other namespace

kerstarno commented 11 months ago

Needs another look in light of https://github.com/SAA-SDT/eas-schemas/issues/62

fordmadox commented 11 months ago

Do lists get superseded by the "formattingExtention" element? If not, this is ready for testing. If so, then I think we just need a list of available XHTML elements to permit in that new wrapper (if we're going to validate that extension?).

kerstarno commented 10 months ago

With the suggested introduction of the element <formattingExtension>, chronological lists indeed would not be part of the EAD 4.0 schema anymore. Instead, <formattingExtension> would allow for the encoding of lists by using the relevant XHTML namespace and elements (see #62 for details of suggested XHTML elements).

@marieelia - leaving this issue open as a review issue for EAC-CPF at a later stage as part of a future major revision.

MicheleCombs commented 10 months ago

I may be too late with this comment, or perhaps it’s already been discussed and addressed, but reading over all these changes it seems to me we are “genericizing” an awful lot of EAD. One of the nice things about EAD has always been that it was mostly self-contained (i.e., it had everything you needed, and you didn’t have to stress over multiple namespaces, and pulling in all kinds of other tag sets) and it was mostly self-explanatory (i.e., the element names actually meant what they were so it was easy to learn and to teach and to use). I feel like we’re getting away from that and I wonder if that’s a good thing. Are we (again) falling into the habit of privileging the automated/database approach, and as a side effect making it harder for places that hand-encode their finding aids?

Anyway, just a thought.

Michele

From: Kerstin Arnold @.> Sent: Monday, January 8, 2024 7:31 AM To: SAA-SDT/eas-schemas @.> Cc: Subscribed @.***> Subject: Re: [SAA-SDT/eas-schemas] Review the use of the new element also for EAC-CPF; here: encoding of chronological lists (Issue #56)

With the suggested introduction of the element , chronological lists indeed would not be part of the EAD 4.0 schema anymore. Instead, would allow for the encoding of lists by using the relevant XHTML namespace and elements (see #62https://github.com/SAA-SDT/eas-schemas/issues/62 for details of suggested XHTML elements).

@marieeliahttps://github.com/marieelia - leaving this issue open as a review issue for EAC-CPF at a later stage as part of a future major revision.

— Reply to this email directly, view it on GitHubhttps://github.com/SAA-SDT/eas-schemas/issues/56#issuecomment-1880917639, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAOWWY2MU7M7PTAPQFZLX3LYNPRG3AVCNFSM6AAAAAA2VMQVOWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBQHEYTONRTHE. You are receiving this because you are subscribed to this thread.Message ID: @.**@.>>

SAA-SDT / eas-schemas