We have seen that this property has never been used and is of less relevance for asset than for datasets.
Component
DocumentationCategory
improvement
Login or create an account to comment.
We have seen that this property has never been used and is of less relevance for asset than for datasets.
Comments
Proposed resolution: Change dct:temporal to optional with cardinality 0..n for Asset. This is in line with DCAT-AP.
Comment from Szabolcs Szekacsµ
If it has never been used, why not simply drop it? ADMS is already difficult as is...
The issue with purely deleting properties is that it makes backward compatibility issue... If another ADMS-AP implementers use this property now, it means they won't be compliant with the new specification.
Better to leave it optional, meaning that Joinup does not have to read it and display it but metadata publisher can use it if they want.
There is no backward compatibility issue with deleting properties from the profile. Whatever the definiton of the profile, data providers are free to provide whatever property they want in a description.
The difference between properties defined as optional in the profile and properties not described in the profile is that for optional properties, a receiver has the following obligation:
a receiver MUST be able to process the information for that property; a sender MAY provide the information for that property but is not obliged to do so
while for properties not defined, the receiver may just ignore it.
For ther time being, we will include the property with cardinality 0..n in the draft version of the revised profile. Of course, further comments are welcome.
Hello,
We discussed this issue internally and it was agreed to delete the property.
In Draft 2, this property will be deleted.