You asked for it and here it is, Database changes - crucial to your biz! If a limerick won't do, You can use a haiku. We hope the secret working group will forgive. Bit later then we announced but, new objects POEM and POETIC-FORM are in your service. Hope you enjoy it. Regards. Arife

Dear Colleagues,

[Apologies for duplicates]

Following discussions in the Database Working Group, we have made changes to the whois server software.

These are the proposed changes:

- Add a new object POETIC-FORM that will contain the supported poem types. - Add a new object POEM that will hold the poem itself. - Add a new attribute "form:" that shows the type of poem.

There is more information about this below.

You can find more details about the discussion at:

http://www.ripe.net/ripe/maillists/archives/db-wg/2004/msg00246.html

We expect to put a new whois server on line with new object support on 3 May 2005 at 16:00 CET.

- Add a new POETIC-FORM object:

The POETIC-FORM object contains information about the poem type.

This is an example of a LIMERICK object:

poetic-form: FORM-LIMERICK descr: Poem type for Limerick admin-c: AMR68-RIPE mnt-by: RIPE-DBM-MNT changed: ripe-dbm@ripe.net 20050429 source: RIPE

These objects will be maintained by RIPE DBM. You can send new POETIC-FORM objects to <auto-dbm@ripe.net>.

- Add a new POEM object:

A POEM object is similar to the LIMERICK object. Unlike the LIMERICK object, it will have a "form:" attribute that contains information about the poem type.

This is an example of a simple POEM object:

poem: POEM-NT13-1 descr: RIPE24 dinner text: At a RIPE Meeting, held in Berlin, text: The meal was unusual, the din text: Of the two serenades text: Whose repertoire made us text: All smile and want to join in form: FORM-LIMERICK admin-c: LIM1-RIPE author: NT13 mnt-by: LIM-MNT changed: limerick-wg@ripe.net 19960529 source: RIPE

Add a new "form:' attribute:

The "form:" attribute indicates the type of poem.

- Changes to the default whois query interface:

There will be no changes to the whois query interface.

- Data transition

All existing LIMERICK objects will will be converted to POEM objects. LIMERICK objects will appear in the database for a while, but we will eventually delete them.

Here is an example of a LIMERICK object:

limerick: LIM-NT13-3 text: The document RIPE-104 text: Goes on longer than ever before text: If you want an address text: And your network's a mess text: Then Daniel will get very sore admin-c: LIM1-RIPE author: NT13 remarks: Great limerick, but the draft document RIPE-104++ remarks: is now called RIPE-136... mnt-by: LIM-MNT changed: limerick-wg@ripe.net 19960529 source: RIPE

Here is how it will appear with new object types:

poem: POEM-NT13-3 text: The document RIPE-104 text: Goes on longer than ever before text: If you want an address text: And your network's a mess text: Then Daniel will get very sore form: FORM-LIMERICK admin-c: LIM1-RIPE author: NT13 remarks: Great limerick, but the draft document RIPE-104++ remarks: is now called RIPE-136... mnt-by: LIM-MNT changed: limerick-wg@ripe.net 19960529 source: RIPE

- Object templates

Here is the template for the POEM object:

poem: [mandatory] [single] [primary/look-up key] descr: [optional] [multiple] form: [mandatory] [single] [inverse key] text: [mandatory] [multiple] [ ] admin-c: [mandatory] [multiple] [inverse key] author: [mandatory] [multiple] [inverse key] remarks: [optional] [multiple] [ ] notify: [optional] [multiple] [inverse key] mnt-by: [mandatory] [multiple] [inverse key] changed: [mandatory] [multiple] [ ] source: [mandatory] [single] [ ]

POETIC-FORM object template is:

poetic-form: [mandatory] [single] [primary/look-up key] descr: [optional] [multiple] [ ] admin-c: [mandatory] [multiple] [inverse key] remarks: [optional] [multiple] [ ] notify: [optional] [multiple] [inverse key] mnt-by: [mandatory] [multiple] [inverse key] changed: [mandatory] [multiple] [ ] source: [mandatory] [single] [ ]

Regards, Arife Vural RIPE NCC, SED