Closed kerstarno closed 1 month ago
Couldn't find Venkat as a member of the SAA-SDT workspace and there's more than one on GitHub, so just mentioning here that this is a shared assignment.
Hi @cartivist - thanks for the question re <title>
.
Its foreseen usage in EAD 4.0 is indeed focussing in on the context of <findAidDesc>
only, i.e. on titles identifying different instantiations of the finding aid as a resource.
Looking at the draft for
In the description, it could then be an option to give some more examples for the usage of <title>
within <findAidDesc>
, e.g. something like:
@localType
with <title>
to differentiate between the general title and a subtitle or the title of an overarching series. <part>
to break a title down into aspects such as an edition statement ("2nd edition").<title>
elements distinguished by their @localType
-s when describing e.g. a .pdf or a .docx instantiation of a finding aid to give the publication title for display on the one hand and the file title of the .pdf or the .docx file on the other hand.With regard to the "See also" section, I think you've actually described these alternatives fine. The only thing that I'd do differently is that I'd not mention <referringString>
here. While the note you have included isn't incorrect, it's more a note that is relevant in the context of moving from an EAD3 to an EAD 4.0 XML document. I would, however, not include it in the tag library when describing what <title>
is used for in EAD 4.0.
Hope that makes sense.
Thank you - now amended.
I am a little confused about https://github.com/SAA-SDT/EAS-TagLibraries/blob/ead4/tei/shared/en/attr-status.xml. Tried to incorporate the procedure outlined in the tutorial (thanks, all!), but would be grateful if this can be glanced at once - is this grammar consistent with the rest of the edits, @cartivist ?
For attributes like https://github.com/SAA-SDT/EAS-TagLibraries/blob/ead4/tei/shared/en/attr-calendar.xml, https://github.com/SAA-SDT/EAS-TagLibraries/blob/ead4/tei/shared/en/attr-certainty.xml, https://github.com/SAA-SDT/EAS-TagLibraries/blob/ead4/tei/shared/en/attr-era.xml @kerstarno : How are we incorporating 'potential future change in EAC-CPF (using data type token instead of NMTOKEN)' in the datatype? Hope the way I have done it is appropriate?
For attributes like https://github.com/SAA-SDT/EAS-TagLibraries/blob/ead4/tei/ead4/en/attr-descriptionOfComponentsType.xml, https://github.com/SAA-SDT/EAS-TagLibraries/blob/ead4/tei/ead4/en/attr-level.xml @kerstarno @cartivist Slightly confused about reading the EAD4 schema. Do I have it right that the datatype is token as per EAD4 schema? And do we retain any predefined values from previous schema? Thanks.
Hi @vns2 - thanks for your questions.
As for @calendar
, @certainty
, and @era
your edits are correct, i.e. having two <p>
within <div type="datatype">
and using one <p>
with @type="eac"
and the other with @type="ead"
to cater for the currently different data types.
For @status
I added one further sentence in the <p type="ead">
of the description in order to refer to the new attribute @statusEncoding
in <control>
. With this attribute, one can indicate if the "EASList" of values (essentially those values that were previously defined in the schema) are used or if an "otherStatusEncoding" approach is applied.
The same is true for @descriptionOfComponentsType
and @level
. @descriptionOfComponentsTypeEncoding
and @levelEncoding
in <control>
are meant to detail whether the EAS lists of values are used or if there are other value lists applied. With this, attributes like @otherlevel
from EAD3 are obsolete.
I have just updated https://github.com/SAA-SDT/EAS-TagLibraries/blob/ead4/tei/ead4/en/attr-status.xml, https://github.com/SAA-SDT/EAS-TagLibraries/blob/ead4/tei/ead4/en/attr-descriptionOfComponentsType.xml, and https://github.com/SAA-SDT/EAS-TagLibraries/blob/ead4/tei/ead4/en/attr-level.xml, if you'd want to have another look. Hope it makes sense. Please feel free to adapt the phrasing if necessary.
Thanks, @kerstarno Sorry about missing that earlier. I have made some small changes to the sentence. Should be okay, I think?
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).
Creator of issue
The issue relates to
Wanted change/feature
Text: Create and update the TEI XML files for the following EAD-specific attributes and elements as well as shared attributes . Mark your progress by checking the check boxes of those TEI XML files that are already created/updated.
[x] approximate.xml
[x] archDesc.xml
[x] c.xml
[x] c01.xml
[x] c02.xml
[x] c03.xml
[x] c04.xml
[x] c05.xml
[x] c06.xml
[x] c07.xml
[x] c08.xml
[x] c09.xml
[x] c10.xml
[x] c11.xml
[x] c12.xml
[x] dateChar.xml
[x] descriptionOfComponents.xml
[x] descriptionOfComponentsType.xml
[x] ead.xml
[x] findAidDesc
[x] level.xml
[x] title.xml
[x] calendar.xml
[x] certainty.xml
[x] era.xml
[x] notAfter.xml
[x] notBefore.xml
[x] standardDate.xml
[x] status.xml