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]/
RIPE Handle document
- Previous message (by thread): RIPE Handle document
- Next message (by thread): RIPE Handle document
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Piet Beertema
Piet.Beertema at cwi.nl
Tue Dec 7 17:01:12 CET 1993
See above: a local registry may generate unique handles, but they don't serve the purpose of uniqueness in the context where that uniqueness is required. If an handle is unique it could be used in many different contexts, i.e. database with source: RIPE and source: SOMETHINGELSE True, but that would only make the problem worse: then you could have e.g. 10 Person objects which are each unique in their own [source] context but which actually refer to one and the same person. In such a case I'd still prefer to have a specific tag (like a handle) assigned centrally by RIPE even when the source of the object is not RIPE. The problem of delay in registrations by "regional" registries could perhaps be overcome by an automated "handle assignment" service by RIPE, where a handle could be obtained interactively by authorised persons. Piet
- Previous message (by thread): RIPE Handle document
- Next message (by thread): RIPE Handle document
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]