– DRAFT –
Data Privacy Vocabularies and Controls Community Group Teleconference

<axelpolleres> I'd appreaciate if ber could chair, I am still stuck in meetings and afraid, it won't end as soon as I hoped... sorry about that.

<axelpolleres> @Bert, ok for you to jump in chairing?

Roll call, select scribe, agenda

<Bert> last meeting

approve last time minutes:

Resolved: minutes accepted

Action items

<Bert> action items

Fajar: Action 128 is still ongoing - most of the tasks assigned to Harsh

<Bert> action-130?

<trackbot> action-130: Bud P. Bruegger to Discuss with eva to start a use case document? -- due 2019-09-10 -- OPEN

Bud: Action 130 and 132 is ongoing and he sent the summary of the current progress to the mailing list

<axelpolleres> the only thing i have to report is that IDS got back to us on liaisons, more on theat in two weeks.

<axelpolleres> Sorry again for dropping off short notice today, regrets and thanks to Bert for jumping in!

Bud: Eva and Harsh have discussed the use case, and hopefully will have the use case definition by the end of the week (action-130).

Bud: the use case is about online shopping, additional use case would be interesting to have.

Fajar: will write to christoph fabianek (OwnYOurData) regarding the potential additional use case for the DPVCG

<Bert> issues

Issues

Bud: issue-3 is already linked to action-132, but will not addressing the issue altogether, might be as an input to solve the issue.

<Bert> issue-14?

<trackbot> issue-14: We may want to add a non-normative comment in the spec that/how the taxonomy can be used as skos. -- open

<Bert> issue-15?

<trackbot> issue-15: Personal data cateories collected might be collected in an approximate manner (e.g. age vs. age range), should we provide a mechanism in the vocabulary to distinguish this? -- open

Bud: issue-15 is related to the precision of the data collected from data subject, e.g., on the location accuracy (cm vs metre)

Bud: it will need a lot of efforts to be able to address this issue, since there are many complications to it

Bert: probably we can suggest standard solutions to this problem, but currently we don't know yet what are the standards

<Bert> issue-16?

<trackbot> issue-16: Do we need to further structure consent notice? -- open

bud: on issue-16, bud will try to find his notes on this, and will send it around if he found it.

<Bert> issue-18?

<trackbot> issue-18: Do we need further temporal annotations for the personal data handling class? -- open

Fajar: what does it really mean? probably we need to clarify it with Axel

Bert: the information about consent is actually equipped with the temporal information, not sure what would be the scope of the issue mentioned by Axel here

<Bert> issue-19?

<trackbot> 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? -- raised

all: postpone the decision on the raised issue until the next call

look over Fajar's document... do we still need it?

Action: Fajar: convert feedback from the spreadsheet into raised issues

<trackbot> Created ACTION-134 - Convert feedback from the spreadsheet into raised issues [on Fajar Ekaputra - due 2019-11-05].

thanks!

<Bert> s/what does it really means/