Hi,
And if an object was to be created I would propose on the model of limerick object
Since I am always in favour of a general approach, I support the Poem Object.
whois -t poem
poem: [mandatory] [single] [primary/look-up key] descr: [optional] [multiple] [ ] text: [mandatory] [multiple] [ ] admin-c: [mandatory] [multiple] [inverse key] author: [mandatory] [multiple] [inverse key] remarks: [optional] [multiple] [ ] notify: [optional] [multiple] [inverse key] type: [mandatory] [single] [ ] mnt-by: [mandatory] [multiple] [inverse key] changed: [mandatory] [multiple] [ ] source: [mandatory] [single] [ ] Where type would be one of the folllowing : LIMERICK, PROSE, QUATRAIN, SONNET, HAIKU, ASCII-ART ...
Such a solution would broadly sataisfy any sysadmin wanting to express his art freely.
is there a deep reason for this beeing the only object not haveing a tech-c: ? Meaning the one who created the poem (i.e. admin-c) might not be the one manageing it (i.e. tech-c).
For managers I would propose a MEMO object too. Because, the whois DB might be the fully legitimate place for such a thing, the last place where you are gonna search for such an abomination. ;)
and in that context the official ORDER object too. like Manager: I gave you an order! Admin: Where? Manager: in 'ORDER-CONNECT-CUSTOMER' SCNR lG uk -- Ulrich Kiermayr Zentraler Informatikdienst der Universitaet Wien Network - Security - ACOnet-CERT Universitaetsstrasse 7, 1010 Wien, AT eMail: ulrich.kiermayr@univie.ac.at Tel: (+43 1) 4277 / 14104 PGP Key-ID: 0xA8D764D8 Fax: (+43 1) 4277 / 9140