Closed kerstarno closed 5 months ago
The EAD sub-team discussed <function>
and <occupation>
during their meeting on 24 November 2023 and again during their meeting on 15 December 2023, the second time in the more general context of discussing relations in EAD.
For <function>
, it has been decided to establish the element more as a related entity rather than a piece of descriptive information, along with <agent>
(#58) and <formAvailable>
(#65).
<function>
out of <controlaccess>
and <index>
(for the latter two see #67)<function>
as a required and repeatable sub-element to <functions>
(#68)<function>
to the content model defined in EAC-CPF 2.0
<part>
and add <term>
instead as a required and repeatable sub-element<date>
, <dateRange>
, and <dateSet>
<placeName>
as an optional, repeatable sub-element<descriptiveNote>
as an optional, not repeatable sub-element@audience
@altrender
@target
@lang
and @script
to @languageOfElement
and @scriptOfElement
@identifier
with @valueURI
and @source
with @vocabularySource
, add @vocabularySourceURI
, and remove @rules
(replaced by @conventionDeclarationReference
, see next point)@conventionDeclarationReference
, @maintenanceEventReference
, and @sourceReference
@localType
and add @localTypeDeclarationReference
@encodinganalog
@relator
(replaced by <targetRole>
, see next point)<targetType>
, <targetRole>
, and <relationType>
as optional and repeatable sub-elements to <function>
(see #33 for the detailed definition of these elements)For <occupation>
as sub-element of <controlaccess>
and <index>
see #67.
In a future revision of EAC-CPF, <targetType>
, <targetRole>
, and <relationType>
would need to be added as optional and repeatable sub-elements of <function>
(see #33 for the detailed definition of these elements). There might then also be the question whether this would be the same for all other singular elements.
Tested with the XSD and the RNG and can confirm that this has been implemented as described.
Creator of issue
The issue relates to
Wanted change/feature
<function>
and<occupation>
across EAD and EAC-CPF, including conversations had in the Functions sub-team and considering that both could form under the RiC entity "Activity".<controlAccess>
(or<controlledAccess>
), i.e. they are used with a required and repeatable<part>
sub-element plus a series of attributes with regard to linking to vocabularies, which in EAD 4.0 would be@valueURI
,@vocabularySource
,@vocabularySourceURI
and the element<targetRole>
, plus@conventionDeclarationReference
which could be used to point to any rules applied in formulating the elements' content.<term>
sub-element and also allow for one of the date elements,<placeName>
, and<descriptiveNote>
; they also allow for@valueURI
,@vocabularySource
,@vocabularySourceURI
(and@conventionDeclarationReference
), but not for<targetRole>
.