.
FRDCSA | internal codebases | KBFS

KBFS Architecture Diagram: GIF

Jump to: Project Description | Capabilities

Project Description

Capabilities

• kbfs should operate like LogicMoo, having a MUD like representation of the file system.
• This new system is the basis for critic, kbfs (now we have the KB for it), gourmet's ontology, etc, etc, etc.
• Develop a self-organizing file system (kbfs).
• Cleversafe should interface kbfs.
• We can have kbfs do transparent compression of non-active, inefficient files.
• kbfs could use dvdisaster
• Have a lost and found facility in kbfs, if you have lost any files, describe the data, etc. kbfs may find it for you eventually.
• I just noticed that with locate, you often get a directory, we could design a kbfs version of locate that summarized the different chunks.
• kbfs then ought to have a mode that works like this. If we have file IDs, etc. We can approximate file derivation from this database. Maybe it should be part of kbfs.
• sanctus should eliminate pornography, illegally obtained media, (should work with kbfs to tag all incoming data), etc.
• Should break up books into functionality (like CCM) and then verify using our kbfs/architect requirements traceability mappings.
• Not only should kbfs know what file a given request matches too, but architect (or something) ought to know which functions or objects implement the described capabilities.
• Often times, certain files implement certain solutions. We will want to track that information with kbfs.
• Should probably make an effort to determine all files that are modified by us, and what they are and represent (i.e. kbfs)
• I think maybe we ought to use kbfs with SourceManager
• Add to kbfs something that goes around cleaning things up.
• kbfs depends on cdcat
• kbfs should have a classifier that automatically classifies items, using the classification system I am to write tonight.
• kbfs should track what important project information is where. For instance, if we were to move all packages to the projectbox server, and delete them to free space, kbfs should know that
• Should configure kbfs to start commenting on files. For instance - konik_laird_ilp2004.pdf is related to corpus.
• Inventory management/kbfs should make use of a common system to manage instances of important items/data.
• numerous ideas on the subject: should have classes be a type hierarchy. Maybe build a grpahical tool to interactivcely classify these. Convert these system over to kbfs::Cache, keeping a copy of current method. For each icodebase and common (agentified), add a class. For instance, rather than classifying into a vague category, you could classy directly to "pse, goal", etc.
• I bet we could store all personal data on an encrypted loopback file system, which would be part of say, kbfs.
• could configure clear to use kbfs and then in this way, it would be capable of correctly processing documents (as in identification via metadata)
• Naturally clear should provide the ability to search backwards through what has been read, in order to answer questions and so forth. For instance if I read something to the effect that this truth is as clear as the sun, searching for this should get me the results I want. This reinforces the notion that clairvoyance should keep a central kbfs implementation of voy files, and run against that, as these can then easily be equipped for searching by a common search interface.
• Also, we want to change the library directory of clear to be under /var/lib/clear/library or something, or even kbfs
• For kbfs?
• (OntoFerret for kbfs::Digest)
• (kbfs - WebCache::Digest kbfs - WebFS::FileCopy)
• (kbfs - http://search.cpan.org/modlist/File_Name_System_Locking)
• (kbfs::Pack - Algorithm::Knapsack - brute-force algorithm for the knapsack problem)
• Forgot to mention need to work on classification system and kbfs using those new perl mods.