Closed kerstarno closed 5 months ago
fordmadox
commented
6 months ago Available for testing in the development branch.
Note: currently, "reference/span" is allowed in EAC-CPF / EAD4, so "reference/referringString" is also permitted in the above branch.
kerstarno
commented
5 months ago Tested with the XSD and the RNG.
Most of the above has been implemented as expected, apart from:
<head> should still kept in EAD 4.0 for use within <did> and the numbered and unnumbered <c> elements, but has currently been removed; hence the changes here cannot be checked<num> should have been removed (apologies for the mixed messages in the original post)@localType is still included in <identificationDataNote>, but should be removed (same for @localTypeDeclaration)I created a pull request for the above pending changes (#80). Once the pull request has been merged, this issue will need retesting.
fordmadox
commented
5 months ago Sorry, I had thought that head was going away with a suggestion for folks to use h1-h6 in its place, so thanks for adding that back in. Should be ready for testing again now.
kerstarno
commented
5 months ago Sorry, I had thought that
headwas going away with a suggestion for folks to use h1-h6 in its place, so thanks for adding that back in. Should be ready for testing again now.
Thanks. And, yes, it's a bit confusing. <head> is only kept in those contexts where it wasn't used alongside the block formatting elements. In those contexts, where <head> went side-by-side with <p>, <list>, etc. it's been removed as it would be taken care of by using <h1> etc. within <formattingExtension>.
kerstarno
commented
5 months ago Re-tested with the XSD and RNG and can confirm that the remaining changes have now been implemented as expected.
florenceclavaud
commented
2 months ago Hi everybody, what about adding to the new referringString element an attribute to specify the kind of relation that exists between the records described and the entity that is referred to (just as we have the relationType element elsewhere)? This would be great for some users at least, otherwise they may be compelled to encode, out of the textual element, a minimal description of the agent, place, function or subject referred to, in addition to using referrinString, which would be somewhat redundant.
I hope I am clear.
kerstarno
commented
2 months ago Hi everybody, what about adding to the new
referringStringelement an attribute to specify the kind of relation that exists between the records described and the entity that is referred to (just as we have therelationTypeelement elsewhere)? This would be great for some users at least, otherwise they may be compelled to encode, out of the textual element, a minimal description of theagent,place,functionorsubjectreferred to, in addition to usingreferrinString, which would be somewhat redundant. I hope I am clear.
I've added this suggestion as #111 for the next milestone.
Creator of issue
The issue relates to
Wanted change/feature
<referringString>to allow for the tagging of named entities within textual descriptions using one dedicated element instead of having a long list of mixed content elements to take into account. This would also allow for<span>to be more specifically used for formatting and highlighting aspects by using@style(as it has been in EAC-CPF all along).<referringString>should hence be added in all contexts that allow for<span>. (status of this needs to be reviewed in the current (1 December 2023) draft schema for EAD 4.0)<referringString>@audience,@id,@target,@languageOfElement,@scriptOfElement,@conventionDeclarationReference,@maintenanceEventReference,@sourceReference,@localType, and@localTypeDeclarationReference@valueURI,@vocabularySource, and@vocabularySourceURIUpdate (5 January 2024): Following the EAD team's meeting on 15 December, the details of this issue have been updated to the latest status with the additions below this paragraph. The current development version of the schema might still represent what was outlined initially, while further changes might be necessary and require another round of testing.
Ultimately, the introduction of
<span>(which replaces<emph>, see #71) and<referringString>along with the use of<reference>will lead to a minimal mixed content model in the EAD 4.0 general schema, which might be further reduced in the core schema.<abbr(eviation)>,<expan(sion)>, and<foreign>with<referringString>in<container><dimensions><head><materialSpec><num><physDesc><physFacet><physLoc><unitDate><unitId><unitTitle><ptr>with<reference>in<container><dimensions><head><materialSpec><num><physDesc><physFacet><physLoc><unitDate><unitId><unitTitle><corpname>,<date>,<famname>,<function>,<genreform>,<geogname>,<name>,<num>,<occupation>,<persname>,<subject>, and<title>with<referringString>in<physFacet><unitTitle><footnote>and<quote>with<span>in<physFacet><unitTitle><lb>from<container><dimensions><head><materialSpec><num><physDesc><physFacet><physLoc><unitDate><unitId><unitTitle>For the replacement of<emph>with<span>in all the elements mentioned above see #71.For
<identificationDataNote>(was:<didNote>), which currently also includes the above mentioned sub-elements, a different approach is taken:<identificationDataNote>with the one of<descriptiveNote><abbr(eviation)>,<expan(sion)>,<foreign>,<ptr>,<ref>,<emph>and<lb>from<didNote><p>as required and repeatable sub-element instead@audience@targetas an optional attribute@langto@languageOfElementand@scriptto@scriptOfElement@conventionDeclarationReference,@maintenanceEventReference, and@sourceReference@altrender,@localtype,@label, and@encodinganalogFor the alignment of the descriptive, shared elements
<abstract>,<reference>(replacing<ref>, see #40), and<p>see #47. For the alignment of data-centric, shared elements such as<addressLine>or the single date elements in terms of mixed content see #70.