Closed coret closed 1 year ago
Duplicate of #53, itself a duplicate of #37?
Indeed, long standing issue resulting in duplicates.
Current status: the CISO of the maintainer of the Dataset Register has been asked to see if we don't run into GDPR issues when processing schema:Person
.
Legal has reviewed the fact that dataset descriptions could include personal information and has determined (the requirements under which) the Dataset Register can process this data. We can therefor add schema:Person as a valid class for schema:creator and schema:publisher (and also introduce schema:contactPoint - issue 55).
After the req's have been ammended, the Dataset Register component should reflect the changes (read: be able to validate and convert) as does the demonstrator.
Now only possibility to specify an organization. Person must have URI (like ORCID)? Look at GDRP implications (when the Dataset register copies and stores person information, do we need to have privacy policy?) Request from ATM.