Skip to content
This repository was archived by the owner on Apr 14, 2026. It is now read-only.
This repository was archived by the owner on Apr 14, 2026. It is now read-only.

In functionalities.json, at the functionality level, remove level keys and ensure requirements array is always present #7

Description

@basicavisual

What:
On https://github.com/GovStackWorkingGroup/machine-readable-specs/pull/6/changes @categulario proposed adding empty arrays for functionalities on CFRs that did not have requirements. Example here.

This is issue is a proposal to apply the same pattern on functionalities.json

In practice that would mean that functionality is either informative or declarative and is not to be tested against.

Example of how this is implemented in functionalities.json:

    {
      "identifier": "https://wallet.govstack.global/spec/1/kdf/10",
      "link": "https://wallet.govstack.global/4-key-digital-functionalities#id-4.6.5.-complaint-submission-to-supervisory-body",
      "title": "Complaint Submission to Supervisory Body",
      "content": "The wallet must provide a mechanism for users to submit complaints about a verifier to the respective supervisory body.",
      "requirements": []
    }

Why:

The current pattern on functionalities.json was that some functionalities did not have requirements and some have. This was resolved by adding a level key of either RECOMMENDED or REQUIRED. However this is less mantainable than just adding a requirements array in every case and just leave it empty whenever there aren't any requirements for that functionality.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions