search

uropa-project / uropa

Universal record of processing activities (UROPA) standardized protocol.
21 stars 4 forks source link

Drop securityMeasureType Allowed values enum #7

Open milstan opened 2 years ago

milstan commented 2 years ago

In UROPA, for most of the properties you allow free text to be entered. However you do define 3 allowed values for securityMeasureType.

This is suboptimal. If someone wants to use UROPA together with DPV which defines terms for Security Measures they can't but they are obliged to chose one of your values (or map DPV values to them).

I suggest you simply drop the enum, and leave it to the implementing system to chose the vocabulary they want to use.

Jabuf commented 2 years ago

Hello @milstan, we're unlikely to drop enums as explained here. However I think for some will may be adding a other value and add a non-required string field for people to be able to precise it.

@KBKat does it make sense to have a other value for this case ?

KBKat commented 2 years ago

Hi again ! The structure of the SecurityMeasures was one of the issues we had with the DPV (which I explain here. The DPV classification of Security measures can however be used as description.

We will think about making the type required or not in our review of the required field. Thank you for the feedback.