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

Update metadata of the RDF definition of DCAT3 #1508

Merged
merged 38 commits into from
Jan 19, 2023

Conversation

andrea-perego
Copy link
Contributor

@andrea-perego andrea-perego commented May 12, 2022

Some of the metadata of the RDF definition of DCAT3 are not up to date, and some are missing.

As a first proposal, the following revisions have been included in this PR:

The proposal includes also some editorial and bug fixes:

  • re-ordered alphabetically properties used in the definition of classes and properties
  • fixed bugs in the definition of dcat:resource to align it with the specification, and added Italian translation
  • added rdfs:subPropertyOf where missing, to align the RDF definition with the specification

@@ -155,9 +163,13 @@
owl:versionInfo "Toto je aktualizovaná kopie slovníku DCAT 3, převzatá z https://www.w3.org/ns/dcat.ttl"@cs ;
skos:editorialNote "English language definitions updated in this revision in line with ED. Multilingual text unevenly updated."@en ;
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This note may need to be updated before the file is published in W3C space:

English language definitions updated in this revision in line with REC. Multilingual text unevenly updated.

dcat/rdf/dcat3.ttl Outdated Show resolved Hide resolved
dcat/rdf/dcat3.ttl Outdated Show resolved Hide resolved
dcat/rdf/dcat3.ttl Outdated Show resolved Hide resolved
dcat/rdf/dcat3.ttl Outdated Show resolved Hide resolved
@andrea-perego andrea-perego added this to the DCAT3 CR milestone May 13, 2022
@andrea-perego
Copy link
Contributor Author

@plehegar , in the RDF definition of DCAT3 we specified W3C as publisher,:

dcterms:publisher <https://www.w3.org/> ;

The question is whether it is fine we use https://www.w3.org/ as the URI for W3C - as far as I know, there is no RDF description associated with it, or embedded in the corresponding HTML page.

In other words, which is the "official" URI to be used when referring to W3C in an RDF graph?

@danbri
Copy link

danbri commented May 19, 2022 via email

@riccardoAlbertoni
Copy link
Contributor

I notice that https://www.w3.org/ uses content-negotiation, so adding an RDF "view" of it would probably be feasible?

NB: if we did that, we would still need to distinguish the web-page (https://www.w3.org/) from the organization (https://www.w3.org/#this).

I have implemented the changes discussed in the last DCAT subgroup meeting (see https://www.w3.org/2022/11/29-dxwgdcat-minutes).
To be consistent with the resolution (https://www.w3.org/2022/11/29-dxwgdcat-minutes#r04), we do not distinguish between the web page (https://www.w3.org/) and the organisation (https://www.w3.org/#this).

@pchampin: Do you still think that distinction is pivotal?

dcat/rdf/dcat3.ttl Outdated Show resolved Hide resolved
foaf:homepage <http://okfn.org> ;
foaf:name "Open Knowledge Foundation" ;
bibo:editor [
a foaf:Person ;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure I merit an 'editor' credit on v3.
I've only been a distant participant ...

Copy link
Contributor

@dr-shorthair dr-shorthair left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A few minor comments inline

@pchampin
Copy link
Contributor

pchampin commented Jan 9, 2023

@riccardoAlbertoni

@pchampin: Do you still think that distinction is pivotal?

It really depends on who is going to consume that RDF metadata, and how pedantic they will be about it. In order to be future-proof, I would refrain from conflating the webpage and the organization. I'll make a suggestion in my review.

Copy link
Contributor

@pchampin pchampin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I made suggestions on the TTL version only. The corresponding changes should be made on the RDF/XML and JSON-LD version as well...

dcat/rdf/dcat3.ttl Outdated Show resolved Hide resolved
dcterms:modified "2022-05-12"^^xsd:date ;
dcterms:modified "2022-05-23"^^xsd:date ;
dcterms:modified "2023-01-05"^^xsd:date ;
dcterms:publisher <https://www.w3.org/> ;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is conflating a web page and an organization. As we don't have, currently, a nice IRI identifying the organization, I think the easiest path we have is this:

Suggested change
dcterms:publisher <https://www.w3.org/> ;
dcterms:publisher [ foaf:homepage <https://www.w3.org/> ] ;

This pattern is already used for people and their affiliation in this schema.
This could be enriched further, e.g.

Suggested change
dcterms:publisher <https://www.w3.org/> ;
dcterms:publisher [
a org:Organization;
foaf:homepage <https://www.w3.org/>;
foaf:name "World Wide Web Consortium (W3C)";
rdfs:seeAlso <https://www.wikidata.org/entity/Q37033>;
] ;

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have accepted the second option providing further erichment.

dcat/rdf/dcat3.ttl Outdated Show resolved Hide resolved
dcat/rdf/dcat3.ttl Outdated Show resolved Hide resolved
@riccardoAlbertoni
Copy link
Contributor

@riccardoAlbertoni

@pchampin: Do you still think that distinction is pivotal?

It really depends on who is going to consume that RDF metadata, and how pedantic they will be about it. In order to be future-proof, I would refrain from conflating the webpage and the organization. I'll make a suggestion in my review.

Ok, let's try to be future proof, no objection from my side.

riccardoAlbertoni and others added 5 commits January 12, 2023 10:52
Co-authored-by: Pierre-Antoine Champin <github-100614@champin.net>
Co-authored-by: Pierre-Antoine Champin <github-100614@champin.net>
Co-authored-by: Pierre-Antoine Champin <github-100614@champin.net>
@riccardoAlbertoni
Copy link
Contributor

@pchampin I have accepted your suggestions and updated the .jsonld and .rdf vocabulary serialisations.
If you can approve the PR, I would merge it, also considering that quite a large number of interventions have been piled into this PR, and keeping track of the changes is getting complex.

@riccardoAlbertoni riccardoAlbertoni merged commit 6a8b195 into gh-pages Jan 19, 2023
@riccardoAlbertoni riccardoAlbertoni deleted the dcat-rdf-metadata branch January 19, 2023 15:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants