Compliance Levels for FACET-related Implementations
This article defines compliance levels for FACET-related implementations, allowing the ecosystem to distinguish partial integrations from full implementations and set clear expectations for enterprise use.
Why it matters
Defining clear compliance levels is crucial for the FACET ecosystem to ensure interoperability, trust, and evolution of the standard.
Key Points
- 1FACET defines four compliance levels: Conceptual (L0), Structural (L1), Deterministic (L2), and Reference (L3)
- 2Compliance levels are declarative and auditable, and components must declare their compliance level
- 3Adapters have their own compliance axis, with L1 for structural mapping and L2 for deterministic mapping
- 4Claiming a higher compliance level than implemented is considered a specification violation
Details
The article outlines the purpose of compliance levels, which is to distinguish partial FACET integrations from full implementations, avoid false claims of determinism, set clear expectations for enterprise use, and evolve the standard without breaking attribution or trust. It defines four compliance levels: L0 (Conceptual) for documentation and ideas only, L1 (Structural) for canonical JSON and schema adherence, L2 (Deterministic) for full determinism and reproducibility, and L3 (Reference) for spec-complete, reference-grade implementations. The article also discusses adapter compliance, where adapters can be L1 or L2 compliant, and the importance of accurately representing compliance levels to avoid misrepresentation.
No comments yet
Be the first to comment