dcat:theme and dcat:themeTaxonomy in class diagram Fig 1

[riccardoAlbertoni]

• the ranges of dcat:theme and dcat:themeTaxonomy have been relaxed, do we want to mirror that in fig1?

Originally posted by @riccardoAlbertoni in #1556 (comment)

[dr-shorthair]

Have we retained the suggestion or permission to use the SKOS elements, in a non-normative advice somewhere?

[riccardoAlbertoni]

DCAT 3 defines the range of dcat:theme as rdfs:Resource, DCAT 2 had skos:Concept. https://w3c.github.io/dxwg/dcat/#Property:catalog_themes

skos:Concept is one of the option. I expect the majority of cases will use skos:Concept, the diagram ranging with skos:Concept, skos:ConceptScheme is not wrong, and in principle, can be kept as it is.

However, we know that people often use the diagram as the primary reference. I know we can't prevent incomplete reading, but not including skos:Concept, skos:ConceptScheme forces people to read the normative definition ...

[riccardoAlbertoni]

However, we know that people often use the diagram as the primary reference. I know we can't prevent incomplete reading, but not including skos:Concept, skos:ConceptScheme forces people to read the normative definition ...

In case we want to drop dcat:theme and dcat:themeTaxonomy in the class diagram; PR #1558 acts the change

[riccardoAlbertoni]

foaf:Agent can be dropped as well in the figure see discussion in the call https://www.w3.org/2023/02/07-dxwgdcat-minutes.html