New profile for DCAT US v3 #314
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Use the same files in examples used in the shacl tests, don't use separate dataset dicts on each test.
For the parsing ones we are using the existing dataset.rdf file which has a DCAT AP flavour. We can replace it with a US centric if we can come up with a good existing example.
Use org:Organization and add a skos:prefLabel property
From landing page and documentation if there is no title defined for them. See Usage note in https://doi-do.github.io/dcat-us/#properties-for-document
As they are modeled as Data Services, the outputs fails validation because they don't contain publisher and contact point. We can revisit this if we implement first class support for Data Services
Rather than just include a Literal, add it as a node
(with a class if provided) with a RDFS.label property, eg:
dct:accessRights [ a dct:RightsStatement ;
rdfs:label "Statement about access rights" ] ;
An URI can also be used:
dct:accessRights <https://example.org/vocab/access-right/TODO/PUBLIC> ;
[...]
<https://example.org/vocab/access-right/TODO/PUBLIC> a dct:RightsStatement .
This is in line with the recommendation in the DCAT 3 spec:
https://www.w3.org/TR/vocab-dcat-3/#ex-license-and-access-rights
Values like floats caused an exception here, and the fields get index as text in Solr anyway
Both at the dataset and distribution level. This are implemented as (single) repeating subfields with url, format and license properties supported. Potential future improvements: license fallback to dataset's and link to datastore data dictionary automatically
This was already supported in DCAT AP 2, so moved the handling of these two properties to the DCAT AP 2 profile so all profiles support it
Adds support for dct:contributor to dcat-us, and fixes dct:creator in dcat-ap to allow multiple values. The logic for parsing and serializing has been updated to support multiple instances by default, and we special case dct:publisher which is the only Agent property that has a 0..1 requirement.
|
cc @jqnatividad |
|
WOOOOOHOOOOO!!!! Sorry, been busy and missed this... but WOW! We'll make this the foundation for the Phase II work we're doing with Water Data clients for sure! Will start using it too for all the projects we're involved in! Amazing! |
This was referenced Nov 11, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds a new profile class for the DCAT-US v3 application profile.
All mandatory properties and most of the recommended and optional ones are supported. The few remaining can be implemented later on if there's interest for them. The full list of implemented properties can be found here.
During the implementation of this work a few adjustments have been done to the base DCAT profile:
Includes #313
Todo: