Closed riccardoAlbertoni closed 3 years ago
@riccardoAlbertoni as per my comments on the issue, I don't think we should change the labels on the spec, but it would be useful to add skos:altLabel
in the RDF serialisations
@riccardoAlbertoni as per my comments on the issue, I don't think we should change the labels on the spec, but it would be useful to add
skos:altLabel
in the RDF serializations
Thanks, Alejandra, That could be an alternative, let's see how the discussion on https://github.com/w3c/dxwg/issues/1246#issuecomment-808413945 evolves.
This PR has been superseded by https://github.com/w3c/dxwg/pull/1348, it is kept just as a reference for past discussions, and it will be deleted as soon as we agree on #1348 and we close the related issues.
1348 merged, but #1246 will remain open until we address the two final points - this PR should be closed IMO
+1 to close it.
This PR addresses the first two points of the issue https://github.com/w3c/dxwg/issues/1246
As for point 1 of the issue, this PR changes
rdfs:label
for object properties named after the class they range to but with an uncapitalized starting letter.Relations labels whose refs:label changed from “ X “ to “has X” are
Labels for the other properties are not changed as they do not ‘clash' with their range classes.
As for point 2, examples of resources in catalog definition are moved in usage note.
Still to discuss Translations of labels for languages different from English are not provided, I wonder if we want to guess them via automatic translation services, leave them as they are, or ask native-speaking people to provide translations.
We will add new stuff in DCAT 3, so I would suggest planning language revisions of the translation when delivering the last version of DCAT3. Perhaps we need a separate issue to track translations?
TODO (once we have agreed on the changes) -To Update other RDF serializations