Closed SJagodzinski closed 2 years ago
Just a note: do we want to add a test to the Schematron to ensure that there is only 1 "true" preferredForm, or are multiple values okay?
Tag Library Text:
Summary: Attribute that specifies whether or not a <nameEntry>
provides the preferred form of the name of the EAC-CPF entity.
Values: false, true
Just a note: do we want to add a test to the Schematron to ensure that there is only 1 "true" preferredForm, or are multiple values okay?
I guess, multiple values would be ok in several name entries that are not bundled in a name entry set or if you have several name entry sets, eg one for each language, and have to declare the preferred form per set.
Tested as part of Schema Team's schema testing:
@preferredForm
is an optional attribute in <nameEntry>
The above applies to both schemas, RNG and XSD.
The attribute is ready.
Tag Library Text:
Summary: Attribute that specifies whether or not a
<nameEntry>
provides the preferred form of the name of the EAC-CPF entity. Values: false, true
@ailie-s : Could we add information that the preferred form of a name is meant for display purposed, cf https://eac.staatsbibliothek-berlin.de/schema/taglibrary/cpfTagLibrary2019_EN.html#elem-preferredForm
Preferred Form of Name
@preferredForm
to<nameEntry>
to indicate if a name entry is the preferred form for displayCreator of issue
Related issues / documents
<preferredForm>:
turn into attribute #71 Topic_names_20200130.pdfEAD3 Reconciliation
new EAC attribute
Context
new EAC attribute, was element
<preferredForm>
beforeSolution documentation:
Summary, Description and Usage and Attribute usage needed
May occur within:
<nameEntry>
Values: false, trueExample encoding