14:08:28 RRSAgent has joined #dpvcg 14:08:28 logging to https://www.w3.org/2019/05/07-dpvcg-irc 14:08:37 pp has joined #dpvcg 14:08:43 chair: axelPolleres 14:08:51 scribe: elmar 14:09:04 agenda :https://lists.w3.org/Archives/Public/public-dpvcg/2019May/0002.html 14:09:19 Me neither 14:09:23 Maybe than easier if Bert chairs... 14:09:38 pp has left #dpvcg 14:09:45 Axel, could you try headphones? 14:10:00 ...apologies, have no headphones close by at the moment. 14:10:16 Agenda item 2: Approval of F2F minutes 14:10:23 PROPOSED: approve F2F minutes as per agenda links 14:10:25 +1 14:10:26 +1 14:10:29 Fajar has joined #dpvcg 14:10:33 +1 14:10:36 +1 14:10:46 +1 14:10:49 RESOLVED: approve F2F minutes as per agenda links 14:11:12 harch sent a long list of things we can close... 14:11:25 s/things/action items/ 14:11:30 mail: https://lists.w3.org/Archives/Public/public-dpvcg/2019May/0001.html 14:12:03 Mark has joined #dpvcg 14:12:04 Will close the action items from Harsh's Email offline 14:12:15 ACTION: bert to close actions to be closed as per https://lists.w3.org/Archives/Public/public-dpvcg/2019May/0001.html 14:12:15 'bert' is an ambiguous username. Please try a different identifier, such as family name or username (e.g., bbos, bertv). 14:12:31 https://docs.google.com/spreadsheets/d/13d1eRXZZBCw84vYGoCJeMU08rzkkzadDzxY3n2iOi8k/edit#gid=1356512815 14:12:35 ACTION: bbos to close actions to be closed as per https://lists.w3.org/Archives/Public/public-dpvcg/2019May/0001.html 14:12:36 Created ACTION-103 - Close actions to be closed as per https://lists.w3.org/archives/public/public-dpvcg/2019may/0001.html [on Bert Bos - due 2019-05-14]. 14:12:36 Vocabulary spreadsheet 14:12:53 it should all be on the spreadsheet. 14:15:10 I essentially added all contributors as authors to the draft. 14:15:14 https://github.com/dpvcg/extract-sheets/ 14:15:19 Harsh tried to run the script to generate the documentation from the spreadsheet 14:15:26 https://dpvcg.github.io/extract-sheets/index.html 14:15:33 there is a script now to generate a spec doc from the gdoc and the gsheet. 14:16:04 present+ rigo 14:16:19 present+ 14:16:43 FWIW, I also had worked further on the overall document... 14:17:07 https://docs.google.com/document/d/1Z3Eb5rZjrdWcE5u5o0CYzA_LPyGaTqmg84ecGve_ZLA/edit# 14:17:35 Processing: 14:18:01 Processing tab - not sure about description for (32) Exchange and (42) Restrict 14:19:17 Exchange is not in the GDPR, Restrict is 14:22:21 Rigo: Exchange is confusing - would need to list all kinds of disclosures and have a new class for all constraints - would be overkill 14:23:20 Rigo: we need transfer, but we don't need exchange. 14:23:31 Exchange = 2xtransfer 14:23:47 Rigo: propose to remove exchange from Processing 14:23:48 +1 14:23:57 question: do we need otherwise conditional disclosure? 14:24:10 aren't these very close to ODRL actions? 14:25:49 Axel: Could we not refer to ODRL ACTIONS for processing conditions? 14:30:10 I consider this an ISSUE (which we do not have to resolve now. 14:31:06 i.e.: ISSUE: do we need a generic mechanism to describe conditions and restrcitions to a specific processing. 14:34:50 PROPOSED issue: ISSUE: do we need a generic mechanism to describe conditions and restrcitions to a specific processing or can we re-use ODRL' 14:35:00 s mechanism here? 14:37:44 Rigo: Constraint is a very general concept; we need to find out what the best place is to put constraints in the taxonomy. 14:39:20 PROPOSED: make the modeling of constraints an ISSUE? 14:39:22 PROPOSED issue: ISSUE: do we need a generic mechanism to describe conditions, constraints and restrcitions to a specific processing or data category can we re-use ODRL's mechanism? 14:39:35 +1 14:39:37 +1 14:39:44 +1 14:39:48 +1 14:40:17 RESOLVED: raise ISSUEdo we need a generic mechanism to describe conditions, constraints and restrcitions to a specific processing or data category or can we re-use ODRL's mechanism? 14:40:44 ISSUE: do we need a generic mechanism to describe conditions, constraints and restrcitions to a specific processing or data category or can we re-use ODRL's mechanism? 14:40:45 Created ISSUE-19 - Do we need a generic mechanism to describe conditions, constraints and restrcitions to a specific processing or data category or can we re-use odrl's mechanism?. Please complete additional details at . 14:41:39 Axel: How do we link the issues to the draft document? 14:41:56 Just as links to issues? 14:43:16 ACTION: Harsh to discuss with Axel to make sure ISSUEs are reflected in FPWD 14:43:16 Created ACTION-104 - Discuss with axel to make sure issues are reflected in fpwd [on Harshvardhan Pandit - due 2019-05-14]. 14:44:17 harsh: processing action "exchange" was removed (unclear what it meains 14:45:27 harsh: we should make sure that classes from the base ontology aren't dublicated in the subsheets. 14:46:37 Top-level concepts (dpv:processing etc.) should be put in the base ontology. 14:47:11 ACTION: harsh to remove duplicate top-level classes from subsheets. 14:47:11 Created ACTION-105 - Remove duplicate top-level classes from subsheets. [on Harshvardhan Pandit - due 2019-05-14]. 14:49:45 topic: timeline 14:50:09 Harsh regarding timeline: by the next call, there can be a complete draft version of the document to review. 14:50:14 harsh: By next call: spec should be finished. we will also try to make progresss on the document 14:50:45 +1 sounds good 14:50:47 harsh: aims to send around document by this weekend. 14:51:03 collaboration/help/assists welcome in the Google Doc 14:51:13 should we action some people for internal review? 14:51:25 or next time? 14:51:44 harsh: Should agree on how exactly to publish it. 14:51:54 ACTION-99 14:51:54 ACTION-99 -- Bert Bos to Look into where to publish our cg spec, and how to redirect from the namespace doc to the spec. -- due 2019-04-12 -- OPEN 14:51:54 https://www.w3.org/community/dpvcg/track/actions/99 14:51:57 we need a vanilla HTML version of the doc ... 14:52:13 by vanilla - you mean without Google Doc css/styles? 14:52:31 yes, it should use W3C spec stylesheets 14:52:37 or no? 14:52:44 Yes, that would be better 14:53:01 I'll try to strip out the CSS in the script itself, and then include w3c CSS 14:53:57 the trouble is at the moment we use gdoces instead of plain HTML, but we can maybe move to plain HTML with the FPWD and then stick with the plain HTML for editiing, leaving the google spreadsheets. 14:55:32 we can generate vanilla HTML from gdocs as well by using a css-remover on the gdocs html 14:55:51 the ad industry has 27000 classes for profiling, where is the limit? 14:57:26 @rigo is there any way to access these 27k classes? Would be great to build into a vocabulary. 14:57:56 We can always refer to external vocabularies, if available, but we will not invent them 14:58:18 Yes, I meant creating an external vocabulary instead of merging into dpvcg 14:58:33 We can discuss to name them as an extension, is there a link to these? 15:00:12 isn't that already possible? i.e. someone can mark data both as locationdata and as sensitivedata or just one of those? 15:00:23 I need to run, sorry. 15:00:25 If we include levels of sensitivity in the taxonomy, then that's some real knowledge we can transfer. 15:00:53 (We should adjourn to the next call in two weeks, FWIW or raise an ISSUE) 15:04:36 ISSUE: how to express sensity of data? 15:04:36 Created ISSUE-20 - How to express sensity of data?. Please complete additional details at . 15:05:47 Propose: Derived data as a class instead of a property 15:06:02 ACTION: Elmar to change isderived to a class 15:06:02 Created ACTION-106 - Change isderived to a class [on Elmar Kiesling - due 2019-05-14]. 15:06:42 next meeting 23rd May 15:07:51 Privmas Eve 15:07:58 May 23rd - 19:39:24 RRSAgent has joined #dpvcg 19:39:24 logging to https://www.w3.org/2019/05/07-dpvcg-irc 19:39:37 RRSAgent, make logs public 19:39:44 RRSAgent, make minutes v2 19:39:44 I have made the request to generate https://www.w3.org/2019/05/07-dpvcg-minutes.html Bert