Hello!
> a timestamp indicating when the Event description was written.
I consider this could be useful.
Furthermore, I noticed a couple of issues when it comes to dates in the
PREMIS schema at
http://www.loc.gov/standards/premis/v2/premis-v2-0.xsd specially
xs:simpleType name="edtfSimpleType"
which - as of today - doesn't match the description given in the
specification of EDTF
http://www.loc.gov/standards/datetime/spec.html (a work-in-progress). I
would suggest to add a clarification in the PREMIS schema explaining where
this interpretation of EDTF was found.
I also noticed some mismatches between the examples given and the regexes
in the @value on the xs:pattern elements, which are children of the
restriction describing the edtfRegularExpressions xs:simpleType as
follows:
> value="\d{2}(\d{2}|\?\?|\d(\d|\?))(-(\d{2}|\?\?))?~?\??"
could be shortened as
value="\d{2}(\?\?|\d(\d|\?))(-(\d{2}|\?\?))?~?\??"
I also consider that it is important to note that
> value="((\d{4}(-\d{2})?)|UNKNOWN)/((\d{4}(-\d{2})?)|UNKNOWN|OPEN)"
does not exclude expressions such as:
2011-06/2012
or
2011/2012-06
which, according to the description given on line 966 in
http://www.loc.gov/standards/premis/v2/premis-v2-0.xsd do not seem to be
considered valid:
> years: 'yyyy/yyyy'; or year/month: yyyy-mm/yyyy-mm.
All of these regexes could be rewritten to avoid validation of months,
days, hours, minutes and seconds with too high numerical values, such as:
2011-77
or
20110706T777777
Regards!
SaaĊĦha,
|
