Downloads
Raw schema JSON
Every published schema as a standalone JSON file — the same compact form the schema pages display. Regenerated on every site build.
Shared
- Acronym.jsonAn acronym.Download
- NamePrefix.jsonThe prefix before a person's name, such as Dr., Mr., Mrs.Download
- License.jsonInformation about the license for an object.Download
- AuthoritySource.jsonThe penultimate authority of a Thing.Download
- Language.jsonxDownload
- NameSuffix.jsonThe suffix to a Person's name.Download
- Country.jsonA nation with it's own government.Download
- HierarchyItem.jsonDownload
- BibTexCitation.jsonDownload
- CoreMetaData.jsonCommon record-keeping metadata carried by every GRC Schema Thing: creation and modification provenance, lifecycle status, integrity checksum, and supersession links.Download
Cambridge Dictionary
DISA
NIST
- Profile.jsonEach OSCAL profile is defined by a profile element.Download
- Catalog.jsonA structured, organized collection of control information.Download
- ComponentDefinition.jsonA collection of component descriptions, which may optionally be grouped by capability.Download
- SystemSecurityPlan.jsonA system security plan, such as those described in NIST SP 800-18.Download
- AssessmentPlan.jsonAn assessment plan, such as those provided by a FedRAMP assessor.Download
- AssessmentResults.jsonSecurity assessment results, such as those provided by a FedRAMP assessor in the FedRAMP Security Assessment Report.Download
- MappingCollection.jsonA collection of relationship-based control and/or control statement mappings.Download
- PlanOfActionAndMilestones.jsonA plan of action and milestones which identifies initial and residual risks, deviations, and disposition, such as those required by FedRAMP.Download
Open Controls
- Opencontrolsusagelicensev1.jsonDownload
- UsageLicenseStamp.jsonDownload
- Dictionary.jsonA dictionary of canonical headwords with their general definitions, classification axes, and surface-form variants. Where a glossary records what one authority means by a term, the dictionary records the term itself: its lemma, part of speech, general definition, and every form it appears under in real text (acronyms, abbreviations, plurals, tenses, misspellings).Download
- Opencontrolslicensegrantv1.jsonA PRIVATE, per-grantee license grant — the credential a licensee holds when a source separately licenses rights (e.g. a TDM, derivative, or distribution license) that the public usage-license verdict reports as restricted. This is the mirror image of the public OpenControls Usage License: the verdict says what the world may do; a grant says what one named grantee may ADDITIONALLY do. It is layered on the public verdict for that grantee only and can only OPEN rights for the holder — it never restricts further and never changes another party's verdict. A grant is authoritative only when explicitly provided and verified; it is never inferred. Held locally by the grantee; optionally registered with OpenControls as a verifiable record that confirms possession without exposing terms. Sibling vocabulary to opencontrolsusagelicensev1; reuses its rights keys and condition codes. Not legal advice.Download
- Glossary.jsonA framework-scoped glossary: the set of terms a specific authority (a regulation, standard, or framework) defines, with the sense each term carries inside that authority's text. The same term may appear in many glossaries with different senses; a glossary records what one authority means, not what a word means in general.Download
- Thesaurus.jsonA thesaurus of semantic relations between terms, expressed as SKOS-style links. Where the dictionary records what a term is and the glossary records what an authority means by it, the thesaurus records how terms relate to each other: broader, narrower, related, and exact-match concepts.Download
RegGenome
- RgBibtexCitation.jsonDownload
- Reggenomedocumentmetadata.jsonSchema describing every property RegGenome emits for a corpus document in all-documents.json. Derived by walking 8,865 records on 2026-06-09. Source file: Nexus/06 – Engineering/Data Files/all-documents.json. Every record is a flat object at the top level (no nested arrays of records). All fields except `processed` and the deeper sector levels are present in 100% of records.Download