Closed jmaferreira closed 2 months ago
@shsdev @karinbredenberg What do you think of these release notes? Are they inline with your vision for this?
@shsdev @karinbredenberg What do you think of these release notes? Are they inline with your vision for this?
Looks good to me.
Only thing is that for me some of the links looks like a 8 character hex code, if possible get them to say something people can understand instead.
Otherwise OK!
Thanks Karin and Sven. The links are commit numbers. I didn't have an Issue to refer to, but I'll try to make it nicer.
17th May 2024
Specification Changes
Version 2.2.0 of the SIP specification introduces textual enhancements and clarifications, rectification of previously detected typographical errors, adjustments to the cardinality of certain METS elements, along with comprehensive reviews and updates to examples and METS profiles. Further, enhancements in indentation have been applied to augment the legibility of the examples.
Corrections
SIP19
from 'The submitting agent has a note providing a unique identification code for the archival creator.' to 'The submitting agent has a note providing a unique identification code for the submitter.' [#126]<agent>
element from SHOULD to MUST (requirement SIP12). [827cede48fc3870eb049fca733ab713308025681], [#101], [#102]RECORDSTATUS
controlled vocabulary entry fromREPLEACEMENT
toREPLACEMENT
. [827cede48fc3870eb049fca733ab713308025681]TEST
fromeb
toen
. [9176fc889af2decd3e5d44dfdaec1884e7d27dba]Administrative
Website and PDF Presentation