Also alignment with Algoritmekader team about using f.e. URNs to link "maatregelen" to instruments in the instrument register. Notice that each 'maatregel' is a combination of tasks in the instrument (multiple sources(/instruments)).
Thought: the AI Act object we currently have in the Instrument Register is not an Instrument. Maybe we should rename the register to something like "Task Register".
Discuss with Corine from AK
Implementation Notes:
Propose to rename the Instrument register tov "Task Registry". Within the "Task Registry" we can have the Algoritmekader with the maatregelen and the instruments with the tasks.
Also we can have a concept like an individual task such that we can include the decision tree.
Technical Notes:
Readme with the definitions of Tasks, Maatregel, Instrument, Requirements
Rename mentions of Instrument Registry to task register (Code, Repo, Click-Up and other docs rename Instrument Registry also)
Digilab deployment rename
Keep endpoints like /instruments
Task Registry also include in projects of ai-validation
Also in other repo's like AMT we need to refactor (We don't need to keep them both alive, can be stuck for a while)
Introduction
Also alignment with Algoritmekader team about using f.e. URNs to link "maatregelen" to instruments in the instrument register. Notice that each 'maatregel' is a combination of tasks in the instrument (multiple sources(/instruments)).
Thought: the AI Act object we currently have in the Instrument Register is not an Instrument. Maybe we should rename the register to something like "Task Register".
Discuss with Corine from AK
Implementation Notes:
Technical Notes: