-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Values for Evidence #20
Comments
Proposed resolutionFollowing the proposed resolution from #21 , we would differentiate between the information required for the end-users from the data required for providing the service in compliance with the OOP. This discussion will need to continue concerning the extended model of the SDG and the OOP model: how to match values between on the one hand criteria, their information requirements and constraints (so the specific value(s) expected to answer to a certain criterion through its information requirement(s) and according to its constraints) and on the other hand, evidence (so the specific value(s) provided together with the right level of trust as response to the criterion). For this part, we need further alignment with the CCCEV, TOOP and any other relevant model. RationaleThe requirements from the SDGR are precise concerning certain information to be provided:
Therefore, we would propose to require public administrations to provide the types of evidence and their formats for each public service. However, we would leave optional to link this information with a description of the criterion to be met with those pieces of evidence. In our understanding, having the Criterion class is important since it formalises why specific pieces of evidence are required. Alternatively, this could be discussed as part of the SDG extended model. |
Criterion/evidence can be quite broad. For instance, in the example of applying for licensing/protected title, we see only one situation (a master's degree in medicine/a certificate is required). However, such a service is meant for a much broader spectrum of occupations, not just medicine. If we apply this model in the way shown in the example, it would be required to exhaustively list all possible degrees and certificates. I wonder if this is feasible. Wouldn't it be better to stick here to a plain-text description of 'the requirements' for the service as opposed to having CA's list every specific requirement individually?
The list used in the SDG TOOP project seems to have a more practical level
The text was updated successfully, but these errors were encountered: