Governance

A transparent path from working drafts to reviewed, interoperable, cross-industry specifications.

RFC processEngineering reviewOpen implementation

Initial roles

  • MatJSON editor
  • Technical reviewers
  • Implementation contributors
  • Industry advisory group

RFC process

Major semantic changes should be documented through short, versioned MatJSON RFCs or architecture decision records.

MJ-RFC-0001 Core terminology and profiles
MJ-RFC-0002 Units and quantities
MJ-RFC-0003 Rule applicability expressions
MJ-RFC-0004 Source-document invocation
MJ-RFC-0005 Compliance evidence model

Review levels

Technical review should be traceable to a reviewer, source edition, scope, and date. Automated extraction and schema validation cannot substitute for independent engineering review.

Proposed licensing

AssetProposed direction
Schemas and softwareApache License 2.0
Specification and vocabulariesCC BY 4.0 or approved equivalent
Synthetic examplesCC0 or CC BY 4.0
Standards-derived packagesGoverned by source rights and access policy
This is a proposed licensing model, not legal advice or a finalized project license.