<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2653.12">
<TITLE>RE: [db-wg] proposal: haiku object</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2>Robert S. Plaul <<A HREF="mailto:robert@plaul.de">mailto:robert@plaul.de</A>> wrote:</FONT>
<BR><FONT SIZE=2>> Proposal for Adding a Haiku Object to the RIPE Database</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Requirement:</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> System Administrators and other users of the RIPE Database need some</FONT>
<BR><FONT SIZE=2>> avocation beside their exhausting work with ip address space</FONT>
<BR><FONT SIZE=2>> assignments, routing and other occupations concerning database</FONT>
<BR><FONT SIZE=2>> objects which have to be taken seriously. The existing limerick</FONT>
<BR><FONT SIZE=2>> object provides such avocation but obviously has some limitations:</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>[...]</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Solution:</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>...</FONT>
</P>
<P><FONT SIZE=2>Even Though I fully agree with the need for a haiku object, because I am not sure of my limmericks (LIM-ROSE LIM-FRIENDS LIM-STRESS) I don't think the creation of an haiku object -per se- might be the solution. Mayhaps can we reuse the limerick objects and use the remarks field with one of the possible value :</FONT></P>
<P><FONT SIZE=2>HAIKU, for haiku</FONT>
<BR><FONT SIZE=2>SONNET for such</FONT>
<BR><FONT SIZE=2>PROSE for freestyle poetry</FONT>
<BR><FONT SIZE=2>....</FONT>
<BR><FONT SIZE=2>Therefore not only would we satisfy :</FONT>
<BR><FONT SIZE=2>- sysadmin that like well labelled object for easier retrieval,</FONT>
<BR><FONT SIZE=2>- poets for increasing their potentiality,</FONT>
<BR><FONT SIZE=2>- RIPE dba for not chaging the actual object. </FONT>
</P>
<P><FONT SIZE=2>And if an object was to be created I would propose on the model of limerick object</FONT>
</P>
<P><FONT SIZE=2>whois -t poem</FONT>
</P>
<P><FONT SIZE=2>poem: [mandatory] [single] [primary/look-up key]</FONT>
<BR><FONT SIZE=2>descr: [optional] [multiple] [ ]</FONT>
<BR><FONT SIZE=2>text: [mandatory] [multiple] [ ]</FONT>
<BR><FONT SIZE=2>admin-c: [mandatory] [multiple] [inverse key]</FONT>
<BR><FONT SIZE=2>author: [mandatory] [multiple] [inverse key]</FONT>
<BR><FONT SIZE=2>remarks: [optional] [multiple] [ ]</FONT>
<BR><FONT SIZE=2>notify: [optional] [multiple] [inverse key]</FONT>
<BR><FONT SIZE=2>type: [mandatory] [single] [ ]</FONT>
<BR><FONT SIZE=2>mnt-by: [mandatory] [multiple] [inverse key]</FONT>
<BR><FONT SIZE=2>changed: [mandatory] [multiple] [ ]</FONT>
<BR><FONT SIZE=2>source: [mandatory] [single] [ ]</FONT>
<BR><FONT SIZE=2>Where type would be one of the folllowing :</FONT>
<BR><FONT SIZE=2>LIMERICK, PROSE, QUATRAIN, SONNET, HAIKU, ASCII-ART ...</FONT>
</P>
<P><FONT SIZE=2>Such a solution would broadly sataisfy any sysadmin wanting to express his art freely. </FONT>
</P>
<P><FONT SIZE=2>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. ;)</FONT></P>
<P><FONT SIZE=2>Regards, </FONT>
</P>
<P><FONT SIZE=2>Julien Tayon</FONT>
</P>
</BODY>
</HTML>