Challenge Schema structure

[cre8]

When migrating the Exel to json each column was treated as one value. But when you want to filter the input, it get's tricky:
If you want to define the attribute "crypto agility", the answer could be true or false. In this case a filter is easy to implement and also the input validation.
But for some attributes you want to add some information to clarify the answer. Like: "it has crypto agility, but you can only use EC based curves". For such cases these attributes need a second field. We could implement it as a nested object or as Boolean. Json schema allows us to treat it as Boolean and a specific field and to validate it during the cicd pipeline.

Suggestions:

• define a general object for filter based fields (e.g. { value: boolean, description: string }
• challenge all existing data and update them

Another point is how to deal with resources. Right now we can insert links directly in the value and it will get rendered as a html link. But could it be better to add links in a separate field for more use cases?