lagHmn'infovido'WITTGENSTEIN

name::
* McsEngl.lagHmn'infovido'WITTGENSTEIN,

Wittgenstein's view in the Tractatus Logico-Philosophicus more or less agreed with Russell that language ought to be reformulated so as to be unambiguous, so as to accurately represent the world, so that we could better deal with the questions of philosophy.
[http://en.wikipedia.org/wiki/Ordinary_language_philosophy]

lagHmn'CONCIOUS'UNCONCIOUS'KNOWING

name::
* McsEngl.lagHmn'CONCIOUS'UNCONCIOUS'KNOWING,

lagHmnlingo'grammar.SYNTHESIS

name::
* McsEngl.lagHmnlingo'grammar.SYNTHESIS,
* McsEngl.conceptCore474.15,

_SPECIFIC:
* CONTENT-WORD--CREATION
   * NAME-WORD--CREATION#cptCore474.8#
   * FORM-WORD--CREATION#cptCore474.7#
* FUNCTION-WORD--CREATION

lagHmnlingo'NAME-WORD-SYNTESIS (namology)

name::
* McsEngl.lagHmnlingo'NAME-WORD-SYNTESIS (namology),
* McsEngl.conceptCore474.8,
* McsEngl.lh'unit'creation,
* McsEngl.lh'word'creation,
* McsEngl.word'creation-of-language@cptCore474.8,
* McsElln.ΔΗΜΙΟΥΡΓΙΚΟ-ΓΛΩΣΣΑΣ,

_DEFINITION:
LANGUAGE-CREATION is the part of GRAMMAR#ql:hl'gramar# that deals with the creation of words.
[hmnSngo.2001-12-02_nikkas]

_SPECIFIC_COMPLEMENT:
* FORMATION#cptCore474.7#

_PART:
* DERIVATING (derivology)#cptCore642.3: attPar#
* compoundation-(compoundology)#cptCore642.4: attPar#
[hmnSngo.2001-12-02_nikkas]

lagHmnlingo'FORM-WORD-SYNTHESIS (formology)

_CREATED: {2003-01-19} {2001-12-03}

name::
* McsEngl.lagHmnlingo'FORM-WORD-SYNTHESIS (formology),
* McsEngl.conceptCore474.7,
* McsEngl.form-word-synthesis,
* McsEngl.formology,
* McsEngl.individual-namero-creation@cptCore474.7,
* McsEngl.lh'word'formation,
* McsEngl.language-formation,
* McsEngl.formation@cptCore474.7,
* McsEngl.word-formation@cptCore474.7,
* McsElln.ΔΗΜΙΟΥΡΓΙΑ-ΤΥΠΩΝ-ΛΕΞΕΩΝ,

_DEFINITION:
LANGUAGE-FORMATION is the part of GRAMAR#ql:hl'gramar# that deals with the creation of word forms (types).
[hmnSngo.2001-12-02_nikkas]

FORM-WORD#cptCore453.16#

FORMATION-SUFFIX#cptCore59.16#

lagHmnlingo'SYNTACTIC'SYNTHESIS (CREATION)

_CREATED: {2003-11-28}

name::
* McsEngl.lagHmnlingo'SYNTACTIC'SYNTHESIS (CREATION),
* McsEngl.conceptCore474.13,

_DEFINITION:
* SYNTACTIC-SYNTHESIS is the process of first and second logo-hierarchy creation.
[hmnSngo.2003-11-28_nikkas]

* The process of LOGO#cptCore474# creation from semantic-words#cptCore449#.
[hmnSngo.2003-01-19_nikkas]

lagHmnlingo'EKSPRESERO'DUDINO

name::
* McsEngl.lagHmnlingo'EKSPRESERO'DUDINO,
* McsEngl.conceptCore474.4,
* McsEngl.grammar-as-word-creation-formation@cptCore474.4,
* McsElln.ΓΡΑΜΑΤΙΚΗ,

=== _NOTES: grammar is a word that is used also as synonym to "logation". I could use the word "creatax".
[hknu@cptCore2003-07-15_nikkas]

_DEFINITION:
* GRAMAR is the part of LOGATION#ql:hl'logation# that deals with word-creation and word-formation.
[hmnSngo.2001-12-02_nikkas]

* GRAMMAR I call the rules a hl uses to create WORD-FORMS and DERIVED-WORDS.
[hmnSngo.2001-11-17_nikkas]

_WHOLE:
* LOGATION#cptCore474.3#

PARTIAL-COMPLEMENT:
* SYNTAX#cptCore474.2#

_PARTS:
- creation (creatology)
- derivation (derivology)
- compoundation (compoundology)
- FORMATION (formology)
[hmnSngo.2001-12-02_nikkas]

τυπικό|τυπολογικό|κλητικό σύστημα

The two main branches of morphology are inflectional and derivational morphology, which deal with different uses to which morphological structures are put: distinguishing inflections and lexemes respectively. E.g. in baby-sitters, the affix -s is inflectional because it distinguishes the plural inflection, while -er is derivational, because it distinguishes the lexeme BABY-SITTER from BABY-SIT, and the combination of roots baby and sit is also handled by derivational morphology because it relates this lexeme to two simpler lexemes, BABY and SIT.
[wg enc, 1998.12]

http.GRAMMAR:
* http://angli02.kgw.tu-berlin.de/call/webofdic/grammars.html: http://angli02.kgw.tu-berlin.de/call/webofdic/grammars.html

lagHmnlingo'SYNTAX'DUDINO

name::
* McsEngl.lagHmnlingo'SYNTAX'DUDINO,
* McsEngl.conceptCore474.2,
* McsEngl.hl'syntax,
* McsEngl.syntactic'relation@cptCore474.2,
* McsEngl.relation.syntactic@cptCore474.2,
* McsEngl.language's'syntax@cptCore474.2,
* McsEngl.SYNTAX,
* McsEngl.syntax-of-mdlogero@cptCore474.2,
* McsElln.ΣΥΝΤΑΚΤΙΚΟ-ΓΛΩΣΣΑΣ,
* McsElln.ΣΥΝΤΑΚΤΙΚΟ@cptCore474.2,
* McsElln.ΣΥΝΤΑΞΗ,

_GENERIC:
* lingoHmn-syntax

_DEFINITION:
SYNTAX= the node (content and token) structure of a model-logo.
[hmnSngo.2006-01-15_nikkas]

SYNTAX= the content-node identification. SYNTACTIC-ANALYSIS is the process of syntax identification.
[hmnSngo.2006-01-04_nikkas]

* Syntactic-Relation is any LANGUAGE-RELATION, PART of logo, responsible for the arrangment of expressions#cptCore35#.
[hmnSngo.2002-08-15_nikkas]

* SYNTAX is the rules of expression predicate-relations and statemental-relations.
[hmnSngo.2002-05-31_nikkas]

SYNTAX is the part of LOGATION#ql:hl'logation# that deals with the relations of logo creation.
[hmnSngo.2001-12-02_nikkas]

ΣΥΝΤΑΚΤΙΚΟ ΓΛΩΣΣΑΣ είναι οι ΣΧΕΣΕΙΣ των αντικειμένων γλώσσας#cptCore93.a#.
[hmnSngo.1995.04_nikos]

"A presents B with C" equals "A presents C to B" is syntactic information.
[hmnSngo.1998-08-13_nikos]

ΚΑΝΟΝΑΣ = ΔΙΑΔΙΚΑΣΙΑ = RULE
[hmnSngo.1995.04_nikos]

Let us first consider syntax which refers to the relationship that words bear to each other in a sentence. Several aspects of this grammatical structure are well-captured using statistical methods.
The simplest useful way of thinking about syntax is to define it as word order constraint. That is, only certain words can follow certain other words.
[http://www.cse.ogi.edu/CSLU/HLTsurvey/, 1996, 11.2.6]

"ΣΥΝ-ΤΑΞΗ, ΟΠΩΣ ΔΗΛΩΝΕΙ ΚΑΙ Η ΕΤΥΜΟΛΟΓΙΑ, ΕΙΝΑΙ ΚΑΤΑΡΧΗ Η ΣΕΙΡΑ ΠΟΥ ΜΠΑΙΝΟΥΝ ΟΙ ΛΕΞΕΙΣ Η ΜΙΑ ΠΛΑΙ ΣΤΗΝ ΑΛΛΗ. Η ΣΕΙΡΑ ΚΑΘΟΡΙΖΕΤΑΙ ΑΠΟ ΠΕΡΙΠΛΟΚΟΟΥΣ ΚΑΝΟΝΕΣ, ΠΟΥ ΑΚΟΛΟΥΘΟΥΝ ΒΕΒΑΙΑ ΓΕΝΙΚΕΣ ΑΡΧΕΣ ΠΟΥ ΙΣΧΥΟΥΝ ΓΙΑ ΟΛΕΣ ΤΙΣ ΓΛΩΣΣΕΣ, ΔΙΑΦΕΡΟΥΝ ΟΜΩΣ ΣΤΗΝ ΕΠΙΜΕΡΟΥΣ ΕΦΑΡΜΟΓΗ-ΤΟΥΣ ΑΠΟ ΓΛΩΣΣΑ ΣΕ ΓΛΩΣΣΑ"
[ΠΕΤΡΟΥΝΙΑΣ, 1984, 65#cptResource191#]

"SYNTAX is the grammatical structure of sentences. Recovering the syntax of a sentence is called parsing"
[Tanimoto, 1990, 356#cptResource461#]

"ΤΟ ΣΥΝΤΑΚΤΙΚΟ ΕΞΕΤΑΖΕΙ ΤΟΥΣ ΚΑΝΟΝΕΣ ΣΥΜΦΩΝΑ ΜΕ ΤΟΥΣ ΟΠΟΙΟΥΣ ΟΙ ΛΕΞΕΙΣ ΣΥΝΤΑΣΣΟΝΤΑΙ ΜΕΣΑ ΣΤΗΝ ΠΡΟΤΑΣΗ"
[Close et al, 1982, 6#cptResource338#]

"SURFACE-STRUCTURE" is the name for "logo-structure" other use. "DEEP-STRUCTURE" is the "info-tech structure". The names they use shows confusion in these entities.
[hmnSngo.2001-12-04_nikkas]

_WHOLE:
* LOGO-RELATION#cptCore474.3#

PARTIAL-COMPLEMENT:
* GRAMMAR#cptCore474.4#

_SENTENCE:
"ΟΠΩΣ Η ΛΕΞΗ, ΠΑΡΟΛΟ ΠΟΥ ΔΕ ΛΕΓΕΤΑΙ ΜΟΝΗ-ΤΗΣ, ΑΠΟΤΕΛΕΙ ΤΗ ΒΑΣΙΚΗ ΔΟΜΗ ΤΗΣ ΛΕΞΙΛΟΓΙΚΗΣ ΑΝΑΛΥΣΗΣ, ΕΤΣΙ ΚΑΙ Η ΠΡΟΤΑΣΗ ΑΠΟΤΕΛΕΙ ΤΗ ΒΑΣΙΚΗ ΔΟΜΗ ΤΗΣ ΣΥΝΤΑΧΤΙΚΗΣ ΑΝΑΛΥΣΗΣ".
[ΠΕΤΡΟΥΝΙΑΣ, 1984, 152#cptResource191#]

VERB SYNTAX:
Every verb (which a language uses to express a 'relation') has its OWN syntax in every language, eg: in ancient-greek uses cases to express the predicatals of the relation, in greek uses operators and in english uses similar or different operators.
We MUST know this different syntax for every relation or group of relations, on every language in order to translate from one logo to another.
· _stxEngl: _stxSbj:he _stxVrb:{died} _stxArg:from starvation.
· _stxElln: _stxVrb:πέθανε _stxArg:από λιμό.
_stxElla: _stxArg:Λιμῷ _stxVrb:ἀπέθανον.
[hmnSngo.2001-11-08_nikkas]

_SPECIFIC:
* SYNTACTIC-ANALYSIS (PARSING)#cptCore474.6#
* SYNTACTIC-SYNTHESIS (CREATION)#cptCore474.13#

nmhCbn'DEFINITION

_DESCRIPTION:
Because every koncepto#cptCore383# is part of a brainepto_base#ql:brainepto_base@cptCore*# (atomic or social), dezignepteros are all the "terms" this BB uses in all human languages for this koncepto AND NOT the terms use other BBs for the same koncepo.
Also, because terms change, we must know the terms used for a koncepto in all BBs, in all languages, at any time!!!! if we want to have real communication.
[hmnSngo.2007-11-27_KasNik]

nmhCbn'GENERIC

_GENERIC:
* name.human#cptCore93.42#
* lingo-human-semasio-unit#cptCore473#

nmhCbn'WHOLE

_WHOLE:
* concept.human.brain#cptCore66#
* Dezigneptero is part of a konsepto.
[hmnSngo.2007-09-23_nikkas]

nmhCbn'WholeNo-relation#cptCore546.15#

name::
* McsEngl.nmhCbn'WholeNo-relation,

There is a rich, many-to-many mapping between terms (names, words, and phrases) and concepts (things and ideas).
A single thing or idea can be expressed by synonymous terms or phrases, or known by multiple names, including variations, abbreviations, acronyms, nicknames and aliases.
Conversely, the same word, name, or phrase can represent different things, people, or ideas. This is a problem in information retrieval because text-based retrieval fails to differentiate between multiple senses of a term. Ranking search results is not a solution for finding resources related to a specific sense of a word. A similar problem occurs in social tagging, where users select natural language terms to describe items such as photographs and documents. Research has observed that, on average, people have less than 20% chance of choosing the same word to describe the same concept [1].
1. Furnas, G.W., et al. The Vocabulary Problem in Human-System Communication, Communications of the ACM, 30 (1987) 964-971
[Mining a Large-Scale Term-Concept Network from Wikipedia
Andrew Gregorowicz and Mark A. Kramer
http://www.mitre.org/work/tech_papers/tech_papers_06/06_1028/index.html
http://www.mitrecorporation.net/work/tech_papers/tech_papers_06/06_1028/06_1028.pdf]

nmhCbn'convention

_CREATED: {2012-10-29}

name::
* McsEngl.nmhCbn'convention,
* McsEngl.naming-convention, {2012-10-29}

_DESCRIPTION:
A naming convention is an attempt to systematize names in a field so they unambiguously convey similar information in a similar manner.
[http://en.wikipedia.org/wiki/Name]

nmhCbn'onomatology

name::
* McsEngl.nmhCbn'onomatology,

nmhCbn'structure#cptCore515#

name::
* McsEngl.nmhCbn'structure,

* PRICIPO-YORDERO OF DEZIGNEPTERO
* SEKONDO-YORDERO OF DEZIGNEPTERO

nmhCbn'Toponymy#cptCore678.11#

name::
* McsEngl.nmhCbn'Toponymy,

SPECIFIC

name::
* McsEngl.nmhCbn.specific,
* McsEngl.nameCbh.SPECIFIC#cptCore546.23#,

_SPECIFIC: nameCbh.alphabetically:
* nameCbh.conceptgram#cptCore78.31#ql:cptoldepistem384.12##
* nameCbh.language#cptCore384.7#
* nameCbh.term#cptCore50.29.2#
* nameCbh.termNo#cptCore50.29.3#
* nameCbh.unique#cptCore50.29.6#
* nameCbh.uniqueNo#cptCore50.29.7#
* nameCbh.worldview#cptCore384.10#

nmhCbn.SPECIFIC-DIVISION.term

name::
* McsEngl.nmhCbn.SPECIFIC-DIVISION.term,

_SPECIFIC:
* nameCbh.term#cptCore50.29.2#
* nameCbh.termNo#cptCore50.29.3#
[2008-10-02,]

nmhCbn.SPECIFIC-DIVISION.usage

_CREATED: {2008-10-02}

name::
* McsEngl.nmhCbn.SPECIFIC-DIVISION.usage,

_SPECIFIC:
* nameCbh.name.main#cptCore50.29.5#
* nameCbh.name.secondary#cptCore50.29.4#
===
* NAME_OF_CONCEPT#cptCore384.2#
* TERM_OF_CONCEPT#cptCore384.8#
===
* NAME_TERM_OF_CONCEPT#cptCore384.2#
* NONNAME_TERM_OF_CONCEPT#cptCore384.8#

nmhCbn.SPECIFIC-DIVISION.uniquness

name::
* McsEngl.nmhCbn.SPECIFIC-DIVISION.uniquness,

_SPECIFIC:
* nameCbh.unique#cptCore50.29.6#
* nameCbh.uniqueNo#cptCore50.29.7#
[hmnSngo.2012-08-30]

nmhCbn.SPECIFIC-DIVISION.L-CONCEPT

_CREATED: {2008-03-18}

name::
* McsEngl.nmhCbn.SPECIFIC-DIVISION.L-CONCEPT,

* TERM _CPT_NOUN:
 * TERM _CPT_ORDINARY_NOUN
 * TERM _CPT_CONJUNCTIVE_NOUN
   * TERM _CPT_ADJECTIVE
   * TERM _CPT_ADVERB
 * TERM _CPT_SPECIAL_NOUN
* TERM_CPT_VERB
* TERM _CPT_CONJUNCTION

* auxiliaryNo_of_nameSmsTerm#cptCore453.15#

* NAMERO_ONOMERO:
 * NAMERO_NOUNERO
 * NAMERO_NOUNODEANERO
 * NAMERO_SPECIALERO
 * NAMERO_ADNOUNERO
 * NAMERO_ADVERBERO
* NAMERO_VERBERO
* NAMERO_DEANERO

nmhCbn.SPECIFIC-DIVISION.language

_CREATED: {2008-02-02}

name::
* McsEngl.nmhCbn.SPECIFIC-DIVISION.language,

_SPECIFIC:
* nameCbh.lango#cptCore50.29.8#
* nameCbh.lango.english
* nameCbh.lango.esperanto
* nameCbh.lango.greek
* nameCbh.lango.langoko

nmhCbn.SPECIFIC-DIVISION.WORLDVIEW

_CREATED: {2008-02-02}

name::
* McsEngl.nmhCbn.SPECIFIC-DIVISION.WORLDVIEW,

* TERM _CPT_KasNik

nmhCbn.SPECIFIC_DIVISION.NAMEPTERO

_CREATED: {2008-02-02} _DELETED{2008-03-20}

* NAMERO#cptCore384.2#
* ATRIBERO#cptCore384.1#

nmhCbn.SPECIFIC_DIVISION.GENEREPO

_CREATED: {2008-03}

* NameroGenerepo#cptCore384.9#
* NameroIndividepo#cptCore384.8#

nmhCbn.ABBREVIATION#ql:abbreviation.conceptbrain#

name::
* McsEngl.nmhCbn.ABBREVIATION,

nmhCbn.HYPOCORISTIC

name::
* McsEngl.nmhCbn.HYPOCORISTIC,
* McsEngl.hypocoristic@cptCore384i,
* McsEngl.hypocorism@cptCore384i,

A hypocoristic (or hypocorism) is a lesser form of the given name used in more intimate situations, as a term of endearment, a pet name.
[http://en.wikipedia.org/wiki/Hypocoristic]

nmhCbn.LANGUAGE

_CREATED: {2008-03-24}

name::
* McsEngl.nmhCbn.LANGUAGE,
* McsEngl.conceptCore50.29.8,
* McsEngl.conceptCore384.7,
* McsEngl.language-term-of-concept@cptCore384.7, {2008-10-02}
* McsEngl.namero-of-language@cptCore384.7, {2008-09-27}
* McsEngl.language-namero@cptCore384.7, {2008-03-24}
====== lagoSINAGO:
* McsEngl.nameroLango@lagoSngo, {2008-03-24}

_DEFINITION:
NameroLango is any namero of a koncepo in ONE language.
[hmnSngo.2008-03-24_HokoYono]

WHOLE:
* NameroLango_Set: is all the nameroLangos of a koncepo in ONE language.
[hmnSngo.2008-03-27_HokoYono]

_SPECIFIC:
* one nameroLango has instances the first-namero and its nonfirst-nameros.

nmhCbn.MAIN (most-used)

_CREATED: {2003-03-13} {1998-06-29}

name::
* McsEngl.nmhCbn.MAIN (most-used),
* McsEngl.conceptCore50.29.5,
* McsEngl.conceptCore384.2,
* McsEngl.brnHcpt'name@cptCore66.5, {2012-09-03}
* McsEngl.nameBrnHcpt@cptCore66.5, {2012-08-30}
* McsEngl.nameHcBrn.main@cptCore66.5, {2012-10-28}
* McsEngl.name-term-of-concept@cptCore384.2, {2008-10-02}
* McsEngl.concept's-name,
* McsEngl.name-of-concept@cptCore383.1,
* McsEngl.name-of-cpt@cptCore383.1,
* McsEngl.name@cptCore66.5, {2012-10-28}
* McsEngl.term,
* McsEngl.conceptCore384.1@deleted,
====== lagoSINAGO:
* McsEngl.foEkoKoncosNamo@lagoSngo, {2008-09-28}
* McsEngl.namepo@lagoSngo, {2008-03-18}
* McsEngl.namepero@lagoSngo, {2008-03-17}
* McsEngl.nameptero@lagoSngo, {2008-02-02}
* McsEngl.nameptero@lagoSngo, {2006-06-17}
====== lagoGreek:
* McsElln.ΟΝΟΜΑ-ΕΝΝΟΙΑΣ@cptCore383.1,
* McsElln.όνομα-έννοιας,
=== old,
* McsEngl.concept'expression@cptCore383.1,
* McsElln.ΟΡΟΣ@deleted,

=== _NOTES: A term is a word, or more than one word, that names a concept.
[Kavanagh, Text Analyzer] 1998-07-17

_DEFINITION:
It is the MOST USED dezignator.
[hmnSngo.2012-08-30]
===
* NAMEPTERO is any entity a language uses to refer to a concept without expressing any attribute of it (as with verberos, adnouneros, cases etc).
[hmnSngo.2006-11-12_nikkas]

* NAMEPTERO-OF-KONSEPTO is the nameros#cptCore494# of its nouneros#cptCore549# and any abrevieptero, akronimemptero, formaleptero, relativeptero and simboleptero we use for this konsepto.
[hmnSngo.2006-08-05_nikkas]

* NAME-OF-CONCEPT is the namer of its abjecter.
[hmnSngo.2003-11-23_nikkas]

* NAME-OF-CONCEPT is the name of its noun.
[hmnSngo.2003-11-23_nikkas]

* A concept has only name, all other expression are corelated with a di-concept.
[hmnSngo.2003-03-13_nikkas]

* The name of a concept is the nominative of the its most used noun. Every language has a mechanism that produces names. That's why information and language goes hand with hand.
[hmnSngo.2003-03-13_nikkas]

NAME of a concept I call the most used NOUN.
[hmnSngo.2001]

(the most used word of ONE noun/verb...)

NAME is the most used CONTENT-WORD of a CONCEPT#cptCore383# (meaning units).
[hmnSngo.nikkas_2000-09-05_nikkas]

NAME (CONCEPT NAME) is the WORD of a CONCEPT.
[hmnSngo.1998-08-29_nikos]

_WHOLE:
* sympan'socHmn'setLingoHmn'lingoHmn'nameLingo#cptCore453#
* sympan'socHmn'setLingoHmn'lingoHmn#cptCore93.28#
* sympan'socHmn'setLingoHmn#cptCore93.17#
* sympan'socHmn#cptCore1#

_SYNTAX:
· _stxEngl: he learned many medical terms. [WordNet]

_DOING:
* NAME CREATING

_SPECIFIC:
* NAMEPTERO-MOST-USED
* NAME ABSOLUTE= one worder
* NAME RELATIVE= part of a concepter-structure

nmhCbn.MAIN.NO

name::
* McsEngl.nmhCbn.MAIN.NO,
* McsEngl.conceptCore50.29.4,
* McsEngl.alias@cptCore384i,
* McsEngl.nameHcBrn.secondary@cptCore66.4, {2012-10-29}
* McsEngl.non-name-dezignator-of-brnHcpt@cptCore66.4, {2012-08-30}
* McsEngl.pseudonym@cptCore384i,
* McsEngl.secondary-human-brainname@cptCore66.4, {2012-11-05}

_DEFINITION:
* A pseudonym (Greek: ψευδόνυμον, pseudo + -onym: false name) is an artificial, fictitious name, also known as an alias, used by an individual as an alternative to a person's legal name.
[http://en.wikipedia.org/wiki/Pseudonym] 2007-09-30

* An alias is a pseudonym and may also refer to: ...
[http://en.wikipedia.org/wiki/Alias] 2007-09-30

alias    
 1   alias; aliases
  An alias is a false name, especially one used by a criminal.
   Using an alias, he had rented a house in Fleet, Hampshire.
  N-COUNT
 2   alias
  You use alias when you are mentioning another name that someone, especially a criminal or an actor, is known by.
   Richard Thorp, alias Alan Turner, said yesterday: `It is a sad time for both of us.'
  PREP: n-proper PREP n-proper
 (c) HarperCollins Publishers.

nmhCbn.NICKNAME

name::
* McsEngl.nmhCbn.NICKNAME,
* McsEngl.nickname@cptCore384i,

_DEFINITION:
* A nickname is a name of a person or thing other than its proper name. It may either substitute or be added to the proper name. It may be a familiar or truncated form of the proper name, such as Bob, Bobby, Rob, Robbie, Robin, and Bert for Robert.
[http://en.wikipedia.org/wiki/Nickname] 2007-09-30

nickname    
 1   nickname; nicknames
  A nickname is an informal name for someone or something.
   Red got his nickname for his red hair.
  N-COUNT
 
 2   nickname; nicknames; nicknaming; nicknamed
  If you nickname someone or something, you give them an informal name.
   When he got older I nicknamed him Little Alf.
   Which newspaper was once nicknamed The Thunderer?
  VB
 
(c) HarperCollins Publishers.

nmhCbn.nomenclature.BIOLOGICAL#cptCore72.2#

name::
* McsEngl.nmhCbn.nomenclature.BIOLOGICAL,

nmhCbn.nomenclature.CHEMICAL#cptCore942.5#

name::
* McsEngl.nmhCbn.nomenclature.CHEMICAL,

nmhCbn.nomenclature.PLANETARY

name::
* McsEngl.nmhCbn.nomenclature.PLANETARY,

Planetary nomenclature, like terrestrial nomenclature, is a system of uniquely identifying features on the surface of a planet or natural satellite so that the features can be easily located, described, and discussed. The task of assigning official names to features is taken up by the International Astronomical Union since its founding in 1919. [1]
[http://en.wikipedia.org/wiki/Planetary_nomenclature]

nmhCbn.nomenclature.TERRESTRIAL

name::
* McsEngl.nmhCbn.nomenclature.TERRESTRIAL,

nmhCbn.PICTOGRAPH

name::
* McsEngl.nmhCbn.PICTOGRAPH,
* McsEngl.conceptCore384.12,
* McsEngl.pictograph@cptCore384i,

nmhCbn.PORTMANTEAU

name::
* McsEngl.nmhCbn.PORTMANTEAU,
* McsEngl.portmanteau@cptCore384i,

_DEFINITION:
A portmanteau (IPA pronunciation: /p??t?m?nt??/ RP, /p??rt?m?nto?/ US) is a word or morpheme that fuses two or more words or word parts to give a combined or loaded meaning. A folk usage of portmanteau refers to a word formed by combining both sounds and meanings from two or more words (e.g., spork from spoon and fork, animatronics from animation and electronics, ginormous from gigantic and enormous, or blaxploitation from black and exploitation). Typically, portmanteaux are nonce words or neologisms - in recent years, the practice of creating them has become known as "smushing" or "smooshing", and can often be seen playing an active minor role in some online media discussion. Portmanteaux are commonly used in scientific literature for a wide variety of technical words, such as cyborg from cybernetic and organism.
[http://en.wikipedia.org/wiki/Portmanteau]

nmhCbn.PROPER-NAME

_CREATED: {2012-10-28}

name::
* McsEngl.nmhCbn.PROPER-NAME,
* McsEngl.proper-name,

_DESCRIPTION:
A proper noun is a noun that in its primary application refers to a unique entity, such as London, Jupiter, Sarah, or Microsoft, as distinguished from a common noun, which usually refers to a class of entities (cities, planets, persons, corporations), or non-unique instances of a certain class (a city, another planet, these persons, our corporation).[1] Some proper nouns occur in plural form (optionally or exclusively), and then they refer to groups of entities considered as unique (the Hendersons, The Azores, the Pleiades). Proper nouns can also occur in secondary applications, for example modifying nouns (the Mozart experience; his Azores adventure), or in the role of common nouns (he's no Pavarotti; a few would-be Napoleons). The detailed definition of the term is problematic and to an extent governed by convention.[2]
A distinction is normally made in current linguistics between proper nouns and proper names. By this strict distinction, because the term noun is used for a class of single words (tree, beauty), only single-word proper names are proper nouns: Peter and Africa are both proper names and proper nouns; but Peter the Great and South Africa, while they are proper names, are not proper nouns.
[http://en.wikipedia.org/wiki/Proper_name] {2012-10-28}

nmhCbn.RELATIVE

_CREATED: {2012-10-31}

name::
* McsEngl.nmhCbn.RELATIVE,
* McsEngl.conceptCore50.29.16,
* McsEngl.relative-name-of-hmn-cpt-brain@cptCore66.16, {2012-10-31}
====== lagoGreek:
* McsElln.σxετικό-όνομα@cptCore66.16, {2012-10-31}

_DESCRIPTION:
* it is a name of a brain-concept, RELATIVE to the context it is expressed. Usually names with more than one word are shorted in a specific text for economy reasons. For example instead of human-brain-concept-name I use brain-name.
[hmnSngo.2012-10-31]

nmhCbn.SYNSET

name::
* McsEngl.nmhCbn.SYNSET,
* McsEngl.conceptCore50.29.14,
* McsEngl.synonymset@cptCore93i,
* McsEngl.synset@cptCore93.i,

_DESCRIPTION:
For each koncepto, the language denotes, we must know all the dezignepteros in all brainepto-bases the language describes, that denote this same koncepto.
[hmnSngo.2007-12-12_KasNik]

nmhCbn.TERM

_CREATED: {2008-03-30}

name::
* McsEngl.nmhCbn.TERM,
* McsEngl.conceptCore50.29.2,
* McsEngl.conceptCore384.8,
* McsEngl.termBrnHmnCpt@cptCore66.2, {2012-09-03}
* McsEngl.termCptHmnBrn@cptCore384.8,
* McsEngl.term-of-brainoHmnConcept@cptCore66.2, {2012-08-30}
* McsEngl.term-of-concept@cptCore384.8, {2008-10-19}
* McsEngl.nonname-term-of-concept@cptCore384.8, {2008-10-02}
* McsEngl.term-of-logal-concept@cptCore384.8, {2008-09-28}
* McsEngl.individual-namero@cptCore384.8,
====== lagoSINAGO:
* McsEngl.foEtoKoncosTermo@lagoSngo, {2008-09-28}
* McsEngl.nameroIndividepo@lagoSngo, {2008-03-30}

_DEFINITION:
* Term of concept is any construction a language uses to denote a concept created from its dikteros#cptCore577#.
[hmnSngo.2009-01-11]
===
Term = designator - name.
[2008-10-19]
===
NameroIndividepo is an individepo namero of a koncero.
[hmnSngo.2008-03-30_HokoYono]

nmhCbn.TERM.NO

_CREATED: {2009-01-11}

name::
* McsEngl.nmhCbn.TERM.NO,
* McsEngl.conceptCore50.29.3,
* McsEngl.conceptCore384.11,
* McsEngl.non-term-of-concept@cptCore384.11,

_DEFINITION:
It is any designator_of_concept, which is not term, such as symbols.
"Names" are and terms (=nouns) and non_terms.
[hmnSngo.2009-01-11]

_SPECIFIC:
* NON_TERM_NAME
* NON_TERM_SYMBOL

nmhCbn.TERM-OF-ENDEARMENT

name::
* McsEngl.nmhCbn.TERM-OF-ENDEARMENT,
* McsEngl.term-of-endearment@cptCore384i,

A term of endearment is a word or phrase used to address and/or describe a person or animal for which the speaker feels affection.
Terms of endearment are used for a variety of reasons, ranging from parents addressing their children, to lovers whispering sweet nothings to each other.
[http://en.wikipedia.org/wiki/Term_of_endearment] 2007-09-30

nmhCbn.UNIQUE

name::
* McsEngl.nmhCbn.UNIQUE,
* McsEngl.conceptCore50.29.6,
* McsEngl.conceptCore384.4,
* McsEngl.identifier,
* McsEngl.identifier-of-koncepo@cptCore384.4,
* McsEngl.idfier-of-koncepo@cptCore384.4,
* McsEngl.koncepo'identifier@cptCore384.4,
* McsEngl.koncepo'idfier@cptCore384.4,
* McsEngl.unique'namero@cptCore384.4, {2008-03-20}
====== lagoEsperanto:
* McsEngl.unika'nomo@cptCore384.4@lagoEspo,
* McsEspo.unika'nomo@cptCore384.4,
====== lagoSINAGO:
* McsEngl.namoYunikero@lagoSngo, {2008-03-22}
* McsEngl.namo-yunikero@lagoSngo, {2008-03-20}
* McsEngl.identigo@lagoSngo,
* McsEngl.identifeptero@lagoSngo,

_DEFINITION:
* IDENTIFEPTERO is a dezigneptero that UNIQUELY identifies a konsepto.
[hmnSngo.2006-06-18_nikkas]

* IDENTIGO is a DEZIGNATO that uniquely identifies the akpt.
[hmnSngo.2006-01-29_nikkas]

* SC's DESIGNATER is a UNIQUE designater that identifies it.
[hmnSngo.2004-09-27_nikkas]

_SPECIFIC:
* knsa.aa.identifier,

nmhCbn.UNIQUE.NO

_CREATED: {2012-08-30}

name::
* McsEngl.conceptCore50.29.7,
* McsEngl.non-unique-dezignator-of-brnHcpt66.7, {2012-08-30}

_DEFINITION:
It is a dezignator which is NOT unique per context, language, author, book, lingo.
[hmnSngo.2012-08-30]

nmhCbn.WORLDVIEW

_CREATED: {2008-10-02}

name::
* McsEngl.conceptCore384.10,
* McsEngl.worldview-term-of-concept@cptCore384.10, {2008-10-02}

_DEFINITION:
it is any term_of_concept in ONE worldview in any language.
[hmnSngo.2008-03-24_HokoYono]

nmhCbn.ATRIBEPERO

_CREATED: {2008-02-02}

name::
* McsEngl.conceptCore384.1,
* McsEngl.conceptCore384.1,
* McsEngl.atribepero@cptCore384.1,
* McsEngl.atribeptero@cptCore384.1,

_DEFINITION:
Atribeptero is the nonimeros (nameros or formeros) a language uses to refer to a concept by expressing AND an attribute of it (such as in verberos, adnouneros, cases etc).
[hmnSngo.2008-02-02_nikkas]

_SPECIFIC_COMPLEMENT:
* NAMEPTERO

_EVOLUTING:
* {2008-03-20} DELETED.

nmhCbn.GENEREPO

_CREATED: {2008-03-30}

It is same with name-of-concept.
[2008-10-02]

name::
* McsEngl.conceptCore384.9,
* McsEngl.general-namero@cptCore384.9,
====== lagoSINAGO:
* McsEngl.nameroGenerepo@lagoSngo, {2008-03-30}
* McsSngo.nameroGenerepo@cptCore384.9, {2008-03-30}

_DEFINITION:
* This koncepo is IDENTICAL with first-termCp#cptCore494old#t.
[hmnSngo.2008-04-13_HokoYono]

NameroGenerepo is a generepo namero of a koncero.
[hmnSngo.2008-03-30_HokoYono]

nmhCbn.NOUNEPTERO

_CREATED: {2008-02-04}

name::
* McsEngl.conceptCore384.3,
* McsEngl.nouneptero@cptCore384.3,

_DEFINITION:
Nouneptero is the nameros of its nouneros.
[hmnSngo.2008-02-04_KasNik]

_EVOLUANO:
* {2008-03-20} DELETED.

SPECIFIC

name::
* McsEngl.idxBrnHcpt.specific,

idxBrnHcpt.TECHNICAL-TERMINOLOGY#attOth#

name::
* McsEngl.idxBrnHcpt.TECHNICAL-TERMINOLOGY,

Technical terminology is the specialized vocabulary of any field, not just technical fields. The same is true of the synonyms technical terms, terms of art, shop talk and words of art, which do not necessarily refer to technology or art.[1][2][3] Within one or more fields, these terms have one or more specific meanings that are not necessarily the same as those in common use. Jargon is similar, but more informal in definition and use. Legal technical terms, often called (legal) terms of art or (legal) words of art, have meanings that are strictly defined by law.
[http://en.wikipedia.org/wiki/Technical_terminology]

DEFINITION

_DESCRIPTION:
KATEGORY is the-most-generic with a-concrete-attribute.
[hmnSngo.2015-05-18]
===
CATEGORY is the ROOT-CONCEPT of a generic-specific-structure.
[hknm2012-08-31]

CATEGORY is any concept created with ending-synthetic-definition or starting-analytic-definition.
[hmnSngo.2009-01-11]

KATEGORO is any konsepto with jenereino only the entepto.
[hmnSngo.2007-10-27_KasNik]

ΚΑΤΗΓΟΡΙΑ είναι η [ΓΕΝΙΚΗ]-ΕΝΝΟΙΑ που δε μπορεί να ΓΕΝΙΚΕΥΤΕΙ άλλο.
[hmnSngo.1995.04_nikos]

A category is defined on a number of individuals.
[hmnSngo.2001-01-29_nikkas]

ΚΑΤΗΓΟΡΙΑ λέγεται η έννοια που στο χαρακτηριστικο "GENERAL CONCEPT(374)" έχει τιμη NONE(374-1)
[hmnSngo.1994-09-16_nikos]

CATEGORY/ΚΑΤΗΓΟΡΙΑ είναι ΕΝΝΟΙΑ ΠΟΥ ΔΕΝ ΜΠΟΡΕΙ ΝΑ ΓΕΝΙΚΕΥΤΕΙ ΑΛΛΟ. ΑΡΑ ΕΙΝΑΙ ΦΙΛΟΣΟΦΙΚΕΣ ΕΝΝΟΙΕΣ.
[hmnSngo.1993.11_nikos]

wholeNo-relation#cptCore546.15#

* leaf_concept#cptCore383.27#

SPECIFIC

* INFO#cptCore181#
* PART_CATEGORY = WHOLE_CATEGORY
* SPECIFIC_CATEGORY = GENERIC_CATEGORY

ROOT.GENERIC (category)

_CREATED: {2012-08-31}

name::
* McsEngl.ROOT.GENERIC (category),
* McsEngl.conceptCore50.29.12,
* McsEngl.generic-root-brnHmnCpt-epistem66.12, {2012-08-31}
* McsEngl.category-epistem66.12, {2012-08-31}

ROOT.WHOLE

_CREATED: {2012-08-31}

name::
* McsEngl.ROOT.WHOLE,
* McsEngl.category,

DEFINITION

brnHcptUnt'GENERIC

_GENERIC:
* entity.model.info.human.conceptBrain#cptCore66#

brnHcptUnt'WHOLE

_WHOLE:
* view.human.conceptBrain#cptCore93.33#
* concept.human.brain#cptCore66#

brnHcptUnt'WholeNo-relation#cptCore546.15#

name::
* McsEngl.brnHcptUnt'WholeNo-relation,

PRAGMATIC-CORELATION#cptCore382#:
* REFERENTO#cptCore181.68#

EXPRESSION-CORELATION:
* nameLingo#cptCore453#

brnHcptUnt'EVOLUTION#cptCore546.171#

name::
* McsEngl.brnHcptUnt'EVOLUTION,

{time.2002-01-04}:
FROM "Conceptual-System" I made this sc TO "CptSys Unit" and
the "Concept" I renamed to "Conceptual-System" because before realizing that a 'concept' is a 'system' organization of other concepts, when I was speaking for a concept, unconsciously I was speaking for a "CptSys".
[nikkas]

SPECIFIC

name::
* McsEngl.brnHcptUnt.specific,

_SPECIFIC:
===
* relation-or-process#cptCore399#
* non-relation-or-process#cptCore538#

Mcs'ID

name::
* McsEngl.Mcs'ID,
* McsEngl.conceptCore50.28.17,
* McsEngl.Mcs'ID,

_Notation:
* working-idea: cbsWorldviewSubwdv999, 2013-03-30,
* aaj: Entity's-relation @hknu.symb-1@
* folioviews: data [cptIt242#cptIt242#],
* ww: entity@hknm/symb/1/
===
* name[number.number], in current view
* name[number], in current view
* name[view-number.number], in current worldView
* name[worldView.view-number.number],
[hmnSngo.2011-05-28]
===
* owl:=ontology or ontology=:owl
Idea to denote the worldview.
[hmnSngo.2011-09-05]

_Numbering:
* K0'000-000001
* K0'000-999999
* K2'001-000000
...
* K2'999-999999
* K3'001-000000
======
* K0x001 = 1
* K0x999 = 999
* K1x001-K0x000 = 1'000
* K1x001-K0x001 = 1'001
* K1x002-K0x000 = 2'000
* K1x999-K0x000 = 999'000
* K2x001-K1x000-K0x000 = 1'000'000 (million)
* K3x001 = 1'000'000'000 (billion)
* K4x001 = 1'000'000'000'000 (trillion)
===
* A000000 = 1
* A999999 = 999'999
* B000000 = 1'000'000 (million)
* B999999 = 1'999'999
* C000000 = 2'000'000
* D000000 = 3'000'000
======
1
...
1000000    1 mil
1-1
...
1-1000000    2 mil
2-1
...
2-1000000    3 mil
...
1000000-1000000  1 mil mil (tera) = 1^12
1-0-1
...
1 tera tera = 1^24
[hmnSngo.2012-02-09]

_Notation:

_AAj:
Entity @hknu.symb-7@

_C++:
* namspace::bar,

_Folioviews:
* term#cptCore343#
* class_rdf, class_owl,

_HTML:
* to look like regular terms, but when we hover the mouse, a label to show its id, with a link to its definition.
[hmnSngo.2011-09-05]

_RDF:
rdfs:Datatype,
rdf:XMLLiteral,

_XML:
An XML namespace is declared using the reserved XML pseudo-attribute xmlns or xmlns:prefix, the value of which must be a valid namespace name.

For example, the following declaration maps the "xhtml:" prefix to the XHTML namespace:

xmlns:xhtml="http://www.w3.org/1999/xhtml"
[http://en.wikipedia.org/wiki/XML_namespace]

Mcs'NAMERO

name::
* McsEngl.Mcs'NAMERO,
* McsEngl.conceptCore50.28.13,
* McsEngl.namero-of-koncespo@cptCore356.13,
====== lagoSINAGO:
* McsEngl.namero-koncespo@lagoSngo, {2008-03-20}

_ENIVEINO:
* DEZIGNATOR_OF_CONCEPT#cptCore50.29.1#

Mcs'YUNIKERO

_CREATED: {2008-03-31}

name::
* McsEngl.Mcs'YUNIKERO,
* McsEngl.conceptCore50.28.14,
====== lagoSINAGO:
* McsEngl.koncespos-yunikero-356.14@lagoSngo, {2008-03-31}
* McsEngl.koncespo'ID-356.14@lagoSngo, {2008-03-31}

_DEFINITION:
Any namoYunikero or FileName that uniquly identifies the koncespo.
[hmnSngo.2008-03-31_HokoYono]

Mcs'NAMOyUNIKERO

name::
* McsEngl.Mcs'NAMOyUNIKERO,
* McsEngl.conceptCore50.28.8,
* McsEngl.unique-identifier-of-sconcept@cptCore356.8,
* McsEngl.unique-namero-of-koncespo@cptCore356.8,
* McsEngl.unique'name-of-koncespo@cptCore356.8,
* McsEngl.idfier-of-knsa@cptCore356.8,
* McsEngl.knsa'identifier@cptCore356.8,
* McsEngl.knsa'idfier@cptCore356.8,
====== lagoSINAGO:
* McsEngl.namoYunikero@lagoSngo, {2008-03-21}
* McsEngl.identigo@lagoSngo,
* McsEngl.identifeptero@lagoSngo,
====== lagoEsperanto:
* McsEngl.unika'nomo@cptCore356.8@lagoEspo,
* McsEspo.unika'nomo@cptCore356.8,

_DEFINITION:
* IDENTIGO is a DEZIGNATO that uniquely identifies the akpt.
[hmnSngo.2006-01-29_nikkas]

* SC's DESIGNATER is a UNIQUE designater that identifies it.
[hmnSngo.2004-09-27_nikkas]

_SPECIFIC:
* knsa.aa.identifier

Mcs'NAMESPO

name::
* McsEngl.Mcs'NAMESPO,
* McsEngl.conceptCore50.28.5,
* McsEngl.namespo@cptCore356.5,
* McsEngl.namepo-of-koncespo@cptCore356.5,
* McsEngl.namepero-of-ksp@cptCore356.5,
* McsEngl.knsa'name@cptCore356.5,

_DEFINITION:
* The name of a SC, as in a concept, is its namer of its first abjecter.
[hmnSngo.2004-03-30_nikkas]

* Every SC has a 'name' and a unique id. Its name can change, but not its id.
[hmnSngo.1997-10-23_nikos]

* every sc as its corespending 'concept' has a name.

* ΟΝΟΜΑ δομημένης πληροφορίας είναι το ΣΤΑΝΤΑΡΝΤ όνομά της.
[hmnSngo.1994.11_nikos]

* ΟΝΟΜΑ ΔΟΜΗΜΕΝΗΣ ΕΝΝΟΙΑΣ είναι ένα <ΟΝΟΜΑ ΓΛΩΣΣΑΣ>, λέξη και σημασία. Ομως θα αποτελειται απο ΔΥΟ λεξεις. ΑΝ η έννοια ειναι χαρακτηριστικο ΤΟΤΕ σαν πρωτη λέξη θα έχει το όνομα της έννοιας-οντοτητα. ΑΝ η έννοια είναι μερική ΤΟΤΕ σα δεύτερη λέξη θα έχει τη λέξη της γενικης-εννοιας.
[hmnSngo.1994-09-12_nikos]

* Δίνοτας ιεραρχικα ονόματα μπορώ να διαβάζω το ΔΟΜΗΜΕΝΟ ΕΝΝΟΙΑΚΟ ΣΥΣΤΗΜΑ συριακά. Στα αγγλικά είναι τουλάχιστον δυο λέξεις με ΠΡΩΤΗ τη λέξη της έννοιας πχ <economy ELEMENT>. Στα ελληνικά το ίδιο όμως η λέξη της έννοιας είναι σε ΓΕΝΙΚΗ ΠΤΩΣΗ (φανερώνει κτήση) πχ <οικονομιας ΣΤΟΙΧΕΙΟ>
[hmnSngo.1994.09_nikos]

_SPECIFIC:
* FOLIOVIEWS: its name is on the relation (rl 3, rl 4) which define it.
* AA#cptItsoft1047.2#

DEFINITION

DEFINITION.RECURSIVE:
A-MCS is a-concept comprised of:
- a-title: the-main-name of the-concept
- a-list of attributes: where an-attribute is a-Mcs or an-attribute-unit.
An-attribute-unit is:
- a-text-phrase.
- a-text-sentence.
- a-text-paragraph.
- a-list of text-paragraphs.
- the-previous plus images, videos, audios, or tables, lists, trees with text-info.
[hmnSngo.2017-10-15]

DEFINITION.RECURSIVE:
A-MCS is a-concept comprised of:
- a-title
- a-list of attributes
where an-attribute is a-Mcs.
[hmnSngo.2017-04-02]

DEFINITION.RECURSIVE:
A-MCS is a-concept comprised of:
- a-title
- a-list of attributes
where an-attribute could be a-Mcs.
[hmnSngo.2017-03-18]

Ολα ξεκινούν, στο δομημένο εννοιακό σύστημά μου, απο εδώ. Ορίζω τη δομημένη πληροφορία, και χτίζω το δομημένο εννοιακό σύστημά μου. Αρα ξεκινώ απο αρχικό ορισμό σύνθεσης. Φυσικά με το χτήσιμο, προσθέτω ΑΝΑΔΡΟΜΙΚΑ χαρακτηριστικά στη δομημένη πληροφορία.
[hmnSngo.1995-03-31_nikos]

analytic

Koncesto is any sensorial analogical representation of a KONCEPTO#cptCore383#.
[hmnSngo.2008-01-21_KasNik]

A structured-concept is a textual mapon-entity of a CONCEPT with these attributes: Designaters (ID, name, nouner, verber, adnouner, adverber, corelater, formal-name, short-name, abbreviation) Definition Part concepts Whole concepts Generic concepts Specific concepts Environment concepts I'm using logo to describe the attributes of a structured-concept.
[hmnSngo.2005-01-24_nikkas]

A Structured-Concept is a REPRESENTATION of a CONCEPT#cptCore383#.
[hmnSngo.2002-05-20_nikkas]

STRUCTURED-CONCEPT (or structured-conceptual-system) is a textual representation of a CONCEPTUAL-SYSTEM (concept).
[hmnSngo.2002-01-04]

SC--Conceptual-System is ANY system of STRUCTURED-CONCEPTS that maps a Conceptual-System.
[hmnSngo.2001-12-31_nikkas]

A 'concept' resides in a human brain. We don't know yet how exactly the brain stores a real concept. I'm creating the STUCTURED-CONCEPT (SC) by mapping it to a concept. The better a SC maps a concept, the most accurate my representation is.
[hmnSngo.2001-12-30]

A structured-concept is a [FORMAL] CONCEPT (the indivisible element of human-knowledge which preserve its characteristics) with these features:
1.Name
2.Synonyms
3.Definition
4.Attributes
5.Whole concepts
6.General concepts
7.Sibling concepts
8.Subgeneral concepts
9.Environment.
I treat the structured-concept as a SYSTEM (in system's theory terms) with objects and relations.
It's 'Attributes' are parts of this system and they are also subsystems (new concepts). The Name/Synonyms/Definition characteristics are special 'attributes' of the concept. The Whole/General/Sibling/Subgeneral characteristics are special relations of the system (structured-cpt) with the corresponding objecsts.
Every other relation of the structured-cpt to any other entity, I put in 'Environment' characteristic.
[hmnSngo.1999-02-22_nikos]

STRUCTURED-CONCEPT (SC) is a CONCEPT#cptCore1017# in which I express ALL its known relations with other concepts (internal & external) in an organized way. Because every sc has a unique name, the statements with sc-names have a unique meaning.
STRUCTURED-CONCEPT BASE I call a 'system' of structured-concepts.
[hmnSngo.1998-03-01_nikos]

RECURSIVELY,
SC is an OBJECT with RELATIONS with other objects.
INTERNAL RELATIONS (these relations and the objects with which they are related comprise the object of the sc):
1) synonym relation
2) definition relation (Definition of a sc are statements that express the 'meaning' of a sc and the 'referents' that reflects)
3) attributes relation.
EXTERNAL RELATIONS (environment relations):
4) general relation
5) whole relation
6) subgeneral relation
7) other environment relations
[hmnSngo.1998-03-27_nikos]

synthetic

STRUCTURED-CONCEPT is a system of structured-conceptual-units that map conceptual-units#cptCore95.s#.
[hmnSngo.2002-01-04_nikkas]

ΔΟΜΗΜΕΝΗ ΕΝΝΟΙΑ ορίζω το ΑΝΤΙΚΕΙΜΕΝΟ που έχει τις εξεις σχέσεις με άλλα αντικείμενα.
1. ΣΥΝΟΝΥΜΑ ΣΧΕΣΗ, ΣΥΝΟΝΥΜΑ ΑΝΤΙΚΕΙΜΕΝΟ (λέξεις)
2. ΟΡΙΣΜΟΣ ΣΧΕΣΗ, ΟΡΙΣΜΟΣ ΑΝΤΙΚΕΙΜΕΝΟ (πρόταση)
3. ΑΝΑΦΕΡΟΜΕΝΟΥ ΣΧΕΣΗ, ΑΝΑΦΕΡΟΜΕΝΟΥ ΑΝΤΙΚ. (οποιαδήποτε οντοτητα του κόσμου μας, έξω από το μυαλό μας αλλά και δημιούργημα του μυαλού μας)
4. ΓΕΝΙΚΗ ΣΧΕΣΗ, ΓΕΝΙΚΟ ΑΝΤΙΚΕΙΜΕΝΟ (άλλη έννοια)
5. ΟΛΟΥ ΣΧΕΣΗ, ΟΛΟΥ ΑΝΤΙΚ. (άλλη έννοια)
6. ΜΕΡΟΥΣ ΣΧΕΣΕΙΣ, ΜΕΡΟΥΣ ΑΝΤΙΚ. (έννοιες)
7. ΜΕΡΙΚΗ ΣΧΕΣΗ, ΜΕΡΙΚΑ ΑΝΤΙΚΕΙΜΕΝΑ (έννοιες)
8. ΠΕΡΙΒΑΛΛΟΝΤΟΣ ΣΧΕΣΕΙΣ, ΠΕΡΙΒΑΛΛΟΝΤΟΣ ΑΝΤΙΚΕΙΜΕΝΑ (κάθε άλλη σχεση με έννοιες πέρα από τις παραπάνω)
Ο ορισμός αυτός προϋποθέτει τον ορισμό των εννοιών 'σχεση-αντικείμενο'.
Είναι recursive.
[hmnSngo.1996.12_nikos]

ΟΡΙΣΜΟΣ ΕΡΓΑΣΙΑΣ:
ΔΟΜΗΜΕΝΗ ΠΛΗΡΟΦΟΡΙΑ ορίζω να αποτελείται απο ΣΧΕΣΕΙΣ και ΑΝΤΙΚΕΙΜΕΝΑ. Οι βασικές σχεσεις είναι:
SYNONYMΑ
DEFINITION
WHOLE
GENERAL
VIEWS
SOURCE
SUGENERAL
ENVIRONMENT
REFERENT RELATION
[hmnSngo.1995.04_nikos]

Στο σύστημα δομημένης-πληροφορίας ΟΛΑ ΞΕΚΙΝΟΥΝ ΑΠΟ ΔΩ. Ορίζω τη δομημένη'πληροφορία και χτίζω το σύστημα με αυτή σα δομική μονάδα. ΑΝΑΔΡΟΜΙΚΑ η δομημένη πληροφορία εμπλουτίζεται με χαρακτηριστικά που με τη σειρά τους εμπλουτίζουν τις άλλες ΜΕΡΙΚΕΣ δομημένες πληροφορίες.
[hmnSngo.1995.01_nikos]

Level-of-abstractness

ΕΠΙΠΕΔΑ ΑΦΑΙΡΕΣΗΣ ΧΑΡΑΚΤΗΡΙΣΤΙΚΩΝ εννοιας:
Καθε έννοια x θα έχει χαρακτηριστικά σε επιπεδα αφαίρεσης.
Το ΕΠΙΠΕΔΟ 1 είναι τα συγκεκριμένα-γενικων όπου υπάρχουν (atrxg.1) και τα μοναδικα χαρακτηριστικα της έννοιας (atrx.1).
ΕΠΙΠΕΔΟ 2 είναι τα ανωτέρω και οι μερικές έννοιες αυτών level 2 = level 1 + sgn(atrx.1).1 + sgn(atrx.g1).1.
[hmnSngo.1994.08_nikos]

Code

ΚΩΔΙΚΟΙ ΧΑΡΑΚΤΗΡΙΣΤΙΚΩΝ

ΑΝ το χαρακτηριστικό είναι ΓΕΝΙΚΟ (έχει ορισθεί και σε μια άλλη έννοια) ΔΕΝ παίρνει κωδικο και έτσι μειώνεται κατακόρυφα το άνοιγμα καινούργιων εννοιών. Επίσης κάνω προσπάθεια τα χαρακτηριστικά να κρατιούνται στο επιπεδο 4 για να ψάχνονται εύκολα.
[hmnSngo.1994.11_nikos]

ΚΩΔΙΚΟΙ ΧΑΡΑΚΤΗΡΙΣΤΙΚΩΝ:
Πρεπει ΟΛΑ τα χαρακτηριστικά, για να αναφέρομαι συγκεκριμένα, να έχουν ΜΟΝΑΔΙΚΟΥΣ κωδικους. Επειδή τραβάει πολύ στο σύστημα εδω να δινω αριθμούς όπως cpt. a, Σε κάθε ένα θα δινω υποδιαιρέσεις της έννοιας του της μορφης <CPT. A-1, CPT. A-2, ...>. Με τις παύλες διατηρω το βασικό σχήμα των κωδικων.
<A t r.Unique'number.Level> eg
<a t r.xxx.1>, <a t r.epistemxxx.2>, <s g n.xxx-2.1>
[hmnSngo.1994-09-15_nikos]

Mcs'attribute.SPECIFIC#cptCore546.23#

name::
* McsEngl.Mcs'attribute.SPECIFIC,

Mcs'attribute.SPECIFIC-DIVISION.part

name::
* McsEngl.Mcs'attribute.SPECIFIC-DIVISION.part,

ATRIBO_PARTO:
* DEZIGNEPTERO
* DEFINITION
.....

ATRIBO_PARTO_CO:
* WHOLE (TUTO)
* KOMPLETEALO_PARTO
* SIBLO_PARTO
* GENEREPTO
* KOMPLETEALO_SPESIFEPTO
* SIBLO_SPESIFEPTO
* SPESIFEPTO
* ENVIRONMENT
[hmnSngo.2007-09-18_KasNik]

Mcs'attribute.SPECIFIC-DIVISION.inheritance

name::
* McsEngl.Mcs'attribute.SPECIFIC-DIVISION.inheritance,
* McsEngl.inherited/not-inherited-attribute,
* McsElln.ΣΥΓΚΕΚΡΙΜΕΝΟ/ΓΕΝΙΚΟ-ΧΑΡΑΚΤΗΡΙΣΤΙΚΟ,
* McsElln.κληρονομημένο/μη-κληρονομημένο-χαρακτηρισκό, {1999-01-23}
* McsElln.ΜΟΝΑΔΙΚΟ-ΧΑΡΑΚΤΗΡΙΣΤΙΚΟ,

_DEFINITION:
The inheritted attributes of a concept (as in object-oriented-programming) we can take as it is or we can override them. In the first case we don't create a new xml-file, but we can have an attribute in <conref> element for the link in this attribute in the general concept.
[hmnSngo.1999-01-23_nikos]

** ΓΕΝΙΚΑ ΧΑΡΑΚΤΗΡΙΣΤΙΚΑ έννοιας είναι όλα τα χαρακτηριστικα της γενικης έννοιας της, άν έχει.
[hmnSngo.1994.08_nikos]

** ΑΝ μια έννοια είναι μερικη δυο ή περισσότερων εννοιών ΤΟΤΕ τα γενικα χαρακτηριστικά της είναι το σύνολο των χαρακτηριστικων των γενικών εννοιών της.
[hmnSngo.1994.08_nikos]

ΜΟΝΑΔΙΚΑ ΧΑΡΑΚΤΗΡΙΣΤΙΚΑ ΕΝΝΟΙΑΣ:
Μοναδικα χαρακτηριστικα είναι χαρακτηριστικα που έχει μόνο αυτή.
Ενα τέτοιο χαρακτηριστικο μπορεί να είναι μερική έννοια άλλης γενικης έννοιας.
[hmnSngo.1994.08_nikos]

SUBGENERAL:
** OVERRIDDEN/NOT-OVERRIDDEN ATTRIBUTE:
OVERRIDDEN ATTRIBUTE is the inherited-attribute which is a subgeneral-concept of the inherited-attribute and attribute (part) of current-cpt.
I'm using the oop terms because these are similar concepts.
[hmnSngo.1999-02-25_nikos]

** Σε κάποιο γενικο χαρακτηριστικο, η εννοια x, μπορεί να διαφοροποιείται. Αυτο το διαφοροποιημένο σε σχέση με το γενικο το ονομάζω συγκεκριμένο-γενικο χαρακτηριστικο της εννοιας x. Το συμβολίζω atrxcg.1 και είναι συγχρόνως μερικο του γενικου χαρακτηριστικού της έννοιας x.
[hmnSngo.1994.08_nikos]

_SPECIFIC:
* inherited-from-generic,
* inheritedNo-from-generic,
{2017-09-29}
===
* inheriting-to-specific,
* inheritingNo-to-specific,
{2017-09-29}

Mcs'attribute.SPECIFIC-DIVISION.inliness

_CREATED: {1999-02-25}

name::
* McsEngl.Mcs'attribute.SPECIFIC-DIVISION.inliness,

_DEFINITION:
INLINE attribute I call the attribute we don't have a file for it. We need to have such an attribute for economy reasons. The criterion we use to have an attribute as inline or not IS the amount of information we have for that attribute.
In my folio-scs most attributes are inline, I don't have rl 3 object for them. The price for that is that I can't search for them in synonyms-nfo.
In my java-scs I'm gonna use as inline, not-general concepts.
[hmnSngo.1999-02-25_nikos]

Mcs'attribute.OVERVIEW

name::
* McsEngl.Mcs'attribute.OVERVIEW,
* McsEngl.overview.Mcs,
====== lagoGreek:
* McsElln.επισκόπηση,

Mcs'attribute.DESCRIPTION

name::
* McsEngl.Mcs'attribute.DESCRIPTION,

_GENERIC:
* descriptive-information#cptCore50.33#

_DESCRIPTION:
It is unstractured-information (text) describing the attributes of the cbhs.

Mcs'attribute.GENERIC

_CREATED: {2013-04-04}

name::
* McsEngl.Mcs'attribute.GENERIC,
* McsEngl.Mcs'generic-attribute,

_DESCRIPTION:
To present the PATH of generics to "entity":
* greece cptgSbst society cptgSbst organization cptgSbst entity.
[hkmn-2013-04-04]

Mcs'attribute.NAME

name::
* McsEngl.Mcs'attribute.NAME,

_HTML:
synagonism.net/worldview/name
- if there are many concepts with the same name, a list will show the existing subworldview/name
[hmnSngo.2013-03-21]

Mcs'attribute.WHOLE

_CREATED: {2013-04-04}

name::
* McsEngl.Mcs'attribute.WHOLE,
* McsEngl.Mcs'whole-attribute,

_DESCRIPTION:
To present the PATH of wholes to "symban":
* greece cptgElmof EU cptgElmof earth cptgElmof symban.
[hkmn-2013-04-04]

Mcs'IMPORTANCE#cptCore781#

name::
* McsEngl.Mcs'IMPORTANCE,

Σημασία/σημαντικοτητα έννοιας είναι ο ρόλος μιας τυχαίας έννοιας για αλλες, για τον άνθρωπο κλπ.

Mcs'measure#cptCore88#

name::
* McsEngl.Mcs'measure,

DEFINITION

_DESCRIPTION:
Cbs_method uses only ONE data-type to express knowledge, the "cbs".
"Attribute" is any cbs RELATED with another cbs.
"Relation" is the attribute-cbs that denotes the relationship of a cbs with another cbs.
[hmnSngo.2011-09-06]
===
"cbs-theory" and "cbs" are the same concepts.
[hmnSngo.2011-05-28]
===
KNtheory is an INFORMATION_THEORY in which I suggest the storage of information with SENSORIAL_KOGNEPTOS in a computer, instead of text or speech as done before.
[hmnSngo.2008-01-10_KasNik]

Mcs'brainin-info#cptCore181.61#

name::
* McsEngl.Mcs'brainin-info,

Mcs'Logal-info#cptCore93.39#

name::
* McsEngl.Mcs'Logal-info,

Mcs'Semasial-info#cptCore50.27#

name::
* McsEngl.Mcs'Semasial-info,

Mcs'Sensorial-info#cptCore181.62#

name::
* McsEngl.Mcs'Sensorial-info,

Mcs'Sensorial-brainual-info#cptCore50.31#

name::
* McsEngl.Mcs'Sensorial-brainual-info,

Mcs'view.brainconcept-human#cptCore93.33#

name::
* McsEngl.Mcs'view.brainconcept-human,

Mcs'view.brainin#cptCore1100.2#

name::
* McsEngl.Mcs'view.brainin,

Mcs'view.brainin-sensorial#cptCore1100.4#

name::
* McsEngl.Mcs'view.brainin-sensorial,

DEFINITION

Kognesto_knowledge_base is the knowledge_base#cptIt497.1# of a koncesto_program.
[hmnSngo.2008-01-21_KasNik]

ARTIFICIAL-BB is a sensible mapping of a BRAINEPTO-BASE#cptCore457#.
[hmnSngo.2007-12-12_KasNik]

ABB is the outermost ABmodel.
[hmnSngo.2007-11-29_KasNik]

cbskb'PART

name::
* McsEngl.cbskb'PART,

_SPECIFIC:
* worldviewConceptBrainualSensorial#cptCore989.5#
===
A koncesto_base is comprised of different kognesto_worldviews or different kognesto_views.
[hmnSngo.2008-01-23_KasNik]

cbskb'Info-Brainual-Sensorial#cptCore50.31#

name::
* McsEngl.cbskb'Info-Brainual-Sensorial,

cbskb'Knowledge-representation

name::
* McsEngl.cbskb'Knowledge-representation,

Every artificio'brainepto'modilo uses some sort of knowledge-representation technique.
Before the advent of computers, the only mean humans had was text. Computers changed the techniques we had to represent knowledge.
Hypertext is the most common used today.
"Meaning-representations" is what we see in AI systems.
I unconsiously began using "conceptual-models". First with hypertext and now with "meaning-represantation" which are not umbigous.

Also audio, picture and video information is easily incorporated into an abm.
[kas-nik, 2007-06-19]

cbskb'View-Brainual-Sensorial#cptCore1100.4#

name::
* McsEngl.cbskb'View-Brainual-Sensorial,

cbskb'Refereino

name::
* McsEngl.cbskb'Refereino,

The universe.

cbskb'WorldView-Brainual-Sensorial#cptCore989.5: attPar#

name::
* McsEngl.cbskb'WorldView-Brainual-Sensorial,

SPECIFIC

name::
* McsEngl.cbskb.SPECIFIC,

_SpecifiAlphabetically:
* Folioviews-Dos, 1992#cptCore50.28.20: attSpe#
* Folioviews-Win, 1994#cptCore50.28.21: attSpe#

_SPECIFIC_DIVISION.SYSTEM:
* PAPER_KKB (1984)#cptIt356.18#
* DBASE_IV_KKB (1990)#cptIt356.19#
* Folioviews-Dos, 1992#cptCore50.28.20#
* Folioviews-Win, 1994#cptCore50.28.21#
* AAj_KKB-(1997)#ql:aaj'abb-*##cptItsoft1047i#
* HTML_KKB (2007)

_SPECIFIC_DIVISION.INTEGRATION:
* INTEGRATED_KKB
* SEMI_INTEGRATED_KKB
* NON_INTEGRATED_KKB

cbskb.Folio-Views-Win (1994)

name::
* McsEngl.cbskb.Folio-Views-Win (1994),
* McsEngl.conceptCore50.28.21,
* McsEngl.folio-views-win@cptCore454i, {2007-12-17}
* McsEngl.abb.folioviews.win@cptCore417, {2007-12-16}
* McsEngl.BBmanager'FolioViews3.01@cptCore417, {2007-11-30}
* McsEngl.bbmfv@cptCore417,
* McsEngl.folio-views-3.01-windows-electronic-book,
* McsEngl.folio-views-3.01-scs-infobase,
* McsEngl.fvSCS@cptCore417,
* McsEngl.infobase.301scs@cptCore417,
* McsEngl.scs.FV3.01@cptCore417,

_DEFINITION:
FolioViews3.01 SCS-KMS is a SCS-KMS written with the Folio Views 3.01 hypertext program.
[hmnSngo.1997-11-09_nikos]

* Folio views 3.01electronic book, είναι το βιβλίο αυτό εδώ. Είναι μια προσπάθεια κατασκευής δομημένου εννοιακού συστήματος όπου το ρόλου του SSS παίζει το Folio views 3.01 program.

cbskb.FOLIO-VIEWS-DOS (1992)

name::
* McsEngl.cbskb.FOLIO-VIEWS-DOS (1992),
* McsEngl.conceptCore50.28.20,
* McsEngl.folio-views-dos-kkb@cptCore454i, {2008-01-21}
* McsEngl.folio-views-dos-abb@cptCore454i, {2007-12-17}
* McsEngl.BBmanager'FolioViews2.1, {2007-11-28}
* McsEngl.folio-views-2.1-scs,
* McsEngl.folio-views-2.1-electronic-book,
* McsEngl.infobase.21scs@cptCore174,
* McsEngl.scs.FolioViews2.1@cptCore174,

_DESCRIPTION:
* FolioViews 2.1 SCS is a SCS written with the FolioViews2.1 hypertext program.
[hknu@cptCore1997-11-09_nikos]
===
* FOLIO VIEWS ELECTRONIC BOOK: Η ΠΡΟΣΠΑΘΕΙΑ ΚΑΤΑΣΚΕΥΗΣ ΕΝΟΣ ΔΟΜΗΜΕΝΟΥ ΕΝΝΟΙΑΚΟΥ ΣΥΣΤΗΜΑΤΟΣ, OBJECT ORIENTED, ΜΕ ΤΗ ΒΟΗΘΕΙΑ ΤΟΥ ΠΡΟΓΡΑΜΑΤΟΣ FOLIO VIEWS.
[hknu@cptCore1994-01-29_nikos]

cbskb.DBASE-IV (1990)

name::
* McsEngl.cbskb.DBASE-IV (1990),
* McsEngl.conceptCore50.28.19,
* McsEngl.dbase-iv-abb@cptCore454.i, {2007-12-17}
* McsEngl.BBmanager'DBASE'IV@cptCore505, {2007-11-30}
* McsEngl.dbase-iv-SCS-KMS,

_DEFINITION:
An abb created with the database_program DBASEIV#cptItsoft588#.
[hmnSngo.2007-12-17_KasNik]

cbskb.PAPER {1984}

name::
* McsEngl.cbskb.PAPER {1984},
* McsEngl.conceptCore50.28.18,
* McsEngl.paper-kkb@cptCore454i, {2008-01-21}
* McsEngl.paper-abb@cptCore454i, {2007-12-17}
* McsEngl.BBmanager'paper@cptCore454i@deleted, {2007-11-30}
* McsEngl.paper-scs-kms@deleted,
* McsEngl.scs.paper@cptCore454i@deleted,

_DESCRIPTION:
Είχα ντοσιέ για διάφορα θέματα, πχ κοινωνία, οικονομία, πολιτική κλπ (20 θέματα, 49 ντοσιέ).
** Κάθε έννοια είχε ανεξάρτητο φύλλο χαρτιού με συγκεκριμένο αριθμό.
** Για κάθε πληροφορία είχα και την πηγή της.
** βασικά συγκέντρωνα πληροφορίες για κάθε έννοια.
** Για να προσθέσω μία 'πληροφορία':
α) αποφάσιζα πού να την κατατάξω, σε ποιό ντοσιέ
β) αποφάσιζα σε ποιά έννοια
γ) κοίταζα το αριθμητικό και αλφαβητικό ευρετήριο άν υπάρχει αυτή η έννοια
δ) άν υπήρχε τότε την πρόσθετα στο τέλος της έννοιας.
ε) άν δέν υπήρχε τότε άνοιγα καινούργια έννοια με αριθμό τον τελευταίο +1 αριθμό στο αριθμητικό-ευρετήριο.
[hmnSngo.1997-11-09_nikos]

cbskb.Integrated

_CREATED: {2011-06-25} {1993}?

name::
* McsEngl.cbskb.Integrated,
* McsEngl.conceptEconomy356.22,
* McsEngl.artificial--brainepto-model, {2006-06-01}
* McsEngl.artificial'brainepto'model@cptCore0,
* McsEngl.ABM-0,
* McsEngl.Artificial--Brain-Model, {2006-01-09}
* McsEngl.Artificial-Brain-Model,

* McsEngl.concept-base,
* McsEngl.computer-brain-model,
* McsEngl.cbm@cptCore0,
* McsEngl.cbskbi@cptCore356.22,

* McsEngl.iabb@cptCore0,
* McsEngl.iabm@cptCore0,
* McsEngl.ics,
* McsEngl.integrated'artificial'brainepto'base@cptCore0, {2007-12-12}
* McsEngl.integrated--artificial-brainepto-model,
* McsEngl.integrated'artificial'brainepto'model@cptCore0,
* McsEngl.integrated-conceptbase, {2001-05-11}
* McsEngl.integrated-concept-base, {2001-04-28}
* McsEngl.integrated-concept-system,
* McsEngl.integrated--kognesto-base@cptCore0, * cpt.2008-01-18:
* McsEngl.integrated--sensorial-kognepto-base@cptCore0, {2007-12-22}
* McsEngl.integrated--sensory-kognepto-base@cptCore0, {2007-12-22}
* McsEngl.integrated-mental-model, {2001-12-23}
* McsEngl.iskb@cptCore0,

* McsEngl.modilo'brainepto'artificio'integrated@cptCore0, {2007-07-07}
* McsEngl.mdbai@cptCore0,
* McsEngl.modilo'brainepto'integrated@cptCore0, {2007-07-06}
* McsEngl.mdbi@cptCore0,
* McsEngl.modilo'brainepto'artificio@cptCore0,
* McsEngl.model-breinepto--artificial,
* McsEngl.model'breinepto'artificial@cptCore0,
* McsEngl.mdba@cptCore0,

* McsEngl.organized-concept-base, {2001-05-17}
* McsEngl.structured-concept--brain-model, {2004-09-12}
* McsEngl.scbm@cptCore0,
* McsEngl.structured-concept--mental-model, {2003-10-27}
* McsEngl.structured-concept--model, {2003-01-16}
* McsEngl.structured'concept'model@cptCore0,
* McsEngl.scm@cptCore0,
* McsEngl.scmodel@cptCore0,
* McsEngl.scmm--0, {2001-12-26}
* McsEngl.sc-mental-model,
* McsEngl.scmm--0,
* McsEngl.scb, {1998-08-28}
* McsEngl.scb@cptCore0,
* McsEngl.scs-knowledge-base, {1998-02-10} {1998-08-23}
* McsEngl.structured-concept-system-knowledge-base,
* McsEngl.structured-concept-base, {1998-02-26}
* McsEngl.structured-concept-system-knowledge-base,
* McsEngl.structured-information-system,
* McsEngl.structured-conceptual-system,
* McsEngl.SCS,
* McsEngl.SIS,
====== lagoGreek:
* McsElln.*-ενν.2001-05-11:,
* McsElln.ΟΛΟΚΛΗΡΩΜΕΝΗ-ΒΑΣΗ-ΕΝΝΟΙΩΝ,
* McsElln.ΒΑΣΗ-ΔΟΜΗΜΕΝΩΝ-ΕΝΝΟΙΩΝ,
* McsElln.ΒΑΣΗ-ΓΝΩΣΕΩΝ-ΣΥΣΤΗΜΑΤΟΣ-ΔΟΜΗΜΕΝΩΝ-ΕΝΝΟΙΩΝ,
* McsElln.ΔΟΜΗΜΕΝΟ-ΣΥΣΤΗΜΑ-ΠΛΗΡΟΦΟΡΙΩΝ,
* McsElln.ΣΔΠ@cptCore0,
* McsElln.ΣΥΣΤΗΜΑ-ΔΟΜΗΜΕΝΩΝ-ΠΛΗΡΟΦΟΡΙΩΝ,
* McsElln.ΣΥΣΤΗΜΑ'ΔΟΜΗΜΕΝΩΝ'ΠΛΗΡΟΦΟΡΙΩΝ@cptCore0,

=== _NOTES: Διαλέγω το όνομα ΣΥΣΤΗΜΑ ΔΟΜΗΜΕΝΩΝ'ΕΝΝΟΙΩΝ επειδή το όνομα 'έννοια' είναι ιστορικά καθιερωμένο.
[hknu-nikos_1996]
===
Διαλέγω το όνομα ΔΟΜΗΜΕΝΟ ΣΥΣΤΗΜΑ ΠΛΗΡΟΦΟΡΙΩΝ γιατί χτίζεται με τον ορισμό της ΔΟΜΗΜΕΝΗΣ-ΠΛΗΡΟΦΟΡΙΑΣ.
[hknu@cptCore1994.11_nikos]
===
ONTOLOGY is the name used by AI to name this entity.
[hknu@cptCore2001-07-29_nikkas]

_GENERIC:
* KnowledgebaseConceptBrainualSensorial#cptCore50.28.16#

* SYSTEM_HIERARCHY#cptCore348#
* VUDESPTO#cptCore1100.4#
* KNOWLEDGE-BASE#ql:[Level CONCEPT:rl? conceptIt500]##cptIt500#
===
Concept-Bases exists every where. With the help of our language we express concept-bases.
My 'structured-concept-bases' differ in their degree of their intrenal-organization.
My 'structured-concept-systems' help me to build integrated sc-bases.
I want my jSCS to present this information in greek and english logo.
[hmnSngo.2001-04-28_nikkas]

_WHOLE:
* animal-brain#cptCore501.4#
* ειναι χαρακτηριστικο της γνωσης του κόσμου.

Mcs'Manager-system

name::
* McsEngl.Mcs'Manager-system,
* McsEngl.cbs-system,
* McsEngl.cbs-worldview-system,

_DESCRIPTION:
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.
[hmnSngo.2010]

_PART:
* knowledge-base#ql:cbs'knowledge_base#,
* tool,
* user,

_SPECIFIC:
* cbs-worldview-computer-system#ql:cbs_worldview_computer_system-356i#,
* cbs-paper-system,

Mcs'manager.Paper (1985)

name::
* McsEngl.Mcs'manager.Paper (1985),
* McsEngl.cbs-paper-system,
* McsEngl.paper-cbs-system,
* McsEngl.paper-koncesto-system@cptCore356.7,

_DEFINITION:
This is NOT a koncesto_program, it is a koncesto_system.

My first "System". Every koncepto belonged to independed paper sheets. Quickly became apparent that as the quantity of knowledge increased the same happened to the effort to manage this knowledge.

KNOWLEDGE_BASE#cptCore454i#

_GENERIC
* KONCESTO_SYSTEM#cptIt356.2#

Mcstool.ManagerProgram#cptIt356#

name::
* McsEngl.Mcstool.ManagerProgram,

Mcs'Author

name::
* McsEngl.Mcs'Author,

Mcs'Holder

name::
* McsEngl.Mcs'Holder,

Mcs'UNIT

name::
* McsEngl.Mcs'UNIT,
* McsEngl.knsa'unit,
* McsEngl.structured'concept'unit,
* McsEngl.unit-of-structured'concept,
* McsEngl.structured'conceptual'unit,

_DEFINITION:
UNIT-OF-STRUCTURED-CONCEPT is the unit#cptCore348# of structured--conceptual-systems#cptCore356#.
[hmnSngo.2002-01-04_nikkas]

THEORIST#cptEconomy364.26: attWho#

ΝΙΚΟΣ#cptAaa103#

ΑΝΑΔΡΟΜΙΚΑ η δομημενη έννοια σα θεωρια, θα έχει καποιους ανθρωπους σχετικοι με την εξελιξη της ΔΟΜΗΜΕΝΗΣ-ΕΝΝΟΙΑΣ. Οι επιστήμονες της μη δομημενης έννοιας, θα βρίσκονται στο "θεωριες για την έννοια"

Mcs'SCIENCE#cptCore406: attWho#

name::
* McsEngl.Mcs'SCIENCE,

_DEFINITION:
SCIENCE OF AN ARTIFICIAL-KONSEPTO is any SCIENCE that has this konsepto in its subject-matter.
[kas-nik, 2007-08-25]

ΠΕΡΙΒΑΛΛΟΝ ΕΝΝΟΙΑΣ (εξωτερικες σχεσεις)#cptCore756#

name::
* McsElln.ΠΕΡΙΒΑΛΛΟΝ ΕΝΝΟΙΑΣ (εξωτερικες σχεσεις),

Αφου τη δομημενη-έννοια την αντιλαμβάνομαι σα ΣΥΣΤΗΜΑ, θα έχει περιβαλον (εξωτερικές σχεσεις με άλλες έννοιες).

THEORY-OF-MENTAL-MODELS

name::
* McsEngl.theory-of-mental'models,

One of the most influential theories to be formulated in cognitive psychology in recent years is Johnson-Laird’s (1983) theory of mental models. The theory seeks to provide a general explanation of human thought; at its core is the assertion that humans represent the world they are interacting with through mental models. Johnson-Laird credits Craik (1943) with the original statement of this idea.
...
Johnson-Laird (1983) proposed that there are three types of mental representations:
1. propositional representations, which are pieces of information resembling natural language;
2. mental models, which are structural analogies of the world; and
3. mental imagery, which are perceptual correlates of models from a particular point of view.
...
1983 was the year which put mental models on the cognitive research map: it saw not only the publication of Johnson-Laird’s (1983) seminal volume, but also the publication of a collection of papers with the same title edited by Gentner & Stevens (1983). Despite having the same title, the two publications represent very different directions in research on mental representations.
The collection surveys and discusses a variety of internalised and externalised models, ranging from "naive" models of natural phenomena, such as electricity, to instructional models of scientific concepts, often used for teaching purposes. The collection also contains two of the earliest papers of mental models of computer systems by Norman (1983) and Young (1983), which are reviewed in detail under 4.2.1 and 4.2.3, respectively. Unlike Johnson-Laird (1983), who seeks to formulate a cognitive theory to explain human thought in general, the authors of each of these papers seek to model beliefs about a specific domain – i.e. a natural phenomenon or device. The common theme which emerges from the study of diverse domains is analogical reasoning: people attempt to form an understanding of an unknown phenomenon by transferring inferences from an existing mental model to the new phenomenon. Collins & Gentner (1987) suggest that mental models are always constructed through analogical reasoning; on the other hand, the process of structure-mapping between two domains seems to require that the two phenomena have similar surface characteristics (Genter, 1983).
Johnson-Laird (1983) describes mental models as structural analogues, but this is different from analogical reasoning as discussed in Genter & Stevens (1983). Johnson-Laird focuses on the structural analogy between the externalised phenomenon and its internalised representation; Genter & Stevens focus on the transfer from one internalised model to another. For them, structural similarity includes surface characteristics and syntactic features, whereas Johnson-Laird focuses on meaning. As Payne (1992) points out, Johnson-Laird’s theory encompasses the basic theoretical commitment shared by all authors in the Genter & Stevens volume: that people’s existing knowledge has a considerable influence on their reasoning about a new problem, phenomenon, device or idea. Johnson-Laird’s theory of mental models is more developed in that it specifies the format of representations, and procedures which are used to operate them.
[http://www.cs.ucl.ac.uk/staff/a.sasse/thesis/chapter03.html]

MATH-GRAPH-THEORY#cptCore89.37#

The graph_theory can be used in bbtheory because a brainepto_base is a graph of concepts plus its non-concept part.
[hmnSngo.2007-12-16_KasNik]

SEMANTIC-WEB#it19#

BBtheory is about the "unified_science". The internet will be the mean for the collaborative efort with the BBprogram.
[hmnSngo.2007-12-02_KasNik]

Giant Global Graph
Submitted by timbl [t.b.Lee] on Wed, 2007-11-21 18:45. :: Semantic Web Technologies

Well, it has been a long time since my last post here. So many topics, so little time. Some talks, a couple of Design Issues articles, but no blog posts. To dissipate the worry of expectation of quality, I resolve to lower the bar. More about what I had for breakfast.

So The Graph word has been creeping in. BradFitz talks of the Social Graph as does Alex Iskold, who discusses social graphs and network theory in general, points out that users want to own their own social graphs. He alo points out that examples of graphs are the Internet and the Web. So what's with the Graph word?
[http://dig.csail.mit.edu/breadcrumbs/node/215]

UNIFIED-SCIENCE

"Unified Science" can refer to any of three related strands in contemporary thought.
* Belief in the unity of science was a central tenet of logical positivism. Different logical positivists construed this doctrine in several different ways, e.g. as a reductionist thesis, that the objects investigated by the special sciences reduce to the objects of a common, putatively more basic domain of science, usually thought to be physics; as the thesis that all of the theories and results of the various sciences can or ought to be expressed in a common language or "universal slang"; or as the thesis that all the special sciences share a common method.
* The writings of Edward Haskell and a few associates, seeking to rework science into a single discipline employing a common artificial language. This work culminated in the 1972 publication of Full Circle: The Moral Force of Unified Science. The vast part of the work of Haskell and his contemporaries remains unpublished, however. Timothy Wilken and Anthony Judge have recently revived and extended the insights of Haskell and his coworkers.
* Unified Science has been a consistent thread since the 1940s in Howard T. Odum's systems ecology and the associated Emergy Synthesis, modeling the "ecosystem": the geochemical, biochemical, and thermodynamic processes of the lithosphere and biosphere. Modeling such earthly processes in this manner requires a science uniting geology, physics, biology, and chemistry (H.T.Odum 1995). With this in mind, Odum developed a common language of science based on electronic schematics, with applications to ecology economic systems in mind (H.T.Odum 1994).
[http://en.wikipedia.org/wiki/Unified_Science]

UNITY-OF-SCIENCE

The unity of science is a thesis in philosophy-of-science#ql:philosophy'of'science-*# that says that all the sciences form a unified whole.

Even though, for example, physics and sociology are distinct disciplines, the thesis of the unity of science says that in principle they must be part of a unified intellectual endeavor, science. The unity of science thesis is usually associated with the view of levels of organization in nature, where physics is the most basic, chemistry the level above physics, biology above chemistry, sociology above biology, and so forth. Further, cells, organisms, and cultures are all biological, but they represent three different levels of biological organization.

The thesis of a unity of science simply says that common scientific laws apply everywhere and on all levels of organization. On some levels of organization, the scientists there will call these laws by another name, or emphasize the importance of one over another. For example, thermodynamics or the laws of energy seem to be universal across a number of disciplines. That is almost certainly because nearly all systems in nature operate using transactions in energy.

Science is a human endeavor, a part of our culture. It is unified in the sense that it is understood as a single endeavor, and there are not scientists studying alternative realities. To the extent that they do, however, one could argue that they are not unified. It is the perception of a single reality that results in a unity of science.

Separately, science is also apparently on a path toward simplification or actually a "universalization" of discrete scientific theories about energy that physicists call unification. This has led to string theory and its derivatives, and is probably related to the notion that, at bottom, there is only the energy that was released in the big bang, and really nothing else.

The unity of science thesis is most famously clarified and tentatively argued for by Ludwig von Bertalanffy's General System Theory, Paul Oppenheim and Hilary Putnam. It is most famously argued against by Jerry Fodor.
[http://en.wikipedia.org/wiki/Unity_of_science]

[Cat, Jordi, "The Unity of Science", The Stanford Encyclopedia of Philosophy (Fall 2007 Edition), Edward N. Zalta (ed.), URL = <http://plato.stanford.edu/archives/fall2007/entries/scientific-unity/>.]

MONISM vs PLURALISM

Unity is not the opposite of pluralism. Unity of sciences means the creation of ONE integrated_world_view. But the existance of MANY integrated_world_views or integrated_views will improve communication of knowledge and this will lead in the development of MORE accurate_knowledge.
[hmnSngo.2008-01-07_KasNik]

UNIFIED-THEORIES-OF-COGNITION

Unified theories of cognition is a book written by Allen Newell in 1987. Newell argues for the need of a set of general assumptions for cognitive models that account for all of cognition: a unified theory of cognition (UTC).

A UTC must explain how intelligent organisms flexibly react to stimuli from the environment, how they exhibit goal-directed behaviour and acquire goals rationally, how they represent knowledge (or which symbols they use), and learning.

Newell's UTC argues that the mind functions as a single system. He also claims the established cognitive models are vastly underdetermined by experimental data. Therefore, a UTC accounting for the experimental data would provide constraints on the modeling process, resulting in more rigorous and predictive models. A UTC could also be applied as theoretical constructs to a much wider range of cognitive phenomena. When a phenomenon cannot plausibly be explained by the UTC's mechanisms, it could indicate the UTC is wrong.

Newell understands the term cognition to include perception and motor control.

The cognitive architecture Soar is an implementation of a UTC.

Further reading
* Newell, A. (1994).Unified Theories of Cognition, Harvard University Press; Reprint edition, ISBN 0-674-92101-1.
* Newell, A. (1973). "You can’t play 20 questions with nature and win: Projective comments on the papers of this symposium". In W. G. Chase (ed.), Visual Information Processing. New York: Academic Press. (Read article online.)
[http://en.wikipedia.org/wiki/Unified_theory_of_cognition]

Newell wrote and co-authored more than 250 publications, including 10 books. His final book, Unified Theories of Cognition was based on the thesis that tools are at hand that will allow cognitive scientists to develop one unified theory to describe many different types of behavior, instead of building separate theories to cover isolated aspects, as has long been the practice. A system based on a unified theory could support the full range of intelligent behaviors.
[http://diva.library.cmu.edu/Newell/biography.html] 2007-12-01

COGNITIVE-MODEL

BALLARD; RICHARD L

Richard L Ballard Ph.D. (born 1940-03-22) is the first to define knowledge as a science rather than as a philosophy. Knowledge science is articulated in such documents as "Physical Theory of Knowledge and Computation",[1] a definition of knowledge "Knowledge = Theory + Information", "Axiomatic Definition of Knowledge & Human-like Constraint-based Reasoning, "[2] (originally released as "General, Quantitive Theory of Knowledge" 1987-1993 [3]), Knowledge Engineering Methodology, and development of the world's first theory-based semantic software architecture and knowledge capture product called Mark 3[4], that simulates concepts, ideas, thought patterns and instance models that are constrained by well-justified theory to define their relationships. Ballard has forged a unique career combining teaching, scientific research, practical engineering projects of national importance and business development. He has been a founding member of four industries: computer software, computer-based education, computer-based publishing, and knowledge science and engineering. He has been a noted teacher and leader in all four. Ballard has received 128 software citations, developed 21 Educational Software Workshops, 3 Management Software Workshops and a 10 Week Professional Knowledge Engineering course. He has been published in 35 publications and technical reports. He earned a Doctor of Philosophy, with Distinction in Solid State Physics, UC Berkeley 1970, and holds a NASA Fellowship, Institute for Space Physics, Columbia University 1963.

Primary Principles of Knowledge Science Knowledge science defines a physical theory of knowledge that is consistent across the physical domains of human thought, nature and the physics. Within this science is defined an understanding of human thought, it explicit and tacit expression, and how machines can capture and simulate all human knowledge and reason with that knowledge the way people do.

Theory-based semantics is the discipline of precisely defining the meaning of concepts, ideas and thought patterns by their relationship to other concepts and ideas, based on well-justified theory. Because meaning is represented by concept relationships, theory-based semantic is language independent, expressing the precise meaning held in the mind, rather than what is expressed through language. First proposed by Richard L. Ballard, Ph.D. between 1987-1993, theory-based semantics is the governing principle of theory-based semantic systems which allows machines to reason with the same theories that humans use.

Reference Source: "Fundamental Definitions in Knowledge Science & Engineering" by Dr. Richard L. Ballard, 12/2004, self-published - course book for 1st knowledge enginering course taught at UC, Irvine, California entitled: "Creating Systems That Know." Other supporting sources are Ballard's Physical Theory of Knowledge and Computation (2006). White papers and presentations can be viewed at at KnowledgeFoundations.com.

Language Independence The Knowledge Science of Richard L. Ballard states that theory-based semantic technologies are language independent because their concept, idea and thought patterns are faithful representations of the language of thought that occurs in the human brain, not in language. Language is descriptive and for that reason, highly ambiguous. There can be multiple meanings for words, or multiple words to represent a meaning. Theory-based semantics regards language, and more appropriately, the words of language, as dataforms, being no different to the software than an object such as a "gif", "jpeg" or any other object.

For this reason, Language of thought concept, idea and thought pattern representations, once captured, are easily and cost effectively output to any language.

Thought Patterns Based on the knowledge science of Richard L. Ballard, 1940 - , thought patterns are rational compositions of concepts that are repeatedly used and understood by humans once learned. Examples of thought patterns include hierarchical relationships such as organizational charts or parent/child taxonomies relationships, sets and lists. Broader and more abstract thought patterns might include the rational thought pattern of beginning-middle-end. The beginning-middle-end thought pattern applies to many aspects of human life such as games, music, literature, formal correspondence, periods of history and so forth. Thought patterns are an essential element of the "language of thought" and theory-based semantics.

Knowledge = Theory + Information Knowledge and its descriptive formula "Knowledge = Theory + Information", is a core principle of Knowledge Science (based in part on the work of Carl Sagan and John Sowa), advanced and proposed by Dr. Ballard, between 1987-1993. The premise of Ballard's argument is that knowledge is anything that decreases the uncertainty of questions. This occurs through a "declarative" process involving theory (conditional reasoning power), and information (the facts of situations and circumstances). When combined through an A priori and/or analytical reasoning process, uncertainty is decreased and replaced with a state of knowingness. Lessons learned from the application of theory to solve questions are then spontaneously applied to other situations and circumstances. Knowledge can be captured from documents, drawings, illustrations, forms, spreadsheets, books, contracts, policies and procedures, reference sources and from the very minds of people through a methodology called Knowledge engineering. Knowledge engineering work products are called editforms. Editforms are feed into theory-based semantic publishing tools that are used to automate complex decision-making or to transfer job knowledge, among other uses.

Theory represents more than 85% of knowledge. Theory is “A priori” (known before the fact). It is the element that constrains the meaning to concepts, ideas and thought patterns, and the conditional reasoning power required to answer our "How", "Why" and "What if" questions. Learned through enculturation, education and life experience, theory shapes our behavior and the way we understand our world. Well-justified theories such as those proven most successful by science, engineering and business, are most valuable. Theory is predictive and considers all possibilities. Once it is learned it is used for decades, centuries and millenniums. Most of the core theories that shape our social behavior, for example, were conceived 20,000 to 40,000 years ago, passed down through the generations. Much of our financial theories, such as "buy low, sell high", or "the principles of interest", were conceived and put into use by our ancestors millenniums ago. Modern theories, such as those underlying the wireless communications, were conceived in the 1940s and put into practice in the 1970s. The facts of circumstances and situations may change rapidly, but the underlying theory that gives them meaning, do not.

Information represents approximately 15% of knowledge content and is the instances of anything that exists in time and space that can be processed by the senses, measured and counted. Information is the facts of circumstances and situations. Information is “A posteriori (known after the fact). It is the "who", "what", "when", "where" and "how much" instances of circumstances and situations. Conventional information technologies are designed to store and transport facts, but these systems require people to use the theory in their brains to understand and apply those facts for useful ends.
[http://en.wikipedia.org/wiki/Richard_L._Ballard]

COLLABORATION-RELATED

INTEGRATION-RELATED

COGNITIVE-ARCHITECTURE

A cognitive architecture is a blueprint for intelligent agents. It proposes (artificial) computational processes that act like certain cognitive systems, most often, like a person, or acts intelligent under some definition. Cognitive architectures form a subset of general agent architectures. The term 'architecture' implies an approach that attempts to model not only behavior, but also structural properties of the modelled system. These need not be physical properties: they can be properties of virtual machines implemented in physical machines (e.g. brains or computers).
[http://en.wikipedia.org/wiki/Cognitive_architecture]

Jakob Johann von Uexku"ll (1864 - 1944)

Von Uexku"ll was interested in how living beings subjectively perceive their environment. Picture, for example, a meadow as seen through the compound eyes of a fly, continually flying through the air, and then as seen in black and white by a dog (with its highly efficient sense of smell), and then again from the point of view of a human. Von Uexku"ll called these subjective worlds Umwelt.
[http://en.wikipedia.org/wiki/Jakob_von_Uexk%C3%BCll]

Roy A. Rappaport (1926-1997)

name::
* McsEngl.Roy A. Rappaport (1926-1997),

Rappaport coined the distinction between a people's cognized environment and their operational environment, that is between how a people interpret their ecological niche and how their reality actually exists.
[http://en.wikipedia.org/wiki/Roy_Rappaport]

Weltanschauung

A world view (or worldview) is a term calqued from the German word Weltanschauung (pronounced [?v?lt.?an??a?.??]) Welt is the German word for 'world,' and Anschauung is the German word for 'view' or 'outlook'. It implies a concept fundamental to German philosophy and epistemology and refers to a wide world perception. Additionally, it refers to the framework of ideas and beliefs through which an individual interprets the world and interacts in it. The German word is also in wide use in English, as well as the translated form world outlook. (Compare with ideology).
...
The language of a people reflects [citation needed] the Weltanschauung of that people in the form of its syntactic structures and untranslatable connotations and its denotations.
[http://en.wikipedia.org/wiki/Weltanschauung]

Mcs'Function

name::
* McsEngl.Mcs'Function,

Η εννοια ΚΑΘΕΑΥΤΗ σαν σύστημα έχει μια λειτουργια συνολικη. Την όσο το δυνατο καλλιτερη αντανάκλαση του αναφερομενου της.

Mcs'goal (CCCC)

name::
* McsEngl.Mcs'goal (CCCC),
* McsEngl.cccc-cbhs,

_GOAL:
- Classified (all concepts have a DEFINITION showing its position in the structure)
- Clear (no vague boundaries)
- Consistent (no contradictions)
- Complete (no holes).
[hmnSngo.2011-07-20]

1) CLASSIFIED:
- DEFINED, Non_ambigous_knowledge =
defined knowledge. UnDefined is knowledge without definitions.

2) CLEAR:
- Non_vague_knowledge =
- clear boundaries knowledge
- unambiguous,

3) CONSISTENT_knowledge =
not contradictions.

4) COMPLETE:
- COHERENT_knowledge =
- integrated,
- not wholes.

The goal of my theory is the creation of
- consistent,
- coherent,
- integrated
knowledge.
[hmnSngo.2007-10-21_KasNik]

Mcs'Usage

name::
* McsEngl.Mcs'Usage,

Η έννοια σα πληροφορια θα έχει καποιες χρησεις στη ζωή των ανθρωπων.

Mcs'doing.ATTRIBUTE.GENERIC.ADD

name::
* McsEngl.Mcs'doing.ATTRIBUTE.GENERIC.ADD,

_DESCRIPTION:
Add an-attribute which is attribute and its generic-concept.
[hmnSngo.2017-10-07]

_ALGO:
1. Find specific-attributes of generic-concept
2. Ask editor which to add
3. Add selected-attributes to current-concept.

_SPECIFIC:
* generic-overridden,
* generic-overriddenNo (same as generic)
===
* generic-specific-sg,
* generic-specificNo-sNgN,

Mcs'doing.ATTRIBUTE.GENERIC.NO.ADD

name::
* McsEngl.Mcs'doing.ATTRIBUTE.GENERIC.NO.ADD,

_DESCRIPTION:
Add an-attribute to current[a] which is NOT attribute of its[a] generic-concept.
[hmnSngo.2017-10-07]

_SPECIFIC:
* genericNo-specific-sgN,
* genericNo-specificNo-sNgN,

Mcs'doing.ATTRIBUTE.SPECIFIC.ADD

name::
* McsEngl.Mcs'doing.ATTRIBUTE.SPECIFIC.ADD,

_DESCRIPTION:
ADD in current-concept[a] an-attribute which is attribute of a-specifc of it[a].
[hmnSngo.2017-10-14]

Mcs'doing.ATTRIBUTE.GENERALIZE

name::
* McsEngl.Mcs'doing.ATTRIBUTE.GENERALIZE,

_DESCRIPTION:
Make current-attribute AND attribute of its generic-concept.
[hmnSngo.2017-10-07]

Mcs'doing.CONCEPT.GENERIC.CREATE

name::
* McsEngl.Mcs'doing.CONCEPT.GENERIC.CREATE,
* McsEngl.generalize-concept.Mcs,
* McsEngl.mce'generalize-concept,

_DESCRIPTION:
From existing-concept create a-generic.
- Ask which attributes to generalize
[hmnSngo.2017-10-09]

Mcs'doing.CONCEPT.SPECIFIC.CREATE

name::
* McsEngl.Mcs'doing.CONCEPT.SPECIFIC.CREATE,
* McsEngl.specialize-concept.Mcs,
* McsEngl.mce'specialize-concept,

_DESCRIPTION:
From existing-concept create a-specific.
[hmnSngo.2017-10-09]
===
* Find attributes of generic.
* Ask which are specific.

Mcsf'Program

name::
* McsEngl.Mcsf'Program,

Mcsf'My-Worldview#cptCore50.28.26#

name::
* McsEngl.Mcsf'My-Worldview,

McsHitp'Name

name::
* McsEngl.McsHitp'Name,

_DESCRIPTION:
A-concept can-have many names.
Its UNIQUE-NAME is its URL.
===
The-names of diferent languages with similar alphabets will be:
* cptDeu, * cptFra, * cptIta, ...
[hmnSngo.2017-06-13]

McsHitp'Title

name::
* McsEngl.McsHitp'Title,

McsHitp'Attribute

name::
* McsEngl.McsHitp'Attribute,

_DESCRIPTION:
The-part-attributes are displayed first in the-list of attributes.
[hmnSngo.2017-03-12]

McsHitp'Hitp-language

name::
* McsEngl.McsHitp'Hitp-language,

_GENERIC:
* Hitp-language#ql:idHitp#

McsHitp'ID

name::
* McsEngl.McsHitp'ID,

_DESCRIPTION:
Every file-McsHitp has the-ids:
- idHeader: goes in the-beginning of the-doc, contains title.
- idName:
- idDescription:
- idFooter:
- idMeta:
- idSupport:
- idComment:
===
ALL mch have 'idDescription' and 'idName'.
[hknm.2016-08-08]

NOTATION:
- idConceptAattribute: attribute of concept.
- idConceptPattribute: part-attribute of concept.
- idConceptSattribute: specific-attribute of concept.
- idConceptGattribute: generic-attribute of concept.
- idConceptWattribute: whole-attribute of concept.
[hmnSngo.2017-06-11]
===
The ids are the FIRST attributes of element.
[hmnSngo.2013-08-07]

McsHitp'ModelInfoView

name::
* McsEngl.McsHitp'ModelInfoView,

McsHitp'ModelInfoWorld#ql:worldview.synagonism#

name::
* McsEngl.McsHitp'ModelInfoWorld,

McsHitp'Paragraph

name::
* McsEngl.McsHitp'Paragraph,

_DESCRIPTION:
The-titles of paragraphs are-denoted as:
Words-of-name::
Sentences of paragraphs.
[hknm.2016-08-08]

McsHitp'Sentence

name::
* McsEngl.McsHitp'Sentence,

_DESCRIPTION:
Every sentence in a-paragraph begins in a-new-line.
[hknm.2016-08-08]

McsHitp'Index

name::
* McsEngl.McsHitp'Index,

_DESCRIPTION:
* index.name.A.html,
* index.cpt.dirTchInf.html

McsHitp'DOING

name::
* McsEngl.McsHitp'DOING,

_SPECIFIC:
* creating,
* editing,
* searching,
* naming,
* validating,

McsHitp'doing.NAMING

name::
* McsEngl.McsHitp'doing.NAMING,

_DESCRIPTION:
* ATTRIBUTE:
- entity'attribute,
- entittyattribute,
* SPECIFIC:
- entitySpecific,
- entity.specific,
* MULTIWORD_NAME:
- word-word,
- word_word,
[hmnSngo.2017-05-26]

McsHitp'doing.SEARCHING

name::
* McsEngl.McsHitp'doing.SEARCHING,
* McsEngl.McsHitp'searching,
* McsHitp'searching,

_DESCRIPTION:
McsHitp-docs are-searched for CONCEPTS.
Writting 'cpt . name' you find a-concept.
Not a-text containing the-name of a-concept.
[hmnSngo.2017-04-01]

McsHitp'doing.CONVERTING

name::
* McsEngl.McsHitp'doing.CONVERTING,
* McsEngl.fv-to-McsHitp,
* McsEngl.fv2HitpMcs,
* McsEngl.fv2McsHitp,
* McsEngl.McsHitp'conversion,
* McsEngl.McsHitp'converting,

* McsEngl.fv2hitpMcs,
* McsEngl.hitpMcs-from-fv,
* McsEngl.pfv2hitpMcs,

_GENERIC:
* pfv-to-hitp#ql:idHitpfpfv#

McsHitp'doing.SPLITTING

_CREATED: {2017-06-07}

name::
* McsEngl.McsHitp'doing.SPLITTING,
* McsEngl.McsHitp'splitting,

_DESCRIPTION:
In-order to have quick access to structured-concepts, we hold them in about a-size of 1MB.
When they exceed this size we split them.

_PROCESS:
1. The-name of the new file is related to old: filMcsBcnnet => filMcsBcnnetBtc.
2. The first and last parts of the-old are-coppied to new.
3. Links to new#idBtc are-becoming filMcsBcnnetBtc.html#idBtc
4. Search on new '"#id([^(Eth)])' to find internal-links of the original file-
THEN the-ids must-have common-prefix.
Search new-files for OLD prefixes in id.
5. jEdit macro \Users\synagonism\AppData\Roaming\jEdit\macros\HITP\hitp-convert-h2-to-h1.bsh converts h2 to h1 concepts.
6. The-version, the-visitors must continue the-parent-file.
7. New files have idDescription, idName.
8. Images on links, to become internal.

McsHitp'Problem

name::
* McsEngl.McsHitp'Problem,
* McsEngl.McsHitp'issue,
* McsEngl.McsHitp'problem,

['Keynes.book....] is removed after 'node name'
[2017-06-18]

McsHitp'TODO

name::
* McsEngl.McsHitp'TODO,

namidx can-store different quantities of names:
- most used names in relatively small files, other names in bigger files.
{2018-07-22}

block.name'char:
* remove 'char
{2018-08-26}

SPECIFIC

name::
* McsHitp.specific,
* McsEngl.McsHitp.specific,
* McsEngl.McsHitpSpc,

_SPECIFIC:
* http://synagonism.net/dMiw/dTchInf/filMcsLjs.html,
* http://synagonism.net/hitp/,

McsHitp.Javascript

name::
* McsEngl.McsHitp.Javascript,

oCpt = {
oDescription: {
sDsn1: '...',
sDsn2: '..',
aName: [
Name1,
Name2
]
},
aGeneric: [
],
aWhole: [
],
oSpecific: {
}
}

McsHitp.H1

name::
* McsEngl.McsHitp.H1,
* McsEngl.file-McsHitp,
* McsEngl.McsHitpFile,
* McsEngl.McsHitpH1,

_DESCRIPTION:
A-McsHitp with:
- title: header-element.
- attributes: h1-elements.

McsHitp.H2

name::
* McsEngl.McsHitp.H2,
* McsEngl.McsHitpH2,

_DESCRIPTION:
A-McsHitp with child-attributes h2.

McsHitp.H3

name::
* McsEngl.McsHitp.H3,
* McsEngl.McsHitpH3,

_DESCRIPTION:
A-McsHitp with child-attributes h3.

McsHitp.H4

name::
* McsEngl.McsHitp.H4,
* McsEngl.McsHitpH4,

_DESCRIPTION:
A-McsHitp with child-attributes h4.

McsHitp.H5

name::
* McsEngl.McsHitp.H5,
* McsEngl.McsHitpH5,

_DESCRIPTION:
A-McsHitp with child-attributes h5.

McsHitp.H5

name::
* McsEngl.McsHitp.H5,
* McsEngl.McsHitpH5,

_DESCRIPTION:
A-McsHitp with child-attributes h6.

McsHitp.PARAGRAPH

name::
* McsEngl.McsHitp.PARAGRAPH,
* McsEngl.McsHitpP,

_CODE.HITP:
<p id="idX">Title::
<br>Description:: ...
<br>
<br>Name::
<br>* cpt . name,
<a class="clsHide" ...

Mcsh'att.ID

name::
* McsEngl.Mcsh'att.ID,

FORMAT:
* worldview-dddddd-dddddd: hknu-0-3,
* worldview_string-ddd: hknu-hbody-7,
[hmnSngo.2010-09-16]

Mcsh'modelWorld

name::
* McsEngl.Mcsh'modelWorld,
* McsEngl.Mcsh'worlview,

_DESCRIPTION:
Every cptH must belong to one or more worldviews UNAMBIGOUSLY (= with id and definition).
[hmnSngo.2014-03-03]

Mcsh'program

name::
* McsEngl.Mcsh'program,

_DESCRIPTION:
No matter how a cptH it is stored (html-file, h-element, p-element, ...), the program must have the ability to represent it as an htmlfile-cptH.
[hmnSngo.2014-03-03]

SPECIFIC

name::
* McsEngl.Mcsh.specific,

_SPECIFIC:
* html-sfi#file:///D:/File1a/CBSWCS/index.html#
* wikiConcept-cbs#ql:wcpt'cbs###
===
1) with <h1> and relations <h2>
2) with <p> and relations <br/><span class="u">Generic</span>:
3) inside <p> with only the definitin:
<br/>* <a name="nlLeafNode"/>hcpt: <b>LEAF-NODE</b>:
A node without children.
4) with <h0> and relations <h1>
[hmnSngo.2010-06-06]

Mcsh.HTML-FILE

name::
* McsEngl.Mcsh.HTML-FILE,

_DESCRIPTION:
A whole file is dedicated to one concept.

Mcsh.H1-ELEMENT

name::
* McsEngl.Mcsh.H1-ELEMENT,

Mcsh.H2-ELEMENT

name::
* McsEngl.Mcsh.H2-ELEMENT,

_NOTATION:
<h2>
..<a name="nlSmConcept"/>
..hcpt:: HL's-SEMASIAL-CONCEPT (sml-cpt)
</h2>
<h3>
..Definition
</h3>
<p>
..Semasial..
</p>

Mcsh.H3-ELEMENT

name::
* McsEngl.Mcsh.H3-ELEMENT,

_NOTATION:
<h3>
..<a name="nlSmConcept"/>
..hcpt:: NAME
</h3>
<h4>
..Definition
</h4>
<p>
..Semasial..
</p>

Mcsh.PARAGRAPH-ELEMENT

name::
* McsEngl.Mcsh.PARAGRAPH-ELEMENT,

_NOTATION:
<p>
..<a name="knower"/>
..hcpt:: <b>LANGUAGE's-KNOWER</b>:
..<br/><span class="u">Definition</span>:
....<br/>A human or a machine who <b>knows</b> the language is the
....
..<br/><span class="u">Specific</span>:
....<br/>* <a href="lango_ho_eng.html#knower">English</a>,
....<br/>* <a href="lango_ho_kml.html#knower">Komo</a>.
</p>

Mcsh.INSIDE-PARAGRAPH-ELEMENT

name::
* McsEngl.Mcsh.INSIDE-PARAGRAPH-ELEMENT,

_NOTATION:
..<br/><span class="u">Specific</span>:
....<br/>* <a name="..."/>hcpt:: <b>NAME</b>:
......the definition of the cpt.
....<br/>* <a href="lango_ho_kml.html#knower">Komo</a>.
</p>

analytic

CONCEPTUAL-MODEL is a MIXED-HIERARCHY of CONCEPTS located in a human's BRAIN, organized with 2 hierarchies part-whole-environment and specific-generic#cptCore758#.
[hmnSngo.2003-03-01_nikkas]

CONCEPTUAL-MODEL is a MIXED-HIERARCHY of CONCEPTS located in a human's BRAIN, with concepts organized in generic-specific-hierarchies, whole-part-hierarchies (system|set).
[hmnSngo.2003-02-19_nikkas]

CONCEPTUAL-MODEL is a RECURSIVE-SYSTEM#cptCore348# of CONCEPTS located in a human's BRAIN.
[hmnSngo.2003-01-13_nikkas]

CONCEPTUAL-MODEL is HUMAN-INFORMATION#cptCore445.a# created as systems of concepts.
[hmnSngo.2002-01-02_nikkas]

CONCEPT-BASE is a MODEL of reality created by concepts. Each individual has its unique conceptbase with which interacts with his environment. The Conceptual-Information describes conceptbases.
[hmnSngo.2001-07-28_nikkas]

synthetic

CONCEPTUAL-MODEL is the outermost-system in system-hierarhy of CONCEPTS. Sensory and perceptual information is integrated with concepts.
[hmnSngo.2001-12-30_nikkas]

CONCEPTUAL-MODEL is the part of MENTAL-MODEL#cptCore985.a# that is composed solely by CONCEPTS.
[hmnSngo.2001-12-29_nikkas]

SENSORIAL-KONCEPTO-MODEL

name::
====== lagoSINAGO:
* McsEngl.foEkoSeoKoncoVudo@lagoSngo,
* McsEngl.sensorial-concept-subworldview@lagoSngo,
* McsEngl.sensorial-koncepto-model@lagoSngo,

Relation'BrnHview-and-smsView

name::
* McsEngl.Relation'BrnHview-and-smsView,
* McsEngl.conceptCore757.2,
* McsEngl.conceptual'model'and'descriptive'information@cptCore757.2,
* McsEngl.di'and'conceptual'model@cptCore757.2,
* McsEngl.koncepto-model-and-langeto-model@cptCore757.2,

_Node:
* this
* smsView#cptCore1100.3#

_DESCRIPTION:
Humans are using and other means to repersent their conceptual-models. Images and video is one example.
[hmnSngo.2003-03-27_nikkas]
===
That's why we say: a picture is equal to one thousand of words.
[hmnSngo.2003-03-31_nikkas]
===
DI is a part-whole-environment hierarchy of STATETMENTS.
CptModel is a part-whole-environment and specific-generic-hierarchy of CONCEPTS.
[hmnSngo.2003-03-13_nikkas]
===
Descriptive-Information is NOT stored in human-memory. It is generated "on the fly" in order to "express" it with logo (oral or written) to communicate subjective "conceptual-models". All of us have felt that we "know" something but we have dificulties to express it, usually forgeting the names a language uses for the concepts and not the 'syntax' of them.
[hmnSngo.2003-01-16_nikkas]
===
The descriptive-information (which is associated with the human-language) is the entity that mostly diferentiates humans from nonhumans. Also we map names to concepts when we use them in descriptive-information. Generic-Concepts, in some respect, have and the nonhumans. They identify their enemies from their main attributes.
[hmnSngo.2002-08-16_nikkas]
===
Descriptive-Information is an outermost system of a SYSTEM OF STATEMENTS#cptCore531#.
Conceptual-Model is the outermost system of the SYSTEM OF CONCEPTS (conceptual-units).
The concepts also are the elements of statements, but not the units of Descriptive-Information.
[hmnSngo.2002-05-21_nikkas]
===
LOGO-ANALYSIS:
A machine will manage to analyze the logo of a book or a person if:
a) it is able to create the mental-model that this logo represents.
b) it can find the internal contradictions of this mental-model.
c) it can compare with a mental-model we consider 'true'.
[hmnSngo.2001-12-23_nikkas]
===
COMMUNICATION:
People communicate their mental'models with languages. A language maps Descrptive-Information (noto) to Logo. The knowers of a language generate and understand logo. In communication we are dealing with logo, BUT the most important is not the noto (the meaning) a logo express but the 'mental-model' the noto describes.
It is an everyday operation of teachers to distiguish which students understood the mental-model which try to communicate to them FROM the logo the students use to describe the mental-model.
[hmnSngo.2001-12-23_nikkas]
===
ConceptBase is a MODEL of reality created by concepts.
Conceptual-Information is a system of concepts that DESCRIBES a ConceptBase.
[hmnSngo.2001-07-29]

Relation'BrnHview-and-lagHmn

name::
* McsEngl.Relation'BrnHview-and-lagHmn,
* McsEngl.conceptCore757.3,
* McsEngl.conceptual-model-and-human-language,
* McsEngl.conceptual'model'and'language@cptCore757.3,
* McsEngl.language'and'conceptual'model@cptCore757.3,

_Node:
* this,
* human-language#cptCore93#

_DESCRIPTION:
A model-concept can NOT exist without a language-human. A concept is created by giving a name to a preconcept. Every language has a mechanism to create names. Then a model-concept is language depedent.
[hmnSngo.2006-01-06_nikkas]

With the language we express a PART of our conceptual-models.
[hmnSngo.2003-04-03_nikkas]

Gestural, spoken and written languages contributed in the creation of more and more complex conceptual-models which are impossible to be created without a language.
[hmnSngo.2003-01-18_nikkas]

A language provides ONLY names in a conceptual-model. That's why we can create a language independent conceptual-model if we use eg numbers for names.
In contrast, descriptive-information is language dependent because its parts are directly corelated with linguistic entities. And if a language does not have an entity the same happens and for the coresponding di-entity.
[hmnSngo.2003-03-13_nikkas]

relation.CONCEPTUAL-MODEL--SENSORY-INFORMATION

name::
* McsEngl.relation.CONCEPTUAL-MODEL--SENSORY-INFORMATION,
* McsEngl.conceptCore757.1,
* McsEngl.conceptual'model'and'sensory'information@cptCore757.1,
* McsEngl.sensory'info'and'conceptual'model@cptCore757.1,

_Node:
* this,
* preconceptual-information#cptCore760.7#

_DESCRIPTION:
Sensory-information is NOT separated from the conceptual-model of an individual. It is integrated with the conceputal-model.
[hmnSngo.2003-01-16_nikkas]

archetypeCbh.OWNERSHIP#cptCore546.34#

name::
* McsEngl.archetypeCbh.OWNERSHIP,

analytic

LOGO is a PART-WHOLE-ENVIRONMENT-HIERARCHY of FRASI that MAPS DESCRIPTIVE-INFORMATION#cptCore593#.
[hmnSngo.2003-05-06_nikkas]

LOGO is a RECURSIVE-SYSTEM of FRASIS and a REPRESENTATION of a DESCRIPTIVE-INFORMATION#cptCore593.a#.
[hmnSngo.2003-01-12_nikkas]

LOGO is the 'message' we create with a language that 'express' a meaning.
[hmnSngo.2000-09-05_nikkas]

LOGO is a REPRESENTATION of descriptive-information#cptCore593.a#.

Conceptual-Information is mapped, with the use of a language, to a material entity. This is called EXPRESSION/LOGO.
[hmnSngo.2000-10-09_nikkas]

synthetic

LOGO is any outermost frasal-system that maps descriptive-information#cptCore593.s#.
[hmnSngo.2002-05-22_nikkas]

LOGO is >>>ANY<<< frasian-system, wordal-system or diktal-system.
[hmnSngo.2002-01-10_nikkas]

LOGO is ANY >>>system<<< of FRASI that maps Statement-Systems.
[hmnSngo.2002-01-08_nikkas]

LOGO is ANY system of FRASIS that maps Statement-Systems.
[hmnSngo.2001-12-31_nikkas]

LOGO is the SYSTEM-HIERARCHY of 'statements#cptCore531#' that describes a menta-model. Statements are the units of logo and concepts are the units of 'mental-model#cptCore985#'.
[hmnSngo.2001-12-26_nikkas]

LOGO is a SYSTEM of LOGEMES#cptCore643#.
[hmnSngo.2001-12-09_nikkas]

LOGO is the SPOKEN-LOGO >>>or<<< the WRITTEN-LOGO.
[hmnSngo.2001-12-08_nikkas]

LOGO is a SYSTEM of WORDS and word is a system of characters.
[hmnSngo.2001-11-11_nikkas]

LOGO is ANY SENTENCE-supersystem, product of a LANGUAGE#cptCore93#, that express CONCEPTUAL-INFORMATION.
[hmnSngo.2000-09-15_nikkas]

LOGO is a supersystem of SENTENCE, product of a LANGUAGE#cptCore93# that express INFORMATION#cptCore445.s#.
[hmnSngo.2000-09-02_nikkas]

LOGO I call the speech/text we create, with the help of our LANGUAGE, that EXPRESSES (maps) conceptual-information. In literature we can see to name as 'information' what I call here logo and human-information.

LOGUM is the outermost FRASIAN-STRUCTURE-X#cptCore787#.
[hmnSngo.2001-12-25_nikkas]

The EXPRESSION of a SUPERSTATEMENT#cptCore593.a# is called SUPERFRASIS.
[hmnSngo.2000-10-08_nikkas]

analytic

FRASAL-SYSTEM is ANY SYSTEM of frasi that represents a statemental-system.
[hmnSngo.2002-05-22_nikkas]

More than one independent-verberos

synthetic

FRASAL-SYSTEM is the mechanism (system of frasis) that maps Statemental-Systems.
[hmnSngo.2002-01-10_nikkas]

FRASIAN-STRUCTURE-X is a SYSTEM of FRASIAN-STRUCTURE-(X-1), where frasian-structure- 1 is a system of frasis.
[hmnSngo.2001-12-25_nikkas]

OTHER-VIEW

In semantics, discourses are linguistic units composed of several sentences — in other words, conversations, arguments or speeches.
[http://en.wikipedia.org/wiki/Discourse] 2007-06-21

lagHmnlingo'languageHuman#cptCore93#

name::
* McsEngl.lagHmnlingo'languageHuman,

lagHmnlingo'SmsView#cptCore1100.3#

name::
* McsEngl.lagHmnlingo'SmsView,

* EKSPRESUDINO-HOMO#cptCore93.58#

* KOMPRENUDINO-HOMO#cptCore93.59#

lagHmnlingo'EKSPRESERO'ANALYSIS

name::
* McsEngl.lagHmnlingo'EKSPRESERO'ANALYSIS,
* McsEngl.conceptCore474.14,
* McsEngl.ekspresero'analysis,

lagHmnlingo'SYNTAX'ANALYSIS

name::
* McsEngl.lagHmnlingo'SYNTAX'ANALYSIS,
* McsEngl.conceptCore474.6,
* McsEngl.syntactic-process@cptCore474.6,
* McsEngl.order'analysis,

_DEFINITION:
* SYNTACTIC-ANALYSIS is the process of analysis of first and second logo-hierarchies.
[hmnSngo.2003-11-28_nikkas]

* PARSING, THE PROCESS of syntactic analysis.
[Winston et al, 1990, 138#cptResource112#]

nodLog'Expression

name::
* McsEngl.nodLog'Expression,
* McsEngl.conceptCore474.33,
* McsEngl.expression-of-lgNode@cptCore474.33,
* McsEngl.logo-expression@cptCore474.33,
* McsEngl.ekspresero-of-nodero@cptCore474.33,
====== lagoSINAGO:
* McsEngl.ekspresero@lagoSngo,

_DEFINITION:
* Every node has a textero or a parolero we communicate with.
[hmnSngo.2006-10-23_nikkas]

SPECIFIC

name::
* McsEngl.nodLog.specific,

_SPECIFIC: nodLingHmn.alphabetically:
* nodLingHmn.nameLingo (2nd unit)#cptCore453#
* nodLingHmn.concept.conjunction#cptCore1104#
* nodLingHmn.concept.naun#cptCore256#
* nodLingHmn.concept.verb#cptCore551#
* nodLingHmn.mapped#cptCore474.28#
* nodLingHmn.mappedNo#cptCore474.29#
* nodLingHmn.sentence (1st unit)#cptCore557#
* nodLingHmn.speech#cptCore1060.1#
* nodLingHmn.stop#cptCore474.37#
* nodLingHmn.stop.main#cptCore474.40#
* nodLingHmn.stop.secondary#cptCore474.39#
* nodLingHmn.stopNo#cptCore474.34#
* nodLingHmn.system_of_main_units#cptCore59.1#
* nodLingHmn.system_of_main_units.used#cptCore643#
* nodLingHmn.system_of_main_units.used.free (word)#cptCore59.9#
* nodLingHmn.system_of_main_units.used.word.name#cptCore494.1#
* nodLingHmn.system_of_main_units.used.word.function#cptCore59.24#
* nodLingHmn.system_of_main_units.used.freeNo#cptCore59.10#
* nodLingHmn.system_of_nonmain_units#cptCore474.31#
* nodLingHmn.system_of_nouns#cptCore645.1#
* nodLingHmn.system_of_sentences#cptCore787#
* nodLingHmn.text#cptCore1059.5#
* nodLingHmn.unit.main (3rd rootunit)#cptCore78.1#
* nodLingHmn.unit.mainNo#cptCore474.30#
* nodLingHmn.verbargument#cptCore557.30#
* nodLingHmn.verbnode.agent#cptCore557.33#
* nodLingHmn.verbnode.object#cptCore557.36#
* nodLingHmn.verbnode.object2#cptCore557.37#
* nodLingHmn.verbnode.subject#cptCore557.32#
* nodLingHmn.verbnode.subject_complement#cptCore557.35#
* nodLingHmn.view (outermost)#cptCore474#
* nodLingHmn.view_node#cptCore474.9#

_SPECIFIC: nodLingHmn.SPECIFIC_DIVISION.MEDIUM:
* nodLingHmn.text_node#cptCore1059.5#
* nodLingHmn.speech_node#cptCore1060.1#

* nodLingHmn.mapped#cptCore474.28#
* nodLingHmn.mappedNo#cptCore474.29#

* nodLingHmn.stop#cptCore474.37#
* nodLingHmn.stopNo#cptCore474.34#

* nodLingHmn.view (outermost)#cptCore474#
* nodLingHmn.system_of_sentences#cptCore787#
* nodLingHmn.sentence (1st rootunit)#cptCore557#

* nodLingHmn.verbargument#cptCore557.30#
* nodLingHmn.verbnode.subject#cptCore557.32#
* nodLingHmn.verbnode.object#cptCore557.36#
* nodLingHmn.verbnode.object2#cptCore557.37#
* nodLingHmn.verbnode.agent#cptCore557.33#
* nodLingHmn.verbnode.subject_complement#cptCore557.35#

* nodLingHmn.system_of_nouns#cptCore645.1#
* nodLingHmn.nameLingo (2nd rootunit)#cptCore453#
* nodLingHmn.concept.conjunction#cptCore1104#
* nodLingHmn.concept.naun#cptCore256#
* nodLingHmn.concept.verb#cptCore551#

* nodLingHmn.NAME-WORD--STRUKTURO#cptCore494.2#
* nodLingHmn.system_of_main_units#cptCore59.1#
* nodLingHmn.system_of_main_units.used#cptCore643#
* nodLingHmn.system_of_main_units.used.free (word)#cptCore59.9#
* nodLingHmn.system_of_main_units.used.word.name#cptCore494.1#
* nodLingHmn.system_of_main_units.used.word.function#cptCore59.24#
* nodLingHmn.system_of_main_units.used.freeNo#cptCore59.10#
* nodLingHmn.unit.main (3rd rootunit)#cptCore78.1#

* nodLingHmn.system_of_nonmain_units#cptCore474.31#
* nodLingHmn.unit.mainNo#cptCore474.30#

nodLingHmn.MAPPED

name::
* McsEngl.nodLingHmn.MAPPED,
* McsEngl.conceptCore474.28,
* McsEngl.nodero-mapeino@cptCore474.28,
* McsEngl.mapped-logal-node@cptCore474.28, {2012-08-22}

_GENERIC:
* entity.attribute.node.nodSysStree.nodSstwpe.nodLingo#cptCore93.34#
* entity.attribute.node.nodSysStree.nodSstwpe#cptCore348.41#
* entity.attribute.node.nodSysStree#cptCore348.12#
* entity.attribute.node#cptCore515.4#
* entity.attribute#cptCore398#
* entity#cptCore387#

_DEFINITION:
MAPEELERO is a nodero which is corelated with a mineto|brainepto.
[hmnSngo.2006-12-05_nikkas]

_EKSPRESERO:
The logero of the nodero.

_SPECIFIC:
* NODETRO-MAPEINO#cptCore1059.15#
* NODEPRO-MAPEINO

nodLingHmn.mapeino'MAPEOLO

name::
* McsEngl.nodLingHmn.mapeino'MAPEOLO,
* McsEngl.conceptCore474.36,
* McsEngl.mapeolo-of-nodero'mapeino@cptCore474.36,
* McsEngl.mapealero-of-nodero'mapeino@cptCore475.36, (mape-ino -alo -ero)

_DEFINITION:
The "original" in this deino is the mineto.
[hmnSngo.2007-02-04_nikkas]

Is the "content" of a nodero-mapeino. The mineto|brainepto it nenotes.
[hmnSngo.2006-12-05_nikkas]

nodLingHmn.MAPPED.NO

name::
* McsEngl.nodLingHmn.MAPPED.NO,
* McsEngl.conceptCore474.29,
* McsEngl.nodero-mapeinoco@cptCore474.29,
* McsEngl.non-mapped-logal-node@cptCore474.29, {2012-08-22}

_GENERIC:
* entity.attribute.node.nodSysStree.nodSstwpe.nodLingo#cptCore93.34#
* entity.attribute.node.nodSysStree.nodSstwpe#cptCore348.41#
* entity.attribute.node.nodSysStree#cptCore348.12#
* entity.attribute.node#cptCore515.4#
* entity.attribute#cptCore398#
* entity#cptCore387#

_SPECIFIC:
* MAPEELNOETRO#cptCore1059.4#
* MAPEELNOEPRO

* YORDERO (free--used-lektero)#cptCore59.9#
* AFIXERO (captive--used-lektero)#cptCore59.10#
* LEKTERO-USED#cptCore643#
* lingHmnSysUntsMain#cptCore59.1#
* SILABERO#cptCore612#
* lingoHmnUnitMain#cptCore78.1#

* PUNKTERO#cptCore474.11#

nodLingHmn.STOP

_CREATED: {2012-08-30} ?

name::
* McsEngl.nodLingHmn.STOP,
* McsEngl.conceptCore93.41,
* McsEngl.conceptCore78.7,
* McsEngl.conceptCore474.37,
* McsEngl.node.lingo.human.stop@cptCore93.41, {2012-09-24}
* McsEngl.stop-logal-node@cptCore474.37,
* McsEngl.stop-logo-node@cptCore474.37,
====== lagoSINAGO:
* McsEngl.foEtoNodoStopetino@lagoSngo,
* McsEngl.stopero@lagoSngo,

_GENERIC:
* entity.attribute.node.nodSysStree.nodSstwpe.nodLingo#cptCore93.34#
* entity.attribute.node.nodSysStree.nodSstwpe#cptCore348.41#
* entity.attribute.node.nodSysStree#cptCore348.12#
* entity.attribute.node#cptCore515.4#
* entity.attribute#cptCore398#
* entity#cptCore387#

_DEFINITION:
* STOPERO is any nodero a language uses to SEPARATE the other noderos.
[hmnSngo.2006-12-17_nikkas]

_SPECIFIC:
* nodLingHmn.stop.main#cptCore474.40#
* nodLingHmn.stop.secondary#cptCore474.39#
* nodLingHmn.stop.blankspace#cptCore474.38#
* nodLingHmn.stop.punctuation#cptCore474.11#
========
* MAIN_STOP_NODE#cptCore474.40#
* SECONDARY_STOP_NODE#cptCore474.39#
==========
* BLANKSPACE#cptCore474.38#
* PUNCTUATION#cptCore474.11#
=========
* STOPETRO#cptCore1059.21#
* STOPEPRO#cptCore1060.4#

nodLingHmn.stop.MAIN

_CREATED: {2008-10-30}

name::
* McsEngl.nodLingHmn.stop.MAIN,
* McsEngl.conceptCore474.40,
* McsEngl.main-stopNode@cptCore474.40,

_GENERIC:
* entity.attribute.node.nodSysStree.nodSstwpe.nodLingo#cptCore93.34#
* entity.attribute.node.nodSysStree.nodSstwpe#cptCore348.41#
* entity.attribute.node.nodSysStree#cptCore348.12#
* entity.attribute.node#cptCore515.4#
* entity.attribute#cptCore398#
* entity#cptCore387#

_DEFINITION:
it is the stop_node that separates the main parts of logo.
[hmnSngo.2008-10-30]

nodLingHmn.stop.SECONDARY

_CREATED: {2008-10-21}

name::
* McsEngl.nodLingHmn.stop.SECONDARY,
* McsEngl.conceptCore474.39,
* McsEngl.period-stopNode@cptCore474.39,
* McsEngl.secondary-stopNode@cptCore474.39,

_GENERIC:
* entity.attribute.node.nodSysStree.nodSstwpe.nodLingo#cptCore93.34#
* entity.attribute.node.nodSysStree.nodSstwpe#cptCore348.41#
* entity.attribute.node.nodSysStree#cptCore348.12#
* entity.attribute.node#cptCore515.4#
* entity.attribute#cptCore398#
* entity#cptCore387#

_DEFINITION:
it is the stop_node inside a period.
[hmnSngo.2008-10-21]

_SPECIFIC:
* BLANKSPACE#cptCore474.38#
* PUNCTUATION#cptCore474.11#

nodLingHmn.stop.PUNCTUATION#cptCore474.11#

name::
* McsEngl.nodLingHmn.stop.PUNCTUATION,

nodLingHmn.stop.BLANKSPACE

_CREATED: {2008-09-28}

name::
* McsEngl.nodLingHmn.stop.BLANKSPACE,
* McsEngl.conceptCore474.38,
* McsEngl.blankspace@cptCore474.38,
====== lagoSINAGO:
* McsEngl.separatero@lagoSngo,

_GENERIC:
* entity.attribute.node.nodSysStree.nodSstwpe.nodLingo#cptCore93.34#
* entity.attribute.node.nodSysStree.nodSstwpe#cptCore348.41#
* entity.attribute.node.nodSysStree#cptCore348.12#
* entity.attribute.node#cptCore515.4#
* entity.attribute#cptCore398#
* entity#cptCore387#

_SPECIFIC:
* WHITESPACE#cptCore1059.20#
*

nodLingHmn.STOP.NO (tnr)

name::
* McsEngl.nodLingHmn.STOP.NO (tnr),
* McsEngl.conceptCore474.34,
* McsEngl.non-stop-logal-node@cptCore474.34, {2012-08-22}
* McsEngl.tokenero@cptCore474.34,
* McsEngl.nonstop-logal-node@cptCore474.34,

_GENERIC:
* entity.attribute.node.nodSysStree.nodSstwpe.nodLingo#cptCore93.34#
* entity.attribute.node.nodSysStree.nodSstwpe#cptCore348.41#
* entity.attribute.node.nodSysStree#cptCore348.12#
* entity.attribute.node#cptCore515.4#
* entity.attribute#cptCore398#
* entity#cptCore387#

_DEFINITION:
* TOKENEROS are the noderos created with stoperos#cptCore474.37#.
[hmnSngo.2007-02-25_nikkas]

* TOKENEROS are the stoperos and the nodes the stoperos create such as yorderos, instanseros, dezignepteros.
[hmnSngo.2006-10-22_nikkas]

_SPECIFIC:
--- MISC ---
* MAIN_NONSTOP_NODE
* PERIOD_NODE
* PERIOD_S_WHOLE
* PERIOD_S_PART
_SPECIFIC_DIVISION.MEDIUM ---
* TOKENETRO#cptCore1059.7#
 * TOKENEPRO#cptCore1060.5#

nodLingHmn.STRUKTURO

name::
* McsEngl.nodLingHmn.STRUKTURO,
* McsEngl.conceptCore474.35,
* McsEngl.strukturero@cptCore474.35,

nodLingHmn.UNIT.MAIN.NO#cptCore78.6#

name::
* McsEngl.nodLingHmn.UNIT.MAIN.NO,

SPECIFIC

_SPECIFIC:
* ltph.lango.english#cptCore78.11#
* ltph.lango.frence#cptCore78.13#
* ltph.lango.german#cptCore78.10#
* ltph.lango.greek#cptCore78.14#
* ltph.lango.spanish#cptCore78.12#

LANGO.ENGLISH

name::
* McsEngl.LANGO.ENGLISH,
* McsEngl.conceptCore78.11,
* McsEngl.conceptCore301,
* McsEngl.ENGLISH-letter-to-phoneme-correspodence,
* McsEngl.English-LetterToPhoneme@cptCore301,
* McsEngl.letter'phoneme'correspodence'english@cptCore301,
* McsEngl.mapping.diktim.english@cptCore301,
====== lagoGreek:
* McsElln.ΑΓΓΛΙΚΗ-ΓΡΑΜΜΑ-ΦΩΝΗΜΑ-ΑΝΤΙΣΤΟΙΧΙΑ,

_WHOLE:
* english-language#cptCore569#

_DESCRIPTION:
ΑΓΓΛΙΚΗ ΓΡΑΜΜΑ-ΦΩΝΗΜΑ ΑΝΤΙΣΤΟΙΧΙΑ είναι ΓΡΑΜΜΑ-ΦΩΝΗΜΑ-ΑΝΤΙΣΤΟΙΧΙΑ#cptCore70.a# της 'αγγλικης γλωσσας'.
[hmnSngo.1995.04_nikos]