CR3 Repository. Remove the property adms:supportedSchema or change the property range.

05/01/2016

This property has been added to support backward compatibility and announce to the metadata consumers which ADMS profile is used. However, as far as we know, no organisations is implementing ADMS.SW or ADMS (except maybe for W3C). Furthermore, we have seen in our daily utilisation of ADMS-AP that this field was never filled in. This can also be explained by the range of the property (i.e. adms:Asset), which makes the metadata publisher obliged to describe the ADMS asset he is using.

Component

Documentation

Category

improvement

Comments

Tue, 05/01/2016 - 14:11

Proposed resolution: In the future, there may be two profiles in use: the current ADMS-AP and the one that we are developing. It may be useful to indicate for an interim period which profile is used. The fact that a schema is described as an Asset seems to be a good approach. The ADMS-AP schemas can be published and described by Joinup. DCAT-AP does not specify this property for Catalogue.

Sun, 10/01/2016 - 09:57

This issue may need further discussion.

Sun, 07/02/2016 - 12:03

As there was no further discussion, we will remove this property in the draft version of the revised profile. Of course, further comments are welcome.

Mon, 08/02/2016 - 09:05

+1 

Mon, 15/02/2016 - 14:49

Resolved

The content of this field is kept private and will not be shown publicly.