MatJSON Core
Shared values, units, provenance, expressions, selectors, citations, identifiers, vocabularies, and extension rules.
v0.1 · Working draftExplore CoreThe open standard for materials data in JSON
MatJSON defines interoperable schemas for material specifications, application requirements, evidence records, and compliance results—structured for APIs, automation, and AI.
Example: synthetic-alloy.matspec.json
1{
2"matspec": "0.2",
3"specification": {
4"designation": "MJ-100",
5"organization": "MatJSON Examples",
6"title": "Synthetic Alloy Plate",
7"edition": "2026"
8},
9"grades": [
10{
11"id": "MJ-100-A"
12}
13]
14}
The MatJSON schema suite
Five complementary profiles establish one material-data lifecycle—from a governing specification to auditable compliance results.
MatSpecJSON
Intrinsic requirements of a material or product specification, including acceptance limits, tests, certification, and marking.
v0.2.10 · Working draftExplore MatSpecMatReqJSON
Additional requirements imposed by codes, service standards, equipment standards, fabrication practices, and purchaser specifications.
v0.2 · Working draftExplore MatReqMatRecordJSON
Normalized representation of MTRs, CMTRs, material certificates, test reports, and supporting evidence.
v0.1 · Working draftExplore MatRecordMatCheckJSON
Machine-readable compliance outcomes that preserve requirement origin, evidence, comparison, and review status.
v0.1 · Working draftExplore MatCheckInteroperableConsistent structures support exchange across tools, organizations, and industries.
TraceableBuilt-in provenance and citations preserve the origin of every requirement and result.
ExtensibleNamespaced extension points let domains add requirements without fragmenting the core.
AutomatableDesigned for APIs, validators, workflow engines, analytics, and AI applications.
One requirements stack, preserved end to end
MatJSON keeps intrinsic material criteria, application overlays, purchaser requirements, evidence, and evaluation results separate—but interoperable.
01
MatSpec
Defines what the material or product specification intrinsically requires.
02
MatReq
Adds service, code, equipment, fabrication, and purchaser requirements.
03
Requisition
Invokes standards, resolves purchaser decisions, and adds project-specific criteria.
04
MatRecord
Normalizes MTRs, CMTRs, test reports, and supporting evidence.
05
MatCheck
Returns traceable pass, fail, gap, missing-evidence, or manual-review outcomes.
Protocol, not a database
Publish once. Process everywhere.
MatJSON standardizes how materials data is represented so that any conforming publisher or consumer can use the same parsers, APIs, validators, and automation scripts.
- Separate source-document edition from MatJSON profile version.
- Preserve source normativity, project activation, applicability, and evidence.
- Keep proprietary standards data separate from open schemas and synthetic examples.
- Distinguish schema validity from independent engineering verification.
Canonical public surface
/schema/Immutable, versioned JSON Schema files and `latest` convenience paths.
/profiles/Human-readable documentation for each MatJSON profile.
/registry/Canonical identifiers, package metadata, edition history, and access policy.
/examples/Original synthetic examples that are safe to share and test publicly.
/tools/Validator, CLI, SDK, resolver, and compliance tooling roadmap.
Roadmap
All five MatJSON profiles are now working drafts. Current work focuses on real-world validation, stable requirement identity, and converging genuinely shared semantics into MatJSON Core.
MatSpecJSON
Working draft v0.2.10. Continue completeness audits, formula semantics, and stable atomic requirement identity.
MatReqJSON
Working draft v0.2. Continue effective-requirement resolution, decision graphs, and project-input semantics.
MatRecordJSON
Working draft v0.1. Validate normalization across diverse MTR, CMTR, laboratory, NDE, and process evidence packages.
MatCheckJSON
Working draft v0.1. Exercise auditable resolution and evidence comparison across real material-review workflows.
Start with the architecture, then implement the profile.
Download the preserved project context, current schemas, and synthetic examples from this starter site.