The current cardinality of the property dct:modified obliges the metadata publisher to provide a value (i.e. it is a mandatory property). However, we have seen that this value is always outdated when not computed automatically by a system. Even in the latter case, this value is of no use for us and does not bring additional information.
Component
DocumentationCategory
improvement
Login or create an account to comment.
Comments
Proposed resolution: Remove dct:modified from Asset Repository
NOTE: This is different from the proposal submitted by the Joinup team. The proposed resolution is based on the comment in the last sentence in the problem statement. In DCAT-AP, this property is recommended for Catalogue.
The proposal submitted by the Joinup team: Align the cardinality of the property dct:modified associated to the class adms:AssetRepository with DCAT-AP, i.e. make the property optional with a cardinality of 0..1 instead of 1..1.
Comment from Szabolcs Szekacs
+1 – but to be discussed with the Joinup + EFIR team.
In case of automatic updates, how shall the system determine which are the most recent updates? Perhaps this information is indeed not needed, and joinup can simply overwrite any metadata with the newly received information, assuming that the newly received package is always the newest one.
I think in Drupal, every content will have a creation and last modification date. They don't need to be described in ADMS-AP. Everytime there is an import to update elements, we can check the time of import and compare with the existing version.
If I read the comments well, the consensus seems to be that this property be dropped. We will remove it in the draft version of the revised profile. Of course, further comments are welcome.
+1 @Makx
Resolved