CR20 Modify cardinality of dcat:theme to 0..N


A proposal is made to make the indication of a theme recommended rather than mandatory for Asset. This proposal is made dependent on the resolution of CR38 (…)






Tue, 05/01/2016 - 13:04

Proposed resolution: Specify the use the MDR Data Theme vocabulary instead of the Eurovoc domains, which is in line with usage in DCAT-AP.

Wed, 06/01/2016 - 16:22

This proposed resolution should be indeed discussed further. As explained in the change requests list document, the different terms of the MDR data theme voc do not really apply to the context of interoperability solutions. Interoperability solutions are today created in a certain number of policy domains of which a lot could be categorised through the themes “Economy and Finance”, “Government and public sector”, “Health” and “Science and technology”. Again, the benefits of having 80% of solutions categorised under four different themes is debatable.


As it is proposed to keep the theme a mandatory property, the values should be really relevant for Joinup.

Wed, 06/01/2016 - 16:25

Comment from Szabolcs Szekacs:

I agree with TK. Data can be better categorised than software or specs imho into the MDR data theme vocs.

For Joinup, these categories do not add value for the user.

We should either create better categories (1), use the MDR data theme, but as optional only (3), or completely drop the whole thing (2).

Can we have some data on how people search on Joinup?  do they use the themes at all? (I have strong doubts, based on discussions with the EFIR team).



I am more towards either dropping the theme completely (so not even optional) or defining a better theme taxonomy.




Fri, 08/01/2016 - 08:42

@Szabolcs Szekacs:


Unfortunately no there is no way to know whether the 'theme' filter is used in the faceted search. However, even if people would try to use it, there are so many themes that this functionality cannot be used very effectively.

Sun, 10/01/2016 - 11:38

So is the alternative to just drop it? In that case, also the themaTaxonomy for Repository may be dropped.

Wed, 20/01/2016 - 09:18

@Stijn, do you have any opinion on this?

Sun, 07/02/2016 - 12:08

Looking at the discussion so far, I think there is some consensus that theme and theme taxonomy don't make much sense for Joinup, at least not the way it is specified now. If that is the case, we will drop both properties in the draft version of the revised profile. Of course, further comments are welcome.

Mon, 08/02/2016 - 09:26

Making the theme recommended rather than mandatory fits the conceptual model of the new Joinup platform. 

Wed, 10/02/2016 - 19:39

OK. So, rather than deleting the properties themeTaxonomy and theme, we'll make them recommended.

Mon, 15/02/2016 - 14:27

Can be closed

Login or create an account to comment.