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/db-wg@ripe.net/
[db-wg] Proposal: make phone number optional in person objects
- Previous message (by thread): [db-wg] Proposal: make phone number optional in person objects
- Next message (by thread): [db-wg] Proposal: make phone number optional in person objects
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Peter Koch
pk at DENIC.DE
Fri Apr 17 15:49:22 CEST 2015
On Fri, Apr 17, 2015 at 01:43:20PM +0000, Shane Kerr wrote: > "person" is the name of the person, so I'd say that needs to exist. > "address" probably should be optional. > "phone" probably should be optional. > "nic-hdl" is the key, so that needs to exist. > "mnt-by" is used to protect the object, so that needs to exist. > "changed" probably should be optional. > "source" is required to distinguish between RPSL sources, so that needs > to exist. agree with all of this. > I'm happy to include "address" and "changed" in the list of optional > attributes! So, that would mean the business logic should mandate at least one out of those attributes to be present - or we should extend the proposal to make the whole person object optional (what's the point in having a person object just with a name? Well, could hide the IM crediential in remarks ...) -Peter
- Previous message (by thread): [db-wg] Proposal: make phone number optional in person objects
- Next message (by thread): [db-wg] Proposal: make phone number optional in person objects
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]