Explanations

• Element names and the shared namespace nobody has checked this yet, still a draft
  Why the OSCAL schema names its elements as it does: OSCAL’s own keys as slot names (last-modified, and class_ for OSCAL’s class), UpperCamelCase classes and enums, and every element under oscal:; and why its adapt copy gives LOKF’s Role, Parameter, Citation and Revision an Oscal prefix and seventeen keys an oscal_ one, and shares seven keys (attestations, dependencies, parties, provenance, subject, value, actions) with slsa’s and github-actions’ copies under another IRI.

• Scope, influences and mappings nobody has checked this yet, still a draft
  What the OSCAL schema renders and leaves out, and why: OSCAL 1.2.3’s eight models as NIST’s metaschema defines them, no influence beyond OSCAL apart from lmodel/slsa’s module layout, release asset and governance files, no mapping yet to another vocabulary, and the metaschema constraints it does not check (index, index-has-key, is-unique, expect and has-cardinality).