Skip to content

Welcome to the Functional Conformance Assessment Framework

This website documents the Functional Conformance Assessment Framework (FCAF) for the European Digital Identity Wallet ecosystem.

The FCAF provides a harmonised approach for defining and applying functional conformance test cases and framework content to support wallet certification and improve interoperability across Member States.

⚠️ Status: This documentation contains content under active development.

Content is published early to enable feedback, structured review, and iterative refinement. Individual releases may provide implementation-ready subsets of functionality, but may not yet cover the full scope of the framework. Content progresses through defined maturity stages:

  • Submitted - latest working draft; not yet suitable for implementation; may contain errors
  • Reviewed (beta) - technically correct and implementable in isolation
  • Release candidate (RC) - consolidated and suitable for validation and pilot use
  • Released baseline - stable for its defined scope and suitable for regulatory use in certification

Individual releases may provide implementation-ready subsets of functionality, but may not yet cover the full scope of the framework.

The documentation includes:

  • High-level introduction to functional conformance testing and its scope
  • Description of the FCAF framework content (e.g. structure, test specifications, test books, configuration data, traceability, and guidance)
  • The initial System Under Test (SUT): Wallet Solution
  • Templates used to create consistent test cases across components
  • An indicative roadmap

The FCAF evolves through incremental and iterative releases, with quality and coverage increasing towards v1.0.0, which will define the first full-scope baseline suitable for certification.

Contributing

Please read CONTRIBUTING.md in the source repository for details on our code of conduct, and the process for contributing to the FCAF.

Authors

See the list of contributors who participated in this project.

Versioning & changelog

SemVer is used for versioning. For available versions, see the tags on this repository.

Two changelogs are kept:

  • Framework & site changelog - build, MkDocs configuration, styling, templates and other scaffolding (version-based).
  • FCAF changelog - changes to the test-case content itself, recorded per maturity stage.

Versioning reflects both coverage (vX.Y.Z) and maturity (beta, release candidate, released baseline):

  • v0.0.x - Bootstrap phase (structure, orientation, initial content)

  • vX.Y.Z-beta.n - Reviewed content

  • technically correct and implementable in isolation

  • may not yet be fully consistent or consolidated across all layers

  • vX.Y.Z-rc.n - Release candidate

  • consolidated across applicable specifications, profiles, and regulatory layers

  • suitable for implementation, validation, and pilot use

  • vX.Y.Z - Released baseline

  • stable and sufficiently validated for its defined scope
  • suitable for implementation and conformance assessment

The v0.X.Y series represents iterative development, where coverage is expanded incrementally across functional areas.

Individual releases in this phase may contain implementation-ready subsets of functionality, but do not yet represent the full scope of the framework.

The v1.0.0 release will represent the first full-scope baseline that is:

  • stable,
  • sufficiently validated, and
  • suitable for certification.

For versions with major version 0, the framework is under active development and minor and patch releases may introduce changes, including structural or interpretative refinements.

Stability expectations apply to all released baselines (vX.Y.Z), which are considered stable for their defined scope.

License

See the LICENSE.md file details.