- db-wg - mailman.ripe.net

Re: [db-wg] IRT object creation is easy
by Wilfried Woeber, UniVie/ACOnet 17 Mar '04

17 Mar '04

>I wouldn't say this. I sent request day ago and unil now I didn't >get any response from people approving it. "... didn't get ANY response ..." I guess you should have got an automatic reply, with a ticket number?! Wilfried.

1 0

person objects update
by Pieterjan d'Hertog 17 Mar '04

17 Mar '04

Dear all, Just a sugestion Could it be possible to include the full name of the person in the detailed explanations of the ripe-dbm robot when creating new person objects in the ripe database ? If I remember well, in the previous version this was done ? This will be very usefull to more easily parse the results of an update and to import them in our own database. Example : The following object(s) were processed SUCCESSFULLY: --- Create SUCCEEDED: [person] CS2321-RIPE ***Info: Authorisation for [person] CS2321-RIPE using mnt-by: authenticated by: SKYNETBE-MNT Could be : Create SUCCEEDED: [person] Chris Sanders NEW nic-hdl : CS2321-RIPE Thanks, --- Pieterjan d'Hertog, Belgacom ANS/ROC Internet Expertise Center

5 9

SUCCESS: [New person: Test User]
by ripe-dbm＠ripe.net 16 Mar '04

16 Mar '04

> From: "Robert S. Plaul" <robert(a)plaul.de> > Subject: [New person: Test User] > Date: Tue, 16 Mar 2004 16:12:55 +0100 (CET) > Reply-To: robert(a)plaul.de > Message-ID: <Pine.LNX.4.58.0403161611570.3525(a)klendathu.crossline.org> SUMMARY OF UPDATE: Number of objects found: 1 Number of objects processed successfully: 1 Create: 1 Modify: 0 Delete: 0 No Operation: 0 Number of objects processed with errors: 0 Create: 0 Modify: 0 Delete: 0 Syntax Errors: 0 DETAILED EXPLANATION: ***Warning: Invalid keyword(s) found: [New, person:, Test, User] ***Warning: All keywords were ignored ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The following object(s) were processed SUCCESSFULLY: --- Create SUCCEEDED: [person] TU107-RIPE ***Info: Authorisation for [person] TU107-RIPE using mnt-by: authenticated by: CROSSLINE-MNT ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For assistance or clarification please contact: RIPE Database Administration <ripe-dbm(a)ripe.net> Regards, Robert S. Plaul -- RSP-RIPE

1 0

person objects update
by Pieterjan d'Hertog 16 Mar '04

16 Mar '04

Dear all, Just a sugestion Could it be possible to include the full name of the person in the detailed explanations of the ripe-dbm robot when creating new person objects in the ripe database ? If I remember well, in the previous version this was done ? This will be very usefull to more easily parse the results of an update and to import them in our own database. Example : The following object(s) were processed SUCCESSFULLY: --- Create SUCCEEDED: [person] CS2321-RIPE ***Info: Authorisation for [person] CS2321-RIPE using mnt-by: authenticated by: SKYNETBE-MNT Could be : Create SUCCEEDED: [person] Chris Sanders NEW nic-hdl : CS2321-RIPE Thanks, --- Pieterjan d'Hertog, Belgacom ANS/ROC Internet Expertise Center

1 0

RE: [db-wg] proposal: haiku object
by Titley, Nigel 16 Mar '04

16 Mar '04

