Roadmap¶

Done¶

v0.1: initial starter: definitions, principles, practices, Semantic Authority
v0.2: practices made independently adoptable
v0.3: machine-readable reference and CLI (since moved to reference/)
v0.4.x: discipline framing, perspectives, gross margin example, Semantic Contracts, contracts in context, licensing, consistency and plain-language passes; published at github.com/Semantic-Management/framework
v0.5.0: Apache Ossie alignment, Binding provenance and drift fields, contributor backlog

[x] License: CC BY 4.0 (framework and docs) and Apache-2.0 (reference code). See LICENSING.md
[ ] Owner review of the neighbor-discipline hand-offs (docs/discipline.md), especially MDM and model risk management (#13)
[ ] Practitioner notes on each practice from real (anonymized) experience (#14)
[ ] Second worked example outside finance (e.g., "Active Customer" or "Region") (#16)
[ ] One-page executive brief and slide version of the discipline story (#17)
[ ] Formal name and trademark check for "Semantic Management Framework"; short naming and usage policy (#15)

Maturity model assessed per practice, so partial adoption is a valid state, derived from closed gaps in the gap catalogue rather than self-assessment
A workbench that renders the metamodel for an organization's own files, shows gaps as missing connections, and writes only SMF documents and patches to other standards' files (no catalog of its own)
Crosswalks to DAMA-DMBOK, ISO/IEC 42001, NIST AI RMF and COBIT
Reference patterns: catalog-centric, semantic-layer-centric, open-source stack (drafted)
Upstream conversations: ODCS (Bitol), Apache Ossie, OpenLineage and Egeria, about referencing Metric Contracts and perspectives (for Ossie: a native pointer to a governing definition, in place of the custom_extensions convention)
Field testing with two or three organizations of different sizes