Service Announcements
  • All of our services are operating normally.
Check Network Health

Implementation of poem object

Archived This content has been archived and is no longer actively maintained.

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 [1].
  • Add a new object poem that will hold the poem itself. [2]
  • Add a new attribute "form:" that shows the type of poem. [3]

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 2 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@localhost 20050429
source: RIPE

These objects will be maintained by RIPE DBM. You can send new poetic-form objects to auto-dbm _at_ ripe _dot_ 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@localhost 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@localhost 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@localhost 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] [ ]