Niall O'Reilly wrote: > On 13 Mar 2004, at 03:33, der Mouse wrote: > >> >>> A low blow.... and also one that is incorrect. Look again, >>> "serenaders" rhymes (or is more strictly an assonance) with "made >>> us". >> >> Only in UK English. > > No; only in certain dialects of British English. This rhyme won't > work too well in Glasgow, or in the Welsh valleys. > > 8-) Niall Well, as I said, its really an assonance rather than a rhyme, the "a" in "serenaders" is an assonance with the "a" in "made us". It's a perfectly valid poetic device and very common in ballads, although possibly fights slightly shy of the RIPE database definition of a limerick. Nigel -- Nigel Titley Peering Coordinator, FLAG Telecom +44 20 7478 9579 ********************************************************************** This e-mail message is confidential and is intended only for the use of the individual or entity named above and contains information which is or may be confidential, non-public or legally privileged. Any dissemination or distribution of this message other than to its intended recipient is strictly prohibited. You should not copy it or use it for any purpose nor disclose the contents to any other person. If you have received this message in error, please notify us by email to postmaster(a)flagtelecom.com immediately and delete the original message and all copies from all locations in your computer systems. This e-mail has been swept by Mailsweeper TM for viruses. However, FLAG Telecom cannot accept liability for any damage which you may sustain as a result of software viruses. ********************************************************************** This message has been scanned for viruses by MailControl - www.mailcontrol.com

2 1

RE: [db-wg] proposal: haiku object
by Titley, Nigel 14 Mar '04

14 Mar '04

Shane Kerr wrote: > Titley, Nigel wrote: >> >> Does the RIPE NCC have a view >> On provision of objects haiku? >> Are you bored and depressed >> And in need of a rest? >> Is this just too much extra to do? > > I think that I shall never see, > A class as lovely as a tree. > Trees like ash and bitternut, > May be only made by God but, > Objects are made by fools like me. > > [ With apologies to Alfred Joyce Kilmer ] > > > Anyway, we are certainly willing to implement any feature that the > community thinks is necessary, including but not limited to new > classes, attributes, access methods, etc. > > > Having said that, we have some problems with the current limerick > class. > > First, we are having trouble coming up with a good way to detect > whether limerick contents match the rhyming scheme. We can implement > this, although we will probably limit it to English (even though > there are Dutch, French, German, and other limericks), and will have > to make it a warning rather than an error, to allow for artistic > leave (to help people who think that "serenaders" rhyme with "join > us", like in LIM-NT13-1). A low blow.... and also one that is incorrect. Look again, "serenaders" rhymes (or is more strictly an assonance) with "made us". The last line "join in" rhymes with "the din". Some sort of soundex scheme would possibly have found this... however I agree that this is not an easy problem. > > Second, it is difficult for us to enforce the requirement that the > poem is humorous. I tried various algorithms, but none of the > software I came up with seemed to find any of the limericks funny at > all. Actually, I thought my computer was angry enough to swear at > me, until I remembered that I had tried Perl, and the punctuation > symbols were just the program itself. Well, as you know, I'm not at all sure that limericks are *required* to be humourous. I agree that the database definition says they are, but I feel that this is too limiting. I would propose modification of the specification to be "usually humourous". Of course if the verse-form proposal below is adopted, this can be dealt with in the descriptive limerick. > Anyway, I find the haiku an interesting proposal, but I do like the > generality of the poem proposal. I also agree that limiting the > types of poems to a pre-defined set of types. Therefore I suggest we > use the database to self-document the types of poems using a > meta-poem object. So poems would look like this: > > 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] [ ] > > The "form:" attribute will reference a poetic-form object: > > poetic-form: [mandatory] [single] [primary/look-up key] > descr: [optional] [multiple] [ ] > admin-c: [mandatory] [multiple] [inverse key] > tech-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] [ ] > > The "descr:", "admin-c:", "tech-c:", "remarks:", "notify:", "mnt-by:", > "changed:", and "source:" attributes are required in all RPSL objects > according to RFC 2622. > > Initially we would have: > > poetic-form: VERSE-LIMERICK > desr: A limerick object represents a humorous poem that has > five lines and the rhyme scheme "aabba". > admin-c: LIM1-RIPE > tech-c: LIM1-RIPE > mnt-by: RIPE-DBM-MNT > changed: ripe-dbm(a)ripe.net 20040401 > source: RIPE > > poetic-form: VERSE-HAIKU > descr: A haiku object represents a poem that usually has three > lines with 5, 7 and 5 units. In languages other than > Japanese units are generally applied as syllables. > There is no rhyme scheme at all. > admin-c: HIKU1-RIPE > tech-c: HIKU1-RIPE > mnt-by: RIPE-DBM-MNT > changed: ripe-dbm(a)ripe.net 20040401 > source: RIPE > > We would restrict new poetic-form objects to creation by RIPE DBM, but > adding additional forms for sonnets, free verse, blank verse, and so > on, should be easy. If the community feels that identifying and > documenting poetic forms falls out of the scope of the RIPE NCC > activities, we can consider an alternative mechanism. Perhaps ICANN > would be able to perform this activity? I personally wouldn't trust ICANN to create any verse-form other than a writ, although in mitigation, we have an ex-speaker for the secret working group embedded as a mole within the organisation, and now may be the time to activate him. > In any case, we would need a conversion project to change the existing > limerick objects into poem objects. There are currently 152 of > these, so we need to be careful not to interfere with these in a way > that affect the production services that depend on them. Oh quite. Perhaps the RIPE NCC could come up with a migration plan. I think the above is an excellent proposal, and I further endorse the later suggestion that the description be in the verse form itself. Best regards -- Nigel Titley Peering Coordinator, FLAG Telecom +44 20 7478 9579 ********************************************************************** This e-mail message is confidential and is intended only for the use of the individual or entity named above and contains information which is or may be confidential, non-public or legally privileged. Any dissemination or distribution of this message other than to its intended recipient is strictly prohibited. You should not copy it or use it for any purpose nor disclose the contents to any other person. If you have received this message in error, please notify us by email to postmaster(a)flagtelecom.com immediately and delete the original message and all copies from all locations in your computer systems. This e-mail has been swept by Mailsweeper TM for viruses. However, FLAG Telecom cannot accept liability for any damage which you may sustain as a result of software viruses. ********************************************************************** This message has been scanned for viruses by MailControl - www.mailcontrol.com

