Hello,
I do agree somewhat at least, I do think it is reasonable that there
would not have to be person objects since if the internet resource owner
is a natural person, they will still have an organisation object.
This really made me consider it, and I can't really see a valid reason
to require person objects to create a maintainer for example.
Kind regards,
Cynthia Revström
On 2018-09-21 15:52, Agoston Horvath via db-wg wrote:
Good point -- actually there is no need to have any person objects in
the database, except for:
- the owner of internet resource is in fact a natural person;
- voluntarily offering personal data, e.g. if admins willingly want to
share their details by referencing person objects from a role object.
Agoston
On Thu, Sep 20, 2018 at 3:52 PM denis walker via db-wg <[email protected]> wrote:
Hi Alexander
GDPR is the necessary 'force'. If there is personal data in the database that
cannot be justified according to the defined purpose of the database and
governing policies then it should be removed.
cheers
denis
co-chair DB-WG
________________________________
From: Alexander Stranzky via db-wg <[email protected]>
To: [email protected]; "[email protected]" <[email protected]>
Sent: Thursday, 20 September 2018, 15:45
Subject: [db-wg] PERSON objects in the RIPE Database
Am 20.09.18 um 15:40 schrieb denis walker:
Hi Alexander
You may well be right but duplicated personal data in a public database
for 'convenience' is probably not acceptable.
Hi Dennis,
I totally agree with you. But unfortunately it's difficult to force ISPs
to clean up their data.
Regards,
Alexander Stranzky
--
velia.net Internetdienste GmbH * Hessen-Homburg-Platz 1 * 63452 Hanau
Geschäftsführer: Franz G. Köhler, Arek Akilli * AG Hanau * HRB 7588
Tel: +49 6181 1898119 * http://www.velia.net
