Change Management / Data Versioning

[apowers313]

Hi, I'm new to the DPV spec and not especially familiar with the scope so apologies if this question is off-base.

One of the use cases I'd like to use DPV for is tracking change management for systems -- if a new regulation comes out, how does that change the actors, controls, etc. that are in scope for compliance. Right now the ontology seems like a snapshot in time and it doesn't have any versioning of concept or relationship data to capture changes over time. (Not to be confused with the overall ontology / schema version, which does seem to have a version).

Would change management and data version control be in scope? Is it worth a WG conversation?

[coolharsh55]

Hi @apowers313 thanks for your query. I'm not sure I understand it clearly, sorry. Can you elaborate more, an example would be ideal. Also, is versioning the same as that proposed in #359 to state which concepts were added/deprecated in which version of the DPV?

[bact]

To my understanding, it is about the temporal aspect of legal applicability, due to ongoing changes in the legal landscape.

For example, for the same piece of data, before- and after GDPR enforcement, or before- and after an Executive Order revocation, the scope of compliance for that data will change.

Is that correct? @apowers313