[dp-tf] Quadlogy of person proposals

Manfredo Miserocchi wrote:
> Denis,
>
>
>   
>>>> think, we have to build.
>>>>         
>> I am not quite sure what you mean here. I 'think' you are saying you
>> want some means of recording that you have permission to publish data
>> in
>> the RIPE Database that you do not own and indicating who has the
>> responsibility for this data. Is that correct?
>>     
>
> No, the answer is to interface us only with members. They have a contract
> with us ans they must get the responsability to give us permission to
> publish personal data.
>   

That is not going to work with the current database and business models.
Also maintaining all data will not restrict data to members only. At the
moment anyone can put data into the database. A student with nothing to
do one afternoon can create person/mntner objects and enter all their
friends details without permission. We have no contract with such a
student. In that case a clause in the database T&C requiring consent
would cover it.

We also have lots of PI space holders who have no contract with the RIPE
NCC and therefore can only be held to account by database T&C. There are
also people in other regions who create aut-num and route objects with
person/mntner objects in our database. We can't easily cover all of
these people with a contract.

A change to the standard contract may cover a large proportion of the
database users. But the only way to cover them all is with the database T&C.

cheers
denis

>   
>>> Very good point. I think the best approach is to have the
>>>       
>> responsibilty
>>     
>>> reside with the maintainer. It would be good to have this in the
>>>       
>> service
>>     
>>> contract (i.e. the service contract should say that by putting a
>>>       
>> person
>>     
>>> object in the RIPE database, you acknowledge that you did get the
>>> approval
>>> of the person to publish his/her data). This is what we have in the
>>>       
>> .hu
>>     
>>> registration rules.
>>>       
>> Don't forget that not everyone who enters data into the RIPE Database
>> is
>> a member. So this statement may be better in the Database Terms and
>> Conditions.
>>     
>
>
> Yes, but if we'll have all object maintained it seems that only members
> will do.
>
> cheers
> Manfredo
>
>
>
>
>
> Si precisa che le informazioni contenute in questo messaggio sono riservate e ad uso esclusivo del destinatario. Qualora il presente messaggio Le fosse pervenuto per errore, La invitiamo ad eliminarlo senza copiarlo ed a non inoltrarlo a terzi, dandocene gentilmente comunicazione. Grazie.
>
> You are hereby informed that this message contains confidential informations intended for the addressee's use only. If yu're not the addressee and have received this message by mistake, please delete it and immediately notify us. You may not copy or disseminate this message to anyone. Thank you.
>
>
>