diff --git a/.editorconfig b/.editorconfig
new file mode 100644
index 0000000..c764a92
--- /dev/null
+++ b/.editorconfig
@@ -0,0 +1,22 @@
+# EditorConfig is awesome: https://EditorConfig.org
+
+# top-most EditorConfig file
+root = true
+
+[*]
+line_length = 120
+indent_style = space
+indent_size = 4
+end_of_line = lf
+charset = utf-8
+trim_trailing_whitespace = true
+insert_final_newline = true
+
+[*.md]
+trim_trailing_whitespace = false
+
+[*.{yml,yaml,json,js,html}]
+indent_size = 2
+
+[LICENSE]
+insert_final_newline = false
diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS
new file mode 100644
index 0000000..c0508e9
--- /dev/null
+++ b/.github/CODEOWNERS
@@ -0,0 +1 @@
+* @MinBZK/ai-validation-team
diff --git a/.github/ISSUE_TEMPLATE/1-bug.yml b/.github/ISSUE_TEMPLATE/1-bug.yml
new file mode 100644
index 0000000..d6eea3a
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/1-bug.yml
@@ -0,0 +1,59 @@
+name: Bug Report
+description: Let us know about an unexpected error, a crash, or an incorrect behavior.
+labels: ["bug", "triage"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+       # Thank you for opening an issue.
+
+        ## Filing a bug report
+
+        To fix problems, we need clear reproduction cases. Please fill in the bug report as exact as possible to help us resolve the issue.
+
+  - type: textarea
+    id: version
+    attributes:
+      label: Version
+      description: Specify the version of the software that you use
+      placeholder: 0.1.0
+      value:
+    validations:
+      required: true
+
+  - type: textarea
+    id: expected
+    attributes:
+      label: Expected Behavior
+      description: What should have happened?
+      placeholder: What should have happened?
+      value:
+    validations:
+      required: true
+
+  - type: textarea
+    id: actual
+    attributes:
+      label: Actual Behavior
+      description: What actually happened?
+      placeholder: What actually happened?
+      value:
+    validations:
+      required: true
+
+  - type: textarea
+    id: context
+    attributes:
+      label: Additional Context
+      description: |
+        Are there anything atypical about your situation that we should know?
+      placeholder: Additional context...
+      value:
+    validations:
+      required: false
+
+
+  - type: markdown
+    attributes:
+      value: |
+        **Note:** If the submit button is disabled and you have filled out all required fields, please check that you did not forget a **Title** for the issue.
diff --git a/.github/ISSUE_TEMPLATE/2-feature.yml b/.github/ISSUE_TEMPLATE/2-feature.yml
new file mode 100644
index 0000000..1c9594f
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/2-feature.yml
@@ -0,0 +1,49 @@
+name: Feature Request
+description: Suggest a new feature or other enhancement.
+labels: ["enhancement", "triage"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        # Thank you for opening a feature request.
+
+  - type: textarea
+    id: version
+    attributes:
+      label: Version
+      description: Specify the version of the software that you use
+      placeholder: 0.1.0
+      value:
+    validations:
+      required: true
+
+  - type: textarea
+    id: use-case
+    attributes:
+      label: Use Cases
+      description: |
+        In order to properly evaluate a feature request, it is necessary to understand the use cases for it.
+        Please describe below the _end goal_ you are trying to achieve that has led you to request this feature.
+        Please keep this section focused on the problem and not on the suggested solution. We'll get to that in a moment, below!
+      placeholder:
+      value:
+    validations:
+      required: true
+
+  - type: textarea
+    id: proposal
+    attributes:
+      label: Proposal
+      description: |
+          If you have an idea for a way to address the problem via a change to our product features, please describe it below.
+          If you're not sure of some details, don't worry! When we evaluate the feature request we may suggest modifications as necessary to work within the design constraints of OpenTofu Core.
+      placeholder:
+      value:
+    validations:
+      required: false
+
+
+  - type: markdown
+    attributes:
+      value: |
+        **Note:** If the submit button is disabled and you have filled out all required fields, please check that you did not forget a **Title** for the issue.
diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml
new file mode 100644
index 0000000..3ba13e0
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/config.yml
@@ -0,0 +1 @@
+blank_issues_enabled: false
diff --git a/.github/dependabot.yml b/.github/dependabot.yml
new file mode 100644
index 0000000..d24384c
--- /dev/null
+++ b/.github/dependabot.yml
@@ -0,0 +1,29 @@
+version: 2
+updates:
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+      day: "monday"
+      time: "08:00"
+      timezone: "Europe/Amsterdam"
+    labels:
+      - "dependencies"
+    groups:
+      allgithubactions:
+        patterns:
+        - "*"
+
+  - package-ecosystem: "pip"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+      day: "monday"
+      time: "08:00"
+      timezone: "Europe/Amsterdam"
+    labels:
+      - "dependencies"
+    groups:
+      allpippackages:
+        patterns:
+        - "*"
diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
new file mode 100644
index 0000000..068812e
--- /dev/null
+++ b/.github/pull_request_template.md
@@ -0,0 +1,19 @@
+# Description
+
+Describe in detail the changes you are proposing, and the rationale.
+
+Link all GitHub issues fixed by this PR.
+Make sure to first open an issue, get community approval and only then create Pull Request to resolve it.
+All Pull Requests must have an issue attached to them
+
+Resolves #
+
+## Checklist
+
+Please check all the boxes that apply to this pull request using "x":
+
+- [ ]  I have tested the changes locally and verified that they work as expected.
+- [ ]  I have followed the project's coding conventions and style guidelines.
+- [ ]  I have rebased my branch onto the latest commit of the main branch.
+- [ ]  I have squashed or reorganized my commits into logical units.
+- [ ]  I have read, understood and agree to the [Developer Certificate of Origin](../blob/main/DCO.md), which this project utilizes.
diff --git a/.github/release.yml b/.github/release.yml
new file mode 100644
index 0000000..14adb4d
--- /dev/null
+++ b/.github/release.yml
@@ -0,0 +1,16 @@
+changelog:
+  exclude:
+    labels:
+      - ignore-for-release
+    authors:
+      - dependabot[bot]
+  categories:
+    - title: Breaking Changes 🛠
+      labels:
+        - breaking-change
+    - title: Exciting New Features 🎉
+      labels:
+        - enhancement
+    - title: Other Changes
+      labels:
+        - "*"
diff --git a/.github/workflows/automerge.yml b/.github/workflows/automerge.yml
new file mode 100644
index 0000000..210ba78
--- /dev/null
+++ b/.github/workflows/automerge.yml
@@ -0,0 +1,31 @@
+name: AutoMerge
+on: pull_request
+
+
+jobs:
+  automerge:
+    runs-on: ubuntu-latest
+    if: github.actor == 'dependabot[bot]'
+    permissions:
+      contents: write
+      pull-requests: write
+    steps:
+      - name: Dependabot metadata
+        id: metadata
+        uses: dependabot/fetch-metadata@v2
+        with:
+          github-token: "${{ secrets.GITHUB_TOKEN }}"
+
+      - name: Enable Auto-Approve for Dependabot PRs
+        if: steps.metadata.outputs.update-type == 'version-update:semver-minor' || steps.metadata.outputs.update-type == 'version-update:semver-patch'
+        run: gh pr review --approve "$PR_URL"
+        env:
+          PR_URL: ${{github.event.pull_request.html_url}}
+          GH_TOKEN: ${{secrets.GITHUB_TOKEN}}
+
+      - name: Enable auto-merge for Dependabot PRs
+        if: steps.metadata.outputs.update-type == 'version-update:semver-minor' || steps.metadata.outputs.update-type == 'version-update:semver-patch'
+        run: gh pr merge --auto --merge "$PR_URL"
+        env:
+          PR_URL: ${{github.event.pull_request.html_url}}
+          GH_TOKEN: ${{secrets.GITHUB_TOKEN}}
diff --git a/.github/workflows/codeql.yml b/.github/workflows/codeql.yml
new file mode 100644
index 0000000..dde4191
--- /dev/null
+++ b/.github/workflows/codeql.yml
@@ -0,0 +1,38 @@
+name: "CodeQL"
+
+on:
+  push:
+    branches: [ "main" ]
+  pull_request:
+    branches: [ "main" ]
+
+jobs:
+  analyze:
+    name: Analyze (${{ matrix.language }})
+    runs-on: 'ubuntu-latest'
+    timeout-minutes: 360
+    permissions:
+      security-events: write
+      packages: read
+      actions: read
+      contents: read
+    strategy:
+      fail-fast: false
+      matrix:
+        include:
+        - language: python
+          build-mode: none
+    steps:
+    - name: Checkout repository
+      uses: actions/checkout@v4
+
+    - name: Initialize CodeQL
+      uses: github/codeql-action/init@v3
+      with:
+        languages: ${{ matrix.language }}
+        build-mode: ${{ matrix.build-mode }}
+
+    - name: Perform CodeQL Analysis
+      uses: github/codeql-action/analyze@v3
+      with:
+        category: "/language:${{matrix.language}}"
diff --git a/.github/workflows/first-interaction.yml b/.github/workflows/first-interaction.yml
new file mode 100644
index 0000000..0ea633c
--- /dev/null
+++ b/.github/workflows/first-interaction.yml
@@ -0,0 +1,22 @@
+name: Greetings
+
+on: [pull_request, issues]
+
+jobs:
+  greeting:
+    runs-on: ubuntu-latest
+    permissions:
+      issues: write
+      pull-requests: write
+    steps:
+      - uses: actions/first-interaction@v1
+        with:
+          repo-token: ${{ secrets.GITHUB_TOKEN }}
+          issue-message: |
+            Welcome to our community :hugs: and thank you for your first contribution.
+
+            As a first time contributor please make sure to review our [contribution guidelines](../blob/main/CONTRIBUTING.md) :heart:
+          pr-message: |
+            Welcome to our community :hugs: and thank you for your first contribution.
+
+            As a first time contributor please make sure to review our [contribution guidelines](../blob/main/CONTRIBUTING.md) :heart:
diff --git a/.github/workflows/stale.yml b/.github/workflows/stale.yml
new file mode 100644
index 0000000..052e75f
--- /dev/null
+++ b/.github/workflows/stale.yml
@@ -0,0 +1,22 @@
+name: "Close stale"
+on:
+  schedule:
+    - cron: "0 4 * * *"
+  workflow_dispatch:
+
+jobs:
+  stale:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write # only for delete-branch option
+      issues: write
+      pull-requests: write
+    steps:
+      - uses: actions/stale@v9
+        with:
+          days-before-stale: 90
+          days-before-close: 30
+          stale-issue-message: "This issue did not have any activity in the last 90 days and will be removed after 30 days"
+          stale-pr-message: "This PR did not have any activity in the last 90 days and will be removed after 30 days"
+          close-pr-message: "This PR is closed due to inactivity"
+          close-issue-message: "This issue is closed due to inactivity"
diff --git a/.gitignore b/.gitignore
new file mode 100644
index 0000000..563569c
--- /dev/null
+++ b/.gitignore
@@ -0,0 +1,23 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+
+# Unit test / coverage reports
+.coverage
+.coverage.*
+coverage.xml
+htmlcov/
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Environments
+.venv
+
+# pytest
+.pytest_cache/
+
+# ruff linter
+.ruff_cache/
diff --git a/.pre-commit-config.yaml b/.pre-commit-config.yaml
new file mode 100644
index 0000000..0f092f1
--- /dev/null
+++ b/.pre-commit-config.yaml
@@ -0,0 +1,25 @@
+default_language_version:
+  python: python3.11
+repos:
+  - repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v4.5.0
+    hooks:
+      - id: end-of-file-fixer
+      - id: trailing-whitespace
+      - id: check-yaml
+      - id: check-json
+      - id: check-toml
+      - id: check-added-large-files
+      - id: check-merge-conflict
+      - id: check-toml
+      - id: detect-private-key
+  - repo: https://github.com/astral-sh/ruff-pre-commit
+    rev: v0.3.3
+    hooks:
+      - id: ruff
+      - id: ruff-format
+
+ci:
+  autofix_prs: false
+  autofix_commit_msg: "Auto fix pre-commit.com hooks"
+  autoupdate_commit_msg: "Update .pre-commit-config.yaml"
diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
new file mode 100644
index 0000000..55ab792
--- /dev/null
+++ b/CODE_OF_CONDUCT.md
@@ -0,0 +1,63 @@
+# Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to make participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, nationality, personal
+appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+advances
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, or to ban
+temporarily or permanently any contributor for other behaviors that they deem
+inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
new file mode 100644
index 0000000..3a0007e
--- /dev/null
+++ b/CONTRIBUTING.md
@@ -0,0 +1,107 @@
+# Contributing
+
+First off, thanks for taking the time to contribute! ❤️
+
+All types of contributions are encouraged and valued. See the [Table of Contents](#table-of-contents) for different ways
+to help and details about how this project handles them. Please make sure to read the relevant section before making your
+contribution. It will make it a lot easier for us maintainers and smooth out the experience for all involved. The
+community looks forward to your contributions. 🎉
+
+## Table of Contents
+
+- [Code of Conduct](#code-of-conduct)
+- [I Have a Question](#i-have-a-question)
+- [I Want To Contribute](#i-want-to-contribute)
+- [Reporting Bugs](#reporting-bugs)
+- [Suggesting Enhancements](#suggesting-enhancements)
+
+## Code of Conduct
+
+This project and everyone participating in it is governed by the
+[Code of Conduct](CODE_OF_CONDUCT.md).
+By participating, you are expected to uphold this code. Please report unacceptable behavior to the maintainers.
+
+## I Have a Question
+
+Before you ask a question, it is best to search for existing [Issues](../../issues/)
+that might help you. In case you have found a suitable issue and still need clarification, you can write your question
+in this issue.
+
+If you then still feel the need to ask a question and need clarification, we recommend the following:
+
+- Open an [Issue](../../issues/new).
+- Provide as much context as you can about what you're running into.
+
+We will then take care of the issue as soon as possible.
+
+## I Want To Contribute
+
+> ### Legal Notice
+>
+> When contributing to this project, you must agree that you have authored 100% of the content, that you have the
+necessary rights to the content and that the content you contribute may be provided under the project license.
+
+### Reporting Bugs
+
+#### Before Submitting a Bug Report
+
+A good bug report shouldn't leave others needing to chase you up for more information. Therefore, we ask you to
+investigate carefully, collect information and describe the issue in detail in your report. Please complete the
+following steps in advance to help us fix any potential bug as fast as possible.
+
+- Make sure that you are using the latest version.
+- To see if other users have experienced (and potentially already solved) the same issue you are having, check if there
+is not already a bug report existing for your bug or error in the [bug tracker](../..//issues?q=label%3Abug).
+- Collect information about the bug
+- Possibly your input and the output
+
+#### How Do I Submit a Good Bug Report?
+
+> You must never report security related issues, vulnerabilities or bugs including sensitive information to the issue
+tracker, or elsewhere in public. Instead sensitive bugs must be sent to NCSC. See [Security](SECURITY.md).
+
+We use GitHub issues to track bugs and errors. If you run into an issue with the project:
+
+- Open an [Issue](../../issues/new). (Since we can't be sure at this point whether it
+is a bug or not, we ask you not to talk about a bug yet and not to label the issue.)
+- Explain the behavior you would expect and the actual behavior.
+- Please provide as much context as possible and describe the *reproduction steps* that someone else can follow to
+recreate the issue on their own. This usually includes your code.
+- Provide the information you collected in the previous section.
+
+Once it's filed:
+
+- The project team will label the issue accordingly.
+- A team member will try to reproduce the issue with your provided steps. If there are no reproduction steps or no
+obvious way to reproduce the issue, the team will ask you for those steps and mark the issue as `needs-repro`. Bugs with
+the `needs-repro` tag will not be addressed until they are reproduced.
+- If the team is able to reproduce the issue, it will be marked `needs-fix`, as well as possibly other tags (such as
+`critical`), and the issue will be left to be implemented by someone.
+
+### Suggesting Enhancements
+
+This section guides you through submitting an enhancement suggestion for this project, **including completely new
+features and minor improvements**. Following these guidelines will help maintainers and the
+community to understand your suggestion and find related suggestions.
+
+#### Before Submitting an Enhancement
+
+- Make sure that you are using the latest version.
+- Perform a [search](../../issues) to see if the enhancement has already been
+suggested. If it has, add a comment to the existing issue instead of opening a new one.
+- Find out whether your idea fits with the scope and aims of the project. It's up to you to make a strong case to
+convince the project's developers of the merits of this feature. Keep in mind that we want features that will be useful
+to the majority of our users and not just a small subset.
+
+#### How Do I Submit a Good Enhancement Suggestion?
+
+Enhancement suggestions are tracked as [GitHub issues](../../issues).
+
+- Use a **clear and descriptive title** for the issue to identify the suggestion.
+- **Describe the current behavior** and **explain which behavior you expected to see instead** and why. At this point
+you can also tell which alternatives do not work for you.
+- You may want to **include screenshots and animated GIFs** which help you demonstrate the steps or point out the part
+which the suggestion is related to. You can use [this tool](https://www.cockos.com/licecap/) to record GIFs on MacOS and
+ Windows, and [this tool](https://github.com/colinkeenan/silentcast) or [this tool](https://github.com/GNOME/byzanz) on Linux.
+- **Explain why this enhancement would be useful** for the community. You may also want to point out the
+other projects that solved it better and which could serve as inspiration.
diff --git a/LICENSE b/LICENSE
new file mode 100644
index 0000000..6d8cea4
--- /dev/null
+++ b/LICENSE
@@ -0,0 +1,190 @@
+EUROPEAN UNION PUBLIC LICENCE v. 1.2
+EUPL © the European Union 2007, 2016
+
+This European Union Public Licence (the ‘EUPL’) applies to the Work (as defined below) which is provided under the
+terms of this Licence. Any use of the Work, other than as authorised under this Licence is prohibited (to the extent such
+use is covered by a right of the copyright holder of the Work).
+The Work is provided under the terms of this Licence when the Licensor (as defined below) has placed the following
+notice immediately following the copyright notice for the Work:
+                          Licensed under the EUPL
+or has expressed by any other means his willingness to license under the EUPL.
+
+1.Definitions
+In this Licence, the following terms have the following meaning:
+— ‘The Licence’:this Licence.
+— ‘The Original Work’:the work or software distributed or communicated by the Licensor under this Licence, available
+as Source Code and also as Executable Code as the case may be.
+— ‘Derivative Works’:the works or software that could be created by the Licensee, based upon the Original Work or
+modifications thereof. This Licence does not define the extent of modification or dependence on the Original Work
+required in order to classify a work as a Derivative Work; this extent is determined by copyright law applicable in
+the country mentioned in Article 15.
+— ‘The Work’:the Original Work or its Derivative Works.
+— ‘The Source Code’:the human-readable form of the Work which is the most convenient for people to study and
+modify.
+— ‘The Executable Code’:any code which has generally been compiled and which is meant to be interpreted by
+a computer as a program.
+— ‘The Licensor’:the natural or legal person that distributes or communicates the Work under the Licence.
+— ‘Contributor(s)’:any natural or legal person who modifies the Work under the Licence, or otherwise contributes to
+the creation of a Derivative Work.
+— ‘The Licensee’ or ‘You’:any natural or legal person who makes any usage of the Work under the terms of the
+Licence.
+— ‘Distribution’ or ‘Communication’:any act of selling, giving, lending, renting, distributing, communicating,
+transmitting, or otherwise making available, online or offline, copies of the Work or providing access to its essential
+functionalities at the disposal of any other natural or legal person.
+
+2.Scope of the rights granted by the Licence
+The Licensor hereby grants You a worldwide, royalty-free, non-exclusive, sublicensable licence to do the following, for
+the duration of copyright vested in the Original Work:
+— use the Work in any circumstance and for all usage,
+— reproduce the Work,
+— modify the Work, and make Derivative Works based upon the Work,
+— communicate to the public, including the right to make available or display the Work or copies thereof to the public
+and perform publicly, as the case may be, the Work,
+— distribute the Work or copies thereof,
+— lend and rent the Work or copies thereof,
+— sublicense rights in the Work or copies thereof.
+Those rights can be exercised on any media, supports and formats, whether now known or later invented, as far as the
+applicable law permits so.
+In the countries where moral rights apply, the Licensor waives his right to exercise his moral right to the extent allowed
+by law in order to make effective the licence of the economic rights here above listed.
+The Licensor grants to the Licensee royalty-free, non-exclusive usage rights to any patents held by the Licensor, to the
+extent necessary to make use of the rights granted on the Work under this Licence.
+
+3.Communication of the Source Code
+The Licensor may provide the Work either in its Source Code form, or as Executable Code. If the Work is provided as
+Executable Code, the Licensor provides in addition a machine-readable copy of the Source Code of the Work along with
+each copy of the Work that the Licensor distributes or indicates, in a notice following the copyright notice attached to
+the Work, a repository where the Source Code is easily and freely accessible for as long as the Licensor continues to
+distribute or communicate the Work.
+
+4.Limitations on copyright
+Nothing in this Licence is intended to deprive the Licensee of the benefits from any exception or limitation to the
+exclusive rights of the rights owners in the Work, of the exhaustion of those rights or of other applicable limitations
+thereto.
+
+5.Obligations of the Licensee
+The grant of the rights mentioned above is subject to some restrictions and obligations imposed on the Licensee. Those
+obligations are the following:
+
+Attribution right: The Licensee shall keep intact all copyright, patent or trademarks notices and all notices that refer to
+the Licence and to the disclaimer of warranties. The Licensee must include a copy of such notices and a copy of the
+Licence with every copy of the Work he/she distributes or communicates. The Licensee must cause any Derivative Work
+to carry prominent notices stating that the Work has been modified and the date of modification.
+
+Copyleft clause: If the Licensee distributes or communicates copies of the Original Works or Derivative Works, this
+Distribution or Communication will be done under the terms of this Licence or of a later version of this Licence unless
+the Original Work is expressly distributed only under this version of the Licence — for example by communicating
+‘EUPL v. 1.2 only’. The Licensee (becoming Licensor) cannot offer or impose any additional terms or conditions on the
+Work or Derivative Work that alter or restrict the terms of the Licence.
+
+Compatibility clause: If the Licensee Distributes or Communicates Derivative Works or copies thereof based upon both
+the Work and another work licensed under a Compatible Licence, this Distribution or Communication can be done
+under the terms of this Compatible Licence. For the sake of this clause, ‘Compatible Licence’ refers to the licences listed
+in the appendix attached to this Licence. Should the Licensee's obligations under the Compatible Licence conflict with
+his/her obligations under this Licence, the obligations of the Compatible Licence shall prevail.
+
+Provision of Source Code: When distributing or communicating copies of the Work, the Licensee will provide
+a machine-readable copy of the Source Code or indicate a repository where this Source will be easily and freely available
+for as long as the Licensee continues to distribute or communicate the Work.
+Legal Protection: This Licence does not grant permission to use the trade names, trademarks, service marks, or names
+of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and
+reproducing the content of the copyright notice.
+
+6.Chain of Authorship
+The original Licensor warrants that the copyright in the Original Work granted hereunder is owned by him/her or
+licensed to him/her and that he/she has the power and authority to grant the Licence.
+Each Contributor warrants that the copyright in the modifications he/she brings to the Work are owned by him/her or
+licensed to him/her and that he/she has the power and authority to grant the Licence.
+Each time You accept the Licence, the original Licensor and subsequent Contributors grant You a licence to their contributions
+to the Work, under the terms of this Licence.
+
+7.Disclaimer of Warranty
+The Work is a work in progress, which is continuously improved by numerous Contributors. It is not a finished work
+and may therefore contain defects or ‘bugs’ inherent to this type of development.
+For the above reason, the Work is provided under the Licence on an ‘as is’ basis and without warranties of any kind
+concerning the Work, including without limitation merchantability, fitness for a particular purpose, absence of defects or
+errors, accuracy, non-infringement of intellectual property rights other than copyright as stated in Article 6 of this
+Licence.
+This disclaimer of warranty is an essential part of the Licence and a condition for the grant of any rights to the Work.
+
+8.Disclaimer of Liability
+Except in the cases of wilful misconduct or damages directly caused to natural persons, the Licensor will in no event be
+liable for any direct or indirect, material or moral, damages of any kind, arising out of the Licence or of the use of the
+Work, including without limitation, damages for loss of goodwill, work stoppage, computer failure or malfunction, loss
+of data or any commercial damage, even if the Licensor has been advised of the possibility of such damage. However,
+the Licensor will be liable under statutory product liability laws as far such laws apply to the Work.
+
+9.Additional agreements
+While distributing the Work, You may choose to conclude an additional agreement, defining obligations or services
+consistent with this Licence. However, if accepting obligations, You may act only on your own behalf and on your sole
+responsibility, not on behalf of the original Licensor or any other Contributor, and only if You agree to indemnify,
+defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against such Contributor by
+the fact You have accepted any warranty or additional liability.
+
+10.Acceptance of the Licence
+The provisions of this Licence can be accepted by clicking on an icon ‘I agree’ placed under the bottom of a window
+displaying the text of this Licence or by affirming consent in any other similar way, in accordance with the rules of
+applicable law. Clicking on that icon indicates your clear and irrevocable acceptance of this Licence and all of its terms
+and conditions.
+Similarly, you irrevocably accept this Licence and all of its terms and conditions by exercising any rights granted to You
+by Article 2 of this Licence, such as the use of the Work, the creation by You of a Derivative Work or the Distribution
+or Communication by You of the Work or copies thereof.
+
+11.Information to the public
+In case of any Distribution or Communication of the Work by means of electronic communication by You (for example,
+by offering to download the Work from a remote location) the distribution channel or media (for example, a website)
+must at least provide to the public the information requested by the applicable law regarding the Licensor, the Licence
+and the way it may be accessible, concluded, stored and reproduced by the Licensee.
+
+12.Termination of the Licence
+The Licence and the rights granted hereunder will terminate automatically upon any breach by the Licensee of the terms
+of the Licence.
+Such a termination will not terminate the licences of any person who has received the Work from the Licensee under
+the Licence, provided such persons remain in full compliance with the Licence.
+
+13.Miscellaneous
+Without prejudice of Article 9 above, the Licence represents the complete agreement between the Parties as to the
+Work.
+If any provision of the Licence is invalid or unenforceable under applicable law, this will not affect the validity or
+enforceability of the Licence as a whole. Such provision will be construed or reformed so as necessary to make it valid
+and enforceable.
+The European Commission may publish other linguistic versions or new versions of this Licence or updated versions of
+the Appendix, so far this is required and reasonable, without reducing the scope of the rights granted by the Licence.
+New versions of the Licence will be published with a unique version number.
+All linguistic versions of this Licence, approved by the European Commission, have identical value. Parties can take
+advantage of the linguistic version of their choice.
+
+14.Jurisdiction
+Without prejudice to specific agreement between parties,
+— any litigation resulting from the interpretation of this License, arising between the European Union institutions,
+bodies, offices or agencies, as a Licensor, and any Licensee, will be subject to the jurisdiction of the Court of Justice
+of the European Union, as laid down in article 272 of the Treaty on the Functioning of the European Union,
+— any litigation arising between other parties and resulting from the interpretation of this License, will be subject to
+the exclusive jurisdiction of the competent court where the Licensor resides or conducts its primary business.
+
+15.Applicable Law
+Without prejudice to specific agreement between parties,
+— this Licence shall be governed by the law of the European Union Member State where the Licensor has his seat,
+resides or has his registered office,
+— this licence shall be governed by Belgian law if the Licensor has no seat, residence or registered office inside
+a European Union Member State.
+
+
+                                                         Appendix
+
+‘Compatible Licences’ according to Article 5 EUPL are:
+— GNU General Public License (GPL) v. 2, v. 3
+— GNU Affero General Public License (AGPL) v. 3
+— Open Software License (OSL) v. 2.1, v. 3.0
+— Eclipse Public License (EPL) v. 1.0
+— CeCILL v. 2.0, v. 2.1
+— Mozilla Public Licence (MPL) v. 2
+— GNU Lesser General Public Licence (LGPL) v. 2.1, v. 3
+— Creative Commons Attribution-ShareAlike v. 3.0 Unported (CC BY-SA 3.0) for works other than software
+— European Union Public Licence (EUPL) v. 1.1, v. 1.2
+— Québec Free and Open-Source Licence — Reciprocity (LiLiQ-R) or Strong Reciprocity (LiLiQ-R+).
+
+The European Commission may update this Appendix to later versions of the above licences without producing
+a new version of the EUPL, as long as they provide the rights granted in Article 2 of this Licence and protect the
+covered Source Code from exclusive appropriation.
+All other changes or additions to this Appendix require the production of a new EUPL version.
diff --git a/README.md b/README.md
index 42c66a0..b657d5f 100644
--- a/README.md
+++ b/README.md
@@ -1,3 +1,2 @@
 # instrument-registry
 Registry for instruments / measures such as the IAMA.
-
diff --git a/SECURITY.md b/SECURITY.md
new file mode 100644
index 0000000..8773b5a
--- /dev/null
+++ b/SECURITY.md
@@ -0,0 +1,18 @@
+# Security Policy
+
+## Supported Versions
+
+We release patches for security vulnerabilities. Which versions are eligible for receiving such patches depends on the
+CVSS (Common Vulnerability Scoring System) v4.0 Rating:
+
+| CVSS v4.0 | Supported Versions                        |
+| --------- | ----------------------------------------- |
+| 9.0-10.0  | Releases within the previous months       |
+| 4.0-8.9   | Most recent release                       |
+
+## Reporting a Vulnerability
+
+Please report (suspected) security vulnerabilities to NCSC:
+
+* Nederlands: **[NCSC Kwetsbaarheid melden](https://www.ncsc.nl/contact/kwetsbaarheid-melden)**
+* English: **[NCSC report vulnerability](https://english.ncsc.nl/contact/reporting-a-vulnerability-cvd)**
diff --git a/instruments/iama.yaml b/instruments/iama.yaml
index baf2f71..c322309 100644
--- a/instruments/iama.yaml
+++ b/instruments/iama.yaml
@@ -1,657 +1,654 @@
-systemcard_path: .assessments[]               # append iama.yaml to 'assessments' list in system card 
-schema_version: v_1.0.0
+systemcard_path: .assessments[]               # append iama.yaml to 'assessments' list in system card
+schema_version: 1.1.0
 
 instrument:
   name: "Impact Assessment Mensenrechten en Algoritmes (IAMA)"
   description: "Het IAMA helpt om de risico's voor mensenrechten bij het gebruik van algoritmen in kaart te brengen en maatregelen te nemen om deze aan te pakken."
-  version: 1.0
-  language: "Nederlands"
-  owners:                                 
-    - organization: "" 
+  urn: "urn:nl:aivt:ir:1.0"
+  language: "nl"
+  owners:
+    - organization: ""
       name: ""
       email: ""
       role: ""
   date: ""
   url: "https://www.rijksoverheid.nl/documenten/rapporten/2021/02/25/impact-assessment-mensenrechten-en-algoritmes"
 
-answers: &default_answers                     # anchor for all fields belonging to answer
-  answer: ""                       
-  remarks: ""                    
-  validation: "^[a-zA-Z\\s]+$"    
-  timestamp: ""              
-  authors: 
-    - name: ""                
-      email: ""
-      role: ""
+template: &systemcard_template                  # anchor for all fields belonging to answer
+  question: "$QUESTION"
+  answer: "$ANSWER"
+  remarks: "$REMARKS"
+  timestamp: "$TIMESTAMP"
+  authors:
+    - name: "$AUTHOR.NAME"
+      email: "$AUTHOR.EMAIL"
+      role: "$AUTHOR.ROLE"
 
-tasks:                                    # each question can be seen as a separate task 
+tasks: # each question can be seen as a separate task
   - question: "Licht uw voorstel voor het gebruik/de inzet van een algoritme toe. Wat is de aanleiding hiervoor geweest? Voor welk probleem moet het algoritme een oplossing bieden?"
-    id: 1.1.1
+    urn: "urn:nl:aivt:ir:1.0:1.1.1"
     labels:
-      - key: topic 
+      - key: topic
         value: "Aanleiding en probleemdefinitie"
-    type: "open question"                                    
-    suggested_roles: ["Behoeftesteller", "Gemandateerd verantwoordelijke(n)", "Projectleider", "Domeinspecialist", "Gebruiker"] #suggested roles in IAMA are coupled to roles that are described in the Algoritmekader
-    lifecycle: ["Probleemanalyse"]            # one or more out of 8 options from AK lifecycle: https://minbzk.github.io/Algoritmekader/levenscyclus/
-    links: ["DPIA vraag 1"]                   # optional: list with links to other tasks / instruments (for example: is this question also asked in the DPIA?) 
-    requirements: []                          # optional: what are the requirements for this task? (for example: upload dataset)
-    <<: *default_answers                  
+    type: "open_question"
+    suggested_roles: [ "Behoeftesteller", "Gemandateerd verantwoordelijke(n)", "Projectleider", "Domeinspecialist", "Gebruiker" ] #suggested roles in IAMA are coupled to roles that are described in the Algoritmekader
+    lifecycle: [ "Probleemanalyse" ]            # one or more out of 8 options from AK lifecycle: https://minbzk.github.io/Algoritmekader/levenscyclus/
+    links: [ { "text": "DPIA vraag 1" } ]       # optional: list with links to other tasks / instruments (for example: is this question also asked in the DPIA?)
+    requirements: [ ]                           # optional: what are the requirements for this task? (for example: upload dataset)
+    template: *systemcard_template
   - question: "Wat is het doel dat bereikt dient te worden met de inzet van het algoritme? Wat is hierbij het hoofddoel en wat zijn subdoelen?"
-    id: 1.2.1
+    urn: "urn:nl:aivt:ir:1.0:1.2.1"
     labels:
       - key: topic
         value: "Doelstelling"
-    type: "open question"
-    suggested_roles: ["Behoeftesteller", "Gemandateerd verantwoordelijke(n)", "Projectleider", "Gebruiker"]
-    lifecycle: ["Probleemanalyse"] 
-    links: ["DPIA vraag 4"]
-    requirements: []
-    <<: *default_answers
+    type: "open_question"
+    suggested_roles: [ "Behoeftesteller", "Gemandateerd verantwoordelijke(n)", "Projectleider", "Gebruiker" ]
+    lifecycle: [ "Probleemanalyse" ]
+    links: [ { "text": "DPIA vraag 4" } ]
+    requirements: [ ]
+    template: *systemcard_template
   - question: "Wat zijn de publieke waarden die de inzet van het algoritme ingeven? Indien meerdere publieke waarden de inzet van het algoritme ingeven, kan daar een rangschikking in aangebracht worden?"
-    id: 1.3.1
+    urn: "urn:nl:aivt:ir:1.0:1.3.1"
     labels:
       - key: topic
         value: "Publieke waarden"
-    type: "open question"
-    suggested_roles: ["Behoeftesteller", "Gemandateerd verantwoordelijke(n)", "Jurist", "Gebruiker"]
-    lifecycle: ["Probleemanalyse"] 
-    links: []
-    requirements: []
-    <<: *default_answers
+    type: "open_question"
+    suggested_roles: [ "Behoeftesteller", "Gemandateerd verantwoordelijke(n)", "Jurist", "Gebruiker" ]
+    lifecycle: [ "Probleemanalyse" ]
+    links: [ ]
+    requirements: [ ]
+    template: *systemcard_template
   - question: "Wat zijn de publieke waarden die mogelijk in het gedrang komen door de inzet van het algoritme?"
-    id: 1.3.2
+    urn: "urn:nl:aivt:ir:1.0:1.3.2"
     labels:
       - key: topic
-        value: "Publieke waarden" 
-    type: "open question"
-    suggested_roles: ["Behoeftesteller", "Gemandateerd verantwoordelijke(n)", "Jurist", "Gebruiker"]
-    lifecycle: ["Probleemanalyse"] 
-    links: []
-    requirements: []
-    <<: *default_answers
+        value: "Publieke waarden"
+    type: "open_question"
+    suggested_roles: [ "Behoeftesteller", "Gemandateerd verantwoordelijke(n)", "Jurist", "Gebruiker" ]
+    lifecycle: [ "Probleemanalyse" ]
+    links: [ ]
+    requirements: [ ]
+    template: *systemcard_template
   - question: "Wat is de wettelijke grondslag van de inzet van dit algoritme en van de beoogde besluiten die genomen zullen worden op basis van dit algoritme?"
-    id: 1.4.1
+    urn: "urn:nl:aivt:ir:1.0:1.4.1"
     labels:
       - key: topic
-        value: "Wettelijke grondslag"   
-    type: "open question"
-    suggested_roles: ["Behoeftesteller", "Gemandateerd verantwoordelijke(n)", "Jurist"]
-    lifecycle: ["Probleemanalyse"] 
-    links: ["DPIA vraag 11", "DPIA vraag 12"]
-    requirements: []
-    <<: *default_answers
+        value: "Wettelijke grondslag"
+    type: "open_question"
+    suggested_roles: [ "Behoeftesteller", "Gemandateerd verantwoordelijke(n)", "Jurist" ]
+    lifecycle: [ "Probleemanalyse" ]
+    links: [ { "text": "DPIA vraag 11" }, { "text": "DPIA vraag 12" } ]
+    requirements: [ ]
+    template: *systemcard_template
   - question: "Welke partijen en personen zijn er bij de ontwikkeling/het gebruik/het onderhoud van het algoritme betrokken?"
-    id: 1.5.1
-    labels:
-    - key: topic
-      value: "Betrokkenen en verantwoordelijkheden"
-    type: "open question"
-    suggested_roles: ["Behoeftesteller", "Gemandateerd verantwoordelijke(n)", "Projectleider", "Security officer"]
-    lifecycle: ["Probleemanalyse", "Ontwerp"] 
-    links: ["DPIA vraag 5"]
-    requirements: []
-    <<: *default_answers
+    urn: "urn:nl:aivt:ir:1.0:1.5.1"
+    labels:
+      - key: topic
+        value: "Betrokkenen en verantwoordelijkheden"
+    type: "open_question"
+    suggested_roles: [ "Behoeftesteller", "Gemandateerd verantwoordelijke(n)", "Projectleider", "Security officer" ]
+    lifecycle: [ "Probleemanalyse", "Ontwerp" ]
+    links: [ { "text": "DPIA vraag 5" } ]
+    requirements: [ ]
+    template: *systemcard_template
   - question: "Hoe zijn de verantwoordelijkheden belegd ten aanzien van de ontwikkeling en de inzet van het algoritme, ook nadat het algoritme eenmaal is afgerond?"
-    id: 1.5.2
-    labels:
-    - key: topic
-      value: "Betrokkenen en verantwoordelijkheden"  
-    type: "open question"
-    suggested_roles: ["Behoeftesteller", "Gemandateerd verantwoordelijke(n)", "Projectleider", "Security officer"]
-    lifecycle: ["Probleemanalyse", "Ontwerp", "Monitoring en beheer"] 
-    links: ["DPIA vraag 5"]
-    requirements: []
-    <<: *default_answers
+    urn: "urn:nl:aivt:ir:1.0:1.5.2"
+    labels:
+      - key: topic
+        value: "Betrokkenen en verantwoordelijkheden"
+    type: "open_question"
+    suggested_roles: [ "Behoeftesteller", "Gemandateerd verantwoordelijke(n)", "Projectleider", "Security officer" ]
+    lifecycle: [ "Probleemanalyse", "Ontwerp", "Monitoren", "Beheer" ]
+    links: [ { "text": "DPIA vraag 5" } ]
+    requirements: [ ]
+    template: *systemcard_template
   - question: "Wie is eindverantwoordelijk voor het algoritme?"
-    id: 1.5.3
-    labels:
-    - key: topic
-      value: "Betrokkenen en verantwoordelijkheden" 
-    type: "open question"
-    suggested_roles: ["Behoeftesteller", "Gemandateerd verantwoordelijke(n)", "Projectleider", "Security officer"]
-    lifecycle: ["Probleemanalyse", "Monitoring en beheer"] 
-    links: ["DPIA vraag 5"]
-    requirements: []
-    <<: *default_answers
+    urn: "urn:nl:aivt:ir:1.0:1.5.3"
+    labels:
+      - key: topic
+        value: "Betrokkenen en verantwoordelijkheden"
+    type: "open_question"
+    suggested_roles: [ "Behoeftesteller", "Gemandateerd verantwoordelijke(n)", "Projectleider", "Security officer" ]
+    lifecycle: [ "Probleemanalyse", "Monitoren", "Beheer" ]
+    links: [ { "text": "DPIA vraag 5" } ]
+    requirements: [ ]
+    template: *systemcard_template
   - question: "Wat voor type algoritme wordt gebruikt, of wat voor type algoritme gaat ontwikkeld worden?"
-    id: 2A.1.1 
-    labels:
-    - key: topic
-      value: "Inschatting: type algoritme" 
-    type: "open question"
-    suggested_roles: ["Aanbieder", "Data scientist", "Data engineer", "Projectleider"]
-    lifecycle: ["Ontwerp", "Ontwikkelen"]
-    links: ["DPIA vraag 8"]
-    requirements: []
-    <<: *default_answers
+    urn: "urn:nl:aivt:ir:1.0:2A.1.1"
+    labels:
+      - key: topic
+        value: "Inschatting: type algoritme"
+    type: "open_question"
+    suggested_roles: [ "Aanbieder", "Data scientist", "Data engineer", "Projectleider" ]
+    lifecycle: [ "Ontwerp", "Ontwikkelen" ]
+    links: [ { "text": "DPIA vraag 8" } ]
+    requirements: [ ]
+    template: *systemcard_template
   - question: "Wat voor type data gaat gebruikt worden als input voor het algoritme en uit welke bronnen is de data afkomstig?"
-    id: 2A.2.1
-    labels:
-    - key: topic
-      value: "Databronnen en kwaliteit" 
-    type: "open question"
-    suggested_roles: ["Aanbieder", "Data scientist", "Data engineer"]
-    lifecycle: ["Ontwerp", "Dataverkenning en datapreparatie"]
-    links: ["DPIA vraag 2"]
-    requirements: []
-    <<: *default_answers
+    urn: "urn:nl:aivt:ir:1.0:2A.2.1"
+    labels:
+      - key: topic
+        value: "Databronnen en kwaliteit"
+    type: "open_question"
+    suggested_roles: [ "Aanbieder", "Data scientist", "Data engineer" ]
+    lifecycle: [ "Ontwerp", "Dataverkenning en -preparatie" ]
+    links: [ { "text": "DPIA vraag 2" } ]
+    requirements: [ ]
+    template: *systemcard_template
   - question: "Is de kwaliteit en betrouwbaarheid van de data voldoende voor de beoogde datatoepassing? Leg uit."
-    id: 2.A.2.2
-    labels:
-    - key: topic
-      value: "Databronnen en kwaliteit" 
-    type: "open question"
-    suggested_roles: ["Aanbieder", "Data scientist", "Data engineer"]
-    lifecycle: ["Dataverkenning en datapreparatie"]
-    links: ["DPIA vraag 16"]
-    requirements: []
-    <<: *default_answers
+    urn: "urn:nl:aivt:ir:1.0:2.A.2.2"
+    labels:
+      - key: topic
+        value: "Databronnen en kwaliteit"
+    type: "open_question"
+    suggested_roles: [ "Aanbieder", "Data scientist", "Data engineer" ]
+    lifecycle: [ "Dataverkenning en -preparatie" ]
+    links: [ { "text": "DPIA vraag 16" } ]
+    requirements: [ ]
+    template: *systemcard_template
   - question: "Welke aannames en bias liggen in de data besloten en hoe wordt de invloed daarvan op de output van het algoritme gecorrigeerd of anderszins ondervangen of gemitigeerd?"
-    id: 2A.3.1  
-    labels:
-    - key: topic
-      value: "Bias/aannames in de data" 
-    type: "open question"
-    suggested_roles: ["Aanbieder", "Data scientist", "Data engineer"]
-    lifecycle: ["Dataverkenning en datapreparatie", "Ontwikkelen"]
-    links: ["DPIA vraag 16"]
-    requirements: []
-    <<: *default_answers
+    urn: "urn:nl:aivt:ir:1.0:2A.3.1"
+    labels:
+      - key: topic
+        value: "Bias/aannames in de data"
+    type: "open_question"
+    suggested_roles: [ "Aanbieder", "Data scientist", "Data engineer" ]
+    lifecycle: [ "Dataverkenning en -preparatie", "Ontwikkelen" ]
+    links: [ { "text": "DPIA vraag 16" } ]
+    requirements: [ ]
+    template: *systemcard_template
   - question: "Indien gebruik wordt gemaakt van trainingsdata: is de data representatief voor de context waarin het algoritme ingezet gaat worden?"
-    id: 2A.3.2
-    labels:
-    - key: topic
-      value: "Bias/aannames in de data"
-    type: "open question"
-    suggested_roles: ["Aanbieder", "Data scientist", "Data engineer"]
-    lifecycle: ["Dataverkenning en datapreparatie", "Ontwikkelen"] 
-    links: ["DPIA vraag 16"]
-    requirements: []
-    <<: *default_answers
+    urn: "urn:nl:aivt:ir:1.0:2A.3.2"
+    labels:
+      - key: topic
+        value: "Bias/aannames in de data"
+    type: "open_question"
+    suggested_roles: [ "Aanbieder", "Data scientist", "Data engineer" ]
+    lifecycle: [ "Dataverkenning en -preparatie", "Ontwikkelen" ]
+    links: [ { "text": "DPIA vraag 16" } ]
+    requirements: [ ]
+    template: *systemcard_template
   - question: "Is de data voldoende beveiligd? Maak hierin onderscheid tussen de inputdata en de outputdata."
-    id: 2A.4.1
-    labels:
-    - key: topic
-      value: "Beveiliging en archivering" 
-    type: "open question"
-    suggested_roles: ["Aanbieder", "Data scientist", "Data engineer"]
-    lifecycle: ["Dataverkenning en datapreparatie", "Ontwikkelen"]
-    links: ["DPIA vraag 17"]
-    requirements: []
-    <<: *default_answers
+    urn: "urn:nl:aivt:ir:1.0:2A.4.1"
+    labels:
+      - key: topic
+        value: "Beveiliging en archivering"
+    type: "open_question"
+    suggested_roles: [ "Aanbieder", "Data scientist", "Data engineer" ]
+    lifecycle: [ "Dataverkenning en -preparatie", "Ontwikkelen" ]
+    links: [ { "text": "DPIA vraag 17" } ]
+    requirements: [ ]
+    template: *systemcard_template
   - question: "Is er controle op de toegang tot de data? Maak hierin onderscheid tussen de inputdata en de outputdata."
-    id: 2A.4.2
-    labels:
-    - key: topic
-      value: "Beveiliging en archivering" 
-    type: "open question"
-    suggested_roles: ["Aanbieder", "Data scientist", "Data engineer"]
-    lifecycle: ["Dataverkenning en datapreparatie", "Ontwikkelen"]
-    links: ["DPIA vraag 17"]
-    requirements: []
-    <<: *default_answers
+    urn: "urn:nl:aivt:ir:1.0:2A.4.2"
+    labels:
+      - key: topic
+        value: "Beveiliging en archivering"
+    type: "open_question"
+    suggested_roles: [ "Aanbieder", "Data scientist", "Data engineer" ]
+    lifecycle: [ "Dataverkenning en -preparatie", "Ontwikkelen" ]
+    links: [ { "text": "DPIA vraag 17" } ]
+    requirements: [ ]
+    template: *systemcard_template
   - question: "Hoe worden relevante regels over archivering in acht genomen, zoals die in de Archiefwet zijn vastgelegd?"
-    id: 2A.4.3
-    labels:
-    - key: topic
-      value: "Beveiliging en archivering" 
-    type: "open question"
-    suggested_roles: ["Aanbieder", "Data scientist", "Data engineer"]
-    lifecycle: ["Dataverkenning en datapreparatie"]
-    links: ["DPIA vraag 10"]
-    requirements: []
-    <<: *default_answers
+    urn: "urn:nl:aivt:ir:1.0:2A.4.3"
+    labels:
+      - key: topic
+        value: "Beveiliging en archivering"
+    type: "open_question"
+    suggested_roles: [ "Aanbieder", "Data scientist", "Data engineer" ]
+    lifecycle: [ "Dataverkenning en -preparatie" ]
+    links: [ { "text": "DPIA vraag 10" } ]
+    requirements: [ ]
+    template: *systemcard_template
   - question: "Type algoritme: wat voor soort algoritme wordt gebruikt of gaat worden gebruikt? Hoe werkt het? Onderscheid tussen: A) Een niet-zelflerend algoritme, waarin de mens de regels specificeert die de computer moet volgen, B) Een zelflerend algoritme, waarin de machine zelf leert over de patronen in de data (machine learning)"
-    id: 2B.1.1
-    labels:
-    - key: topic
-      value: "Type algoritme"
-    type: "open question"
-    suggested_roles: ["Data scientist", "Projectleider", "Aanbieder"]
-    lifecycle: ["Ontwerp", "Ontwikkelen"]
-    links: ["DPIA vraag 8"]
-    requirements: []
-    <<: *default_answers
+    urn: "urn:nl:aivt:ir:1.0:2B.1.1"
+    labels:
+      - key: topic
+        value: "Type algoritme"
+    type: "open_question"
+    suggested_roles: [ "Data scientist", "Projectleider", "Aanbieder" ]
+    lifecycle: [ "Ontwerp", "Ontwikkelen" ]
+    links: [ { "text": "DPIA vraag 8" } ]
+    requirements: [ ]
+    template: *systemcard_template
   - question: "Waarom wordt voor dit type algoritme gekozen?"
-    id: 2B.1.2
-    labels:
-    - key: topic
-      value: "Type algoritme" 
-    type: "open question"
-    suggested_roles: ["Data scientist", "Projectleider", "Aanbieder"]
-    lifecycle: ["Ontwerp", "Ontwikkelen"]
-    links: ["DPIA vraag 8"]
-    requirements: []
-    <<: *default_answers
+    urn: "urn:nl:aivt:ir:1.0:2B.1.2"
+    labels:
+      - key: topic
+        value: "Type algoritme"
+    type: "open_question"
+    suggested_roles: [ "Data scientist", "Projectleider", "Aanbieder" ]
+    lifecycle: [ "Ontwerp", "Ontwikkelen" ]
+    links: [ { "text": "DPIA vraag 8" } ]
+    requirements: [ ]
+    template: *systemcard_template
   - question: "Waarom is dit type algoritme het meest geschikt om de bij vraag 1.2 geformuleerde doelstellingen te bereiken?"
-    id: 2B.1.3
-    labels:
-    - key: topic
-      value: "Type algoritme" 
-    type: "open question"
-    suggested_roles: ["Data scientist", "Projectleider", "Aanbieder"]
-    lifecycle: ["Ontwerp", "Ontwikkelen"]
-    links: ["DPIA vraag 8"]
-    requirements: []
-    <<: *default_answers
+    urn: "urn:nl:aivt:ir:1.0:2B.1.3"
+    labels:
+      - key: topic
+        value: "Type algoritme"
+    type: "open_question"
+    suggested_roles: [ "Data scientist", "Projectleider", "Aanbieder" ]
+    lifecycle: [ "Ontwerp", "Ontwikkelen" ]
+    links: [ { "text": "DPIA vraag 8" } ]
+    requirements: [ ]
+    template: *systemcard_template
   - question: "Welke alternatieven zijn er en waarom zijn die minder passend of bruikbaar?"
-    id: 2B.1.4      
-    labels:
-    - key: topic
-      value: "Type algoritme" 
-    type: "open question"
-    suggested_roles: ["Data scientist", "Projectleider", "Aanbieder"]
-    lifecycle: ["Ontwerp"]
-    links: ["DPIA vraag 8"]
-    requirements: []
-    <<: *default_answers
+    urn: "urn:nl:aivt:ir:1.0:2B.1.4"
+    labels:
+      - key: topic
+        value: "Type algoritme"
+    type: "open_question"
+    suggested_roles: [ "Data scientist", "Projectleider", "Aanbieder" ]
+    lifecycle: [ "Ontwerp" ]
+    links: [ { "text": "DPIA vraag 8" } ]
+    requirements: [ ]
+    template: *systemcard_template
   - question: "Indien het algoritme is ontwikkeld door een externe partij: zijn er heldere afspraken gemaakt over eigenaarschap en beheer van het algoritme? Wat zijn die afspraken?"
-    id: 2B.2.1      
-    labels:
-    - key: topic
-      value: "Eigenaarschap en controle" 
-    type: "open question"
-    suggested_roles: ["Aanbieder", "Projectleider", "Jurist"]
-    lifecycle: ["Ontwerp", "Monitoring en beheer"]
-    links: ["DPIA vraag 5"]
-    requirements: []
-    <<: *default_answers
+    urn: "urn:nl:aivt:ir:1.0:2B.2.1"
+    labels:
+      - key: topic
+        value: "Eigenaarschap en controle"
+    type: "open_question"
+    suggested_roles: [ "Aanbieder", "Projectleider", "Jurist" ]
+    lifecycle: [ "Ontwerp", "Monitoren", "Beheer" ]
+    links: [ { "text": "DPIA vraag 5" } ]
+    requirements: [ ]
+    template: *systemcard_template
   - question: "Wat is de accuraatheid van het algoritme, en op basis van welke evaluatiecriteria is deze accuraatheid bepaald?"
-    id: 2B.3.1
-    labels:
-    - key: topic
-      value: "Accuraatheid algoritme" 
-    type: "open question"
-    suggested_roles: ["Data scientist", "Aanbieder", "Domeinspecialist"]
-    lifecycle: ["Verificatie en validatie"]
-    links: ["DPIA vraag 16"]
-    requirements: []
-    <<: *default_answers
+    urn: "urn:nl:aivt:ir:1.0:2B.3.1"
+    labels:
+      - key: topic
+        value: "Accuraatheid algoritme"
+    type: "open_question"
+    suggested_roles: [ "Data scientist", "Aanbieder", "Domeinspecialist" ]
+    lifecycle: [ "Verificatie", "Validatie" ]
+    links: [ { "text": "DPIA vraag 16" } ]
+    requirements: [ ]
+    template: *systemcard_template
   - question: "Is de mate van accuraatheid (vraag 2B.3.1) acceptabel voor de manier waarop het algoritme ingezet zal worden?"
-    id: 2B.3.2
-    labels:
-    - key: topic
-      value: "Accuraatheid algoritme" 
-    type: "open question"
-    suggested_roles: ["Data scientist", "Aanbieder", "Domeinspecialist"]
-    lifecycle: ["Verificatie en validatie"]
-    links: ["DPIA vraag 16"]
-    requirements: []
-    <<: *default_answers
+    urn: "urn:nl:aivt:ir:1.0:2B.3.2"
+    labels:
+      - key: topic
+        value: "Accuraatheid algoritme"
+    type: "open_question"
+    suggested_roles: [ "Data scientist", "Aanbieder", "Domeinspecialist" ]
+    lifecycle: [ "Verificatie", "Validatie" ]
+    links: [ { "text": "DPIA vraag 16" } ]
+    requirements: [ ]
+    template: *systemcard_template
   - question: "Hoe wordt het algoritme getest?"
-    id: 2B.3.3
-    labels:
-    - key: topic
-      value: "Accuraatheid algoritme" 
-    type: "open question"
-    suggested_roles: ["Data scientist", "Aanbieder", "Domeinspecialist"]
-    lifecycle: ["Verificatie en validatie", "Implementatie"]
-    links: ["DPIA vraag 16"]
-    requirements: []
-    <<: *default_answers
+    urn: "urn:nl:aivt:ir:1.0:2B.3.3"
+    labels:
+      - key: topic
+        value: "Accuraatheid algoritme"
+    type: "open_question"
+    suggested_roles: [ "Data scientist", "Aanbieder", "Domeinspecialist" ]
+    lifecycle: [ "Verificatie", "Validatie", "Implementatie" ]
+    links: [ { "text": "DPIA vraag 16" } ]
+    requirements: [ ]
+    template: *systemcard_template
   - question: "Welke maatregelen kunnen worden getroffen om de risicos van reproductie of zelfs versterking van biases tegen te gaan (bijv. andere sampling- strategie, feature modification, ...)?"
-    id: 2B.3.4
-    labels:
-    - key: topic
-      value: "Accuraatheid algoritme" 
-    type: "open question"
-    suggested_roles: ["Data scientist", "Aanbieder", "Domeinspecialist"]
-    lifecycle: ["Ontwikkelen", "Verificatie en validatie"]
-    links: ["DPIA vraag 16"]
-    requirements: []
-    <<: *default_answers
+    urn: "urn:nl:aivt:ir:1.0:2B.3.4"
+    labels:
+      - key: topic
+        value: "Accuraatheid algoritme"
+    type: "open_question"
+    suggested_roles: [ "Data scientist", "Aanbieder", "Domeinspecialist" ]
+    lifecycle: [ "Ontwikkelen", "Verificatie", "Validatie" ]
+    links: [ { "text": "DPIA vraag 16" } ]
+    requirements: [ ]
+    template: *systemcard_template
   - question: "Welke aannames liggen ten grondslag aan de selectie en weging van de indicatoren? Zijn die aannames terecht? Waarom wel/niet?"
-    id: 2B.3.5
-    labels:
-    - key: topic
-      value: "Accuraatheid algoritme" 
-    type: "open question"
-    suggested_roles: ["Data scientist", "Aanbieder", "Domeinspecialist"]
-    lifecycle: ["Ontwikkelen"]
-    links: ["DPIA vraag 16"]
-    requirements: []
-    <<: *default_answers
+    urn: "urn:nl:aivt:ir:1.0:2B.3.5"
+    labels:
+      - key: topic
+        value: "Accuraatheid algoritme"
+    type: "open_question"
+    suggested_roles: [ "Data scientist", "Aanbieder", "Domeinspecialist" ]
+    lifecycle: [ "Ontwikkelen" ]
+    links: [ { "text": "DPIA vraag 16" } ]
+    requirements: [ ]
+    template: *systemcard_template
   - question: "Hoe vaak/erg zit het algoritme ernaast? (bijv. in termen van aantal false positives, false negatives, R-squared, ...)"
-    id: 2B.3.6
-    labels:
-    - key: topic
-      value: "Accuraatheid algoritme" 
-    type: "open question"
-    suggested_roles: ["Data scientist", "Aanbieder", "Domeinspecialist"]
-    lifecycle: ["Verificatie en validatie"]
-    links: ["DPIA vraag 16"]
-    requirements: []
-    <<: *default_answers
+    urn: "urn:nl:aivt:ir:1.0:2B.3.6"
+    labels:
+      - key: topic
+        value: "Accuraatheid algoritme"
+    type: "open_question"
+    suggested_roles: [ "Data scientist", "Aanbieder", "Domeinspecialist" ]
+    lifecycle: [ "Verificatie", "Validatie" ]
+    links: [ { "text": "DPIA vraag 16" } ]
+    requirements: [ ]
+    template: *systemcard_template
   - question: "Is het duidelijk wat het algoritme doet, hoe het dit doet, en op basis waarvan (welke data) het dit doet? Leg uit."
-    id: 2B.4.1
-    labels:
-    - key: topic
-      value: "Transparantie en uitlegbaarheid" 
-    type: "open question"
-    suggested_roles: ["Projectleider", "Data scientist", "Aanbieder", "Communicatieadviseur", "Jurist", "Ethicus"]
-    lifecycle: ["Ontwikkelen", "Verificatie en validatie"]
-    links: ["DPIA vraag 15"]
-    requirements: []
-    <<: *default_answers
+    urn: "urn:nl:aivt:ir:1.0:2B.4.1"
+    labels:
+      - key: topic
+        value: "Transparantie en uitlegbaarheid"
+    type: "open_question"
+    suggested_roles: [ "Projectleider", "Data scientist", "Aanbieder", "Communicatieadviseur", "Jurist", "Ethicus" ]
+    lifecycle: [ "Ontwikkelen", "Verificatie", "Validatie" ]
+    links: [ { "text": "DPIA vraag 15" } ]
+    requirements: [ ]
+    template: *systemcard_template
   - question: "Voor welke personen en groepen binnen en buiten de eigen organisatie wordt de werking van het algoritme transparant gemaakt en hoe gebeurt dit?"
-    id: 2B.4.2
-    labels:
-    - key: topic
-      value: "Transparantie en uitlegbaarheid" 
-    type: "open question"
-    suggested_roles: ["Projectleider", "Data scientist", "Aanbieder", "Communicatieadviseur", "Jurist", "Ethicus"]
-    lifecycle: ["Ontwerp", "Ontwikkelen", "Verificatie en validatie", "Monitoring en beheer"]
-    links: ["DPIA vraag 15"]
-    requirements: []
-    <<: *default_answers
+    urn: "urn:nl:aivt:ir:1.0:2B.4.2"
+    labels:
+      - key: topic
+        value: "Transparantie en uitlegbaarheid"
+    type: "open_question"
+    suggested_roles: [ "Projectleider", "Data scientist", "Aanbieder", "Communicatieadviseur", "Jurist", "Ethicus" ]
+    lifecycle: [ "Ontwerp", "Ontwikkelen", "Verificatie", "Validatie", "Monitoren", "Beheer" ]
+    links: [ { "text": "DPIA vraag 15" } ]
+    requirements: [ ]
+    template: *systemcard_template
   - question: "Voor welke doelgroepen moet het algoritme uitlegbaar zijn?"
-    id: 2B.4.3
-    labels:
-    - key: topic
-      value: "Transparantie en uitlegbaarheid" 
-    type: "open question"
-    suggested_roles: ["Projectleider", "Data scientist", "Aanbieder", "Communicatieadviseur", "Jurist", "Ethicus"]
-    lifecycle: ["Ontwerp", "Ontwikkelen"]
-    links: ["DPIA vraag 15"]
-    requirements: []
-    <<: *default_answers
+    urn: "urn:nl:aivt:ir:1.0:2B.4.3"
+    labels:
+      - key: topic
+        value: "Transparantie en uitlegbaarheid"
+    type: "open_question"
+    suggested_roles: [ "Projectleider", "Data scientist", "Aanbieder", "Communicatieadviseur", "Jurist", "Ethicus" ]
+    lifecycle: [ "Ontwerp", "Ontwikkelen" ]
+    links: [ { "text": "DPIA vraag 15" } ]
+    requirements: [ ]
+    template: *systemcard_template
   - question: "Kan de werking van het algoritme voor de bij vraag 2B.4.3 geïdentificeerde doelgroepen op een voldoende begrijpelijke manier worden uitgelegd?"
-    id: 2B.4.4
-    labels:
-    - key: topic
-      value: "Transparantie en uitlegbaarheid" 
-    type: "open question"
-    suggested_roles: ["Projectleider", "Data scientist", "Aanbieder", "Communicatieadviseur", "Jurist", "Ethicus"]
-    lifecycle: ["Ontwikkelen", "Verificatie en validatie"]
-    links: ["DPIA vraag 15"]
-    requirements: []
-    <<: *default_answers
+    urn: "urn:nl:aivt:ir:1.0:2B.4.4"
+    labels:
+      - key: topic
+        value: "Transparantie en uitlegbaarheid"
+    type: "open_question"
+    suggested_roles: [ "Projectleider", "Data scientist", "Aanbieder", "Communicatieadviseur", "Jurist", "Ethicus" ]
+    lifecycle: [ "Ontwikkelen", "Verificatie", "Validatie" ]
+    links: [ { "text": "DPIA vraag 15" } ]
+    requirements: [ ]
+    template: *systemcard_template
   - question: "Wat gebeurt er met de uitkomsten van het algoritme? Welke beslissingen worden daarop gebaseerd?"
-    id: 3.1.1
-    labels:
-    - key: topic
-      value: "Beslissingen op basis van output algoritme" 
-    type: "open question"
-    suggested_roles: ["Projectleider", "Domeinspecialist", "Security officer", "Ethicus", "Jurist", "Aanbieder"]
-    lifecycle: ["Ontwerp", "Implementatie", "Monitoring en beheer"]
-    links: []
-    requirements: []
-    <<: *default_answers
+    urn: "urn:nl:aivt:ir:1.0:3.1.1"
+    labels:
+      - key: topic
+        value: "Beslissingen op basis van output algoritme"
+    type: "open_question"
+    suggested_roles: [ "Projectleider", "Domeinspecialist", "Security officer", "Ethicus", "Jurist", "Aanbieder" ]
+    lifecycle: [ "Ontwerp", "Implementatie", "Monitoren", "Beheer" ]
+    links: [ ]
+    requirements: [ ]
+    template: *systemcard_template
   - question: "Welke rol spelen mensen bij het nemen van beslissingen op basis van de output van het algoritme ('human in the loop') en hoe worden zij in staat gesteld om die rol te spelen?"
-    id: 3.2.1
-    labels:
-    - key: topic 
-      value: "De rol van de mens in de beslissing" 
-    type: "open question"
-    suggested_roles: ["Projectleider, Data scientist, Ethicus"]
-    lifecycle: ["Ontwerp", "Implementatie", "Monitoring en beheer"]
-    links: []
-    requirements: []
-    <<: *default_answers
+    urn: "urn:nl:aivt:ir:1.0:3.2.1"
+    labels:
+      - key: topic
+        value: "De rol van de mens in de beslissing"
+    type: "open_question"
+    suggested_roles: [ "Projectleider", "Data scientist", "Ethicus" ]
+    lifecycle: [ "Ontwerp", "Implementatie", "Monitoren", "Beheer" ]
+    links: [ ]
+    requirements: [ ]
+    template: *systemcard_template
   - question: "Is er nu en in de toekomst voldoende gekwalificeerd personeel aanwezig om het algoritme te beheren, te herzien en aan te passen indien gewenst/nodig?"
-    id: 3.2.2
-    labels:
-    - key: topic
-      value: "De rol van de mens in de beslissing" 
-    type: "open question"
-    suggested_roles: ["Projectleider, Data scientist, Ethicus"]
-    lifecycle: ["Ontwerp", "Implementatie", "Monitoring en beheer"]
-    links: []
-    requirements: []
-    <<: *default_answers
+    urn: "urn:nl:aivt:ir:1.0:3.2.2"
+    labels:
+      - key: topic
+        value: "De rol van de mens in de beslissing"
+    type: "open_question"
+    suggested_roles: [ "Projectleider", "Data scientist", "Ethicus" ]
+    lifecycle: [ "Ontwerp", "Implementatie", "Monitoren", "Beheer" ]
+    links: [ ]
+    requirements: [ ]
+    template: *systemcard_template
   - question: "Wat zullen de effecten zijn van de inzet van het algoritme voor burgers en hoe wordt rekening gehouden met de 'menselijke maat' bij het nemen van beslissingen op basis van de output van het algoritme?"
-    id: 3.3.1
-    labels:
-    - key: topic 
-      value: "Effecten van het algoritme" 
-    type: "open question"
-    suggested_roles: ["Projectleider", "Data scientist", "Ethicus", "Aanbieder", "Gebruiker"]
-    lifecycle: ["Probleemanalyse", "Ontwerp", "Implementatie", "Monitoring en beheer"]
-    links: ["DPIA vraag 16"]
-    requirements: []
-    <<: *default_answers
+    urn: "urn:nl:aivt:ir:1.0:3.3.1"
+    labels:
+      - key: topic
+        value: "Effecten van het algoritme"
+    type: "open_question"
+    suggested_roles: [ "Projectleider", "Data scientist", "Ethicus", "Aanbieder", "Gebruiker" ]
+    lifecycle: [ "Probleemanalyse", "Ontwerp", "Implementatie", "Monitoren", "Beheer" ]
+    links: [ { "text": "DPIA vraag 16" } ]
+    requirements: [ ]
+    template: *systemcard_template
   - question: "Welke risico's voor stigmatiserende, discriminerende of anderszins schadelijke of nadelige effecten zijn er voor de burger en hoe zullen die worden bestreden of gemitigeerd?"
-    id: 3.3.2
-    labels:
-    - key: topic
-      value: "Effecten van het algoritme" 
-    type: "open question"
-    suggested_roles: ["Projectleider", "Data scientist", "Ethicus", "Aanbieder", "Gebruiker"]
-    lifecycle: ["Probleemanalyse", "Ontwerp", "Ontwikkelen", "Implementatie"]
-    links: ["DPIA vraag 16", "DPIA vraag 17"]
-    requirements: []
-    <<: *default_answers
+    urn: "urn:nl:aivt:ir:1.0:3.3.2"
+    labels:
+      - key: topic
+        value: "Effecten van het algoritme"
+    type: "open_question"
+    suggested_roles: [ "Projectleider", "Data scientist", "Ethicus", "Aanbieder", "Gebruiker" ]
+    lifecycle: [ "Probleemanalyse", "Ontwerp", "Ontwikkelen", "Implementatie" ]
+    links: [ { "text": "DPIA vraag 16" }, { "text": "DPIA vraag 17" } ]
+    requirements: [ ]
+    template: *systemcard_template
   - question: Hoe zullen de verwachte effecten bijdragen aan de oplossing van het probleem dat de aanleiding is voor de ontwikkeling/inzet van het algoritme (zie vraag 1.1) en het bereiken van de daarbij gestelde doelen (zie vraag 1.2)?
-    id: 3.3.3
-    labels:
-    - key: topic
-      value: "Effecten van het algoritme" 
-    type: "open question"
-    suggested_roles: ["Projectleider", "Data scientist", "Ethicus", "Aanbieder", "Gebruiker"]
-    lifecycle: ["Probleemanalyse"]
-    links: []
-    requirements: []
-    <<: *default_answers
+    urn: "urn:nl:aivt:ir:1.0:3.3.3"
+    labels:
+      - key: topic
+        value: "Effecten van het algoritme"
+    type: "open_question"
+    suggested_roles: [ "Projectleider", "Data scientist", "Ethicus", "Aanbieder", "Gebruiker" ]
+    lifecycle: [ "Probleemanalyse" ]
+    links: [ ]
+    requirements: [ ]
+    template: *systemcard_template
   - question: Hoe verhouden de verwachte effecten zich tot de waarden die worden gediend (zie vraag 1.3)? Welke risico's zijn er dat bepaalde waarden onder druk komen te staan en hoe wordt daarmee dan omgegaan?
-    id: 3.3.4
-    labels:
-    - key: topic
-      value: "Effecten van het algoritme" 
-    type: "open question"
-    suggested_roles: ["Projectleider", "Data scientist", "Ethicus", "Aanbieder", "Gebruiker"]
-    lifecycle: ["Probleemanalyse"]
-    links: []
-    requirements: []
-    <<: *default_answers
+    urn: "urn:nl:aivt:ir:1.0:3.3.4"
+    labels:
+      - key: topic
+        value: "Effecten van het algoritme"
+    type: "open_question"
+    suggested_roles: [ "Projectleider", "Data scientist", "Ethicus", "Aanbieder", "Gebruiker" ]
+    lifecycle: [ "Probleemanalyse" ]
+    links: [ ]
+    requirements: [ ]
+    template: *systemcard_template
   - question: "Via welke procedures zullen beslissingen op basis van het algoritme worden genomen?"
-    id: 3.4.1
-    labels:
-    - key: topic
-      value: "Procedures" 
-    type: "open question"
-    suggested_roles: ["Projectleider", "Data scientist", "Ethicus", "Jurist"]
-    lifecycle: ["Ontwerp", "Implementatie", "Monitoring en beheer"]
-    links: []
-    requirements: []
-    <<: *default_answers
+    urn: "urn:nl:aivt:ir:1.0:3.4.1"
+    labels:
+      - key: topic
+        value: "Procedures"
+    type: "open_question"
+    suggested_roles: [ "Projectleider", "Data scientist", "Ethicus", "Jurist" ]
+    lifecycle: [ "Ontwerp", "Implementatie", "Monitoren", "Beheer" ]
+    links: [ ]
+    requirements: [ ]
+    template: *systemcard_template
   - question: "Hoe worden verschillende relevante actoren (bestuurlijke en politiek verantwoordelijken, burgers) bij de besluitvorming betrokken?"
-    id: 3.4.2
-    labels:
-    - key: topic
-      value: "Procedures" 
-    type: "open question"
-    suggested_roles: ["Projectleider", "Data scientist", "Ethicus", "Jurist"]
-    lifecycle: ["Ontwerp", "Implementatie", "Monitoring en beheer"]
-    links: []
-    requirements: []
-    <<: *default_answers
+    urn: "urn:nl:aivt:ir:1.0:3.4.2"
+    labels:
+      - key: topic
+        value: "Procedures"
+    type: "open_question"
+    suggested_roles: [ "Projectleider", "Data scientist", "Ethicus", "Jurist" ]
+    lifecycle: [ "Ontwerp", "Implementatie", "Monitoren", "Beheer" ]
+    links: [ ]
+    requirements: [ ]
+    template: *systemcard_template
   - question: "Hoe wordt gegarandeerd dat in deze procedures wordt voldaan aan de eisen van goed en behoorlijk bestuur en - waar nodig - rechtsbescherming? Hebben burgers een effectieve mogelijkheid om een klacht in te dienen of bezwaar te maken? Zo ja, op welke manier?"
-    id: 3.4.3
-    labels:
-    - key: topic
-      value: "Procedures" 
-    type: "open question"
-    suggested_roles: ["Projectleider", "Data scientist", "Ethicus", "Jurist"]
-    lifecycle: ["Ontwerp", "Implementatie", "Monitoring en beheer"]
-    links: []
-    requirements: []
-    <<: *default_answers
+    urn: "urn:nl:aivt:ir:1.0:3.4.3"
+    labels:
+      - key: topic
+        value: "Procedures"
+    type: "open_question"
+    suggested_roles: [ "Projectleider", "Data scientist", "Ethicus", "Jurist" ]
+    lifecycle: [ "Ontwerp", "Implementatie", "Monitoren", "Beheer" ]
+    links: [ ]
+    requirements: [ ]
+    template: *systemcard_template
   - question: "Tijd/periode: wanneer gaat het algoritme ingezet worden? Hoe lang is de periode dat het ingezet wordt?"
-    id: 3.5.1
-    labels:
-    - key: topic
-      value: "Context" 
-    type: "open question"
-    suggested_roles: ["Projectleider", "Data scientist", "Ethicus"]
-    lifecycle: ["Ontwerp", "Implementatie", "Monitoring en beheer"]
-    links: []
-    requirements: []
-    <<: *default_answers
+    urn: "urn:nl:aivt:ir:1.0:3.5.1"
+    labels:
+      - key: topic
+        value: "Context"
+    type: "open_question"
+    suggested_roles: [ "Projectleider", "Data scientist", "Ethicus" ]
+    lifecycle: [ "Ontwerp", "Implementatie", "Monitoren", "Beheer" ]
+    links: [ ]
+    requirements: [ ]
+    template: *systemcard_template
   - question: "Plaats: waar vindt inzet van het algoritme plaats? Is dat in een bepaald geografisch gebied, is dat bij een bepaalde groep personen of dossiers?"
-    id: 3.5.2
-    labels:
-    - key: topic
-      value: "Context" 
-    type: "open question"
-    suggested_roles: ["Projectleider", "Data scientist", "Ethicus"]
-    lifecycle: ["Ontwerp", "Implementatie", "Monitoring en beheer"]
-    links: []
-    requirements: []
-    <<: *default_answers
+    urn: "urn:nl:aivt:ir:1.0:3.5.2"
+    labels:
+      - key: topic
+        value: "Context"
+    type: "open_question"
+    suggested_roles: [ "Projectleider", "Data scientist", "Ethicus" ]
+    lifecycle: [ "Ontwerp", "Implementatie", "Monitoren", "Beheer" ]
+    links: [ ]
+    requirements: [ ]
+    template: *systemcard_template
   - question: "Kan het algoritme ook nog worden ingezet als contextfactoren veranderen of als het algoritme gebruikt wordt in een andere context dan waarvoor het is ontwikkeld?"
-    id: 3.5.3
-    labels:
-    - key: topic
-      value: "Context" 
-    type: "open question"
-    suggested_roles: ["Projectleider", "Data scientist", "Ethicus"]
-    lifecycle: ["Ontwerp", "Implementatie", "Monitoring en beheer"]
-    links: []
-    requirements: []
-    <<: *default_answers
+    urn: "urn:nl:aivt:ir:1.0:3.5.3"
+    labels:
+      - key: topic
+        value: "Context"
+    type: "open_question"
+    suggested_roles: [ "Projectleider", "Data scientist", "Ethicus" ]
+    lifecycle: [ "Ontwerp", "Implementatie", "Monitoren", "Beheer" ]
+    links: [ ]
+    requirements: [ ]
+    template: *systemcard_template
   - question: "Hoe open kunt u zijn over de werking van het algoritme in het licht van de doelstellingen en context van de inzet ervan?"
-    id: 3.6.1
-    labels:
-    - key: topic 
-      value: "Communicatie" 
-    type: "open question"
-    suggested_roles: ["Projectleider", "Behoeftesteller", "Gemandateerd verantwoordelijke(n)", "Ethicus"]
-    lifecycle: ["Ontwerp", "Implementatie", "Monitoring en beheer"]
-    links: ["DPIA vraag 15"]
-    requirements: []
-    <<: *default_answers
+    urn: "urn:nl:aivt:ir:1.0:3.6.1"
+    labels:
+      - key: topic
+        value: "Communicatie"
+    type: "open_question"
+    suggested_roles: [ "Projectleider", "Behoeftesteller", "Gemandateerd verantwoordelijke(n)", "Ethicus" ]
+    lifecycle: [ "Ontwerp", "Implementatie", "Monitoren", "Beheer" ]
+    links: [ { "text": "DPIA vraag 15" } ]
+    requirements: [ ]
+    template: *systemcard_template
   - question: "Op welke manier beoogt u te communiceren over de inzet van het algoritme?"
-    id: 3.6.2
-    labels:
-    - key: topic
-      value: "Communicatie" 
-    type: "open question"
-    suggested_roles: ["Projectleider", "Behoeftesteller", "Gemandateerd verantwoordelijke(n)", "Ethicus"]
-    lifecycle: ["Ontwerp", "Implementatie", "Monitoring en beheer"]
-    links: ["DPIA vraag 15"]
-    requirements: []
-    <<: *default_answers
+    urn: "urn:nl:aivt:ir:1.0:3.6.2"
+    labels:
+      - key: topic
+        value: "Communicatie"
+    type: "open_question"
+    suggested_roles: [ "Projectleider", "Behoeftesteller", "Gemandateerd verantwoordelijke(n)", "Ethicus" ]
+    lifecycle: [ "Ontwerp", "Implementatie", "Monitoren", "Beheer" ]
+    links: [ { "text": "DPIA vraag 15" } ]
+    requirements: [ ]
+    template: *systemcard_template
   - question: "Wordt de output van het algoritme gevisualiseerd, bijvoorbeeld in een tabel, grafiek of dashboard? Zo ja: is de vorm van visualisatie of weergave een correcte representatie van de output van het algoritme? Is de visualisatie makkelijk te lezen voor verschillende gebruikersgroepen?"
-    id: 3.6.3
-    labels:
-    - key: topic
-      value: "Communicatie" 
-    type: "open question"
-    suggested_roles: ["Projectleider", "Behoeftesteller", "Gemandateerd verantwoordelijke(n)", "Ethicus"]
-    lifecycle: ["Verificatie en validatie", "Implementatie", "Monitoring en beheer"]
-    links: ["DPIA vraag 15"]
-    requirements: []
-    <<: *default_answers
+    urn: "urn:nl:aivt:ir:1.0:3.6.3"
+    labels:
+      - key: topic
+        value: "Communicatie"
+    type: "open_question"
+    suggested_roles: [ "Projectleider", "Behoeftesteller", "Gemandateerd verantwoordelijke(n)", "Ethicus" ]
+    lifecycle: [ "Verificatie", "Validatie", "Implementatie", "Monitoren", "Beheer" ]
+    links: [ { "text": "DPIA vraag 15" } ]
+    requirements: [ ]
+    template: *systemcard_template
   - question: "Is voorzien in goede instrumenten voor evaluatie, auditing en borging van het algoritme?"
-    id: 3.7.1
-    labels:
-    - key: topic
-      value: "Evaluatie, auditing en borging"  
-    type: "open question"
-    suggested_roles: ["Projectleider", "Behoeftesteller", "Gemandateerd verantwoordelijke(n)", "Data scientist"]
-    lifecycle: ["Verificatie en validatie", "Implementatie", "Monitoring en beheer"]
-    links: []
-    requirements: []
-    <<: *default_answers
+    urn: "urn:nl:aivt:ir:1.0:3.7.1"
+    labels:
+      - key: topic
+        value: "Evaluatie, auditing en borging"
+    type: "open_question"
+    suggested_roles: [ "Projectleider", "Behoeftesteller", "Gemandateerd verantwoordelijke(n)", "Data scientist" ]
+    lifecycle: [ "Verificatie", "Validatie", "Implementatie", "Monitoren", "Beheer" ]
+    links: [ ]
+    requirements: [ ]
+    template: *systemcard_template
   - question: "Zijn er voldoende mogelijkheden om rekenschap en verantwoording af te leggen over het algoritme?"
-    id: 3.7.2
-    labels:
-    - key: topic
-      value: "Evaluatie, auditing en borging"  
-    type: "open question"
-    suggested_roles: ["Projectleider", "Behoeftesteller", "Gemandateerd verantwoordelijke(n)", "Data scientist"]
-    lifecycle: ["Ontwerp", "Implementatie", "Monitoring en beheer"]
-    links: []
-    requirements: []
-    <<: *default_answers
+    urn: "urn:nl:aivt:ir:1.0:3.7.2"
+    labels:
+      - key: topic
+        value: "Evaluatie, auditing en borging"
+    type: "open_question"
+    suggested_roles: [ "Projectleider", "Behoeftesteller", "Gemandateerd verantwoordelijke(n)", "Data scientist" ]
+    lifecycle: [ "Ontwerp", "Implementatie", "Monitoren", "Beheer" ]
+    links: [ ]
+    requirements: [ ]
+    template: *systemcard_template
   - question: "Welke mogelijkheden zijn er voor auditors en toezichthouders om (formele) consequenties te verbinden aan de inzet van een algoritme door de overheid (bijv. terugkoppeling van bevindingen, doen van aanbevelingen, budgettaire consequenties, ...)"
-    id: 3.7.3
-    labels:
-    - key: topic
-      value: "Evaluatie, auditing en borging"   
-    type: "open question"
-    suggested_roles: ["Projectleider", "Behoeftesteller", "Gemandateerd verantwoordelijke(n)", "Data scientist"]
-    lifecycle: ["Implementatie", "Monitoring en beheer"]
-    links: []
-    requirements: []
-    <<: *default_answers
+    urn: "urn:nl:aivt:ir:1.0:3.7.3"
+    labels:
+      - key: topic
+        value: "Evaluatie, auditing en borging"
+    type: "open_question"
+    suggested_roles: [ "Projectleider", "Behoeftesteller", "Gemandateerd verantwoordelijke(n)", "Data scientist" ]
+    lifecycle: [ "Implementatie", "Monitoren", "Beheer" ]
+    links: [ ]
+    requirements: [ ]
+    template: *systemcard_template
   - question: "Wordt er een grondrecht geraakt door het in te zetten algoritme?"
-    id: 4.1.1
-    labels:
-    - key: topic
-      value: "Grondrecht" 
-    type: "open question"
-    suggested_roles: ["Projectleider", "Domeinspecialist", "Jurist"]
-    lifecycle: ["Probleemanalyse"]
-    links: ["DPIA vraag 16"]
-    requirements: []
-    <<: *default_answers
+    urn: "urn:nl:aivt:ir:1.0:4.1.1"
+    labels:
+      - key: topic
+        value: "Grondrecht"
+    type: "open_question"
+    suggested_roles: [ "Projectleider", "Domeinspecialist", "Jurist" ]
+    lifecycle: [ "Probleemanalyse" ]
+    links: [ { "text": "DPIA vraag 16" } ]
+    requirements: [ ]
+    template: *systemcard_template
   - question: "Zijn er specifieke wettelijke bepalingen of richtsnoeren van toepassing op de grondrechteninbreuk?"
-    id: 4.2.1
-    labels:
-    - key: topic
-      value: "Specifieke wetgeving en richtsnoeren" 
-    type: "open question"
-    suggested_roles: ["Projectleider", "Domeinspecialist", "Jurist"]
-    lifecycle: ["Probleemanalyse"]
-    links: ["DPIA vraag 9"]
-    requirements: []
-    <<: *default_answers
+    urn: "urn:nl:aivt:ir:1.0:4.2.1"
+    labels:
+      - key: topic
+        value: "Specifieke wetgeving en richtsnoeren"
+    type: "open_question"
+    suggested_roles: [ "Projectleider", "Domeinspecialist", "Jurist" ]
+    lifecycle: [ "Probleemanalyse" ]
+    links: [ { "text": "DPIA vraag 9" } ]
+    requirements: [ ]
+    template: *systemcard_template
   - question: "Hoe zwaar wordt een grondrecht geraakt door het algoritme?"
-    id: 4.3.1
-    labels:
-    - key: topic
-      value: "Zwaartebepaling" 
-    type: "open question"
-    suggested_roles: ["Projectleider", "Domeinspecialist", "Jurist"]
-    lifecycle: ["Probleemanalyse"]
-    links: ["DPIA vraag 16"]
-    requirements: []
-    <<: *default_answers
+    urn: "urn:nl:aivt:ir:1.0:4.3.1"
+    labels:
+      - key: topic
+        value: "Zwaartebepaling"
+    type: "open_question"
+    suggested_roles: [ "Projectleider", "Domeinspecialist", "Jurist" ]
+    lifecycle: [ "Probleemanalyse" ]
+    links: [ { "text": "DPIA vraag 16" } ]
+    requirements: [ ]
+    template: *systemcard_template
   - question: "Welke doelen worden met inzet van het algoritme nagestreefd? Kijk hierbij naar uw antwoord op vraag 1.2"
-    id: 4.4.1
-    labels:
-    - key: topic 
-      value: "Doelstellingen" 
-    type: "open question"
-    suggested_roles: ["Projectleider", "Domeinspecialist", "Jurist"]
-    lifecycle: ["Probleemanalyse"]
-    links: []
-    requirements: []
-    <<: *default_answers
+    urn: "urn:nl:aivt:ir:1.0:4.4.1"
+    labels:
+      - key: topic
+        value: "Doelstellingen"
+    type: "open_question"
+    suggested_roles: [ "Projectleider", "Domeinspecialist", "Jurist" ]
+    lifecycle: [ "Probleemanalyse" ]
+    links: [ ]
+    requirements: [ ]
+    template: *systemcard_template
   - question: "Vormt het in te zetten algoritme een doeltreffend middel om de gestelde doelen te realiseren? Leg uit."
-    id: 4.5.1
-    labels:
-    - key: topic
-      value: "Doeltreffendheid/effectiviteit/geschiktheid"
-    type: "open question"
-    suggested_roles: ["Projectleider", "Domeinspecialist", "Jurist"]
-    lifecycle: ["Probleemanalyse"]
-    links: ["DPIA vraag 14"]
-    requirements: []
-    <<: *default_answers
+    urn: "urn:nl:aivt:ir:1.0:4.5.1"
+    labels:
+      - key: topic
+        value: "Doeltreffendheid/effectiviteit/geschiktheid"
+    type: "open_question"
+    suggested_roles: [ "Projectleider", "Domeinspecialist", "Jurist" ]
+    lifecycle: [ "Probleemanalyse" ]
+    links: [ { "text": "DPIA vraag 14" } ]
+    requirements: [ ]
+    template: *systemcard_template
   - question: "Is inzet van dit specifieke algoritme noodzakelijk om dit doel te bereiken en zijn er geen andere of mitigerende maatregelen beschikbaar om dit te doen? Leg uit."
-    id: 4.6.1
-    labels:
-    - key: topic
-      value: "Noodzakelijkheid/subsidiariteit" 
-    type: "open question"
-    suggested_roles: ["Projectleider", "Domeinspecialist", "Jurist"]
-    lifecycle: ["Probleemanalyse"]
-    links: ["DPIA vraag 14"]
-    requirements: []
-    <<: *default_answers
+    urn: "urn:nl:aivt:ir:1.0:4.6.1"
+    labels:
+      - key: topic
+        value: "Noodzakelijkheid/subsidiariteit"
+    type: "open_question"
+    suggested_roles: [ "Projectleider", "Domeinspecialist", "Jurist" ]
+    lifecycle: [ "Probleemanalyse" ]
+    links: [ { "text": "DPIA vraag 14" } ]
+    requirements: [ ]
+    template: *systemcard_template
   - question: "Levert inzet van het algoritme een redelijk evenwicht op tussen de te realiseren doelen en de grondrechten die worden geraakt, en waarom is dat zo?"
-    id: 4.7.1
-    labels:
-    - key: topic
-      value: "Belangenafweging/proportionaliteit" 
-    type: "open question"
-    suggested_roles: ["Projectleider", "Domeinspecialist", "Jurist"]
-    lifecycle: ["Probleemanalyse"]
-    links: ["DPIA vraag 14"]
-    requirements: []
-    <<: *default_answers
-
-
-
+    urn: "urn:nl:aivt:ir:1.0:4.7.1"
+    labels:
+      - key: topic
+        value: "Belangenafweging/proportionaliteit"
+    type: "open_question"
+    suggested_roles: [ "Projectleider", "Domeinspecialist", "Jurist" ]
+    lifecycle: [ "Probleemanalyse" ]
+    links: [ { "text": "DPIA vraag 14" } ]
+    requirements: [ ]
+    template: *systemcard_template
diff --git a/measures/iama.yaml b/measures/iama.yaml
deleted file mode 100644
index 127418c..0000000
--- a/measures/iama.yaml
+++ /dev/null
@@ -1,657 +0,0 @@
-systemcard_path: .assessments[]               # append iama.yaml to 'assessments' list in system card 
-schema_version: iama_v_1.0.0
-
-instrument:
-  name: "Impact Assessment Mensenrechten en Algoritmes (IAMA)"
-  description: "Het IAMA helpt om de risico's voor mensenrechten bij het gebruik van algoritmen in kaart te brengen en maatregelen te nemen om deze aan te pakken."
-  version: 1.0.0
-  language: "Dutch"
-  owners:                                 
-    - organization: "" 
-      name: ""
-      email: ""
-      role: ""
-  date: ""
-  url: "https://www.rijksoverheid.nl/documenten/rapporten/2021/02/25/impact-assessment-mensenrechten-en-algoritmes"
-
-answers: &default_answers                     # anchor for all fields belonging to answer
-  answer: ""                       
-  remarks: ""                    
-  validation: "^[a-zA-Z\\s]+$"    
-  timestamp: ""              
-  authors: 
-    - name: ""                
-      email: ""
-      role: ""
-
-questions:                                    # each question can be seen as a separate task 
-  - question: "Licht uw voorstel voor het gebruik/de inzet van een algoritme toe. Wat is de aanleiding hiervoor geweest? Voor welk probleem moet het algoritme een oplossing bieden?"
-    id: 1.1.1
-    labels:
-      - key: topic 
-        value: "Aanleiding en probleemdefinitie"
-    type: "open question"                                    
-    suggested_roles: ["Behoeftesteller", "Gemandateerd verantwoordelijke(n)", "Projectleider", "Domeinspecialist", "Gebruiker"] #suggested roles in IAMA are coupled to roles that are described in the Algoritmekader
-    lifecycle: ["Probleemanalyse"]            # one or more out of 8 options from AK lifecycle: https://minbzk.github.io/Algoritmekader/levenscyclus/
-    links: ["DPIA vraag 1"]                   # optional: list with links to other tasks / instruments (for example: is this question also asked in the DPIA?) 
-    requirements: []                          # optional: what are the requirements for this task? (for example: upload dataset)
-    <<: *default_answers                  
-  - question: "Wat is het doel dat bereikt dient te worden met de inzet van het algoritme? Wat is hierbij het hoofddoel en wat zijn subdoelen?"
-    id: 1.2.1
-    labels:
-      - key: topic
-        value: "Doelstelling"
-    type: "open question"
-    suggested_roles: ["Behoeftesteller", "Gemandateerd verantwoordelijke(n)", "Projectleider", "Gebruiker"]
-    lifecycle: ["Probleemanalyse"] 
-    links: ["DPIA vraag 4"]
-    requirements: []
-    <<: *default_answers
-  - question: "Wat zijn de publieke waarden die de inzet van het algoritme ingeven? Indien meerdere publieke waarden de inzet van het algoritme ingeven, kan daar een rangschikking in aangebracht worden?"
-    id: 1.3.1
-    labels:
-      - key: topic
-        value: "Publieke waarden"
-    type: "open question"
-    suggested_roles: ["Behoeftesteller", "Gemandateerd verantwoordelijke(n)", "Jurist", "Gebruiker"]
-    lifecycle: ["Probleemanalyse"] 
-    links: []
-    requirements: []
-    <<: *default_answers
-  - question: "Wat zijn de publieke waarden die mogelijk in het gedrang komen door de inzet van het algoritme?"
-    id: 1.3.2
-    labels:
-      - key: topic
-        value: "Publieke waarden" 
-    type: "open question"
-    suggested_roles: ["Behoeftesteller", "Gemandateerd verantwoordelijke(n)", "Jurist", "Gebruiker"]
-    lifecycle: ["Probleemanalyse"] 
-    links: []
-    requirements: []
-    <<: *default_answers
-  - question: "Wat is de wettelijke grondslag van de inzet van dit algoritme en van de beoogde besluiten die genomen zullen worden op basis van dit algoritme?"
-    id: 1.4.1
-    labels:
-      - key: topic
-        value: "Wettelijke grondslag"   
-    type: "open question"
-    suggested_roles: ["Behoeftesteller", "Gemandateerd verantwoordelijke(n)", "Jurist"]
-    lifecycle: ["Probleemanalyse"] 
-    links: ["DPIA vraag 11", "DPIA vraag 12"]
-    requirements: []
-    <<: *default_answers
-  - question: "Welke partijen en personen zijn er bij de ontwikkeling/het gebruik/het onderhoud van het algoritme betrokken?"
-    id: 1.5.1
-    labels:
-    - key: topic
-      value: "Betrokkenen en verantwoordelijkheden"
-    type: "open question"
-    suggested_roles: ["Behoeftesteller", "Gemandateerd verantwoordelijke(n)", "Projectleider", "Security officer"]
-    lifecycle: ["Probleemanalyse", "Ontwerp"] 
-    links: ["DPIA vraag 5"]
-    requirements: []
-    <<: *default_answers
-  - question: "Hoe zijn de verantwoordelijkheden belegd ten aanzien van de ontwikkeling en de inzet van het algoritme, ook nadat het algoritme eenmaal is afgerond?"
-    id: 1.5.2
-    labels:
-    - key: topic
-      value: "Betrokkenen en verantwoordelijkheden"  
-    type: "open question"
-    suggested_roles: ["Behoeftesteller", "Gemandateerd verantwoordelijke(n)", "Projectleider", "Security officer"]
-    lifecycle: ["Probleemanalyse", "Ontwerp", "Monitoring en beheer"] 
-    links: ["DPIA vraag 5"]
-    requirements: []
-    <<: *default_answers
-  - question: "Wie is eindverantwoordelijk voor het algoritme?"
-    id: 1.5.3
-    labels:
-    - key: topic
-      value: "Betrokkenen en verantwoordelijkheden" 
-    type: "open question"
-    suggested_roles: ["Behoeftesteller", "Gemandateerd verantwoordelijke(n)", "Projectleider", "Security officer"]
-    lifecycle: ["Probleemanalyse", "Monitoring en beheer"] 
-    links: ["DPIA vraag 5"]
-    requirements: []
-    <<: *default_answers
-  - question: "Wat voor type algoritme wordt gebruikt, of wat voor type algoritme gaat ontwikkeld worden?"
-    id: 2A.1.1 
-    labels:
-    - key: topic
-      value: "Inschatting: type algoritme" 
-    type: "open question"
-    suggested_roles: ["Aanbieder", "Data scientist", "Data engineer", "Projectleider"]
-    lifecycle: ["Ontwerp", "Ontwikkelen"]
-    links: ["DPIA vraag 8"]
-    requirements: []
-    <<: *default_answers
-  - question: "Wat voor type data gaat gebruikt worden als input voor het algoritme en uit welke bronnen is de data afkomstig?"
-    id: 2A.2.1
-    labels:
-    - key: topic
-      value: "Databronnen en kwaliteit" 
-    type: "open question"
-    suggested_roles: ["Aanbieder", "Data scientist", "Data engineer"]
-    lifecycle: ["Ontwerp", "Dataverkenning en datapreparatie"]
-    links: ["DPIA vraag 2"]
-    requirements: []
-    <<: *default_answers
-  - question: "Is de kwaliteit en betrouwbaarheid van de data voldoende voor de beoogde datatoepassing? Leg uit."
-    id: 2.A.2.2
-    labels:
-    - key: topic
-      value: "Databronnen en kwaliteit" 
-    type: "open question"
-    suggested_roles: ["Aanbieder", "Data scientist", "Data engineer"]
-    lifecycle: ["Dataverkenning en datapreparatie"]
-    links: ["DPIA vraag 16"]
-    requirements: []
-    <<: *default_answers
-  - question: "Welke aannames en bias liggen in de data besloten en hoe wordt de invloed daarvan op de output van het algoritme gecorrigeerd of anderszins ondervangen of gemitigeerd?"
-    id: 2A.3.1  
-    labels:
-    - key: topic
-      value: "Bias/aannames in de data" 
-    type: "open question"
-    suggested_roles: ["Aanbieder", "Data scientist", "Data engineer"]
-    lifecycle: ["Dataverkenning en datapreparatie", "Ontwikkelen"]
-    links: ["DPIA vraag 16"]
-    requirements: []
-    <<: *default_answers
-  - question: "Indien gebruik wordt gemaakt van trainingsdata: is de data representatief voor de context waarin het algoritme ingezet gaat worden?"
-    id: 2A.3.2
-    labels:
-    - key: topic
-      value: "Bias/aannames in de data"
-    type: "open question"
-    suggested_roles: ["Aanbieder", "Data scientist", "Data engineer"]
-    lifecycle: ["Dataverkenning en datapreparatie", "Ontwikkelen"] 
-    links: ["DPIA vraag 16"]
-    requirements: []
-    <<: *default_answers
-  - question: "Is de data voldoende beveiligd? Maak hierin onderscheid tussen de inputdata en de outputdata."
-    id: 2A.4.1
-    labels:
-    - key: topic
-      value: "Beveiliging en archivering" 
-    type: "open question"
-    suggested_roles: ["Aanbieder", "Data scientist", "Data engineer"]
-    lifecycle: ["Dataverkenning en datapreparatie", "Ontwikkelen"]
-    links: ["DPIA vraag 17"]
-    requirements: []
-    <<: *default_answers
-  - question: "Is er controle op de toegang tot de data? Maak hierin onderscheid tussen de inputdata en de outputdata."
-    id: 2A.4.2
-    labels:
-    - key: topic
-      value: "Beveiliging en archivering" 
-    type: "open question"
-    suggested_roles: ["Aanbieder", "Data scientist", "Data engineer"]
-    lifecycle: ["Dataverkenning en datapreparatie", "Ontwikkelen"]
-    links: ["DPIA vraag 17"]
-    requirements: []
-    <<: *default_answers
-  - question: "Hoe worden relevante regels over archivering in acht genomen, zoals die in de Archiefwet zijn vastgelegd?"
-    id: 2A.4.3
-    labels:
-    - key: topic
-      value: "Beveiliging en archivering" 
-    type: "open question"
-    suggested_roles: ["Aanbieder", "Data scientist", "Data engineer"]
-    lifecycle: ["Dataverkenning en datapreparatie"]
-    links: ["DPIA vraag 10"]
-    requirements: []
-    <<: *default_answers
-  - question: "Type algoritme: wat voor soort algoritme wordt gebruikt of gaat worden gebruikt? Hoe werkt het? Onderscheid tussen: A) Een niet-zelflerend algoritme, waarin de mens de regels specificeert die de computer moet volgen, B) Een zelflerend algoritme, waarin de machine zelf leert over de patronen in de data (machine learning)"
-    id: 2B.1.1
-    labels:
-    - key: topic
-      value: "Type algoritme"
-    type: "open question"
-    suggested_roles: ["Data scientist", "Projectleider", "Aanbieder"]
-    lifecycle: ["Ontwerp", "Ontwikkelen"]
-    links: ["DPIA vraag 8"]
-    requirements: []
-    <<: *default_answers
-  - question: "Waarom wordt voor dit type algoritme gekozen?"
-    id: 2B.1.2
-    labels:
-    - key: topic
-      value: "Type algoritme" 
-    type: "open question"
-    suggested_roles: ["Data scientist", "Projectleider", "Aanbieder"]
-    lifecycle: ["Ontwerp", "Ontwikkelen"]
-    links: ["DPIA vraag 8"]
-    requirements: []
-    <<: *default_answers
-  - question: "Waarom is dit type algoritme het meest geschikt om de bij vraag 1.2 geformuleerde doelstellingen te bereiken?"
-    id: 2B.1.3
-    labels:
-    - key: topic
-      value: "Type algoritme" 
-    type: "open question"
-    suggested_roles: ["Data scientist", "Projectleider", "Aanbieder"]
-    lifecycle: ["Ontwerp", "Ontwikkelen"]
-    links: ["DPIA vraag 8"]
-    requirements: []
-    <<: *default_answers
-  - question: "Welke alternatieven zijn er en waarom zijn die minder passend of bruikbaar?"
-    id: 2B.1.4      
-    labels:
-    - key: topic
-      value: "Type algoritme" 
-    type: "open question"
-    suggested_roles: ["Data scientist", "Projectleider", "Aanbieder"]
-    lifecycle: ["Ontwerp"]
-    links: ["DPIA vraag 8"]
-    requirements: []
-    <<: *default_answers
-  - question: "Indien het algoritme is ontwikkeld door een externe partij: zijn er heldere afspraken gemaakt over eigenaarschap en beheer van het algoritme? Wat zijn die afspraken?"
-    id: 2B.2.1      
-    labels:
-    - key: topic
-      value: "Eigenaarschap en controle" 
-    type: "open question"
-    suggested_roles: ["Aanbieder", "Projectleider", "Jurist"]
-    lifecycle: ["Ontwerp", "Monitoring en beheer"]
-    links: ["DPIA vraag 5"]
-    requirements: []
-    <<: *default_answers
-  - question: "Wat is de accuraatheid van het algoritme, en op basis van welke evaluatiecriteria is deze accuraatheid bepaald?"
-    id: 2B.3.1
-    labels:
-    - key: topic
-      value: "Accuraatheid algoritme" 
-    type: "open question"
-    suggested_roles: ["Data scientist", "Aanbieder", "Domeinspecialist"]
-    lifecycle: ["Verificatie en validatie"]
-    links: ["DPIA vraag 16"]
-    requirements: []
-    <<: *default_answers
-  - question: "Is de mate van accuraatheid (vraag 2B.3.1) acceptabel voor de manier waarop het algoritme ingezet zal worden?"
-    id: 2B.3.2
-    labels:
-    - key: topic
-      value: "Accuraatheid algoritme" 
-    type: "open question"
-    suggested_roles: ["Data scientist", "Aanbieder", "Domeinspecialist"]
-    lifecycle: ["Verificatie en validatie"]
-    links: ["DPIA vraag 16"]
-    requirements: []
-    <<: *default_answers
-  - question: "Hoe wordt het algoritme getest?"
-    id: 2B.3.3
-    labels:
-    - key: topic
-      value: "Accuraatheid algoritme" 
-    type: "open question"
-    suggested_roles: ["Data scientist", "Aanbieder", "Domeinspecialist"]
-    lifecycle: ["Verificatie en validatie", "Implementatie"]
-    links: ["DPIA vraag 16"]
-    requirements: []
-    <<: *default_answers
-  - question: "Welke maatregelen kunnen worden getroffen om de risicos van reproductie of zelfs versterking van biases tegen te gaan (bijv. andere sampling- strategie, feature modification, ...)?"
-    id: 2B.3.4
-    labels:
-    - key: topic
-      value: "Accuraatheid algoritme" 
-    type: "open question"
-    suggested_roles: ["Data scientist", "Aanbieder", "Domeinspecialist"]
-    lifecycle: ["Ontwikkelen", "Verificatie en validatie"]
-    links: ["DPIA vraag 16"]
-    requirements: []
-    <<: *default_answers
-  - question: "Welke aannames liggen ten grondslag aan de selectie en weging van de indicatoren? Zijn die aannames terecht? Waarom wel/niet?"
-    id: 2B.3.5
-    labels:
-    - key: topic
-      value: "Accuraatheid algoritme" 
-    type: "open question"
-    suggested_roles: ["Data scientist", "Aanbieder", "Domeinspecialist"]
-    lifecycle: ["Ontwikkelen"]
-    links: ["DPIA vraag 16"]
-    requirements: []
-    <<: *default_answers
-  - question: "Hoe vaak/erg zit het algoritme ernaast? (bijv. in termen van aantal false positives, false negatives, R-squared, ...)"
-    id: 2B.3.6
-    labels:
-    - key: topic
-      value: "Accuraatheid algoritme" 
-    type: "open question"
-    suggested_roles: ["Data scientist", "Aanbieder", "Domeinspecialist"]
-    lifecycle: ["Verificatie en validatie"]
-    links: ["DPIA vraag 16"]
-    requirements: []
-    <<: *default_answers
-  - question: "Is het duidelijk wat het algoritme doet, hoe het dit doet, en op basis waarvan (welke data) het dit doet? Leg uit."
-    id: 2B.4.1
-    labels:
-    - key: topic
-      value: "Transparantie en uitlegbaarheid" 
-    type: "open question"
-    suggested_roles: ["Projectleider", "Data scientist", "Aanbieder", "Communicatieadviseur", "Jurist", "Ethicus"]
-    lifecycle: ["Ontwikkelen", "Verificatie en validatie"]
-    links: ["DPIA vraag 15"]
-    requirements: []
-    <<: *default_answers
-  - question: "Voor welke personen en groepen binnen en buiten de eigen organisatie wordt de werking van het algoritme transparant gemaakt en hoe gebeurt dit?"
-    id: 2B.4.2
-    labels:
-    - key: topic
-      value: "Transparantie en uitlegbaarheid" 
-    type: "open question"
-    suggested_roles: ["Projectleider", "Data scientist", "Aanbieder", "Communicatieadviseur", "Jurist", "Ethicus"]
-    lifecycle: ["Ontwerp", "Ontwikkelen", "Verificatie en validatie", "Monitoring en beheer"]
-    links: ["DPIA vraag 15"]
-    requirements: []
-    <<: *default_answers
-  - question: "Voor welke doelgroepen moet het algoritme uitlegbaar zijn?"
-    id: 2B.4.3
-    labels:
-    - key: topic
-      value: "Transparantie en uitlegbaarheid" 
-    type: "open question"
-    suggested_roles: ["Projectleider", "Data scientist", "Aanbieder", "Communicatieadviseur", "Jurist", "Ethicus"]
-    lifecycle: ["Ontwerp", "Ontwikkelen"]
-    links: ["DPIA vraag 15"]
-    requirements: []
-    <<: *default_answers
-  - question: "Kan de werking van het algoritme voor de bij vraag 2B.4.3 geïdentificeerde doelgroepen op een voldoende begrijpelijke manier worden uitgelegd?"
-    id: 2B.4.4
-    labels:
-    - key: topic
-      value: "Transparantie en uitlegbaarheid" 
-    type: "open question"
-    suggested_roles: ["Projectleider", "Data scientist", "Aanbieder", "Communicatieadviseur", "Jurist", "Ethicus"]
-    lifecycle: ["Ontwikkelen", "Verificatie en validatie"]
-    links: ["DPIA vraag 15"]
-    requirements: []
-    <<: *default_answers
-  - question: "Wat gebeurt er met de uitkomsten van het algoritme? Welke beslissingen worden daarop gebaseerd?"
-    id: 3.1.1
-    labels:
-    - key: topic
-      value: "Beslissingen op basis van output algoritme" 
-    type: "open question"
-    suggested_roles: ["Projectleider", "Domeinspecialist", "Security officer", "Ethicus", "Jurist", "Aanbieder"]
-    lifecycle: ["Ontwerp", "Implementatie", "Monitoring en beheer"]
-    links: []
-    requirements: []
-    <<: *default_answers
-  - question: "Welke rol spelen mensen bij het nemen van beslissingen op basis van de output van het algoritme ('human in the loop') en hoe worden zij in staat gesteld om die rol te spelen?"
-    id: 3.2.1
-    labels:
-    - key: topic 
-      value: "De rol van de mens in de beslissing" 
-    type: "open question"
-    suggested_roles: ["Projectleider, Data scientist, Ethicus"]
-    lifecycle: ["Ontwerp", "Implementatie", "Monitoring en beheer"]
-    links: []
-    requirements: []
-    <<: *default_answers
-  - question: "Is er nu en in de toekomst voldoende gekwalificeerd personeel aanwezig om het algoritme te beheren, te herzien en aan te passen indien gewenst/nodig?"
-    id: 3.2.2
-    labels:
-    - key: topic
-      value: "De rol van de mens in de beslissing" 
-    type: "open question"
-    suggested_roles: ["Projectleider, Data scientist, Ethicus"]
-    lifecycle: ["Ontwerp", "Implementatie", "Monitoring en beheer"]
-    links: []
-    requirements: []
-    <<: *default_answers
-  - question: "Wat zullen de effecten zijn van de inzet van het algoritme voor burgers en hoe wordt rekening gehouden met de 'menselijke maat' bij het nemen van beslissingen op basis van de output van het algoritme?"
-    id: 3.3.1
-    labels:
-    - key: topic 
-      value: "Effecten van het algoritme" 
-    type: "open question"
-    suggested_roles: ["Projectleider", "Data scientist", "Ethicus", "Aanbieder", "Gebruiker"]
-    lifecycle: ["Probleemanalyse", "Ontwerp", "Implementatie", "Monitoring en beheer"]
-    links: ["DPIA vraag 16"]
-    requirements: []
-    <<: *default_answers
-  - question: "Welke risico's voor stigmatiserende, discriminerende of anderszins schadelijke of nadelige effecten zijn er voor de burger en hoe zullen die worden bestreden of gemitigeerd?"
-    id: 3.3.2
-    labels:
-    - key: topic
-      value: "Effecten van het algoritme" 
-    type: "open question"
-    suggested_roles: ["Projectleider", "Data scientist", "Ethicus", "Aanbieder", "Gebruiker"]
-    lifecycle: ["Probleemanalyse", "Ontwerp", "Ontwikkelen", "Implementatie"]
-    links: ["DPIA vraag 16", "DPIA vraag 17"]
-    requirements: []
-    <<: *default_answers
-  - question: Hoe zullen de verwachte effecten bijdragen aan de oplossing van het probleem dat de aanleiding is voor de ontwikkeling/inzet van het algoritme (zie vraag 1.1) en het bereiken van de daarbij gestelde doelen (zie vraag 1.2)?
-    id: 3.3.3
-    labels:
-    - key: topic
-      value: "Effecten van het algoritme" 
-    type: "open question"
-    suggested_roles: ["Projectleider", "Data scientist", "Ethicus", "Aanbieder", "Gebruiker"]
-    lifecycle: ["Probleemanalyse"]
-    links: []
-    requirements: []
-    <<: *default_answers
-  - question: Hoe verhouden de verwachte effecten zich tot de waarden die worden gediend (zie vraag 1.3)? Welke risico's zijn er dat bepaalde waarden onder druk komen te staan en hoe wordt daarmee dan omgegaan?
-    id: 3.3.4
-    labels:
-    - key: topic
-      value: "Effecten van het algoritme" 
-    type: "open question"
-    suggested_roles: ["Projectleider", "Data scientist", "Ethicus", "Aanbieder", "Gebruiker"]
-    lifecycle: ["Probleemanalyse"]
-    links: []
-    requirements: []
-    <<: *default_answers
-  - question: "Via welke procedures zullen beslissingen op basis van het algoritme worden genomen?"
-    id: 3.4.1
-    labels:
-    - key: topic
-      value: "Procedures" 
-    type: "open question"
-    suggested_roles: ["Projectleider", "Data scientist", "Ethicus", "Jurist"]
-    lifecycle: ["Ontwerp", "Implementatie", "Monitoring en beheer"]
-    links: []
-    requirements: []
-    <<: *default_answers
-  - question: "Hoe worden verschillende relevante actoren (bestuurlijke en politiek verantwoordelijken, burgers) bij de besluitvorming betrokken?"
-    id: 3.4.2
-    labels:
-    - key: topic
-      value: "Procedures" 
-    type: "open question"
-    suggested_roles: ["Projectleider", "Data scientist", "Ethicus", "Jurist"]
-    lifecycle: ["Ontwerp", "Implementatie", "Monitoring en beheer"]
-    links: []
-    requirements: []
-    <<: *default_answers
-  - question: "Hoe wordt gegarandeerd dat in deze procedures wordt voldaan aan de eisen van goed en behoorlijk bestuur en - waar nodig - rechtsbescherming? Hebben burgers een effectieve mogelijkheid om een klacht in te dienen of bezwaar te maken? Zo ja, op welke manier?"
-    id: 3.4.3
-    labels:
-    - key: topic
-      value: "Procedures" 
-    type: "open question"
-    suggested_roles: ["Projectleider", "Data scientist", "Ethicus", "Jurist"]
-    lifecycle: ["Ontwerp", "Implementatie", "Monitoring en beheer"]
-    links: []
-    requirements: []
-    <<: *default_answers
-  - question: "Tijd/periode: wanneer gaat het algoritme ingezet worden? Hoe lang is de periode dat het ingezet wordt?"
-    id: 3.5.1
-    labels:
-    - key: topic
-      value: "Context" 
-    type: "open question"
-    suggested_roles: ["Projectleider", "Data scientist", "Ethicus"]
-    lifecycle: ["Ontwerp", "Implementatie", "Monitoring en beheer"]
-    links: []
-    requirements: []
-    <<: *default_answers
-  - question: "Plaats: waar vindt inzet van het algoritme plaats? Is dat in een bepaald geografisch gebied, is dat bij een bepaalde groep personen of dossiers?"
-    id: 3.5.2
-    labels:
-    - key: topic
-      value: "Context" 
-    type: "open question"
-    suggested_roles: ["Projectleider", "Data scientist", "Ethicus"]
-    lifecycle: ["Ontwerp", "Implementatie", "Monitoring en beheer"]
-    links: []
-    requirements: []
-    <<: *default_answers
-  - question: "Kan het algoritme ook nog worden ingezet als contextfactoren veranderen of als het algoritme gebruikt wordt in een andere context dan waarvoor het is ontwikkeld?"
-    id: 3.5.3
-    labels:
-    - key: topic
-      value: "Context" 
-    type: "open question"
-    suggested_roles: ["Projectleider", "Data scientist", "Ethicus"]
-    lifecycle: ["Ontwerp", "Implementatie", "Monitoring en beheer"]
-    links: []
-    requirements: []
-    <<: *default_answers
-  - question: "Hoe open kunt u zijn over de werking van het algoritme in het licht van de doelstellingen en context van de inzet ervan?"
-    id: 3.6.1
-    labels:
-    - key: topic 
-      value: "Communicatie" 
-    type: "open question"
-    suggested_roles: ["Projectleider", "Behoeftesteller", "Gemandateerd verantwoordelijke(n)", "Ethicus"]
-    lifecycle: ["Ontwerp", "Implementatie", "Monitoring en beheer"]
-    links: ["DPIA vraag 15"]
-    requirements: []
-    <<: *default_answers
-  - question: "Op welke manier beoogt u te communiceren over de inzet van het algoritme?"
-    id: 3.6.2
-    labels:
-    - key: topic
-      value: "Communicatie" 
-    type: "open question"
-    suggested_roles: ["Projectleider", "Behoeftesteller", "Gemandateerd verantwoordelijke(n)", "Ethicus"]
-    lifecycle: ["Ontwerp", "Implementatie", "Monitoring en beheer"]
-    links: ["DPIA vraag 15"]
-    requirements: []
-    <<: *default_answers
-  - question: "Wordt de output van het algoritme gevisualiseerd, bijvoorbeeld in een tabel, grafiek of dashboard? Zo ja: is de vorm van visualisatie of weergave een correcte representatie van de output van het algoritme? Is de visualisatie makkelijk te lezen voor verschillende gebruikersgroepen?"
-    id: 3.6.3
-    labels:
-    - key: topic
-      value: "Communicatie" 
-    type: "open question"
-    suggested_roles: ["Projectleider", "Behoeftesteller", "Gemandateerd verantwoordelijke(n)", "Ethicus"]
-    lifecycle: ["Verificatie en validatie", "Implementatie", "Monitoring en beheer"]
-    links: ["DPIA vraag 15"]
-    requirements: []
-    <<: *default_answers
-  - question: "Is voorzien in goede instrumenten voor evaluatie, auditing en borging van het algoritme?"
-    id: 3.7.1
-    labels:
-    - key: topic
-      value: "Evaluatie, auditing en borging"  
-    type: "open question"
-    suggested_roles: ["Projectleider", "Behoeftesteller", "Gemandateerd verantwoordelijke(n)", "Data scientist"]
-    lifecycle: ["Verificatie en validatie", "Implementatie", "Monitoring en beheer"]
-    links: []
-    requirements: []
-    <<: *default_answers
-  - question: "Zijn er voldoende mogelijkheden om rekenschap en verantwoording af te leggen over het algoritme?"
-    id: 3.7.2
-    labels:
-    - key: topic
-      value: "Evaluatie, auditing en borging"  
-    type: "open question"
-    suggested_roles: ["Projectleider", "Behoeftesteller", "Gemandateerd verantwoordelijke(n)", "Data scientist"]
-    lifecycle: ["Ontwerp", "Implementatie", "Monitoring en beheer"]
-    links: []
-    requirements: []
-    <<: *default_answers
-  - question: "Welke mogelijkheden zijn er voor auditors en toezichthouders om (formele) consequenties te verbinden aan de inzet van een algoritme door de overheid (bijv. terugkoppeling van bevindingen, doen van aanbevelingen, budgettaire consequenties, ...)"
-    id: 3.7.3
-    labels:
-    - key: topic
-      value: "Evaluatie, auditing en borging"   
-    type: "open question"
-    suggested_roles: ["Projectleider", "Behoeftesteller", "Gemandateerd verantwoordelijke(n)", "Data scientist"]
-    lifecycle: ["Implementatie", "Monitoring en beheer"]
-    links: []
-    requirements: []
-    <<: *default_answers
-  - question: "Wordt er een grondrecht geraakt door het in te zetten algoritme?"
-    id: 4.1.1
-    labels:
-    - key: topic
-      value: "Grondrecht" 
-    type: "open question"
-    suggested_roles: ["Projectleider", "Domeinspecialist", "Jurist"]
-    lifecycle: ["Probleemanalyse"]
-    links: ["DPIA vraag 16"]
-    requirements: []
-    <<: *default_answers
-  - question: "Zijn er specifieke wettelijke bepalingen of richtsnoeren van toepassing op de grondrechteninbreuk?"
-    id: 4.2.1
-    labels:
-    - key: topic
-      value: "Specifieke wetgeving en richtsnoeren" 
-    type: "open question"
-    suggested_roles: ["Projectleider", "Domeinspecialist", "Jurist"]
-    lifecycle: ["Probleemanalyse"]
-    links: ["DPIA vraag 9"]
-    requirements: []
-    <<: *default_answers
-  - question: "Hoe zwaar wordt een grondrecht geraakt door het algoritme?"
-    id: 4.3.1
-    labels:
-    - key: topic
-      value: "Zwaartebepaling" 
-    type: "open question"
-    suggested_roles: ["Projectleider", "Domeinspecialist", "Jurist"]
-    lifecycle: ["Probleemanalyse"]
-    links: ["DPIA vraag 16"]
-    requirements: []
-    <<: *default_answers
-  - question: "Welke doelen worden met inzet van het algoritme nagestreefd? Kijk hierbij naar uw antwoord op vraag 1.2"
-    id: 4.4.1
-    labels:
-    - key: topic 
-      value: "Doelstellingen" 
-    type: "open question"
-    suggested_roles: ["Projectleider", "Domeinspecialist", "Jurist"]
-    lifecycle: ["Probleemanalyse"]
-    links: []
-    requirements: []
-    <<: *default_answers
-  - question: "Vormt het in te zetten algoritme een doeltreffend middel om de gestelde doelen te realiseren? Leg uit."
-    id: 4.5.1
-    labels:
-    - key: topic
-      value: "Doeltreffendheid/effectiviteit/geschiktheid"
-    type: "open question"
-    suggested_roles: ["Projectleider", "Domeinspecialist", "Jurist"]
-    lifecycle: ["Probleemanalyse"]
-    links: ["DPIA vraag 14"]
-    requirements: []
-    <<: *default_answers
-  - question: "Is inzet van dit specifieke algoritme noodzakelijk om dit doel te bereiken en zijn er geen andere of mitigerende maatregelen beschikbaar om dit te doen? Leg uit."
-    id: 4.6.1
-    labels:
-    - key: topic
-      value: "Noodzakelijkheid/subsidiariteit" 
-    type: "open question"
-    suggested_roles: ["Projectleider", "Domeinspecialist", "Jurist"]
-    lifecycle: ["Probleemanalyse"]
-    links: ["DPIA vraag 14"]
-    requirements: []
-    <<: *default_answers
-  - question: "Levert inzet van het algoritme een redelijk evenwicht op tussen de te realiseren doelen en de grondrechten die worden geraakt, en waarom is dat zo?"
-    id: 4.7.1
-    labels:
-    - key: topic
-      value: "Belangenafweging/proportionaliteit" 
-    type: "open question"
-    suggested_roles: ["Projectleider", "Domeinspecialist", "Jurist"]
-    lifecycle: ["Probleemanalyse"]
-    links: ["DPIA vraag 14"]
-    requirements: []
-    <<: *default_answers
-
-
-
diff --git a/poetry.lock b/poetry.lock
new file mode 100644
index 0000000..192edc0
--- /dev/null
+++ b/poetry.lock
@@ -0,0 +1,243 @@
+# This file is automatically @generated by Poetry 1.8.2 and should not be changed by hand.
+
+[[package]]
+name = "attrs"
+version = "23.2.0"
+description = "Classes Without Boilerplate"
+optional = false
+python-versions = ">=3.7"
+files = [
+    {file = "attrs-23.2.0-py3-none-any.whl", hash = "sha256:99b87a485a5820b23b879f04c2305b44b951b502fd64be915879d77a7e8fc6f1"},
+    {file = "attrs-23.2.0.tar.gz", hash = "sha256:935dc3b529c262f6cf76e50877d35a4bd3c1de194fd41f47a2b7ae8f19971f30"},
+]
+
+[package.extras]
+cov = ["attrs[tests]", "coverage[toml] (>=5.3)"]
+dev = ["attrs[tests]", "pre-commit"]
+docs = ["furo", "myst-parser", "sphinx", "sphinx-notfound-page", "sphinxcontrib-towncrier", "towncrier", "zope-interface"]
+tests = ["attrs[tests-no-zope]", "zope-interface"]
+tests-mypy = ["mypy (>=1.6)", "pytest-mypy-plugins"]
+tests-no-zope = ["attrs[tests-mypy]", "cloudpickle", "hypothesis", "pympler", "pytest (>=4.3.0)", "pytest-xdist[psutil]"]
+
+[[package]]
+name = "jsonschema"
+version = "4.22.0"
+description = "An implementation of JSON Schema validation for Python"
+optional = false
+python-versions = ">=3.8"
+files = [
+    {file = "jsonschema-4.22.0-py3-none-any.whl", hash = "sha256:ff4cfd6b1367a40e7bc6411caec72effadd3db0bbe5017de188f2d6108335802"},
+    {file = "jsonschema-4.22.0.tar.gz", hash = "sha256:5b22d434a45935119af990552c862e5d6d564e8f6601206b305a61fdf661a2b7"},
+]
+
+[package.dependencies]
+attrs = ">=22.2.0"
+jsonschema-specifications = ">=2023.03.6"
+referencing = ">=0.28.4"
+rpds-py = ">=0.7.1"
+
+[package.extras]
+format = ["fqdn", "idna", "isoduration", "jsonpointer (>1.13)", "rfc3339-validator", "rfc3987", "uri-template", "webcolors (>=1.11)"]
+format-nongpl = ["fqdn", "idna", "isoduration", "jsonpointer (>1.13)", "rfc3339-validator", "rfc3986-validator (>0.1.0)", "uri-template", "webcolors (>=1.11)"]
+
+[[package]]
+name = "jsonschema-specifications"
+version = "2023.12.1"
+description = "The JSON Schema meta-schemas and vocabularies, exposed as a Registry"
+optional = false
+python-versions = ">=3.8"
+files = [
+    {file = "jsonschema_specifications-2023.12.1-py3-none-any.whl", hash = "sha256:87e4fdf3a94858b8a2ba2778d9ba57d8a9cafca7c7489c46ba0d30a8bc6a9c3c"},
+    {file = "jsonschema_specifications-2023.12.1.tar.gz", hash = "sha256:48a76787b3e70f5ed53f1160d2b81f586e4ca6d1548c5de7085d1682674764cc"},
+]
+
+[package.dependencies]
+referencing = ">=0.31.0"
+
+[[package]]
+name = "pyyaml"
+version = "6.0.1"
+description = "YAML parser and emitter for Python"
+optional = false
+python-versions = ">=3.6"
+files = [
+    {file = "PyYAML-6.0.1-cp310-cp310-macosx_10_9_x86_64.whl", hash = "sha256:d858aa552c999bc8a8d57426ed01e40bef403cd8ccdd0fc5f6f04a00414cac2a"},
+    {file = "PyYAML-6.0.1-cp310-cp310-macosx_11_0_arm64.whl", hash = "sha256:fd66fc5d0da6d9815ba2cebeb4205f95818ff4b79c3ebe268e75d961704af52f"},
+    {file = "PyYAML-6.0.1-cp310-cp310-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:69b023b2b4daa7548bcfbd4aa3da05b3a74b772db9e23b982788168117739938"},
+    {file = "PyYAML-6.0.1-cp310-cp310-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:81e0b275a9ecc9c0c0c07b4b90ba548307583c125f54d5b6946cfee6360c733d"},
+    {file = "PyYAML-6.0.1-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:ba336e390cd8e4d1739f42dfe9bb83a3cc2e80f567d8805e11b46f4a943f5515"},
+    {file = "PyYAML-6.0.1-cp310-cp310-musllinux_1_1_x86_64.whl", hash = "sha256:326c013efe8048858a6d312ddd31d56e468118ad4cdeda36c719bf5bb6192290"},
+    {file = "PyYAML-6.0.1-cp310-cp310-win32.whl", hash = "sha256:bd4af7373a854424dabd882decdc5579653d7868b8fb26dc7d0e99f823aa5924"},
+    {file = "PyYAML-6.0.1-cp310-cp310-win_amd64.whl", hash = "sha256:fd1592b3fdf65fff2ad0004b5e363300ef59ced41c2e6b3a99d4089fa8c5435d"},
+    {file = "PyYAML-6.0.1-cp311-cp311-macosx_10_9_x86_64.whl", hash = "sha256:6965a7bc3cf88e5a1c3bd2e0b5c22f8d677dc88a455344035f03399034eb3007"},
+    {file = "PyYAML-6.0.1-cp311-cp311-macosx_11_0_arm64.whl", hash = "sha256:f003ed9ad21d6a4713f0a9b5a7a0a79e08dd0f221aff4525a2be4c346ee60aab"},
+    {file = "PyYAML-6.0.1-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:42f8152b8dbc4fe7d96729ec2b99c7097d656dc1213a3229ca5383f973a5ed6d"},
+    {file = "PyYAML-6.0.1-cp311-cp311-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:062582fca9fabdd2c8b54a3ef1c978d786e0f6b3a1510e0ac93ef59e0ddae2bc"},
+    {file = "PyYAML-6.0.1-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:d2b04aac4d386b172d5b9692e2d2da8de7bfb6c387fa4f801fbf6fb2e6ba4673"},
+    {file = "PyYAML-6.0.1-cp311-cp311-musllinux_1_1_x86_64.whl", hash = "sha256:e7d73685e87afe9f3b36c799222440d6cf362062f78be1013661b00c5c6f678b"},
+    {file = "PyYAML-6.0.1-cp311-cp311-win32.whl", hash = "sha256:1635fd110e8d85d55237ab316b5b011de701ea0f29d07611174a1b42f1444741"},
+    {file = "PyYAML-6.0.1-cp311-cp311-win_amd64.whl", hash = "sha256:bf07ee2fef7014951eeb99f56f39c9bb4af143d8aa3c21b1677805985307da34"},
+    {file = "PyYAML-6.0.1-cp312-cp312-macosx_10_9_x86_64.whl", hash = "sha256:855fb52b0dc35af121542a76b9a84f8d1cd886ea97c84703eaa6d88e37a2ad28"},
+    {file = "PyYAML-6.0.1-cp312-cp312-macosx_11_0_arm64.whl", hash = "sha256:40df9b996c2b73138957fe23a16a4f0ba614f4c0efce1e9406a184b6d07fa3a9"},
+    {file = "PyYAML-6.0.1-cp312-cp312-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:a08c6f0fe150303c1c6b71ebcd7213c2858041a7e01975da3a99aed1e7a378ef"},
+    {file = "PyYAML-6.0.1-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:6c22bec3fbe2524cde73d7ada88f6566758a8f7227bfbf93a408a9d86bcc12a0"},
+    {file = "PyYAML-6.0.1-cp312-cp312-musllinux_1_1_x86_64.whl", hash = "sha256:8d4e9c88387b0f5c7d5f281e55304de64cf7f9c0021a3525bd3b1c542da3b0e4"},
+    {file = "PyYAML-6.0.1-cp312-cp312-win32.whl", hash = "sha256:d483d2cdf104e7c9fa60c544d92981f12ad66a457afae824d146093b8c294c54"},
+    {file = "PyYAML-6.0.1-cp312-cp312-win_amd64.whl", hash = "sha256:0d3304d8c0adc42be59c5f8a4d9e3d7379e6955ad754aa9d6ab7a398b59dd1df"},
+    {file = "PyYAML-6.0.1-cp36-cp36m-macosx_10_9_x86_64.whl", hash = "sha256:50550eb667afee136e9a77d6dc71ae76a44df8b3e51e41b77f6de2932bfe0f47"},
+    {file = "PyYAML-6.0.1-cp36-cp36m-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:1fe35611261b29bd1de0070f0b2f47cb6ff71fa6595c077e42bd0c419fa27b98"},
+    {file = "PyYAML-6.0.1-cp36-cp36m-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:704219a11b772aea0d8ecd7058d0082713c3562b4e271b849ad7dc4a5c90c13c"},
+    {file = "PyYAML-6.0.1-cp36-cp36m-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:afd7e57eddb1a54f0f1a974bc4391af8bcce0b444685d936840f125cf046d5bd"},
+    {file = "PyYAML-6.0.1-cp36-cp36m-win32.whl", hash = "sha256:fca0e3a251908a499833aa292323f32437106001d436eca0e6e7833256674585"},
+    {file = "PyYAML-6.0.1-cp36-cp36m-win_amd64.whl", hash = "sha256:f22ac1c3cac4dbc50079e965eba2c1058622631e526bd9afd45fedd49ba781fa"},
+    {file = "PyYAML-6.0.1-cp37-cp37m-macosx_10_9_x86_64.whl", hash = "sha256:b1275ad35a5d18c62a7220633c913e1b42d44b46ee12554e5fd39c70a243d6a3"},
+    {file = "PyYAML-6.0.1-cp37-cp37m-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:18aeb1bf9a78867dc38b259769503436b7c72f7a1f1f4c93ff9a17de54319b27"},
+    {file = "PyYAML-6.0.1-cp37-cp37m-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:596106435fa6ad000c2991a98fa58eeb8656ef2325d7e158344fb33864ed87e3"},
+    {file = "PyYAML-6.0.1-cp37-cp37m-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:baa90d3f661d43131ca170712d903e6295d1f7a0f595074f151c0aed377c9b9c"},
+    {file = "PyYAML-6.0.1-cp37-cp37m-win32.whl", hash = "sha256:9046c58c4395dff28dd494285c82ba00b546adfc7ef001486fbf0324bc174fba"},
+    {file = "PyYAML-6.0.1-cp37-cp37m-win_amd64.whl", hash = "sha256:4fb147e7a67ef577a588a0e2c17b6db51dda102c71de36f8549b6816a96e1867"},
+    {file = "PyYAML-6.0.1-cp38-cp38-macosx_10_9_x86_64.whl", hash = "sha256:1d4c7e777c441b20e32f52bd377e0c409713e8bb1386e1099c2415f26e479595"},
+    {file = "PyYAML-6.0.1-cp38-cp38-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:a0cd17c15d3bb3fa06978b4e8958dcdc6e0174ccea823003a106c7d4d7899ac5"},
+    {file = "PyYAML-6.0.1-cp38-cp38-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:28c119d996beec18c05208a8bd78cbe4007878c6dd15091efb73a30e90539696"},
+    {file = "PyYAML-6.0.1-cp38-cp38-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:7e07cbde391ba96ab58e532ff4803f79c4129397514e1413a7dc761ccd755735"},
+    {file = "PyYAML-6.0.1-cp38-cp38-musllinux_1_1_x86_64.whl", hash = "sha256:49a183be227561de579b4a36efbb21b3eab9651dd81b1858589f796549873dd6"},
+    {file = "PyYAML-6.0.1-cp38-cp38-win32.whl", hash = "sha256:184c5108a2aca3c5b3d3bf9395d50893a7ab82a38004c8f61c258d4428e80206"},
+    {file = "PyYAML-6.0.1-cp38-cp38-win_amd64.whl", hash = "sha256:1e2722cc9fbb45d9b87631ac70924c11d3a401b2d7f410cc0e3bbf249f2dca62"},
+    {file = "PyYAML-6.0.1-cp39-cp39-macosx_10_9_x86_64.whl", hash = "sha256:9eb6caa9a297fc2c2fb8862bc5370d0303ddba53ba97e71f08023b6cd73d16a8"},
+    {file = "PyYAML-6.0.1-cp39-cp39-macosx_11_0_arm64.whl", hash = "sha256:c8098ddcc2a85b61647b2590f825f3db38891662cfc2fc776415143f599bb859"},
+    {file = "PyYAML-6.0.1-cp39-cp39-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:5773183b6446b2c99bb77e77595dd486303b4faab2b086e7b17bc6bef28865f6"},
+    {file = "PyYAML-6.0.1-cp39-cp39-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:b786eecbdf8499b9ca1d697215862083bd6d2a99965554781d0d8d1ad31e13a0"},
+    {file = "PyYAML-6.0.1-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:bc1bf2925a1ecd43da378f4db9e4f799775d6367bdb94671027b73b393a7c42c"},
+    {file = "PyYAML-6.0.1-cp39-cp39-musllinux_1_1_x86_64.whl", hash = "sha256:04ac92ad1925b2cff1db0cfebffb6ffc43457495c9b3c39d3fcae417d7125dc5"},
+    {file = "PyYAML-6.0.1-cp39-cp39-win32.whl", hash = "sha256:faca3bdcf85b2fc05d06ff3fbc1f83e1391b3e724afa3feba7d13eeab355484c"},
+    {file = "PyYAML-6.0.1-cp39-cp39-win_amd64.whl", hash = "sha256:510c9deebc5c0225e8c96813043e62b680ba2f9c50a08d3724c7f28a747d1486"},
+    {file = "PyYAML-6.0.1.tar.gz", hash = "sha256:bfdf460b1736c775f2ba9f6a92bca30bc2095067b8a9d77876d1fad6cc3b4a43"},
+]
+
+[[package]]
+name = "referencing"
+version = "0.35.1"
+description = "JSON Referencing + Python"
+optional = false
+python-versions = ">=3.8"
+files = [
+    {file = "referencing-0.35.1-py3-none-any.whl", hash = "sha256:eda6d3234d62814d1c64e305c1331c9a3a6132da475ab6382eaa997b21ee75de"},
+    {file = "referencing-0.35.1.tar.gz", hash = "sha256:25b42124a6c8b632a425174f24087783efb348a6f1e0008e63cd4466fedf703c"},
+]
+
+[package.dependencies]
+attrs = ">=22.2.0"
+rpds-py = ">=0.7.0"
+
+[[package]]
+name = "rpds-py"
+version = "0.18.1"
+description = "Python bindings to Rust's persistent data structures (rpds)"
+optional = false
+python-versions = ">=3.8"
+files = [
+    {file = "rpds_py-0.18.1-cp310-cp310-macosx_10_12_x86_64.whl", hash = "sha256:d31dea506d718693b6b2cffc0648a8929bdc51c70a311b2770f09611caa10d53"},
+    {file = "rpds_py-0.18.1-cp310-cp310-macosx_11_0_arm64.whl", hash = "sha256:732672fbc449bab754e0b15356c077cc31566df874964d4801ab14f71951ea80"},
+    {file = "rpds_py-0.18.1-cp310-cp310-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:4a98a1f0552b5f227a3d6422dbd61bc6f30db170939bd87ed14f3c339aa6c7c9"},
+    {file = "rpds_py-0.18.1-cp310-cp310-manylinux_2_17_armv7l.manylinux2014_armv7l.whl", hash = "sha256:7f1944ce16401aad1e3f7d312247b3d5de7981f634dc9dfe90da72b87d37887d"},
+    {file = "rpds_py-0.18.1-cp310-cp310-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl", hash = "sha256:38e14fb4e370885c4ecd734f093a2225ee52dc384b86fa55fe3f74638b2cfb09"},
+    {file = "rpds_py-0.18.1-cp310-cp310-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:08d74b184f9ab6289b87b19fe6a6d1a97fbfea84b8a3e745e87a5de3029bf944"},
+    {file = "rpds_py-0.18.1-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:d70129cef4a8d979caa37e7fe957202e7eee8ea02c5e16455bc9808a59c6b2f0"},
+    {file = "rpds_py-0.18.1-cp310-cp310-manylinux_2_5_i686.manylinux1_i686.whl", hash = "sha256:ce0bb20e3a11bd04461324a6a798af34d503f8d6f1aa3d2aa8901ceaf039176d"},
+    {file = "rpds_py-0.18.1-cp310-cp310-musllinux_1_2_aarch64.whl", hash = "sha256:81c5196a790032e0fc2464c0b4ab95f8610f96f1f2fa3d4deacce6a79852da60"},
+    {file = "rpds_py-0.18.1-cp310-cp310-musllinux_1_2_i686.whl", hash = "sha256:f3027be483868c99b4985fda802a57a67fdf30c5d9a50338d9db646d590198da"},
+    {file = "rpds_py-0.18.1-cp310-cp310-musllinux_1_2_x86_64.whl", hash = "sha256:d44607f98caa2961bab4fa3c4309724b185b464cdc3ba6f3d7340bac3ec97cc1"},
+    {file = "rpds_py-0.18.1-cp310-none-win32.whl", hash = "sha256:c273e795e7a0f1fddd46e1e3cb8be15634c29ae8ff31c196debb620e1edb9333"},
+    {file = "rpds_py-0.18.1-cp310-none-win_amd64.whl", hash = "sha256:8352f48d511de5f973e4f2f9412736d7dea76c69faa6d36bcf885b50c758ab9a"},
+    {file = "rpds_py-0.18.1-cp311-cp311-macosx_10_12_x86_64.whl", hash = "sha256:6b5ff7e1d63a8281654b5e2896d7f08799378e594f09cf3674e832ecaf396ce8"},
+    {file = "rpds_py-0.18.1-cp311-cp311-macosx_11_0_arm64.whl", hash = "sha256:8927638a4d4137a289e41d0fd631551e89fa346d6dbcfc31ad627557d03ceb6d"},
+    {file = "rpds_py-0.18.1-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:154bf5c93d79558b44e5b50cc354aa0459e518e83677791e6adb0b039b7aa6a7"},
+    {file = "rpds_py-0.18.1-cp311-cp311-manylinux_2_17_armv7l.manylinux2014_armv7l.whl", hash = "sha256:07f2139741e5deb2c5154a7b9629bc5aa48c766b643c1a6750d16f865a82c5fc"},
+    {file = "rpds_py-0.18.1-cp311-cp311-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl", hash = "sha256:8c7672e9fba7425f79019db9945b16e308ed8bc89348c23d955c8c0540da0a07"},
+    {file = "rpds_py-0.18.1-cp311-cp311-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:489bdfe1abd0406eba6b3bb4fdc87c7fa40f1031de073d0cfb744634cc8fa261"},
+    {file = "rpds_py-0.18.1-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:3c20f05e8e3d4fc76875fc9cb8cf24b90a63f5a1b4c5b9273f0e8225e169b100"},
+    {file = "rpds_py-0.18.1-cp311-cp311-manylinux_2_5_i686.manylinux1_i686.whl", hash = "sha256:967342e045564cef76dfcf1edb700b1e20838d83b1aa02ab313e6a497cf923b8"},
+    {file = "rpds_py-0.18.1-cp311-cp311-musllinux_1_2_aarch64.whl", hash = "sha256:2cc7c1a47f3a63282ab0f422d90ddac4aa3034e39fc66a559ab93041e6505da7"},
+    {file = "rpds_py-0.18.1-cp311-cp311-musllinux_1_2_i686.whl", hash = "sha256:f7afbfee1157e0f9376c00bb232e80a60e59ed716e3211a80cb8506550671e6e"},
+    {file = "rpds_py-0.18.1-cp311-cp311-musllinux_1_2_x86_64.whl", hash = "sha256:9e6934d70dc50f9f8ea47081ceafdec09245fd9f6032669c3b45705dea096b88"},
+    {file = "rpds_py-0.18.1-cp311-none-win32.whl", hash = "sha256:c69882964516dc143083d3795cb508e806b09fc3800fd0d4cddc1df6c36e76bb"},
+    {file = "rpds_py-0.18.1-cp311-none-win_amd64.whl", hash = "sha256:70a838f7754483bcdc830444952fd89645569e7452e3226de4a613a4c1793fb2"},
+    {file = "rpds_py-0.18.1-cp312-cp312-macosx_10_12_x86_64.whl", hash = "sha256:3dd3cd86e1db5aadd334e011eba4e29d37a104b403e8ca24dcd6703c68ca55b3"},
+    {file = "rpds_py-0.18.1-cp312-cp312-macosx_11_0_arm64.whl", hash = "sha256:05f3d615099bd9b13ecf2fc9cf2d839ad3f20239c678f461c753e93755d629ee"},
+    {file = "rpds_py-0.18.1-cp312-cp312-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:35b2b771b13eee8729a5049c976197ff58a27a3829c018a04341bcf1ae409b2b"},
+    {file = "rpds_py-0.18.1-cp312-cp312-manylinux_2_17_armv7l.manylinux2014_armv7l.whl", hash = "sha256:ee17cd26b97d537af8f33635ef38be873073d516fd425e80559f4585a7b90c43"},
+    {file = "rpds_py-0.18.1-cp312-cp312-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl", hash = "sha256:b646bf655b135ccf4522ed43d6902af37d3f5dbcf0da66c769a2b3938b9d8184"},
+    {file = "rpds_py-0.18.1-cp312-cp312-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:19ba472b9606c36716062c023afa2484d1e4220548751bda14f725a7de17b4f6"},
+    {file = "rpds_py-0.18.1-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:6e30ac5e329098903262dc5bdd7e2086e0256aa762cc8b744f9e7bf2a427d3f8"},
+    {file = "rpds_py-0.18.1-cp312-cp312-manylinux_2_5_i686.manylinux1_i686.whl", hash = "sha256:d58ad6317d188c43750cb76e9deacf6051d0f884d87dc6518e0280438648a9ac"},
+    {file = "rpds_py-0.18.1-cp312-cp312-musllinux_1_2_aarch64.whl", hash = "sha256:e1735502458621921cee039c47318cb90b51d532c2766593be6207eec53e5c4c"},
+    {file = "rpds_py-0.18.1-cp312-cp312-musllinux_1_2_i686.whl", hash = "sha256:f5bab211605d91db0e2995a17b5c6ee5edec1270e46223e513eaa20da20076ac"},
+    {file = "rpds_py-0.18.1-cp312-cp312-musllinux_1_2_x86_64.whl", hash = "sha256:2fc24a329a717f9e2448f8cd1f960f9dac4e45b6224d60734edeb67499bab03a"},
+    {file = "rpds_py-0.18.1-cp312-none-win32.whl", hash = "sha256:1805d5901779662d599d0e2e4159d8a82c0b05faa86ef9222bf974572286b2b6"},
+    {file = "rpds_py-0.18.1-cp312-none-win_amd64.whl", hash = "sha256:720edcb916df872d80f80a1cc5ea9058300b97721efda8651efcd938a9c70a72"},
+    {file = "rpds_py-0.18.1-cp38-cp38-macosx_10_12_x86_64.whl", hash = "sha256:c827576e2fa017a081346dce87d532a5310241648eb3700af9a571a6e9fc7e74"},
+    {file = "rpds_py-0.18.1-cp38-cp38-macosx_11_0_arm64.whl", hash = "sha256:aa3679e751408d75a0b4d8d26d6647b6d9326f5e35c00a7ccd82b78ef64f65f8"},
+    {file = "rpds_py-0.18.1-cp38-cp38-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:0abeee75434e2ee2d142d650d1e54ac1f8b01e6e6abdde8ffd6eeac6e9c38e20"},
+    {file = "rpds_py-0.18.1-cp38-cp38-manylinux_2_17_armv7l.manylinux2014_armv7l.whl", hash = "sha256:ed402d6153c5d519a0faf1bb69898e97fb31613b49da27a84a13935ea9164dfc"},
+    {file = "rpds_py-0.18.1-cp38-cp38-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl", hash = "sha256:338dee44b0cef8b70fd2ef54b4e09bb1b97fc6c3a58fea5db6cc083fd9fc2724"},
+    {file = "rpds_py-0.18.1-cp38-cp38-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:7750569d9526199c5b97e5a9f8d96a13300950d910cf04a861d96f4273d5b104"},
+    {file = "rpds_py-0.18.1-cp38-cp38-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:607345bd5912aacc0c5a63d45a1f73fef29e697884f7e861094e443187c02be5"},
+    {file = "rpds_py-0.18.1-cp38-cp38-manylinux_2_5_i686.manylinux1_i686.whl", hash = "sha256:207c82978115baa1fd8d706d720b4a4d2b0913df1c78c85ba73fe6c5804505f0"},
+    {file = "rpds_py-0.18.1-cp38-cp38-musllinux_1_2_aarch64.whl", hash = "sha256:6d1e42d2735d437e7e80bab4d78eb2e459af48c0a46e686ea35f690b93db792d"},
+    {file = "rpds_py-0.18.1-cp38-cp38-musllinux_1_2_i686.whl", hash = "sha256:5463c47c08630007dc0fe99fb480ea4f34a89712410592380425a9b4e1611d8e"},
+    {file = "rpds_py-0.18.1-cp38-cp38-musllinux_1_2_x86_64.whl", hash = "sha256:06d218939e1bf2ca50e6b0ec700ffe755e5216a8230ab3e87c059ebb4ea06afc"},
+    {file = "rpds_py-0.18.1-cp38-none-win32.whl", hash = "sha256:312fe69b4fe1ffbe76520a7676b1e5ac06ddf7826d764cc10265c3b53f96dbe9"},
+    {file = "rpds_py-0.18.1-cp38-none-win_amd64.whl", hash = "sha256:9437ca26784120a279f3137ee080b0e717012c42921eb07861b412340f85bae2"},
+    {file = "rpds_py-0.18.1-cp39-cp39-macosx_10_12_x86_64.whl", hash = "sha256:19e515b78c3fc1039dd7da0a33c28c3154458f947f4dc198d3c72db2b6b5dc93"},
+    {file = "rpds_py-0.18.1-cp39-cp39-macosx_11_0_arm64.whl", hash = "sha256:a7b28c5b066bca9a4eb4e2f2663012debe680f097979d880657f00e1c30875a0"},
+    {file = "rpds_py-0.18.1-cp39-cp39-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:673fdbbf668dd958eff750e500495ef3f611e2ecc209464f661bc82e9838991e"},
+    {file = "rpds_py-0.18.1-cp39-cp39-manylinux_2_17_armv7l.manylinux2014_armv7l.whl", hash = "sha256:d960de62227635d2e61068f42a6cb6aae91a7fe00fca0e3aeed17667c8a34611"},
+    {file = "rpds_py-0.18.1-cp39-cp39-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl", hash = "sha256:352a88dc7892f1da66b6027af06a2e7e5d53fe05924cc2cfc56495b586a10b72"},
+    {file = "rpds_py-0.18.1-cp39-cp39-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:4e0ee01ad8260184db21468a6e1c37afa0529acc12c3a697ee498d3c2c4dcaf3"},
+    {file = "rpds_py-0.18.1-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:e4c39ad2f512b4041343ea3c7894339e4ca7839ac38ca83d68a832fc8b3748ab"},
+    {file = "rpds_py-0.18.1-cp39-cp39-manylinux_2_5_i686.manylinux1_i686.whl", hash = "sha256:aaa71ee43a703c321906813bb252f69524f02aa05bf4eec85f0c41d5d62d0f4c"},
+    {file = "rpds_py-0.18.1-cp39-cp39-musllinux_1_2_aarch64.whl", hash = "sha256:6cd8098517c64a85e790657e7b1e509b9fe07487fd358e19431cb120f7d96338"},
+    {file = "rpds_py-0.18.1-cp39-cp39-musllinux_1_2_i686.whl", hash = "sha256:4adec039b8e2928983f885c53b7cc4cda8965b62b6596501a0308d2703f8af1b"},
+    {file = "rpds_py-0.18.1-cp39-cp39-musllinux_1_2_x86_64.whl", hash = "sha256:32b7daaa3e9389db3695964ce8e566e3413b0c43e3394c05e4b243a4cd7bef26"},
+    {file = "rpds_py-0.18.1-cp39-none-win32.whl", hash = "sha256:2625f03b105328729f9450c8badda34d5243231eef6535f80064d57035738360"},
+    {file = "rpds_py-0.18.1-cp39-none-win_amd64.whl", hash = "sha256:bf18932d0003c8c4d51a39f244231986ab23ee057d235a12b2684ea26a353590"},
+    {file = "rpds_py-0.18.1-pp310-pypy310_pp73-macosx_10_12_x86_64.whl", hash = "sha256:cbfbea39ba64f5e53ae2915de36f130588bba71245b418060ec3330ebf85678e"},
+    {file = "rpds_py-0.18.1-pp310-pypy310_pp73-macosx_11_0_arm64.whl", hash = "sha256:a3d456ff2a6a4d2adcdf3c1c960a36f4fd2fec6e3b4902a42a384d17cf4e7a65"},
+    {file = "rpds_py-0.18.1-pp310-pypy310_pp73-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:7700936ef9d006b7ef605dc53aa364da2de5a3aa65516a1f3ce73bf82ecfc7ae"},
+    {file = "rpds_py-0.18.1-pp310-pypy310_pp73-manylinux_2_17_armv7l.manylinux2014_armv7l.whl", hash = "sha256:51584acc5916212e1bf45edd17f3a6b05fe0cbb40482d25e619f824dccb679de"},
+    {file = "rpds_py-0.18.1-pp310-pypy310_pp73-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl", hash = "sha256:942695a206a58d2575033ff1e42b12b2aece98d6003c6bc739fbf33d1773b12f"},
+    {file = "rpds_py-0.18.1-pp310-pypy310_pp73-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:b906b5f58892813e5ba5c6056d6a5ad08f358ba49f046d910ad992196ea61397"},
+    {file = "rpds_py-0.18.1-pp310-pypy310_pp73-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:f6f8e3fecca256fefc91bb6765a693d96692459d7d4c644660a9fff32e517843"},
+    {file = "rpds_py-0.18.1-pp310-pypy310_pp73-manylinux_2_5_i686.manylinux1_i686.whl", hash = "sha256:7732770412bab81c5a9f6d20aeb60ae943a9b36dcd990d876a773526468e7163"},
+    {file = "rpds_py-0.18.1-pp310-pypy310_pp73-musllinux_1_2_aarch64.whl", hash = "sha256:bd1105b50ede37461c1d51b9698c4f4be6e13e69a908ab7751e3807985fc0346"},
+    {file = "rpds_py-0.18.1-pp310-pypy310_pp73-musllinux_1_2_i686.whl", hash = "sha256:618916f5535784960f3ecf8111581f4ad31d347c3de66d02e728de460a46303c"},
+    {file = "rpds_py-0.18.1-pp310-pypy310_pp73-musllinux_1_2_x86_64.whl", hash = "sha256:17c6d2155e2423f7e79e3bb18151c686d40db42d8645e7977442170c360194d4"},
+    {file = "rpds_py-0.18.1-pp38-pypy38_pp73-macosx_10_12_x86_64.whl", hash = "sha256:6c4c4c3f878df21faf5fac86eda32671c27889e13570645a9eea0a1abdd50922"},
+    {file = "rpds_py-0.18.1-pp38-pypy38_pp73-macosx_11_0_arm64.whl", hash = "sha256:fab6ce90574645a0d6c58890e9bcaac8d94dff54fb51c69e5522a7358b80ab64"},
+    {file = "rpds_py-0.18.1-pp38-pypy38_pp73-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:531796fb842b53f2695e94dc338929e9f9dbf473b64710c28af5a160b2a8927d"},
+    {file = "rpds_py-0.18.1-pp38-pypy38_pp73-manylinux_2_17_armv7l.manylinux2014_armv7l.whl", hash = "sha256:740884bc62a5e2bbb31e584f5d23b32320fd75d79f916f15a788d527a5e83644"},
+    {file = "rpds_py-0.18.1-pp38-pypy38_pp73-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl", hash = "sha256:998125738de0158f088aef3cb264a34251908dd2e5d9966774fdab7402edfab7"},
+    {file = "rpds_py-0.18.1-pp38-pypy38_pp73-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:e2be6e9dd4111d5b31ba3b74d17da54a8319d8168890fbaea4b9e5c3de630ae5"},
+    {file = "rpds_py-0.18.1-pp38-pypy38_pp73-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:d0cee71bc618cd93716f3c1bf56653740d2d13ddbd47673efa8bf41435a60daa"},
+    {file = "rpds_py-0.18.1-pp38-pypy38_pp73-manylinux_2_5_i686.manylinux1_i686.whl", hash = "sha256:2c3caec4ec5cd1d18e5dd6ae5194d24ed12785212a90b37f5f7f06b8bedd7139"},
+    {file = "rpds_py-0.18.1-pp38-pypy38_pp73-musllinux_1_2_aarch64.whl", hash = "sha256:27bba383e8c5231cd559affe169ca0b96ec78d39909ffd817f28b166d7ddd4d8"},
+    {file = "rpds_py-0.18.1-pp38-pypy38_pp73-musllinux_1_2_i686.whl", hash = "sha256:a888e8bdb45916234b99da2d859566f1e8a1d2275a801bb8e4a9644e3c7e7909"},
+    {file = "rpds_py-0.18.1-pp38-pypy38_pp73-musllinux_1_2_x86_64.whl", hash = "sha256:6031b25fb1b06327b43d841f33842b383beba399884f8228a6bb3df3088485ff"},
+    {file = "rpds_py-0.18.1-pp39-pypy39_pp73-macosx_10_12_x86_64.whl", hash = "sha256:48c2faaa8adfacefcbfdb5f2e2e7bdad081e5ace8d182e5f4ade971f128e6bb3"},
+    {file = "rpds_py-0.18.1-pp39-pypy39_pp73-macosx_11_0_arm64.whl", hash = "sha256:d85164315bd68c0806768dc6bb0429c6f95c354f87485ee3593c4f6b14def2bd"},
+    {file = "rpds_py-0.18.1-pp39-pypy39_pp73-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:6afd80f6c79893cfc0574956f78a0add8c76e3696f2d6a15bca2c66c415cf2d4"},
+    {file = "rpds_py-0.18.1-pp39-pypy39_pp73-manylinux_2_17_armv7l.manylinux2014_armv7l.whl", hash = "sha256:fa242ac1ff583e4ec7771141606aafc92b361cd90a05c30d93e343a0c2d82a89"},
+    {file = "rpds_py-0.18.1-pp39-pypy39_pp73-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl", hash = "sha256:d21be4770ff4e08698e1e8e0bce06edb6ea0626e7c8f560bc08222880aca6a6f"},
+    {file = "rpds_py-0.18.1-pp39-pypy39_pp73-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:5c45a639e93a0c5d4b788b2613bd637468edd62f8f95ebc6fcc303d58ab3f0a8"},
+    {file = "rpds_py-0.18.1-pp39-pypy39_pp73-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:910e71711d1055b2768181efa0a17537b2622afeb0424116619817007f8a2b10"},
+    {file = "rpds_py-0.18.1-pp39-pypy39_pp73-manylinux_2_5_i686.manylinux1_i686.whl", hash = "sha256:b9bb1f182a97880f6078283b3505a707057c42bf55d8fca604f70dedfdc0772a"},
+    {file = "rpds_py-0.18.1-pp39-pypy39_pp73-musllinux_1_2_aarch64.whl", hash = "sha256:1d54f74f40b1f7aaa595a02ff42ef38ca654b1469bef7d52867da474243cc633"},
+    {file = "rpds_py-0.18.1-pp39-pypy39_pp73-musllinux_1_2_i686.whl", hash = "sha256:8d2e182c9ee01135e11e9676e9a62dfad791a7a467738f06726872374a83db49"},
+    {file = "rpds_py-0.18.1-pp39-pypy39_pp73-musllinux_1_2_x86_64.whl", hash = "sha256:636a15acc588f70fda1661234761f9ed9ad79ebed3f2125d44be0862708b666e"},
+    {file = "rpds_py-0.18.1.tar.gz", hash = "sha256:dc48b479d540770c811fbd1eb9ba2bb66951863e448efec2e2c102625328e92f"},
+]
+
+[metadata]
+lock-version = "2.0"
+python-versions = "^3.12"
+content-hash = "464f215a9a7130d2e784af1d942d6f03e839168e24df1de76009dc28152813f1"
diff --git a/pyproject.toml b/pyproject.toml
new file mode 100644
index 0000000..be062c6
--- /dev/null
+++ b/pyproject.toml
@@ -0,0 +1,13 @@
+[tool.poetry]
+name = "instrument-registry"
+version = "0.1.0"
+readme = "README.md"
+
+[tool.poetry.dependencies]
+python = "^3.12"
+jsonschema = "^4.22.0"
+pyyaml = "^6.0.1"
+
+[build-system]
+requires = ["poetry-core"]
+build-backend = "poetry.core.masonry.api"
diff --git a/schema.json b/schema.json
new file mode 100644
index 0000000..944b55f
--- /dev/null
+++ b/schema.json
@@ -0,0 +1,245 @@
+{
+  "$id": "http://example.com/schemas/schema_v1.1.0.json",
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "type": "object",
+  "properties": {
+    "systemcard_path": {
+      "type": "string"
+    },
+    "schema_version": {
+      "type": "string",
+      "pattern": "^[0-9]+\\.[0-9]+\\.[0-9]+$",
+      "const": "1.1.0"
+    },
+    "instrument": {
+      "type": "object",
+      "properties": {
+        "name": {
+          "type": "string"
+        },
+        "description": {
+          "type": "string"
+        },
+        "urn": {
+          "type": "string",
+          "pattern": "^urn:nl:aivt:ir:[0-9]+\\.[0-9]+"
+        },
+        "language": {
+          "type": "string",
+          "pattern": "^[a-z]{2}(-[A-Z]{2})?$"
+        },
+        "owners": {
+          "type": "array",
+          "items": {
+            "type": "object",
+            "properties": {
+              "organization": {
+                "type": "string"
+              },
+              "name": {
+                "type": "string"
+              },
+              "email": {
+                "type": "string"
+              },
+              "role": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "organization",
+              "name",
+              "email",
+              "role"
+            ]
+          }
+        },
+        "date": {
+          "type": "string"
+        },
+        "url": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "name",
+        "description",
+        "urn",
+        "language",
+        "owners",
+        "date",
+        "url"
+      ]
+    },
+    "tasks": {
+      "type": "array",
+      "items": {
+        "type": "object",
+        "properties": {
+          "question": {
+            "type": "string"
+          },
+          "urn": {
+            "description": "A unique identifier for the question",
+            "type": "string",
+            "pattern": "^urn:nl:aivt:ir:[0-9]+\\.[0-9]+:[0-9A-Z\\.]+$"
+          },
+          "labels": {
+            "description": "Labels to specify the question",
+            "type": "array",
+            "items": {
+              "type": "object",
+              "properties": {
+                "key": {
+                  "type": "string"
+                },
+                "value": {
+                  "type": "string"
+                }
+              },
+              "required": [
+                "key",
+                "value"
+              ]
+            }
+          },
+          "type": {
+            "description": "Question type",
+            "type": "string",
+            "enum": [
+              "open_question",
+              "closed_question"
+            ]
+          },
+          "suggested_roles": {
+            "description": "Roles suggested to answer question",
+            "type": "array",
+            "items": {
+              "type": "string",
+              "enum": [
+                "Aanbestedingsjurist",
+                "Aanbieder",
+                "Archiefdeskundige",
+                "Behoeftesteller",
+                "Communicatieadviseur",
+                "Contractbeheerder",
+                "Data engineer",
+                "Data scientist",
+                "Domeinspecialist",
+                "Ethicus",
+                "Gebruiker",
+                "Gemandateerd verantwoordelijke(n)",
+                "Informatiebeheerder",
+                "Inkoopadviseur",
+                "Jurist",
+                "Privacy-officer",
+                "Proceseigenaar",
+                "Projectleider",
+                "Security officer"
+              ]
+            }
+          },
+          "lifecycle": {
+            "description": "Part of the algorithm lifecycle to which this question refers",
+            "type": "array",
+            "items": {
+              "type": "string",
+              "enum": [
+                "Probleemanalyse",
+                "Ontwerp",
+                "Dataverkenning en -preparatie",
+                "Ontwikkelen",
+                "Validatie",
+                "Implementatie",
+                "Monitoren",
+                "Beheer",
+                "Archiveren",
+                "Verificatie"
+              ]
+            }
+          },
+          "links": {
+            "description": "Links to other relevant measures / tasks",
+            "type": "array",
+            "items": {
+              "type": "object",
+              "properties": {
+                "text": {
+                  "type": "string"
+                },
+                "urn": {
+                  "type": "string"
+                }
+              }
+            }
+          },
+          "requirements": {
+            "description": "Specific requirements for this question",
+            "type": "array",
+            "items": {
+              "type": "object",
+              "properties": {
+                "text": {
+                  "type": "string"
+                },
+                "urn": {
+                  "type": "string"
+                }
+              }
+            }
+          },
+          "template": {
+            "type": "object",
+            "additionalProperties": {
+              "type": "string",
+              "pattern": "^\\$.*$"
+            },
+            "properties": {
+              "authors": {
+                "type": "array",
+                "items": {
+                  "type": "object",
+                  "properties": {
+                    "name": {
+                      "type": "string",
+                      "const": "$AUTHOR.NAME"
+                    },
+                    "email": {
+                      "type": "string",
+                      "const": "$AUTHOR.EMAIL"
+                    },
+                    "role": {
+                      "type": "string",
+                      "const": "$AUTHOR.ROLE"
+                    }
+                  },
+                  "required": [
+                    "name",
+                    "email",
+                    "role"
+                  ]
+                }
+              }
+            }
+          }
+        },
+        "required": [
+          "urn",
+          "labels",
+          "type",
+          "suggested_roles",
+          "lifecycle",
+          "links",
+          "requirements",
+          "template"
+        ]
+      }
+    }
+  },
+  "required": [
+    "systemcard_path",
+    "schema_version",
+    "instrument",
+    "tasks"
+  ]
+}
diff --git a/schemas/v_1.0.0.json b/schemas/v_1.0.0.json
deleted file mode 100644
index c3afd51..0000000
--- a/schemas/v_1.0.0.json
+++ /dev/null
@@ -1,142 +0,0 @@
-[{
-    "title": "Schema for validating answers to IAMA questions",
-    "type": "object",
-    "properties": {
-        "answers": {
-            "type": "object",
-            "properties": {
-                "answer": {
-                "description": "Answer given to question",
-                "type": "string"
-                },
-                "remarks": {
-                    "description": "Optional remarks added to answer",
-                    "type": "string"
-                },
-                "validation": {
-                    "description": "Validation of answer pattern",
-                    "type": "string"
-                },
-                "timestamp": {
-                    "description": "Timestamp of answer",
-                    "type": "string"
-                },
-                "authors": {
-                    "description": "Authors of answer",
-                    "type": "array",
-                    "items": {
-                        "type": "object",
-                        "properties": {
-                            "name": {
-                                "description": "Name of author",
-                                "type": "string"
-                                },
-                                "email": {
-                                "description": "Email of author",
-                                "type": "string"
-                                },
-                                "role": {
-                                "description": "Role of",
-                                "type": "string"
-                                }
-                                }
-                            }
-                            }
-                        }
-                    }
-            }
-},
-{
-    "title": "Question schema for IAMA tasks",
-    "type": "object",
-    "properties": {
-      "question": {
-          "description": "The question asked",
-          "type": "string"
-      },
-      "id": {
-          "description": "A unique identifier for the question",
-          "type": "string"
-      },
-      "labels": {
-        "description": "Labels to specify the question",
-        "type": "array", 
-        "properties": {
-          "key": {
-            "type": "string"
-          },
-          "value": {
-            "type": "string"
-          }
-        }
-      },
-      "type":{
-        "description": "Question type",
-        "type": "string",
-        "enum": [                   
-          "open question",
-          "closed question"
-        ]                     
-      }, 
-      "suggested_roles":{
-        "description": "Roles suggested to answer question", 
-        "type": "array", 
-        "items": {
-          "type": "string", 
-          "enum": [               
-            "Aanbestedingsjurist", 
-            "Aanbieder", 
-            "Archiefdeskundige", 
-            "Behoeftesteller", 
-            "Communicatieadviseur", 
-            "Contractbeheerder", 
-            "Data engineer", 
-            "Data scientist", 
-            "Domeinspecialist", 
-            "Ethicus", 
-            "Gebruiker", 
-            "Gemandateerd verantwoordelijke(n)", 
-            "Informatiebeheerder", 
-            "Inkoopadviseur", 
-            "Jurist", 
-            "Privacy-officer", 
-            "Proceseigenaar", 
-            "Security officer"
-          ]
-        }
-      }, 
-      "lifecycle":{
-        "description": "Part of the algorithm lifecycle to which this question refers",
-        "type": "array",
-        "items": {
-          "type": "string",
-          "enum": [
-            "Probleemanalyse", 
-            "Ontwerp", 
-            "Dataverkenning en -preparatie",
-            "Ontwikkelen", 
-            "Validatie", 
-            "Implementatie", 
-            "Monitoren", 
-            "Archiveren"
-          ]
-        }
-      },
-      "links": {
-        "description": "Links to other relevant measures / tasks",
-        "type": "array",
-        "items": {
-          "type": "string"
-        }
-      },
-      "requirements": {
-        "description": "Specific requirements for this question", 
-        "type": "array", 
-        "items": {
-          "type": "string"
-        }
-      }
-  }
-}
-]
-        
\ No newline at end of file
diff --git a/script/format b/script/format
new file mode 100755
index 0000000..a0297e8
--- /dev/null
+++ b/script/format
@@ -0,0 +1,3 @@
+#!/usr/bin/env bash
+
+ruff format $@
diff --git a/script/lint b/script/lint
new file mode 100755
index 0000000..a993d18
--- /dev/null
+++ b/script/lint
@@ -0,0 +1,3 @@
+#!/usr/bin/env bash
+
+ruff check --fix $@
diff --git a/script/validate b/script/validate
new file mode 100755
index 0000000..50813c3
--- /dev/null
+++ b/script/validate
@@ -0,0 +1,23 @@
+#!/usr/bin/env python3
+
+import json
+import sys
+
+import jsonschema
+import yaml
+from jsonschema import validate
+
+# Load the YAML file
+with open(sys.argv[2], "r") as yaml_file:
+    data = yaml.safe_load(yaml_file)
+
+# Load the JSON schema
+with open(sys.argv[1], "r") as schema_file:
+    schema = json.load(schema_file)
+
+# Validate the data
+try:
+    validate(instance=data, schema=schema)
+    print("Validation successful.")
+except jsonschema.exceptions.ValidationError as err:
+    print("Validation error:", err.message)