. Search the site
FRDCSA | internal codebases | Bard

Bard

Architecture Diagram: GIF

Jump to: Project Description | Capabilities

Project Description

bard was originally written as a poetry composition system. It is designed to assist the user in composing a wide variety of poems - as communicative devices. The system will make the composition of very complex poems incorporating advanced systems of metre much easier, and while an autist has trouble communicating, learned poetry will put their communication on an equal footing with Neurotypicals. I.e. bard will overcome the lack of credibility. We will finally be able to tell the truth, and tell it well.

Functionality includes:
  • Statistical models over poem copora
  • Checks and suggestions for various systems of bardic composition.
  • Capabilities for automatically generating poems that satsify various requirements.
  • Integration with audience.

Capabilities

  • bard should use nyquist
  • bard v-machine.
  • Write an epic poem about my life in Gaelic or English, or both, using bard.
  • You could add bard wordplay to that!
  • bard should do all the anagrams that make sense.
  • bard - use Lingua::GA::Gramadoir - Check the grammar of Irish language text ...
  • bard should attempt to determine similar sounding things, i.e. the name surnia reminds one of narnia
  • bard should use the word association thesaurus
  • bard's acronym stuff should support trying to fill in an acronym, e.g. radar
  • Use theorem proving to enhance bard's acronym generation.
  • Develop actual database of humor techniques, add it to bard. That way, it can automatically come up with jokes.
  • bard should have a database of word connotations. Could generate this from semantic distance to well known words. Note that some of them depend on the listener.
  • bard doesn't handle all morphology.
  • Should have a bard -d record,index,classify
  • bard should use WordNet::QueryData in addition to CSP.
  • Generally have a system for mnemonics, seems like that would be part of bard.
  • bard can use a CSP to generalize the interface.
  • bard's acronym generation can be funny - Difference Of Opinion Mixture System (DOOMS)
  • Look into other usage models for bard. find out how this is actually done.
  • bard should support subtones or whatever, i.e. I want a word like "executive" but that implies cooperations. Also query expansion selection should be a feature of bard?
  • bard could be called wordsmith
  • Be sure to add look for somehow rhyming or alliterating words to bard that have a particular meaning.
  • clear should consult all/Termios/picform/bard for understanding writings.
  • bard should be able to find all rhyme sets in some list of items, say internal codebases, or external codebases.
  • bard could have a poem in which problemspace and reasonbase rhymed.
  • bard could have a mode for listing meanings.
  • bard: http://www.rhymezone.com/
  • bard can start using source texts to supply seed words and concepts for generating acronyms
  • bard should use "an"
  • Could add a feature to bard for searching for words by sound
  • Maybe bard should also sense disambuigate first
  • It can consult with bard on whether a given item is an insult or not.
  • audience may make use of bard for generating a satire!


This page is part of the FWeb package.
It derives from the Robotics Institute projects page.
Last updated Mon Jan 15 08:33:31 CST 2007 .