-
Notifications
You must be signed in to change notification settings - Fork 47
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
Conversation
@@ -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 ; |
There was a problem hiding this comment.
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.
@plehegar , in the RDF definition of DCAT3 we specified W3C as publisher,: Line 117 in 9d1fea9
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? |
https://www.wikidata.org/entity/Q37033
This has tons of useful rdf factoids nearby!
…On Thu, 19 May 2022 at 22:05, Andrea Perego ***@***.***> wrote:
@plehegar <https://github.com/plehegar> , in the RDF definition of DCAT3
we specified W3C as publisher,:
https://github.com/w3c/dxwg/blob/9d1fea9e04d0a6953549c2dfda3995cbc3011da0/dcat/rdf/dcat3.ttl#L117
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?
—
Reply to this email directly, view it on GitHub
<#1508 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABJSGPB2AFOGQTQGKQZZGLVK2UJHANCNFSM5VZRQEAA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
I have implemented the changes discussed in the last DCAT subgroup meeting (see https://www.w3.org/2022/11/29-dxwgdcat-minutes). @pchampin: Do you still think that distinction is pivotal? |
foaf:homepage <http://okfn.org> ; | ||
foaf:name "Open Knowledge Foundation" ; | ||
bibo:editor [ | ||
a foaf:Person ; |
There was a problem hiding this comment.
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 ...
There was a problem hiding this 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
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. |
There was a problem hiding this 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
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/> ; |
There was a problem hiding this comment.
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:
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.
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>; | |
] ; |
There was a problem hiding this comment.
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.
Ok, let's try to be future proof, no objection from my side. |
Co-authored-by: Pierre-Antoine Champin <[email protected]>
Co-authored-by: Pierre-Antoine Champin <[email protected]>
Co-authored-by: Pierre-Antoine Champin <[email protected]>
@pchampin I have accepted your suggestions and updated the .jsonld and .rdf vocabulary serialisations. |
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:
dcterms:creator
rdfs:isDefinedBy
where missingfoaf:depiction
to link to the DCAT3 diagramdcterms:created
&dcterms:issued
dcterms:title
&dcterms:description
dcterms:publisher
The proposal includes also some editorial and bug fixes:
dcat:resource
to align it with the specification, and added Italian translationrdfs:subPropertyOf
where missing, to align the RDF definition with the specification