Updates: 27560 Comment & ANCR Controller Draft is Posted

Dear WG, The 2 Updates, 1. posted an initial spec outline for the Controller_notice_ Id record draft <https://kantara.atlassian.net/wiki/x/OADaNQ?atlOrigin=eyJpIjoiYTU3NDA5ZTRjYmQ1NDc4YTliYjkzZTAzNmYxZTM2OTYiLCJwIjoiYyJ9> taken from the appendix of ANCR Transparency Reporting specification. It should also contain a link to the google doc in active development. ( Feel free to jump in and comment/ contribute/discuss and edit. if you have ideas for what should be included, or would like to get involved in drafting, please let me know 2. I have also tried to submit late comments - referencing the controller notice id record to 27560, but due to technical account issue (@ standards council of Canada) it was not submitted on time. Even so comments were eventually submitted, so the editors hopefully will get a chance to review them. And, yes, it does recommend the use of the ANCR PII controller_idenitty_ record, (with a Link) to be used in the record information structure, as well as minimumal changes to update to to a notice record and receipt record and information structure, (so as to be suitable for (all use case) including the original Surveillance/Terms and Condition / Cookie use cases). So fingers crossed, the ANCR / Kantara Work might actually work out in the end by not only interoperate in the next edition,with 27560, 29184, 29100, and DPV, but also be useable for ‘operational personal data security/surveillance access and control.’ Which would make the effort definitely worthy while in the end Best, Mark PS. Key Comment Summary #1 comment (imo) is recommending to swap the PII_principal identifier from the record header with with the pii_controller_record_id, (as specified in the ANCR WG) #2 Second most important, is a recommendation of a generic use case for getting permission to identify the pii_principal in the consent record header. (which demo’s how privacy is used for identify management) In the context of providing and withdrawal of consent using a consent receipt for a secondary purpose of use (for any lawful basis) PSS - In essence completing the work to propose a standard that can make a real consent record and receipt 10 years after the v1 was drafted. - comments received or not - is a big milestone in my book.
participants (1)
-
Mark Lizar