Create and update TEI XML files (group 2) as part of creating a draft EAD 4.0 Tag Library

[kerstarno]

Creator of issue

1. Kerstin Arnold
2. TS-EAS member, EAD team lead
3. @kerstarno

The issue relates to

• [ ] EAC-CPF schema issue
• [ ] EAC-CPF Tag Library issue
• [ ] 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: Create and update the TEI XML files for the following EAD-specific elements and shared attributes and elements. Mark your progress by checking the check boxes of those TEI XML files that are already created/updated.

• [x] accruals.xml

• [x] appraisal.xml

• [x] arrangement.xml

• [x] custodHist.xml

• [x] filePlan.xml

• [x] formattingExtension.xml

• [x] otherDescriptiveInfo.xml

• [x] physicalOrTechnicalRequirements.xml

• [x] preferCite.xml

• [x] processInfo.xml

• [x] referringString.xml

• [x] scopeContent.xml

• [x] sourceOfAcquisition.xml

• [x] base.xml

• [x] biogHist.xml

• [x] descriptiveNote.xml

• [x] head.xml

• [x] href.xml

• [x] linkRole.xml

• [x] linkTitle.xml

• [x] p.xml

• [x] reference.xml

• [x] span.xml

• [x] style.xml

[kerstarno]

Couldn't find @erickcardosomx as a member of the SAA-SDT workspace, so tagging him here.

[fordmadox]

@alexduryee , @karinbredenberg , @kerstarno : I think I may have missed how we're providing differences with EAD and EAC in the current TL. in the examples that I've seen, it looks like 'type' is being supplied to paragraph elements. But that TEI element doesn't support that attribute, does it? See https://tei-c.org/release/doc/tei-p5-doc/en/html/ref-p.html. I'll likely go with a slightly different approach for now in my branch, to keep things valid according to TEI, but we can discuss before merging the two.

[karinbredenberg]

@fordmadox we are using our own TEI schema which isnt totally following TEI from the beginning so therefore we have done that solution.

When the elements/attributes are shared fingers crossed there is no need for differences.

[fordmadox]

Ohhh... I see now how that's handled in the transformation process (is our version of TEI defined anywhere so that the input can be validated?). Anyhow, I'll revert my branch to invalid TEI, in that case.

[fordmadox]

For my previous question: I see now that it is defined in this repository, but I don't think it's up to date with our current process. I'll hold off on updating that since I'm not sure how it's used, but that schema should likely include our use of 'type' in a few different areas not currently allowed. e.g. https://github.com/SAA-SDT/EAS-TagLibraries/blob/ead4/schema/tagLibrary_elementDesc.rng#L73

[fordmadox]

I was planning to use @subtype on the divs to keep everything nice and standard (TEI). Perhaps an option in the future, depending on how we add EAF, as well as support for generating PDF/UA output, etc.

[fordmadox]

I'm sure there are typos to fix, etc., but here's a pull request for a the few remaining updates needed from group 2: https://github.com/SAA-SDT/EAS-TagLibraries/pull/142