3 2

RE: [db-wg] proposal: haiku object
by TAYON, Julien 11 Mar '04

11 Mar '04

Titley, Nigel <mailto:NTitley@flagtelecom.com> wrote: > Olaf M. Kolkman wrote: >> I'd suggest the descr: field to be in the poetic form itself. > >> >> Looking at the VERSE-SONNET we may have a problem. There are several >> subclasses that people may wish to use. The Italian Sonnet, The >> English Sonnet and more modern varieties. How do we indicate >> possible sub-classes in the object? >> >> poetic-form: VERSE-SONNET >> variety: ENGLISH >> descr: (Somebody needs to write an English Sonnet) I would propose to Keep It Simple Poetic form: MAJOR-[MINOR][-SUBMINOR][-...] Example : poetic-form: VERSE-SONNET-ITALIAN poetic-form: VERSE-SONNET-ENGLISH ex : Venitian variety of Italian Sonnet could be : >> poetic-form: VERSE-SONNET-ITALIAN-VENITIAN This way we can extend as much as we want the poetic form. This is based on the assumption that Poetric form are homothetic to a tree structure. Which cannot be proven according to Goedel's theorem however I would say it is sufficiently close to reality for me. We will let the work of demonstrating the tree like structure of poetic form to the mathematicians if you don't mind. Regards, -- julien.tayon(a)neuf.com +33 (0)1 70 18 14 45 Gestion des adresses IPs, BU Data n9uf telecom 40 - 42 Quai du Point du Jour 92659 Boulogne Billancourt

1 0

RE: [db-wg] proposal: haiku object
by Titley, Nigel 11 Mar '04

11 Mar '04

