You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am wondering if the textLang element should be available in within the seal element, to allow classification of the language(s) used in the seal legend, if there is one. This would be particularly useful for identifying legends in vernacular languages. Alternatively the mainLang/otherLang attributes could be available for the legend element.
The text was updated successfully, but these errors were encountered:
Yes, we should do this, but based upon discussion today with @holfordm and @schassan, it seems like the desirable solution would be to make a larger change/fix to give seals attributes which are more in line with object/msItem/msPart, treating them similarly to Sammelbände parts of the manuscript, so that they could have separate attributes such as language, material, text, etc. Presumably we would make this work similarly to the way of dealing with endleaves and bindings that comes out of the discussion at the TEI2022 Newcastle msDesc SIG.
An outstanding question is whether we should keep the description of seals as physical items within sealDesc/authDesc or whether we should separate the description of seals as physical and textual items (as objects/msitems, in parallel to the diploma itself) from the description of seals as authenticating items which would be in sealDesc/authDesc, or whether both senses of seals should remain in sealDesc/authDesc.
I am wondering if the
textLang
element should be available in within theseal
element, to allow classification of the language(s) used in the seal legend, if there is one. This would be particularly useful for identifying legends in vernacular languages. Alternatively the mainLang/otherLang attributes could be available for thelegend
element.The text was updated successfully, but these errors were encountered: