hSbc:: SBConcept-System
(SBCS)
#h0#
Specific:
SensorialBrainualConcept-System is a
brainual--knowledge-representation-system
that help us MANAGE (create, store,
integrate, retrieve)
DIFFERENT sensorial-b-worldviews
and consequently
brainual-worldviews,
using sensorial-b-concepts.
#h0.1p1#
EnglishSynonym:
* SBConcept-System,
* SensorialConcept-System,
* SensorialConcept-KnowledgeRepresentationSystem,
* Sensorial-Concept--System,
* vudosimbepto-system,
* brainepto-base--purification-system,
* brainepto-base--management-system,
* brainepto-base--system,
* brainepto-base--manager,
* info-system--management,
* knowledge-system--management,
* knowledge-integrator,
* brainepto-model--integrator,
* artificial--brainepto-model-integrator,
* model-breinepto--management,
* brain-model--management-system,
* Structured-Concept--Knowledge-Management-System,
* Structured-Concept-System--KMS,
* scs-system,
* scs-tool,
* scs--science-support-system,
* Science-Support-System,
#h0.2p1#
List:
* the Sensorial-b-concept--program,
* the computer that runs it and
* the knowledge-base created with the program.
#h0.3p1#
List:
* krs-function.
#h0.4.1p1#
The functions of the program can be classified as storage or retrieval in relation to user. #h0.4.2p1#
List:
* Retrieval-function
* Storage-function
#h0.4.2p2#
Description:
Knowledge retrieval must be easy, fast, intuitive, reliable.
#h0.4.2.1p1#
Generic:
* krs-retrieval.
#h0.4.2.1p2#
Specific:
* 1. SBCS's-ACCESS.
* 2. SBCS's-NAVIGATION.
* 3. SBCS's-PRESENTATION.
#h0.4.2.1p3#
hSbc:: SBCS's-ACCESS:
Description:
It must be an online system (internet) with
FREE access to everyone.
Generic:
* krs-access.
#h0.4.2.1p4#
hSbc:: SBCS's-NAVIGATION:
Generic:
* krs-navigation.
Specific:
* User-interface-navigation:
the reader intuitively must easily understand what to do to
find knowledge.
The user must can choose the natural-language of the
user-interface.
Spoken-Commands:
understanding spoken-commands is the future in user-interface.
* Table-Of-Contents-navigation:
The system must have a table of contents.
* Alphabetical-list-navigation:
The system must have an alphabetical list of contents.
* Finding|Searching-navigation:
The reader must quickly and easily find the
entity s/he wants by writing or pronouncing its name. From there s/he
must find easily any other related knowledge. My AAj does SMART
searching, id can search related concepts.
* Asking (Inferring)-navigation:
The program must have the ability
to answer to reader's questions.
- natural-language question answering.
- spoken question answering.
#h0.4.2.1p5#
hSbc:: SBCS's-PRESENTATION:
Description:
knowledge-presentation is the first thing a
reader encounters in any computer-system.
Generic:
* krs-presentation.
Specific:
* Table-of-Contents-presentation:
Reading on a computer screen
is very different from reading a paper book. On a computer we are
loosing the position in the text we are reading. That's why we must
display in the same screen the whole picture of what we are reading.
My AAj presents every sbConcept with ALL its
relations in a tree. From there also the reader can navigate to any
other related entity.
* Natural-Language-presentation:
The program must "know" all natural-languages and must know to
present its knowledge-base in every language.
Logo-translation:
The system must can translate and any other
text/speech to any other language. For example, a user with a
mobile-phone could speak in his/her native language and the phone
will translate the speech in another language
through a server-connection.
Logo-Comparison:
The system must have the ability to COMPARE|analyze
any other text/speech against its stored-knowledge-base.
* Worldview-presentation:
The system must present the different VIEWS that
exist about an entity.
* Evolution-presentation:
The system must have the ability to present
the evolution of an entity AND the evolution of our knowledge about
this entity.
* Abstraction-presentation:
The system must have the ability to present its knowledge in
different LEVELS-OF-ABSTRACTION. Like the zoom-in, zoom-out functions
in the map-software, it should present the same knowledge-area with
more or less details.
#h0.4.2.1p6#
Description:
The program must automate the procedures needed to
build/store its knowledge-base.
#h0.4.2.2p1#
Generic:
* krs-building.
#h0.4.2.2p2#
hSbc:: SBCS's-KNOWLEDGE-ACQUISITION:
Generic:
* krs-acquisition.
Specific:
* Collaboration-acquisition:
Like wikipedia, the power of the system will be the
collaboration of the authors of the system.
But unlike wikipedia the system will prevent the authors from
adding inconsistences AND will help them to add a different
subWorldview on a same subject.
* Automation-acquisition:
Despite the power of author-collaboration, the amount of
information will force us to automate the procedures.
For example, in a future networked-economy the computers of the
companies and households will automatically feed the servers
with new data.
- mechanical learning.
- Sensor-support:
Brain-organisms have sensory-systems to acquire information
in order to create|update|improve their
Brainual-Worldviews.
Today computers have not sensors. In the future they will have.
#h0.4.2.2p3#
hSbc:: SBCS's-KNOWLEDGE-ADDITION:
Generic:
* krs-addition.
Specific:
* Simple-Addition:
The Author must enter the information
in natural-language form (as statements) and not in any kind of
knowledge-representation-language. This way, AUTHOR can be anyone
and NOT an infotech expert.
Speech:
The system must "know" all natural-languages, understand speech
and store knowledge by transforming speech to sensorial-brainual-worldviews.
* Fast-Addition:
The system helps the author when he adds related concepts.
For example, when it adds a specific sbConcept, the program
automatically adds the attributes of its generic.
* Worldview-Addition:
Because information is a REFLECTION of the universe, it is
a SUBJECTIVE entity. Then we don't try to create ONE integrated
worldview but many. But the program must have the ability to find
inconsistencies and contradictions FIRST inside each brainual-worldview and
SECOND among brainual-worldviews.
* Evolution-Addition:
The universe and our knowledge about it both are constantly
EVOLVING. Then the program must have the ability to store and present
its information evolutionarily. It must be able to present its state
of knowledge at every previous time-point.
* Validation-Addition:
We never manage to store coherent, consistent,
integrated information, if the program will have no
REASONING capabilities.
It must guarantee that the stored-knowledge is a CONSISTENT
whole and must find the violations among the relations
of the concepts.
Definition-validation:
- The chains of part, whole, generic, specific, environment
definitions, must not contain current-cpt.
- A specific-start-definition must be accompanied with a
generic-end-definition.
- A generic-start-definition must be accompanied with a
specific-end-definition.
- A part-start-definition must be accompanied with a
whole-end-definition.
- A whole-start-definition must be accompanied with a
part-end-definition.
Generic-validation:
The attributes of
the generic-cpts of the current-cpt must be attributes of the
current-cpt. If not, the program must report and fix the error.
Also, changing the attributes of a generic, the program must change
the attributes and in its specifics.
Specific-validation:
The specific-cpts
must have as attributes the attributes of the current-cpt. Also a
specific of current-cpt must have as generic the current.
Part-validation:
The parts of the current-cpt must have as
whole the current-cpt.
Whole-validation:
The wholes of the current-cpt must have
as parts the current-cpt.
Specific-complement-validation:
Every sb-concept of a
specific-division must have the others in its specific-complement-attribute.
Also the specifics of an sbConcept must form complete-divisions
on an attribute.
Partial-complement-validation:
Every sbConcept of a
partial-division must have the others in its partial-complement-attribute.
Relation-validation:
Creating a relation of the current-cpt
with concept2, the program must create the same relation in concept2
with the current-cpt.
#h0.4.2.2p4#
hSbc:: SBCS's-KNOWLEDGE-CHANGE:
Generic:
* generic: krs-change.
Specific:
* Terminology-change:
Any change in the name of an sbConcept must take effect all over the
system's knowledge-base.
* Validation-change:
The system must detect the affected concepts when we change one AND
must integrate the new with the existing knowledge-base. For example,
adding an attribute in a generic-sbConcept, then the program adds the
new attribute in all its specifics.
* Update-change:
The world always is changing. The system must follow this change.
- automatic update is a goal.
#h0.4.2.2p5#
Specific:
Sensorial-BConcept--Program is a
Knowledge-Representation-Program
that uses sensorial-b-concepts
to represent brainual-worldviews
of many authors.
#h0.5.1p1#
List:
* Knowledge-Representation-Program.
#h0.5.2p1#
Sensorial-b-concept--KnowledgeBase is the information
stored with the program. It is comprised of many
sensorial-b-worldviews.
THE REAL CHALLENGE is NOT the creation of a good
sensorial-b-concept--program,
but the creation of a "good" knowledge-base without ambiguities,
vaguenesses, contradictions, redundancies, holes, that will accurately
reflect the universe.
I foresee to write sensorial-b-concepts as today we write html pages,
and anybody will patent his sensorial-b-concepts.
The creation of multiple but clear views on same entities, and
the standardization of our terms,
will increase the communication among the authors and will help us
to write more accurate knowledge for the good of our society.-
#h0.6.1p1#
EnglishSynonym:
* SBKnowledgebase.
* Sensorial-brainual--knowledge-base.
#h0.6.2p1#
List:
* KnowledgeBase.
#h0.6.3p1#
List:
* XML-KnowledgeBase.
#h0.6.4p1#
A sensorial-b-concept--program uses networks of sensorial-b-concepts (= the analogical, sensorial representation of a b-concept) to represent content (information). #h0.7.1p1#
EnglishSynonym:
* sbcpt-krm.
* Sensorial-b-concept--representation.
* Sensorial-b-concept--krm.
#h0.7.2p1#
List:
* Knowledge-representation-method.
#h0.7.3p1#
The sensorial-b-concept can be created with many means. #h0.8.1p1#
Without the use of computers it is impossible to have a decent system. #h0.9.1p1#
List:
* brainual-info--knowledge-representation-system.
#h0.10p1#
List:
* 1985: PAPER-SBCS.
* 1990: DBASE_IV-SBCS,
* 1992: FolioViews_DOS-SBCS,
* 1994: FolioViews_WIN-SBCS,
* 1997: AAj-SBCS,
* 2007: HTML-SBCS,
#h0.11.1p1#
List:
* COMPUTER-SBCS.
* PAPER-SBCS.
#h0.11.2p1#
hSbc:: COMPUTER-SBCS (SBCCS):
Definition:
It is a
SBConcept-system that uses
computers to manage SBConcepts.
Synonym:
* Sensorial-BConcept--Computer-System.
#h0.11.2p2#
hSbc:: PAPER-SBCS (1985):
Description:
This was my first SBConcept-system.
I had dossiers for main subjects (sciences)
and I had independent paper-sheets for each sensorial-b-concept.
For each sbConcept I also stored quotes about it with the source of the
quote, the date the quote was written and the date the quote was stored.
Apparently, with the expansion of knowledge it was difficult to manage
that knowledge.
#h0.11.2p3#
hSbc:: DBASE-IV-SBCS (1990):
Description:
Working on my paper-system for about 4 years, its limits became
apparent to me. Also I was then confident that only computers could help
us to manage knowledge. So, in 1989, I went to George Washington University
to study computers (information management). In 1990, my first try with
computers was a word processor (word perfect). In a week, it became obvious
that word procesor was not the right tool for me.
The same year, my second try was a relational database program, the
DBASE-IV. I created a complicated system of formalism to store concepts
per author, per date, per source. I spent enough hours on this system
for nothing!!!
#h0.11.2p4#
hSbc:: FolioViews-DOS-SBCS (1992):
Description:
In order to pay my tuitions for the university, I had to work. I was
lucky, because in one of my jobs, where we created electronic-books, we
used the hypertext fulltext-search Folio-Views program.
It was the best program I have met for what I wanted to do. I began to
store sensorial-b-concepts (as with my paper-system) but now the concepts
were linked and I could easily navigate among them and search for
every word I wrote describing the attributes of concepts.
#h0.11.2p5#
hSbc:: FolioViews-WIN-SBCS (1994):
Description:
In 1994 I bought the windows version of FolioViews. With this I have
created a sensorial-b-concept--knowledge-base with thousands of concepts.
The system, is a working one. But in a few years, it was obvious to me
that I had to write my own program to have the functionality I needed
to manage sensorial-b-concepts. So, in 1997 I began my java program,
AAj.
I still use Folio-Views today, and because of it and my experience
with AAj I created my sensorial-b-concept--information-theory.
The quantity of concepts I cleared in my mind was the cause to
further understand and new other concepts and so my
sensorial-b-concept--theory is becoming more clear day after day.
This knowledge-base contains a very important characteristic.
It contains the EVOLUTION of my
sensorial-b-concept--theory
and the evolution of my
Brainual-Worldview.
This happens because when I added an attribute on an sbConcept,
I added and the date I wrote it, at least on the majority of cases.
#h0.11.2p6#
hSbc:: HTML-SBCS (2007-2010):
Description:
In order to present my home-page, a thought came up to use sensorial-b-concepts
and not text to present AAj and my sensorial-b-concept--theory. So from 2007 I began
to write sensorial-b-concepts in html-format.
2010.05.30: I publish my
HtmlMgr that presents
html-files with LocDocs. Since then, I begun to write
html--sensorial-brainual-concepts (h-sbc) with
LocDocs.
Hcpts now, look like the FolioViews-sbcpts.
#h0.11.2p7#
List:
* SENSORIAL--B-CONCEPT--THEORY.
* THE-59-SENSORIAL--B-CONCEPTS,
#h0.12p1#
1985: Paper-System:
The need to manage my knowledge, led me to construct
a paper-system. I had dossiers for concrete sciences
and I had independent paper-sheets for concrete concepts.
Apparently, with the expansion of knowledge it was difficult to manage
that knowledge.
#h0.13p1#
1990: Science-Support-System Paper:
Writting this paper I understood that only a future
computer-system will help us to integrate our knowledge.
#h0.13p2#
1992: Folio-Views-2.1 (DOS):
My first workable computer-system
with this hypertext program.
#h0.13p3#
1994: Folio-Views-3.01 (WIN):
I started a new system with the
windows version of Folio-Views.
My new system, with the thousands of sensorial-b-concepts, proved one thing to me.
We CAN use the "structured-concept" approach to write scientific knowledge.
Also became apparent to me that I had to write my own program.
#h0.13p4#
1997.05.12: AAj
My first java program (just a user interface).
#h0.13p5#
1997.12.21: AAj-XML
My program uses structured-concepts in
XML format, and the aelfred parser to read it.
#h0.13p6#
1999jan:
I updated the program for the jdk1.2.
I've added the 'help' and 'editor' modules.
#h0.13p7#
1999feb:
I've added the INTEGRATION functions.
#h0.13p8#
1999mar:
I've added the 'smart' search facility.
#h0.13p9#
1999apr:
Multiple SensorialKnowledgeBases are supported.
#h0.13p10#
2000jan:
jSBCS searches for the selected-name in the text.
#h0.13p11#
2001.04.18: WordForms Applet
I publish my WordForms-Applet
that finds the terms of logal-concepts given their names.
#h0.13p12#
2002.02.18: GWCreator Applet
I publish my GreekWordCreator-Applet
that demonstrates the word creation mechanism languages use to
create their words.
#h0.13p13#
2010.05.30: HtmlMgr
I publish my HtmlMgr,
that presents html-files with LocDocs.
#h0.13p14#
A user could be a READER (anyone who retrieves knowledge) or an AUTHOR (anyone who stores knowledge). #h0.14.1p1#
File ToC:
⇨ Definition
⇨ Synonym
⇨ Part
⇨ Function
⇨ Retrieval
⇨ Storage
⇨ Program
⇨ KnowledgeBase
⇨ KnowledgeRepresentationMethod
⇨ SensorialBConcept
⇨ Generic
⇨ Specific
⇨ Date-Division
⇨ Computer-Division
⇨ Evolution
#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/krs.html
* PUBLISHED:
* CREATED: 2007.11.29
* MAIL: userid@domain, where userid=nikkas and domain=otenet.gr
#h0.toc#