Duplicate annotations may lead to semantic conflict when editing/updating an EML file outside of EMLassemblyline.
For example, if /eml:eml/dataset/dataTable has the same annotation at /eml:eml/dataset/dataTable/annotation and /eml:eml/annotations/annotation, it is possible a downstream user may only update the first and not the second.
For this reason it has been suggested that EMLassemblyline stop adding annotations in both places.
Note: The original intent of the duplicate annotation feature was to handle potential variability in uptake by downstream repositories/harvesters.
Duplicate annotations may lead to semantic conflict when editing/updating an EML file outside of EMLassemblyline.
For example, if
/eml:eml/dataset/dataTable
has the same annotation at/eml:eml/dataset/dataTable/annotation
and/eml:eml/annotations/annotation
, it is possible a downstream user may only update the first and not the second.For this reason it has been suggested that EMLassemblyline stop adding annotations in both places.
Note: The original intent of the duplicate annotation feature was to handle potential variability in uptake by downstream repositories/harvesters.