Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dropping skos:Concept and skos:ConceptScheme in fig 1 as the ranges for dcat:theme and dcat:themeTaxonomy #1558

Merged
merged 5 commits into from
Feb 9, 2023

Conversation

riccardoAlbertoni
Copy link
Contributor

Even if we have written that the diagram in fig 1 is not normative and the caveat about open world philosophy, having skos:Concept and skos:ConceptScheme in fig 1 as the ranges for dcat:theme and dcat:themeTaxonomy can be slightly misleading to 'casual' readers.

Shall we remove skos:Concept and skos:ConceptScheme from figure 1, so that there is no chance of confusion?

This PR closes #1557

…of the dcat:theme and dcat:themeTaxonomy relaxation
@riccardoAlbertoni riccardoAlbertoni added this to the DCAT3 CR milestone Feb 6, 2023
@riccardoAlbertoni riccardoAlbertoni changed the title Dropping skos:Concept and skos:ConceptScheme in fig 1 as the ranges for dcat:theme and dcat:themeTaxonomy` Dropping skos:Concept and skos:ConceptScheme in fig 1 as the ranges for dcat:theme and dcat:themeTaxonomy Feb 6, 2023
@riccardoAlbertoni
Copy link
Contributor Author

droped foaf:Agent from the diagram as we discussed in the call https://www.w3.org/2023/02/07-dxwgdcat-minutes.html

Please revised the PR

@davebrowning davebrowning merged commit e8440c8 into gh-pages Feb 9, 2023
@davebrowning davebrowning deleted the dcat-issue-1557 branch February 9, 2023 06:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

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