Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

vocabulary fields to enable privacy-respecting use of datasets #1524

Open
npdoty opened this issue Jul 21, 2022 · 3 comments
Open

vocabulary fields to enable privacy-respecting use of datasets #1524

npdoty opened this issue Jul 21, 2022 · 3 comments
Labels
dcat future-work issue deferred to the next standardization round privacy-needs-resolution Issue the Privacy Group has raised and looks for a response on.

Comments

@npdoty
Copy link

npdoty commented Jul 21, 2022

Communicating privacy-related restrictions regarding a dataset: beyond copyright, could there be terminology about the privacy-relevant restrictions on a dataset? E.g. this dataset has particular policies regarding who can access it, how the data can be used, that individual records can't be re-published, etc.

Indicating whether a dataset contains information about people, or particularly sensitive types of information about people. Could those indicators be used to delete data in dangerous situations? Consider the historical, but still very relevant, example of the destruction of civil registry records in Amsterdam in 1943. Could those indicators help facilitate audits of datasets or use of datasets?

@davebrowning
Copy link
Contributor

(Apologies for the delayed response).

Thanks for raising this issue. This has sparked a bit of a discussion between the editors and then within the WG as a whole. The outcome of that is that we think its a potentially interesting area but we haven't got any use case that needs to communicate the existence of privacy-relevant data within a dataset , nor does any of the active WG membership have any implementation experience with such requirements. On the other hand, we can imagine how it might be useful to know that a dataset had some such information though what a user of such a catalog record would do on the basis of this is more difficult to speculate about. That might be quite domain specific and sit well within a profile, but that's very much getting ahead of our experience/requirements at this time.

What the WG has agreed is that we mark this for future work and defer discussion on privacy to see what the Data Privacy Vocabularies and Controls Community Group develops, and other efforts by other W3C groups. (The WG resolution is documented in the minutes at https://www.w3.org/2022/10/25-dxwg-minutes#r02 )

I hope this is satisfactory.

@davebrowning davebrowning added the future-work issue deferred to the next standardization round label Nov 14, 2022
@pchampin
Copy link
Contributor

@npdoty are you satisfied with @davebrowning's answer and can we close this issue?

@npdoty
Copy link
Author

npdoty commented Nov 20, 2023

Planning for future work is acceptable. Is there any confirmation from the cited CG that they will work on this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dcat future-work issue deferred to the next standardization round privacy-needs-resolution Issue the Privacy Group has raised and looks for a response on.
Projects
None yet
Development

No branches or pull requests

3 participants