Draft catalog role for aggregated profile resources#62
Open
leskneebone wants to merge 2 commits into
Open
Conversation
Profiles often depend on evolving sets of resources such as vocabularies, validators, schemas, and specifications. In practice, these are not always maintained as stable one-by-one profile resource descriptors. Instead, they may be managed through a catalog that aggregates metadata about profile-relevant resources. This role is intended to support that pattern, especially where resources are maintained externally to the profile itself.
Refining the scope and definition of proposed `catalog` role so that there is flexibility in how target classes are interpreted.
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.
Profiles often depend on evolving sets of resources such as vocabularies, validators, schemas, and specifications. In practice, these are not always maintained as stable one-by-one profile resource descriptors. Instead, they may be managed through a catalog that aggregates metadata about profile-relevant resources.
This role is intended to support that pattern, especially where resources are maintained externally to the profile itself.