Same with me.
<Mark> me too
<Mark> but is working now
<Mark> I think
start the meeting
<Mark> I have to drop from the call at 3:30
<scribe> scribe: harsh
Georg is presenting demo of Signatu's use of DPV on call / shared screen
Signatu has a "Data Processing Specification" that records processing info such as data source, processing actions - and this record is helpful towards privacy policies or consent screen information.
DPV is used to populate the fields, such as processing actions
Purpose description is free text
DPV purposes have been added, and some other additional ones have also been added. The ones from DPV (?) are prefixed with W3C, with others from IAB and Signatu indicated using prefixes
There is a separate field called "benefit to the end user" which can be used to indicate benefits, usefulness
Data Security Measures implements Technical and Organisational measures from DPV
Indicating sensitive data changes legal basis specific to sensitive data (Art 9) from DPV
Processing duration uses ISO 8601 notations
Recipients are populated using "tracker detect" which detects third parties
Recipients are specified with role (join controller / processor)
And whether a DPA has been agreed on
DPV does not currently specify 'transfer legal bases' (of which there are 18-19)
Q: what format is this information saved in?
Georg: I don't know all the formats, but we do use JSON (-LD perhaps?) using the W3C format
Mark: where did the categories for transfer (?) come from
Georg: From the GDPR
... Type of data is free text because it is difficult for users
to understand structured data
... there can be groups of data such as health
<Zakim> Bert, you wanted to ask who fills this form
Georg: we also provide a consent receipt that can be cryptographically verified
harsh: does the consent receipt also use DPV?
Georg: I think we do
... we use the same information to generate privacy policies
using a comprehensive questionnaire, with outputs in multiple
languages
... comments to DPV - some of the purpose categories are more
regarding benefits rather than purposes
... we can also suggest additional purpose categories and
transfer legal bases
G
Georg: we have gdprlexicon gdprlexicon.com/ which supports different language which can be used as a starting point for providing concepts in different languages
end meeting
This is scribe.perl Revision: 1.154 of Date: 2018/09/25 16:35:56 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) Default Present: Georg, MarkLizar, RichV Present: Georg MarkLizar RichV Found Scribe: harsh Inferring ScribeNick: harsh WARNING: No "Topic:" lines found. WARNING: No meeting title found! You should specify the meeting title like this: <dbooth> Meeting: Weekly Baking Club Meeting WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth WARNING: No date found! Assuming today. (Hint: Specify the W3C IRC log URL, and the date will be determined from that.) Or specify the date like this: <dbooth> Date: 12 Sep 2002 People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option. WARNING: No "Topic: ..." lines found! Resulting HTML may have an empty (invalid) <ol>...</ol>. Explanation: "Topic: ..." lines are used to indicate the start of new discussion topics or agenda items, such as: <dbooth> Topic: Review of Amy's report WARNING: IRC log location not specified! (You can ignore this warning if you do not want the generated minutes to contain a link to the original IRC log.)[End of scribe.perl diagnostic output]