Create and update TEI XML files (group 1) 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 and shared attributes. Mark your progress by checking the check boxes of those TEI XML files that are already created/updated.

• [x] audienceEncoding.xml

• [x] contactLineTypeEncoding.xml

• [x] coverageEncoding.xml

• [x] descriptionOfComponentsTypeEncoding.xml

• [x] detailLevelEncoding.xml

• [x] levelEncoding.xml

• [x] maintenanceEventTypeEncoding.xml

• [x] maintenanceStatusEncoding.xml

• [x] physDescStructuredTypeEncoding.xml

• [x] publicationStatusEncoding.xml

• [x] statusEncoding.xml

• [x] unitDateTypeEncoding.xml

• [x] conventionDeclarationReference.xml

• [x] countryEncoding.xml

• [x] dateEncoding.xml

• [x] id.xml

• [x] languageEncoding.xml

• [x] languageOfElement.xml

• [x] localType.xml

• [x] localTypeDeclarationReference.xml

• [x] maintenanceEventReference.xml

• [x] repositoryEncoding.xml

• [x] scriptEncoding.xml

• [x] scriptOfElement.xml

• [x] sourceReference.xml

• [x] target.xml

[deletedname]

@karinbredenberg for levelEncoding, should there be language about it being specific to EAD?

[karinbredenberg]

@karinbredenberg for levelEncoding, should there be language about it being specific to EAD?

@deletedname since its just for EAD that is not needed, it will only be present in the EAD TL.

[deletedname]

@karinbredenberg for id, I'm wondering about the wording of "somewhere else" and "other resources" in the description (pasted below), because I can see that being interpreted as in a separate xml record.

An identifier that must be unique within the current document and is used to name the element so that it can be referred to, or referenced from, somewhere else. This facilitates building links between the element and other resources.

suggested edit, I know it's redundant:

...so that it can be referred to, or referenced from, somewhere else in the record. This facilitates building links between the element and other resources within the current document.

does anyone else feel this needs to be more explicit?

[karinbredenberg]

Go ahead!

[kerstarno]

TEI XML files listed in this issue are considered ready for implementation in a first draft EAD 4.0 Tag Library (pending the fixing of potential encoding issues which might be found during the process of creating the Tag Library PDF).

[fordmadox]

@kerstarno : just a note for these files, and almost all the rest, the "xml:id" attribute in the wrapper div will also need to be updated from what was in the template. e.g. xml:id="attr-attributeName" for https://github.com/SAA-SDT/EAS-TagLibraries/blob/ead4/tei/ead4/en/attr-audienceEncoding.xml should be something like xml:id="attr-audienceEncoding".

[fordmadox]

Looks like Alex took care of the above with f9f5bde. Thanks!