ISSUE-1 |
CLOSED |
Timeline/schedule, when should we stop collecting additional use cases? |
2018-08-21 |
|
0 |
| ISSUE-2 |
RAISED |
Do we need to formulate a notion of compliance in scope of the cg? |
2018-09-18 |
|
0 |
| ISSUE-3 |
PENDING REVIEW |
Do we want to revisit a definition of "gdpr rights" in our definitions and taxonomies? |
2018-09-18 |
|
0 |
| ISSUE-4 |
CLOSED |
What are the elements of consent? starting from "onsent = agreement through an [affirmative action] at a specific [time] with a [data controller] to specific [processing] and [storage] of specific [data categories] for specific [purpose] and [duration]" |
2018-10-16 |
|
0 |
| ISSUE-5 |
RAISED |
Shall we extend the scope of the group to machinge-readable requests to execute rights accroding to eva’s classification of rights |
2018-12-04 |
|
0 |
| ISSUE-6 |
RAISED |
Should our taxonomy include a distinction/modeling of data subjects to whom gdpr applies (eu citizens and/or locatedin eu) |
2018-12-04 |
|
0 |
| ISSUE-7 |
CLOSED |
Are the legal grounds except consent and legitimate interest actualy purposes? |
2018-12-10 |
|
0 |
| ISSUE-8 |
CLOSED |
How do we describe unions and intersections of purposes, how doe we describe any vs some “sub”purpose |
2018-12-10 |
|
0 |
| ISSUE-9 |
RAISED |
Where are categories of data controllers used, where are they useful? (cf. recital 98, 99, 100) |
2019-01-22 |
|
0 |
| ISSUE-10 |
RAISED |
Are there mappings to gics from other coding systems naics/nace/isic ... |
2019-02-12 |
|
0 |
| ISSUE-11 |
CLOSED |
Taxonomies on storrage locations and restrictions as well as security measues and restrictions still undefined. |
2019-02-12 |
|
0 |
| ISSUE-12 |
CLOSED |
Shall we get back to action-6, action-19, action-27 (closed without news) |
2019-02-26 |
|
0 |
| ISSUE-13 |
CLOSED |
Decide later whether we need sub-namespaces for different subtaxonomies |
2019-04-04 |
|
0 |
| ISSUE-14 |
OPEN |
We may want to add a non-normative comment in the spec that/how the taxonomy can be used as skos. |
2019-04-04 |
|
0 |
| ISSUE-15 |
OPEN |
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? |
2019-04-04 |
|
0 |
| ISSUE-16 |
OPEN |
Do we need to further structure consent notice? |
2019-04-05 |
|
0 |
| ISSUE-17 |
CLOSED |
Do we need further temporal annotations for the personal data handling class? |
2019-04-05 |
|
0 |
| ISSUE-18 |
OPEN |
Do we need further temporal annotations for the personal data handling class? |
2019-04-05 |
|
0 |
| ISSUE-19 |
RAISED |
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? |
2019-05-07 |
|
0 |
| ISSUE-20 |
OPEN |
How to express sensitivity of data? |
2019-05-07 |
|
0 |
| ISSUE-21 |
CLOSED |
Ask for specific feedback on (un)ambiguity of the term descriptions |
2019-05-23 |
|
0 |
| ISSUE-22 |
CLOSED |
We ask for particular feedback on whether and how to extend the list/taxonomy of controllers and recipients in the current vocabulary. |
2019-06-04 |
|
0 |
| ISSUE-23 |
CLOSED |
Should we add more subclasses to communicationrecording (e.g. distinguishing chats, personalmessaging, videocommunication, telephony, etc.) and which ones? |
2019-06-04 |
|
0 |
| ISSUE-24 |
CLOSED |
Should we add more specific subclasses like countryofcitizenship, countryofresidence, countryofcurrentlocation to country and which ones? |
2019-06-04 |
|
0 |
| ISSUE-25 |
CLOSED |
Should we explicitly note that the the controller is always a recipient of the data, if not, do we need to make this explicit inth vocabulary, by declaring it? |
2019-06-04 |
|
0 |
| ISSUE-26 |
OPEN |
Describe use-cases and examples showing how the vocabulary should be or can be used |
2019-06-18 |
|
0 |
| ISSUE-27 |
OPEN |
Discuss accompanying primer document |
2019-06-18 |
|
0 |
| ISSUE-28 |
OPEN |
Include a way to indicate PII (Personally Identifiable Information) |
2019-11-26 |
|
0 |
| ISSUE-29 |
CLOSED |
Issue in RDF/Ontology: Organise is a subClass of itself |
2019-11-26 |
|
0 |
| ISSUE-30 |
CLOSED |
Issue in RDF/Ontology: conflicting definitions of terms |
2019-11-26 |
|
0 |
| ISSUE-31 |
CLOSED |
Add rdfs:labels to terms in RDF/Ontology |
2019-11-26 |
|
0 |
| ISSUE-32 |
CLOSED |
How to resolve conflicting definitions when adopting the DPV vocabulary? |
2019-11-26 |
|
0 |
| ISSUE-33 |
RAISED |
The categorisation of Pseudoanonymisation and Encryption is not (semantically) correct |
2019-11-26 |
|
0 |
| ISSUE-34 |
CLOSED |
Is the ontology actually modular? Can its individual 'components' be reused? |
2019-11-26 |
|
0 |
| ISSUE-35 |
CLOSED |
Add parent class information to documentation |
2019-11-26 |
|
0 |
| ISSUE-36 |
CLOSED |
Generic document explaining the vocabulary for non-technical audiences |
2019-11-26 |
|
0 |
| ISSUE-37 |
CLOSED |
Credit is repeated twice in DPV |
2020-05-27 |
|
0 |
| ISSUE-38 |
CLOSED |
Article 13/14 requirements using dpv |
2020-06-10 |
|
0 |
| ISSUE-39 |
RAISED |
How to represent collection method of personal data? |
2020-07-08 |
|
0 |
| ISSUE-40 |
CLOSED |
How to specify associated properties such as card's expiry date or cvv such that "card details" will cover all of these? |
2020-11-11 |
|
0 |
ISSUE-41
harsh |
RAISED |
Remove language as sub-class of ethnicity |
2021-02-03 |
|
0 |