nikkas-ToC

Home
Information/Knowledge
SCS
definition
the need
scs-functions
structured-concept
user-domain
SCS-Implementations
jSCS
SCS-Evolution
Related Projects
SSS Paper (1990)
sss-toc
Greek-Word
GWCreator Applet
WordForms Applet
Page Evolution

Structured-Concept System (SCS)

DEFINITION:

SCS is a 'Conceptual-Information' Management-System that creates 'integrated-concept-bases' (concepts organized in 3 hierarchies: part-whole, generic-specific and environmental) using STRUCTURED-CONCEPTS to represent a concept. [2001.4.29]
---

THE NEEDS - THE GOAL:

Is there a need to build a SCS? Yes because of the:
** INFORMATION-EXPLOSION: We are witnesses of this phenomenon and of the chaos that generates with the 'infinite' number of books, magazines, newspapers, web-pages etc. We need a system to put an order to this chaos. [2000.06.17]
** NEED FOR COHERENCY/CONSISTENCY: Subjectivity is a property of knowledge. But the more coherent and consistent some knowledge is the more accurate and unambiguous it is. Building knowledge (concept-systems) and not information (statement-systems) it is easier for a computer-system to find its contradictions. Imagine the benefits of unambiguous national or international LAWS.
** NEED FOR STANDARDIZATION: To exchange information among people and machines we need to standardize our concepts (their names/parts etc). Then we will increase our communication.
** NEED FOR RETRIEVING-KNOWLEDGE: Searching for a concept (and not for statements that use a 'name' that denotes many concepts as we do today in internet) shows the benefits of storing knowledge and not information.
** NEED FOR LEARNING-ENHANCEMENT: The time we need to understand a piece of knowledge, not only depends on its complexity but on its representation. We need to increase the productivity of learning and we can do it by storing clear/consistent/coherent conept-systems (knowledge).
The above needs and many more give us a GOAL to make a system that overcomes them.
---

SCS-FUNCTIONS:

Two are the main functions a SCS must have: knowledge-building and knowledge-retrieving.
KNOWLEDGE-RETRIEVING:
** Presentation: knowledge-presentation is the first thing a reader encounters in any computer-system. Reading in 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 jSCS nicely presents an entity (structured-concept) and all its relations in a tree. From there also you can navigate to any other entity.
** Finding: 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 jSCS does SMART searching, id can search related concepts. My folio-views system can easily find the entity I want.
** Asking (Inferring): The system must have the ability to answer to reader's questions.
** Evolution: The system must have the ability to present the evolution of an entity AND the evolution of our knowledge about this entity.
** Views: The system must present the different VIEWS that exist about an entity.
** Globalization: The system must present the knowledge in any natural language.
** Access: It must be an online system (internet) with free access to everyone.
KNOWLEDGE-BUILDING:
The system must automate the procedures needed to build/store knowledge.
** Consistency-Checking: It must guarantee that the stored-knowledge is a consistent whole. That's why I'm following systems-theory approach and every concept (Structured-Concept) is a system with relations to other systems. The system must find the violations among the relations of the structured-concepts.
** Editing/Integrating: 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 general-concept, then the system adds the new attribute to all subgeneral-concepts.
** Simple-Entrance: 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.
** Terminology-Management: Any change in the name of a concept must take effect all over the system's knowledge-base.
and so on...
THE REAL CHALLENGE:
The real challenge is NOT to create a SCS, but the creation of 'SCS CONCEPT-BASES' with the system that have no ambiguities or vacuums and accurately reflect the real world.
I foresee to write structured-concepts as today we write html pages, and anybody will patent his structured-concepts.
Because information is something subjective, we will have many 'scs knowledge-bases' for the same domain/subject, but this will help us to integrate our knowledge because all these constructs will be consistent.
---

STRUCTURED-CONCEPT:

The structured-concept is my knowledge-representation-formalistm. A structured-concept is a CONCEPT with these formal attributes:

1. Synonyms (noun, verb, adjective, adverb, operator, short-name)
2. Definition
3. Part concepts
4. Whole concepts
5. General concepts
6. Subgeneral concepts
7. Environment concepts

I treat the structured-concept as a SYSTEM (in systems-theory terms) with relations to other concepts/systems.
The synonyms/definition/parts are internal attributes and the whole/general/subgeneral/environment are external attributes.
I'm using Information (statements) to describe the attributes of a structured-concept.

---

USER DOMAIN (content):

Anything.