rockivist
commented
10 years ago Comment from AFNOR relavant to this issue:
Submitted on Thursday, February 27, 2014 - 4:12pm Submitted values are:
Name: Sibille - de Grimouard Claire Affiliation: Service interministériel des archives de France Does this represent an official comment from your affiliated group? Yes Comment:
Another objective was to improve the capacity of EAD to support the
interchange of data and to encourage more conceptual and semantic
consistency. Unfortunately, this principle has not been consistently applied.
For instance, while <descgrp> is removed, the <dsc> tag is not removed
although the division between the upper level description and the remaining
components represent an out of date paper model for archival data that seems
to privilege description at the uppermost level.
After initially agreeing to deprecate
<dsc>and allow components as direct children of<archdesc>, we reversed out decision. That change was in recognition of the challenge of how to migrate existing EAD instances that include multiple<dsc>elements.We resolved to warn the EAD community that although EAD3 will allow for multiple
<dsc>elements, we anticipate that the next revision will deprecate the<dsc>, compelling users to eliminate multiple component hierarchies.Toward that end we should create a schematron that will test for forward compatibility in the event dsc is deprecated. We also need to document that in the tag library somehow.
I'm assigning this to myself for the moment - I will take the lead on addressing this in the tag library. Will transfer assignement to @tcatapano and/or @kshepher when necessary for schematron and tag library work.