initial dcat:CatalogRecord implementation #353
Draft
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Hi,
I'm currently implementing MobilityDCAT for https://github.com/belgium-its-steering-committee here. The MobilityDCAT AP makes
dcat:CatalogRecordrequired.From what I could see, due to its nature, sitting between
dcat:Cataloganddcat:Dataset,dcat:CatalogRecordisn't something one can implement cleanly as an extension ofckanext-dcat(relevant entrypoint here) and requires forking ckanext-dcat. Since thedcat:CatalogRecordbasics are part of core dcat, I thought it might make sense to contribute this upstream.I'm opening a draft PR here to discuss if this is something the https://github.com/ckan/ckanext-dcat maintainers would consider and if so, gather feedback to make this PR mergeable.
Thx!