-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Paul Wilson wrote:

i'm finding this discussion rather anglo-centric. was any consideration given to a "language" descriptor in discussion of this object.

Good point. This clearly needs some global coordination. I propose the establishment of a VFSO (Verse-Form Supporting Organization) underwritten by the RIRs, with authority to arbitrate as necessary on the validity and merit of a verse-form or verse-form instance, its transposition from one language and cultural environment to another, suitable encodings where us-ascii and UTF-8 are inadequate and cryptographic support for global intellectual property rights. The VFSO will also need to delegate authority for languages or verse-forms peculiar[1] to a region to the RIR primarily serving that region, who may at their discretion delegate it further to appropriate agencies[2]. The constitution of the VFSO will be written entirely in canonical verse-forms (though until the canon is defined some transitional arrangement may be necessary). I see commercial opportunities here. For instance, I understand from other recent postings to the list that there is an agency in NL (or at least accessible through NL, though its physical location, if any, is a closely guarded secret) which might be in a position to offer verse-form validation services to APNIC or others. I do not see why they should not make a charge for those services (though under present regulations for money laundering payments might have to be made in CO2 credits, oil or gold). How do we organise the elections to the VFSO? Rodney Tillotson, JANET-CERT +44 1235 822 255 [1] A nice word in English english, meaning specific or distinctive rather than just queer or odd. [2] For instance, the Limerick English segment of the work might be assigned to the Town Council of a small town in one of the English counties to the west of London, UK; the Bawdy Song English segment to a carefully-selected Welsh (UK) rugby club (possibly not the same as the one that oversees Bawdy Song Welsh), and so on. -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 7.0.3 for non-commercial use <http://www.pgp.com> iQA/AwUBQoMijMxy/J7PAuvpEQLMhQCggMiN6h8zHvcCDu/cze+kBXDlqesAn0L4 nSj1Yz/w/DVT/ji+/Z4n0QdD =Vswc -----END PGP SIGNATURE-----

Hey Olaf my literary skills are superb when it comes to writing some blurb but you are right I was employed for writing C functions void I am sure you will all be happy to know I write better C code than poetry :) cheers denis Olaf M. Kolkman wrote:

...

Note the hierarchical naming convention for poetic-form objects, all verse

I have a few maintenance questions.

Although my colleagues are technically competent, they have not been hired for their literary skills(*). So although the RIPE DB staff will technically maintain the poetic-form: we still need a mechanism to ensure the quality of the "poetic-form" objects.

Will RIPE NCC staff need to contact a secret cabal for quality control? Alternatively, will we skip quality control and act on first come first served (serious security considerations: culprits might specify a Haiku in the form of a Dada poem)? Or should a poetic-form first be discussed by the db-wg?

I'd settle for the first option, a secret cabal... I may just know an institution that could perform this task.

The classification scheme may also need some work. How do we classify the different forms? Would the Aphorism have its own class or is it a subclass of PROSE?

In absence of the review process. Hereby a new proposal

poetic-form: PROSE-APHORISM descr: A database entry to be remembered by admin-c: OK65-RIPE tech-c: OK65-RIPE mnt-by: RIPE-DBM-MNT

and

poetic-form: VERSE-HAIKU descr: The haiku object descr: only seven syllables descr: in its density admin-c: OK65-RIPE tech-c: OK65-RIPE mnt-by: RIPE-DBM-MNT

-- Olaf

(*) I am sure I lost credit with my colleagues with this remark but these are matters of high public interest.

---------------------------------| Olaf M. Kolkman ---------------------------------| RIPE NCC