Conformance Levels

Tools do not need to support every feature. OLS v1.0 defines conformance levels so apps can honestly state what they implement.

{
  "conformance": {
    "ols": "1.0.0",
    "levels": ["L0", "L1", "L2", "L5", "L7"],
    "profiles": ["eotc.v1"],
    "unsupported": ["service-instance", "audio-assets"]
  }
}

Make Claims Auditable

A conformance declaration describes implemented capabilities, not the completeness or authority of a particular corpus. Tools should publish the declaration with their version and test results.

The unsupported list is important even when levels are declared. It prevents a consumer from assuming that a validator, editor, or renderer supports every optional entity associated with a profile.

Conformance testing should include schema validation, reference resolution, deterministic calendar fixtures, and round-trip tests for every claimed profile feature.