This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
Modifying references to contact info in the RIPE DB
- Previous message (by thread): Modifying references to contact info in the RIPE DB
- Next message (by thread): Modifying references to contact info in the RIPE DB
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Janos Zsako
zsako at banknet.net
Thu Jun 24 16:05:58 CEST 1999
> From owner-db-wg at ripe.net Thu Jun 24 15:23:02 1999 > From: Joao Luis Silva Damas <joao at ripe.net> > ALMOST NONE except that: > from that point on if someone else with a name equal to one already in the > database is entered into the database the reference will not be made ambiguous > while if we leave it as a reference by name it sure becomes ambiguous. I agree with Joao that there is virtually nothing to lose. I don't think it is better to have a reference by name with a single incorrect instance of a person object with that name, rather than a NIC-handle reference to the same incorrect instance... (By incorrect instance I mean a person object with the same name, but who has nothing to do with the referring object). At the same time the benefit is obvious (see above). Also, the longer one delays this process, the better the chances to have several instances to be handled manually (i.e. to try to identify the correct person object from several ones with the same name). Just my 2 filler (.01 HUF). :)) Janos
- Previous message (by thread): Modifying references to contact info in the RIPE DB
- Next message (by thread): Modifying references to contact info in the RIPE DB
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]