Skip to content
emergent engineering

CASE 1.1 — certification dossier

Generated by bun run conformance:render — do not edit by hand.

Point-by-point certification submission: every conformance requirement against the literal published schema (conform-ed ADR-0013), with emergent’s implementation status, the spec citation, the modelled schema anchors, and the verifying evidence (emergent ADR-0028).

  • Denominator: pinned Coverage Map docs/conformance/maps/case-v1.1.json (generated 2026-06-22), sha256 69179fa2cb04878043ed204f8138fa667b0b17b482cf04c06a02ef3017b0dbdc.
  • Requirements: 9/9 done across 3 profile(s) — consumer, core, provider.
  • Information model: 264/344 literal items modelled.
  • Evidence: each claim cites its [covers:] evidence key; run bun run conformance:prove to resolve these to the proving test names for a submission copy.

Profile: consumer — 2/2 done

Section titled “Profile: consumer — 2/2 done”
Req Level Status Statement Verified by / justification Spec source
CASE-CONS-1 MUST ✅ done A Service Consumer MUST persistently store (‘handle’) every REQUIRED data field it receives and be able to recover it on retrieval. case:1.1:conf:consumer/CASE-CONS-1 CASE 1.1 Cert §Service Consumer (handle required fields) — https://www.imsglobal.org/spec/case/v1p1/cert/
CASE-CONS-2 MUST ✅ done A Service Consumer MUST tolerate the presence of extension data fields without failing the import. case:1.1:conf:consumer/CASE-CONS-2 CASE 1.1 Cert §Service Consumer (tolerate extensions) — https://www.imsglobal.org/spec/case/v1p1/cert/
Modelled schema anchors
  • CASE-CONS-1 → case:1.1:doc:cfdocument/identifier, case:1.1:doc:cfdocument/title, case:1.1:doc:cfitem/identifier, case:1.1:doc:cfitem/fullStatement, case:1.1:doc:cfassociation/associationType, case:1.1:doc:cfassociation/originNodeURI, case:1.1:doc:cfassociation/destinationNodeURI
  • CASE-CONS-2 → case:1.1:doc:cfitem/extensions, case:1.1:doc:cfdocument/extensions, case:1.1:doc:cfassociation/extensions

Profile: core — 4/4 done

Section titled “Profile: core — 4/4 done”
Req Level Status Statement Verified by / justification Spec source
CASE-1 MUST ✅ done A CFPackage MUST contain exactly one CFDocument describing the framework. case:1.1:conf:core/CASE-1 CASE 1.1 §CFPackage — https://www.imsglobal.org/spec/case/v1p1
CASE-2 MUST ✅ done Every CFItem MUST be identified by a globally unique identifier (a UUID). case:1.1:conf:core/CASE-2 CASE 1.1 §CFItem — https://www.imsglobal.org/spec/case/v1p1
CASE-3 MUST ✅ done Every CFAssociation MUST declare its associationType and both its origin and destination nodes. case:1.1:conf:core/CASE-3 CASE 1.1 §CFAssociation — https://www.imsglobal.org/spec/case/v1p1
CASE-4 MUST ✅ done The caseVersion attribute, when present on a CFDocument, MUST have the value ‘1.1’. case:1.1:conf:core/CASE-4 CASE 1.1 §CFDocument (caseVersion) — https://www.imsglobal.org/spec/case/v1p1
Modelled schema anchors
  • CASE-1 → case:1.1:doc:cfpackage/CFDocument
  • CASE-2 → case:1.1:doc:cfitem/identifier
  • CASE-3 → case:1.1:doc:cfassociation/associationType, case:1.1:doc:cfassociation/originNodeURI, case:1.1:doc:cfassociation/destinationNodeURI
  • CASE-4 → case:1.1:doc:cfdocument/caseVersion, case:1.1:def:CFDocument/caseVersion, case:1.1:def:CFPckgDocument/caseVersion

Profile: provider — 3/3 done

Section titled “Profile: provider — 3/3 done”
Req Level Status Statement Verified by / justification Spec source
CASE-PROV-1 MUST ✅ done A Service Provider MUST supply every REQUIRED data field in the JSON payload of each served entity (a CFDocument’s identifier/uri/title/creator/lastChangeDateTime; a CFItem’s identifier/uri/fullStatement; a CFAssociation’s identifier/uri/associationType and origin/destination node references). case:1.1:conf:provider/CASE-PROV-1 CASE 1.1 Cert §Service Provider (required data fields) — https://www.imsglobal.org/spec/case/v1p1/cert/
CASE-PROV-2 MUST ✅ done A Service Provider MUST be capable of supplying every OPTIONAL data field defined for the entities it serves (e.g. a CFItem’s humanCodingScheme and CFItemType, a CFDocument’s officialSourceURL). case:1.1:conf:provider/CASE-PROV-2 CASE 1.1 Cert §Service Provider (optional data fields) — https://www.imsglobal.org/spec/case/v1p1/cert/
CASE-PROV-3 MUST ✅ done A Service Provider MUST NOT include extension data fields in conformance-tested payloads (the extensions point is forbidden for Provider certification). case:1.1:conf:provider/CASE-PROV-3 CASE 1.1 Cert §Service Provider (no extension fields) — https://www.imsglobal.org/spec/case/v1p1/cert/
Modelled schema anchors
  • CASE-PROV-1 → case:1.1:doc:cfdocument/identifier, case:1.1:doc:cfdocument/uri, case:1.1:doc:cfdocument/title, case:1.1:doc:cfdocument/creator, case:1.1:doc:cfdocument/lastChangeDateTime, case:1.1:doc:cfitem/identifier, case:1.1:doc:cfitem/uri, case:1.1:doc:cfitem/fullStatement, case:1.1:doc:cfassociation/identifier, case:1.1:doc:cfassociation/uri, case:1.1:doc:cfassociation/associationType, case:1.1:doc:cfassociation/originNodeURI, case:1.1:doc:cfassociation/destinationNodeURI
  • CASE-PROV-2 → case:1.1:doc:cfitem/humanCodingScheme, case:1.1:doc:cfitem/CFItemType, case:1.1:doc:cfdocument/officialSourceURL
  • CASE-PROV-3 → case:1.1:doc:cfdocument/extensions, case:1.1:doc:cfitem/extensions, case:1.1:doc:cfassociation/extensions