dpvcg / dpv Goto Github PK

It seems to me that the class PersonalDataCategory is wrongly named and should be renamed, probably to PersonalData. The rationale is that, from this name, one may infer that instances of the class are "categories", while my understanding is that the categories are actually the subclasses of this class (like "Financial" or "Historical").

What confirms this hint is the fact that one of the subclass is "SpecialCategoryPersonalData" (rather than "PersonalDataSpecialCategory").

Also, I believe that the immediate subclasses of PersonalDataCategory should be named more explicitly FinancialData, HistoricalData and so on... In general, naming a class with an adjective is odd...

Intense bikeshedding, I know...

See two purpose descriptions below:

1. Security: Security Security of data
2. SellDataToThirdParties: To sell data or information to third parties

The descriptions have different forms, where the first one is descriptive (security) and the second is an action (to sell). What should be the consistent form for such descriptions.

See issue and discussion on mailing list: https://lists.w3.org/Archives/Public/public-dpvcg/2020Nov/0002.html

https://dpvcg.github.io/dpv/#namespaces mentions the ODRL namespace. However, the actual implementation doesn't make any reference to ODRL.

Is an alignment with ODRL planned? I see some things that ODRL and DPV have in common. E.g., DPV defines "Processing" as "The processing performed on personal data", and ODRL says "An Action class indicates an operation that can be exercised on an Asset." And "anonymization" only makes sense on personal data, doesn't it?

Background: I am the maintainer of the International Data Spaces (IDS) Information Model and have some plans to align the IDS Information Model, which already is an extension of ODRL, with DPV.

There are two instances of location as dpv:location which is a property in Technical and Organisation Measures, and dpv:Location which is a Personal Data Category. Suggest changing the location property since Location as a personal data category is more likely to frequently useful.

Happy Holidays!

Just noticed that in w3, some relationships are defined that are not in the ttl of this repo:

E.g.
In w3:
https://www.w3.org/ns/dpv#dpv:LegalEntity is Parent Class of dpv:DataSubject

In ttl (

rdfs:Property is not defined in the rdfs namespace (https://www.w3.org/2000/01/rdf-schema#).

Instead it should be rdf:Property.

Let me know if you'd like me to submit a PR to fix this.

Suggest changing the one in Personal Data Categories as certifications are more likely to be frequently used as an organisational measure.

Hi, I am working on a paper that is related to privacy, and where one of the recommendations is to use a unified terminology, to reduce confusion among users. Do you have a preferred way in which you want this research to be cited? It would be great if you included this info in the readme.

I'm not sure if this is intended, but a lot of the hyperlinks inside the document lead to invalid links.

e.g. https://dpvcg.github.io/extract-sheets/index.html#purpose-classes
All the links under those sections are invalid.