<alternativeSet>

[SJagodzinski]

Alternative Set

• review usage: use cases from National Library of Australia - keep the element
• add optional attributes:
  @audience
@conventationDeclarationReference
@maintenanceEventReference
@scriptOfElement
@sourceReference
@target

Creator of issue

1. Silke Jagodzinski
2. TS-EAS: EAC-CPF subgroup
3. silkejagodzinski@gmail.com

Related issues / documents

alternativeSet / setComponent / componentEntry #154

EAD3 Reconciliation

EAC-CPF specific element

Context

Summary: A container element for two or more authority records derived from two or more authority systems, expressed within a single EAC-CPF instance.
May contain: setComponent
May occur within: cpfDescription
Attributes: @xml:base, @xml:id, @xml:lang - all optional
Availability: Optional, Non-repeatable

Solution documentation: agreed solution for TL and guidelines

Rephrasing Summary, Description and Usage and Attribute usage needed?

May contain: <setComponent>
May occur within: <cpfDescription>
Attributes:
@audience - optional (values limited to: external, internal)
@conventationDeclarationReference - optional
@id - optional
@languageOfElement - optional
@maintenanceEventReference - optional
@scriptOfElement - optional
@sourceReference - optional
@target
Availability: Optional, Non-repeatable

• Topic for Best Practise Guide

Example encoding

<alternativeSet audience="external" base="baseURI" conventionDeclarationReference="convention1" id="as1" languageOfElement="eng" maintenanceEventReference="maintenance1" scriptOfElement="lat" sourceReference="source1" target="control1">
 <setComponent>
  <componentEntry>textual note about the EAC-CPF encoding for one entire authority record</componentEntry>
  <descriptiveNote>
   <p>note about the EAC-CPF encoding for one entire authority record</p>
  </descriptiveNote>
  <objectXMLWrap>
   <non-eas-xml xmlns="">
    <anyElement/>
   </non-eas-xml>
  </objectXMLWrap>
 </setComponent>
</alternativeSet>

[fordmadox]

@SJagodzinski , @ailie-s

Just a note that this element currently contains the following attributes in the draft schema:

• audience
• base
• conventionDeclarationReference
• id
• langaugeOfElement
• maintenanceEventReference
• scriptOfElement
• sourceReference
• target

If this element / module is kept, just let me know if I should remove any of those attributes or not, but I believe that captures what was discussed previously (i.e. "if kept, add lang and ref attributes")

[SJagodzinski]

National Library of Australia uses the <alternativeSet> element to include the original records that they receive from members, and the objectXMLWrap element to include a few different namespaces, including DC and the old EAC formats.

[kerstarno]

Tested as part of schema testing:

• <alternativeSet> is an optional sub-element of <cpfDescription>
• <alternativeSet> cannot be repeated
• <alternativeSet> requires at least one <setComponent> to be present
• <alternativeSet> can be used with the optional attributes @audience, @base, @id, @target, @languageOfElement, @scriptOfElement, @conventionDeclarationReference, @maintenanceEventReference, and @sourceReference
• <alternativeSet> also allows for optional attributes of any other namespace (tested with XLink)

The above applies to both schemas, RNG and XSD.

The element is ready.

[ailie-s]

Draft Tag Library Text

Summary: A container for two or more authority records derived from two or more authority systems, expressed within a single EAC-CPF instance.
May contain: setComponent (1..n)
May occur within: cpfDescription
Attributes:
@audience - Optional (values limited to: external, internal)
@base - Optional
@conventionDeclarationReference - Optional
@languageOfElement - Optional
@id - Optional
@maintenanceEventReference - Optional
@scriptOfElement - Optional
@sourceReference - Optional
@target - Optional
Description and Usage: <alternativeSet> is a container element for two or more authority records derived from two or more alternative systems. Authority record aggregation may be used in cooperative or consortial contexts that gather together records
describing the same CPF entity in different languages, from different rules, or from different contexts, when it is desirable
to provide users with alternative descriptions of the same entity. For example in the context of the European Union, an
international cooperative project may want to provide users the option of storing descriptions in Italian, French, German,
English, Spanish, and on other European languages.
Alternative authority records are contained within the required <setComponent> child elements. This approach allows different descriptions of the same CPF entity to be contained within a single EAC-CPF instance.
Availability: Optional, not repeatable