Olaf M. Kolkman wrote: > I'd suggest the descr: field to be in the poetic form itself. > > > poetic-form: VERSE-LIMERICK > desr: The object consists of a verse > in a format that is far from terse > a-a-b-b-a scheme > around a humorous theme > and is sometimes extremely perverse > > admin-c: LIM1-RIPE > tech-c: LIM1-RIPE > mnt-by: RIPE-DBM-MNT > changed: ripe-dbm(a)ripe.net 20040401 > source: RIPE > > poetic-form: VERSE-HAIKU > descr: The haiku object > only seven syllables > in its density > admin-c: HIKU1-RIPE > tech-c: HIKU1-RIPE > mnt-by: RIPE-DBM-MNT > changed: ripe-dbm(a)ripe.net 20040401 > source: RIPE > > > Looking at the VERSE-SONNET we may have a problem. There are several > subclasses that people may wish to use. The Italian Sonnet, The > English Sonnet and more modern varieties. How do we indicate possible > sub-classes in the object? > > poetic-form: VERSE-SONNET > variety: ENGLISH > descr: (Somebody needs to write an English Sonnet) I'm happy to take an action to write an English Sonnet > poetic-form: VERSE-SONNET > variety: ITALIAN > descr: (Somebody needs to write an Italian Sonnet) -- Nigel Titley Peering Coordinator, FLAG Telecom +44 20 7478 9579 ********************************************************************** This e-mail message is confidential and is intended only for the use of the individual or entity named above and contains information which is or may be confidential, non-public or legally privileged. Any dissemination or distribution of this message other than to its intended recipient is strictly prohibited. You should not copy it or use it for any purpose nor disclose the contents to any other person. If you have received this message in error, please notify us by email to postmaster(a)flagtelecom.com immediately and delete the original message and all copies from all locations in your computer systems. This e-mail has been swept by Mailsweeper TM for viruses. However, FLAG Telecom cannot accept liability for any damage which you may sustain as a result of software viruses. ********************************************************************** This message has been scanned for viruses by MailControl - www.mailcontrol.com

1 0

RE: [db-wg] proposal: haiku object
by TAYON, Julien 11 Mar '04

11 Mar '04

Olaf M. Kolkman <mailto:olaf@ripe.net> wrote: > I'd suggest the descr: field to be in the poetic form itself. > > > poetic-form: VERSE-LIMERICK > desr: The object consists of a verse > in a format that is far from terse > a-a-b-b-a scheme > around a humorous theme > and is sometimes extremely perverse > > admin-c: LIM1-RIPE > tech-c: LIM1-RIPE > mnt-by: RIPE-DBM-MNT > changed: ripe-dbm(a)ripe.net 20040401 > source: RIPE > > poetic-form: VERSE-HAIKU > descr: The haiku object > only seven syllables > in its density > admin-c: HIKU1-RIPE > tech-c: HIKU1-RIPE > mnt-by: RIPE-DBM-MNT > changed: ripe-dbm(a)ripe.net 20040401 > source: RIPE > poetic-form: PROSE descr: Don't let the structure tie your tongue ; if you hate the masochism of verses, remember that you can feel free to use prose, and feel free because you are. admin-c: LIM1-RIPE tech-c: LIM1-RIPE mnt-by: RIPE-DBM-MNT changed: ripe-dbm(a)ripe.net 20040401 source: RIPE

2 1

RE: [db-wg] proposal: haiku object
by Titley, Nigel 11 Mar '04

11 Mar '04

Robert S. Plaul wrote: > On Wed, 10 Mar 2004, Titley, Nigel wrote: > >> All poems are limericks, true. >> There are no need for objects haiku >> This thread is amusing >> It set us all musing >> But we plainly have little to do >> >> Nigel > > The RIPE Database > Guardian of the limericks > Now needs the haiku > > The haiku object - > Greater flexibility > The virtue is clear Does the RIPE NCC have a view On provision of objects haiku? Are you bored and depressed And in need of a rest? Is this just too much extra to do? Nigel -- Nigel Titley Peering Coordinator, FLAG Telecom +44 20 7478 9579 ********************************************************************** This e-mail message is confidential and is intended only for the use of the individual or entity named above and contains information which is or may be confidential, non-public or legally privileged. Any dissemination or distribution of this message other than to its intended recipient is strictly prohibited. You should not copy it or use it for any purpose nor disclose the contents to any other person. If you have received this message in error, please notify us by email to postmaster(a)flagtelecom.com immediately and delete the original message and all copies from all locations in your computer systems. This e-mail has been swept by Mailsweeper TM for viruses. However, FLAG Telecom cannot accept liability for any damage which you may sustain as a result of software viruses. ********************************************************************** This message has been scanned for viruses by MailControl - www.mailcontrol.com

3 2