feat(specifications): add unlisted specification registry built from data files - #59
Merged
Merged
Conversation
carlfredl
approved these changes
Oct 1, 2026
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
2 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.
Summary
Adds a registry of mobility specifications assessed against the MDIP open standard criteria.
What's included
/specifications/): searchable, filterable list of 55 specifications, ordered by number of known adopters./specifications/<id>/): status, verdict and rationale for each MDIP criterion, licensing, adoption and maintainers, with the assessment rules shown under the criteria.data/): one Markdown file per specification and per organization, plusprinciples.csvandlicences.csv. "Suggest a change" on each page opens that entry's file on GitHub for editing./api/): static JSON catalogue, full records, organizations, CSV export, and an OpenAPI description with Swagger docs at/api/docs/.make specs-checkvalidates the data, and runs on every pull request that touches it.See
data/README.mdfor the data format and how to contribute.