Harshvardhan Pandit
Harshvardhan Pandit
The GDPR Article 33 and 34 requires keeping records associated with suspicion or occurrence of a data breach and its impacts, including any communications to the data subjects or authorities...
A proposal to add security incident reporting concepts within the RISK extension. See https://lists.w3.org/Archives/Public/public-dpvcg/2023Jul/0006.html The data breach concepts proposed in #64 will be remodeled to extend these and will be...
This issue is a placeholder for future work regarding Data Breach concepts in DPV
Create an extension for modelling concepts from EU NIS2
Terms from https://www.w3.org/TR/dx-prof/ Declare in metadata: DPV as a specification, declare extensions, declare serialisations - HTML, RDF (various), declare guides.
Currently, only the Consent legal basis has additional information (e.g. status, types) modelled within the taxonomy. Similar concepts should be added for other legal bases. (Update 2024-05-17) The legal bases...
As per https://www.w3.org/2022/12/14-dpvcg-minutes.html the justifications from risk extension will be moved to a new extension so that they are available for general use across all use-cases. The existing list also...
In #90 ISO/IEC 27560 records, information on how to withdraw consent must be provided. Currently in DPV we do not have the ability to express how consent can be withdrawn...
During discussions, we avoided defining the term 'cloud'. However, the term is important as increasingly standards, laws, guidelines, etc. have started to directly refer to 'cloud computing' and 'cloud technology'...
As per the paper "Sources of Risk of AI Systems" https://doi.org/10.3390/ijerph19063641 by Steimers and Schneider, [ISO/IEC 22989](https://www.iso.org/standard/74296.html) has 7 degrees or levels of automation. DPV should reflect these concepts for...