Move aside outdated files and emphasize the JSON Schema#120
Merged
jbrown-xentity merged 1 commit intotiger-teamfrom Apr 3, 2026
Merged
Move aside outdated files and emphasize the JSON Schema#120jbrown-xentity merged 1 commit intotiger-teamfrom
jbrown-xentity merged 1 commit intotiger-teamfrom
Conversation
jbrown-xentity
approved these changes
Apr 2, 2026
Collaborator
jbrown-xentity
left a comment
jbrown-xentity
left a comment
There was a problem hiding this comment.
Doesn't remove much, and simplifies the structure and makes things more straightforward.
zopalmer14
approved these changes
Apr 3, 2026
zopalmer14
left a comment
zopalmer14
left a comment
There was a problem hiding this comment.
LGTM. I agree with James that it might make sense to bring back the .jsonld context file at some point in the future once the schema is mostly stable.
Merged
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
3 participants
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 addresses #44 by focusing on the JSON Schema expression of DCAT-US v3.0.
Agency metadata catalog producers want a single approved format for their metadata catalogs. JSON formatted catalog files are universally used following DCAT-US v1.1 and JSON Schema is the natural way to express the schema of information that should be contained in those catalogs.
Old information might still be useful for context, so we store it away in a clearly-labelled
DEPRECATEDfolder.