hSbc:: AAj
SBConcept--Computer-System
#h0#
AAj is a Sensorial-Brainual-Concept--Computer-System which uses my AAj-program, a free and open-source sensorial-b-concept--program written in java computer-language that uses XML to represent sensorial-b-concepts. #h0.1p1#
EnglishSynonym:
* AAj SensorialConcept-ComputerSystem,
* AAj SensorialConcept-System,
* AAj Brainepto-Base-Purification-System,
* AAj Knowledge-Integrator,
* java Brainepto-Model-Manager,
* java Mental-Model-Management,
* java Structured-Concept Knowledge-Management-System,
* java Structured-Concept-System,
* java Science-Support-System.
#h0.2p1#
AAj comes from the names of my sons A=Apostolos, A=Aristotelis and the name of the programming-language I use j=java. #h0.2p2#
List:
* the AAj-program,
* the computer that runs it and
* the knowledge-base created with the program.
#h0.3p1#
List:
* scs-function.
#h0.4.1p1#
List:
* Retrieval-function
* Storage-function
#h0.4.2p1#
Generic:
* scs-retrieval.
#h0.4.2.1p1#
Specific:
* 1. AAj's-ACCESS.
* 2. AAj's-NAVIGATION.
* 3. AAj's-PRESENTATION.
#h0.4.2.1p2#
hSbc:: AAj's-ACCESS:
Generic:
* scs-access.
#h0.4.2.1p3#
hSbc:: AAj's-NAVIGATION:
Generic:
* scs-navigation.
Specific:
* User-interface:
The program is a global one, in Java terms. Now
it can present the user-interface in English,
Greek, Komo
and Esperanto languages.
* Finding|Searching:
My program has a SMART
search function. It Can search related sbConcepts, for example,
a)the parts of a sbConcept or
b)all the sbConcepts of the same kind.
Of course, it can search ALL the sbConcepts for its names
and synonyms. It can search for a 'word', part of a word,
and for a 'name' (one or more words that name an entity).
* Asking (Inferring):
Now, the system can answer "is a" and "is part of" questions.
#h0.4.2.1p4#
hSbc:: AAj's-PRESENTATION:
Generic:
* scs-presentation.
Specific:
* Table-of-Contents:
The viewer displays
one xConcept at a time AND all its first-level attributes.
The window is divided in two parts. On the left, there is
a tree with the table-of-contents of the xConcept.
On the right, the attributes of the xConcept are displayed.
* Worldviews:
The reader, when searches for an xConcept, can choose the worldview
he is intresting on or all of them.
* The Help:
The system displays its help in the same
format that displays the stored knowledge.
Also it displays it in html format through a simple html
browser.
#h0.4.2.1p5#
Generic:
* scs-storage.
#h0.4.2.2p1#
Specific:
* 1. AAj's-KNOWLEDGE-ACQUISITION.
* 2. AAj's-KNOWLEDGE-ADDITION.
* 3. AAj's-KNOWLEDGE-CHANGE.
#h0.4.2.2p2#
hSbc:: AAj's-KNOWLEDGE-ACQUISITION:
Generic:
* scs-acquisition.
#h0.4.2.2p3#
hSbc:: AAj's-KNOWLEDGE-ADDITION:
Generic:
* scs-addition.
Specific:
* The Editor:
The program has a simple
XML-editor.
Any author who knows XML can use it. Also the editor is a tool
to check if something goes wrong.
* Validation:
Integration:
This is the notable function my system now has.
It CHECKS the part-whole and generic-specific
relations among sbConcepts and FIXES them.
What I mean: Writing an xConcept, you must integrate it with
the existing knowledge-base. Then my system can check for xConcept-relations
violations such as:
Part Integration: The attribute-cpts of the current-cpt must have
as whole-cpt the current-cpt. If not my system fixes the error.
Whole Integration: The whole-cpts of the current-cpt must have as
attribute-cpts the current-cpt. If not my system fixes the error.
Generic Integration: The attribute-cpts of the generic-cpts
of the current-cpt must be attribute-cpts of the current-cpt.
If not my system fixes the error.
Specific Integration: The specific-cpts must have as attribute-cpts
the attribute-cpts of the current-cpt. Also a specific of current-cpt
must have as generic the current. If not my system fixes the error.
Environment Integration: An environment process-or-relation with another 'object'
must be environment process-or-relation also to that 'object' and any environment
process-or-relation must be related at least to two objects.
If not my system fixes the error.
#h0.4.2.2p4#
hSbc:: AAj's-KNOWLEDGE-CHANGE:
Generic:
* scs-change.
Specific:
* Terminology-Management:
Changing the name of an xConcept does NOT affect
the knowledge-base.
#h0.4.2.2p5#
it is a free and open-source sensorial-b-concept--program written in java computer-language that uses XML to represent sensorial-b-concepts. #h0.5.1p1#
EnglishSynonym:
* java-xConcept-program.
#h0.5.2p1#
List:
* Sensorial-BConcept--Program.
#h0.5.3p1#
Its knowledge-base is comprised of many sensorial-b-worldviews. #h0.6.1p1#
EnglishSynonym:
* XKnowledgeBase.
#h0.6.2p1#
hSbc:: X-WORLDVIEW:
Definition:
It is a
sensorial-b-worldview
comprised of x-concepts.
#h0.6.3p1#
hSbc:: X-SUBWORLDVIEW:
Definition:
It is a
sensorial-b--sub-worldview
comprised of x-concepts.
#h0.6.3p2#
List:
* Sensorial-BConcept--System's-KnowledgeBase.
#h0.6.4p1#
AAj uses XML based sensorial-b-concepts. #h0.7.1p1#
EnglishSynonym:
* AAj's-KRM.
#h0.7.2p1#
List:
* Sensorial--b-concept.
#h0.7.3p1#
List:
* Sensorial--b-concept KRM.
#h0.7.4p1#
AAj's sensorial-b-concept is an XML-file or an element in an XML-file if a definition is enough to describe it. This is the dtd I'm using. In the editor's snapshot you can see an example of a sensorial-b-concept. #h0.8.1p1#
EnglishSynonym:
* xcpt.
* xConcept,
* xml--sensorial-b-concept,
* xml-concept,
* x-concept,
* x-cpt.
#h0.8.2p1#
The main-name of an x-concept is its FIRST noun-case. #h0.8.3p1#
hSbc:: FILE-NAME:
Example:
"BConcept@hknu.meta-1@.xml"
#h0.8.5p1#
hSbc:: FORMAL-NAME:
Example:
"BConcept@hknu.meta-1@"
Part:
* FORMAL-TERM--OF-FORMAL-NAME: "BConcept"
* FORMAL-ID--OF-FORMAL-NAME: "hknu.meta-1"
* FORMAL-VIEW--OF-FORMAL-NAME: "hknu.meta"
* FORMAL-WORLDVIEW--OF-FORMAL-NAME: "hknu"
* FORMAL-SUBWORLVIEW--OF-FORMAL-NAME: "meta"
* FORMAL-NUMBER--OF-FORMAL-NAME: "1"
#h0.8.5p2#
hSbc:: UNIQUE-NAME:
Specific:
* file-name: BConcept@hknu.meta-1@.xml
* formal-name: BConcept@hknu.meta-1
* formal-ID: hknu.meta-1
#h0.8.5p3#
List:
* Sensorial--b-concept
#h0.8.6p1#
Description:
The program can run on a stand alone computer.
But its full usefulness will come when will run in a server-client
environment.
#h0.9p1#
Sensorial--b-concept Files:
the directory "AAjKB" contains the XML-files that represent
the sensorial-b-concepts.
#h0.10.1p1#
Term-files (index-files):
contain ALL the terms-of-logal-concepts
of a sensorial-b-concept's-terms and the rest terms in index form.
In contrast, a sensorial-b-concept--file contains only the lg-concept's--names.
Index-files does not contain the information of the usage of terms. This
information is contained in sensorial-b-concept--files in the order of names.
Its directory is: "aaj_dir/AAjKB/AAjINDEXES/"
#h0.10.1p2#
Terminal-Files:
contain the lg-concept-auxiliaries,
special-nouns, conjunctions, prepositions, special-expressions and
the most-used-terms.
#h0.10.1p3#
Java-Files:
the directories
"pk_Html",
"pk_Logo",
"pk_SSemasia",
"pk_Util"
"pk_XKBEditor",
"pk_XKBManager",
contain the binary files of the program.
#h0.10.1p4#
List:
* SBConcept-System.
#h0.11p1#
List:
* SENSORIAL--B-CONCEPT--THEORY.
* THE-59-SENSORIAL--B-CONCEPTS.
#h0.12p1#
See it in scs-evolution. #h0.13p1#
Description:
The program could be used by a READER
(anyone who knows to run a computer program) and an AUTHOR
(anyone who knows to run a computer program,
understands the xConcept-relations and has good
knowledge on a domain. An author does not need to know XML).
#h0.14p1#
File ToC:
⇨ Definition
⇨ Synonym
⇨ Part
⇨ Function
⇨ Program
⇨ KnowledgeBase
⇨ SensorialBConcept
⇨ KnowlReprMethod
⇨ Computer
⇨ Files
⇨ Generic
⇨ Environment
⇨ Evolution
⇨ User
#h0.toc#
AAj ToC:
⇨ Home
⇨ SBConcept-Theory
⇨ Schema
⇨ The-59-SBConcepts
⇨ Bibliography
⇨ Human-Language
⇨ Komo
⇨ KRS
⇨ SBConcept-System
⇨ AAj
⇨ SSS-Paper (1990)
⇨ Site-Evolution
⇨ Author
⇨ All-files
⇨ All-names
#h0.toc#
VERSIONS:
* CURRENT: http://aaj.sourceforge.net/hSbc/aaj-sbccs.html
* PUBLISHED:
* CREATED: 1999.02.10
* MAIL: userid@domain, where userid=nikkas and domain=otenet.gr
#h0.toc#