VCR: EmployeeCredential not in Nuts JSON-LD context

[reinkrul]

The newly introduced EmployeeCredential is not in the Nuts JSON-LD context. Meaning, they can't be issued through the API (we have client-side validation there) and if someone still manages to issue it in JSON-LD format (we use JWT), the fields (name, role, identifier) won't be protected by the signature.

[woutslakhorst]

is this still correct? We can now pass holder credentials with the request-service-access-token flow. The existing context also contains a NutsEmployeeCredential.

This concerns the OpenID4VP user flow where the Nuts node is acting as user wallet. Since we're not going to be a user wallet, removing the rc label.

[reinkrul]

This also applies when performing the service-to-service flow, in which the caller wants to provide employee details. Although the v5 NutsEmpoyeeCredential could be used for that?

[woutslakhorst]

The NutsEmpoyeeCredential can cover any need for user claims (using schema.org namespace). Do we still need this other one?