Integrity of `skos:preflabel` and `skos:prefdefinition`

We are currently implementing the interop spec into use.id, but are concerned about relying on skos:preflabel and skos:prefdefinition of the Access Need Groups to render the UI of the authz agent.

This is because a malicious party might create a mismatch between those two fields and the actual access requests.

For example, I could present the following access needs group:

• skos:preflabel: "Read access to your shopping history"
• In reality, my app asks permission to read the user's medical data

Has the panel considered this situation?

We are thinking to solve this issue by putting a human readable name at the shape tree itself...