description::
× Mcsh-creation: {2017-09-27}
· senso-concept (modelConceptSensorial | Mcs) is a-MODEL of a-mind-concept\a\ OUTSIDE of a-human-brain comprised of:
1) a-title: the-main-name of the-concept\a\ and
2) a list of attributes: which are the related concepts of the-concept\a\.
[Humn1959Sinagu.2019-12-12]
===
· structured-concept (modelConceptStructured | Mcs) is a-MODEL of a-human-concept\a\ OUTSIDE of a-human-brain comprised of:
1) a-title: the-main-name of the-concept\a\ and
2) a list of attributes: which are the related concepts of the-concept\a\.
[Humn1959Sinagu.2017-11-14]
===
· the-goal of structured-concept creation is the-creation of MONOSEMANTIC, consistent, and complete information, readable by humans AND machines.
[Humn1959Sinagu.2018-03-05]
name::
* McshEngl.senso-concept-(modelConceptSenso)!⇒Mcs,
* McshEngl.Mcs!=senso-concept-(modelConceptSenso),
* McshEngl.Mcs!@McshCor000002,
* McshEngl.Mcs!Attrbase,
* McshEngl.Mcs.lagoElln!=αισθητή-έννοια!η,
* McshEngl.Mcs.lagoZhon!=感官概念-GǎnguānGàiniàn,
* McshEngl.McshCor000002.last.html//dirCor//dirMcsh!⇒Mcs,
* McshEngl.dirCor/McshCor000002.last.html!⇒Mcs,
* McshEngl.Mws'04_sensorial_concept!⇒Mcs,
* McshEngl.Mws'sensorial_concept!⇒Mcs,
* McshEngl.Scpt!⇒Mcs, {2021-03-26}
* McshEngl.concept.sensorial!⇒Mcs,
* McshEngl.conceptSenso!⇒Mcs,
* McshEngl.conceptSensorial!⇒Mcs,
* McshEngl.cptSenso!⇒Mcs,
* McshEngl.cptSns!⇒Mcs,
* McshEngl.cptSrl!⇒Mcs,
* McshEngl.modelConceptSenso!⇒Mcs, {2021-06-07}
* McshEngl.modelConceptSensorial!⇒Mcs, {2019-08-23}
* McshEngl.senso-concept!⇒Mcs, {2021-06-07}
* McshEngl.senso-concept-Mcs!⇒Mcs,
* McshEngl.senso-mind-concept!⇒Mcs,
* McshEngl.sensoconcept!⇒Mcs, {2021-06-05}
* McshEngl.sensorial-concept!⇒Mcs,
* McshEngl.sensorial--mind-concept!⇒Mcs,
* McshEngl.sensorial-mind-concept!⇒Mcs, {2020-05-09}
* McshEngl.structured-concepts!~plural!⇒Mcs,
* McshEngl.structured-senso-concept!⇒Mcs, {2025-10-16}
* SensoConcept!⇒Mcs, {2025-08-21}
====== lagoSinagu:
* McshSngu.Mes!⇒Mcs,
* McshSngu.eniuSensu!⇒Mcs,
* enioSenso!⇒Mcs,
* modelo-enio-senso!⇒Mcs,
====== lagoChinese:
* McshZhon.GǎnguānGàiniàn-感官概念!⇒Mcs,
* McshZhon.感官概念-GǎnguānGàiniàn!⇒Mcs,
====== lagoGreek:
* McshElln.Μεα!⇒Mcs,
* McshElln.αισθητή-έννοια!⇨Μεα,
* McshElln.δομημένη-έννοια!⇨Μεα,
* McshElln.έννοια.αισθητή!⇨Μεα,
* McshElln.μοντέλο-δομημένης-έννοιας!⇨Μεα,
* McshElln.μοντέλοΕννοιαΑισθητή!⇨Μεα,
====== lagoTurkish:
* McshTurk.duyusal-kavram!⇒Mcs,
=== old-timely:
* McshEngl.model.002_sensorial_concept!⇒Mcs, {2020-08-04}
* McshEngl.model.sensorial_concept!⇒Mcs, {2020-08-04}
* McshEngl.material-brain-concept!⇒Mcs, {2012-04-27}
* McshEngl.modelConceptStructured!⇒Mcs, {2016-08-20}
* McshEngl.CBS!=ConceptBrainualSensorial!⇒Mcs,
* sensorial-concept!⇒Mcs, {2008-09-12}
* McshEngl.artificial-konsepto!⇒Mcs, {2006-01-29}
* McshEngl.structured-concept!⇒Mcs, {1995-04}
* McshEngl.koncesto!⇒Mcs,
===
* cptBrnSns,
* structured-information,
attribute::
* Mcs'attribute,
===
* Mcs:generic,
===
* Mcs.specific,
===
* Mcs//whole,
===
* Mcs/part,
===
* Mcs;;parent,
===
* Mcs;child,
description::
× Mcsh-creation: {2026-10-04}
· attribute-of-Mcs\a\ is one or more Mcs\b\ related with Mcs\a\.
[Humn1959Sinagu.2019-03-10]
name::
* McshEngl.attribute-of-Mcs!⇒Mcsattr,
* McshEngl.Mcsattr!=attribute-of-Mcs,
* McshEngl.Mcs'attribute!⇒Mcsattr,
* McshEngl.Mcs'characteristic!⇒Mcsattr,
* McshEngl.Mcs'trait!⇒Mcsattr,
* McshEngl.McsAaAttribute!⇒Mcsattr,
* McshEngl.characteristic-of-Mcs!⇒Mcsattr,
* McshEngl.feature-of-Mcs!⇒Mcsattr,
* McshEngl.value/!RDF!⇒Mcsattr,
====== lagoSinagu:
* atro-a-Mes!⇒Mcsattr, {2019-10-20}
* enioSensosAtro, {2019-10-24}
====== lagoGreek:
* McshElln.χαρακτηριστικό-Μεα!⇒Mcsattr,
description::
× Mcsh-creation: {2026-10-04}
· attribute-relation is the-relation between a-concept\a\ and an-attribute of it\a\.
=== implied yǒu-有!~verbZhon!=RltnMcsThenAttribute:
· _SntxZhon: 我 头疼。 :: _SntxSubj:[Wǒ] _SntxSbjc:[tóuténg]. != I have a headache.
· _SntxZhon: 我 就 一 个 哥哥 。 :: _SntxSubj:[Wǒ] _SntxIndividuality:[jiù] _SntxSbjc:[yī gè gēge]. != I only have one brother.
name::
* McshEngl.Mcsattr'relation!⇒RltnMcsThenAttribute,
* McshEngl.RltnMcsThenAttribute,
* McshEngl.Mcsattr'Mcsattr_relation!⇒RltnMcsThenAttribute,
* McshEngl.Mcs-then-attribute--relation!⇒RltnMcsThenAttribute,
* McshEngl.Mcs'attribute_relation!⇒RltnMcsThenAttribute,
* McshEngl.Mcsattr'attribute_relation!⇒RltnMcsThenAttribute,
* McshEngl.attribute-relation--of-Mcs!⇒RltnMcsThenAttribute,
* McshEngl.relation.attribute_of_Mcs!⇒RltnMcsThenAttribute,
* McshEngl.being-RltnMcsThenAttribute!⇒RltnMcsThenAttribute,
* McshEngl.having-RltnMcsThenAttribute!⇒RltnMcsThenAttribute,
* McshEngl.RltnAttribute-of-Mcs!⇒RltnMcsThenAttribute,
* McshEngl.of!~ConjEngl!⇒RltnMcsThenAttribute,
* McshEngl.property@RDF!⇒RltnMcsThenAttribute,
* McshEngl.verb.be!~verbEnglC!⇒RltnMcsThenAttribute,
* McshEngl.verb.have!~verbEnglC!⇒RltnMcsThenAttribute,
====== lagoSinagu:
* rao-atro!⇒RltnMcsThenAttribute,
* a!~ConjSngu!⇒RltnMcsThenAttribute,
====== lagoChinese:
* McshZhon.dòngcí.yǒu_有!⇒RltnMcsThenAttribute,
* McshZhon.yǒu-有!~verbZhon!⇒RltnMcsThenAttribute,
* McshZhon.有-yǒu!~verbZhon!⇒RltnMcsThenAttribute,
====== lagoGreek:
* McshElln.σχέση-χαρακτηριστικού-Μεα!⇒RltnMcsThenAttribute,
description::
× Mcsh-creation: {2026-10-04}
name::
* McshEngl.Mcsattr'generic_specific_tree,
generic-tree::
* McshEngl.Mcsattr:generic,
===
* Mcs:generic,
* concept:generic,
* ...entity:generic,
specific-tree::
* McshEngl.Mcsattr.specific,
=== alphabetically:
* Mcsattr.author!@McshCor000002#idMcsattWhlNAthr,
* Mcsattr.complement!@McshCor000002#idMcsattDvsnclmt,
* Mcsattr.McsattDefinition!@McshCor000002#idMcsattDfn,
* Mcsattr.description!@McshCor000002#idMcsattDsn,
* Mcsattr.division!@McshCor000002#idMcsattDvsn,
* Mcsattr.divisionParts!@McshCor000002#idMcsattPrtdvn,
* Mcsattr.divisionTwo!@McshCor000002#idMcsattDvsnDhm,
* Mcsattr.doing!@McshCor000002#idMcsattDng,
* Mcsattr.doingNo!@McshCor000002#idMcsattDngN,
* Mcsattr.environment!@McshCor000002#idMcsattWhlN,
* Mcsattr.evaluation!@McshCor000002#idMcsattWhlNEval,
* Mcsattr.evoluting!@McshCor000002#idMcsattEvlg,
* Mcsattr.generic_chain!@McshCor000002#idMcsattGncchn,
* Mcsattr.generic!@McshCor000002#idMcsattGnc,
* Mcsattr.inherited_from!@McshCor000002#idMcsattInhf,
* Mcsattr.inherited_fromNo!@McshCor000002#idMcsattInhfN,
* Mcsattr.inherited_to!@McshCor000002#idMcsattInht,
* Mcsattr.inherited_toNo!@McshCor000002#idMcsattInht,
* Mcsattr.name!@McshCor000002#idMcsattNam,
* Mcsattr.part!@McshCor000002#idMcsattPrt,
* Mcsattr.partNo!@McshCor000002#idMcsattPrtN,
* Mcsattr.specific_chain,
* Mcsattr.specific-att!@McshCor000002#idMcsattsptr,
* Mcsattr.specifics_division,
* Mcsattr.supporter-att!@McshCor000002#idMcsattWhlNSptr,
* Mcsattr.title!@McshCor000002#idMcsattPrtTtl,
* Mcsattr.whole_chain!@McshCor000002#idMcsattWhlchn,
* Mcsattr.whole!@McshCor000002#idMcsattWhl,
description::
× Mcsh-creation: {2026-10-04}
* part-att,
* partNo-att,
description::
× Mcsh-creation: {2026-10-04}
· on generic:
* generic-att,
* specific-att,
description::
× Mcsh-creation: {2026-10-04}
· on doing:
* doing-att,
* doingNo-att,
description::
× Mcsh-creation: {2026-10-04}
· on inherited-from:
* inherited-from-att,
* inherited-fromNo-att,
description::
× Mcsh-creation: {2026-10-04}
· this division has NO meaning, because ALL att of a-generic inherited to a-specific.
· the-specific is the-one that has EXTRA att.
[Humn1959Sinagu.2020-01-11]
===
· on inherited-to:
* inherited-to-att,
* inherited-toNo-att,
description::
× Mcsh-creation: {2026-10-04}
· division--of--Mcs-attributes\a\-(part, partNo, specific, all-attributes) is the-SET of attributes of the-Mcs that make-up the-attributes\a\ divided on ONE attribute.
· there-are no overlappings and no holes in the-attributes of the-division.
· the-attributes of one-concept can-have many divisions.
name::
* McshEngl.division-Mcsattr!⇒McsattDivision,
* McshEngl.McsattDivision!=division-Mcsattr,
* McshEngl.Mcsattr.division!⇒McsattDivision,
* McshEngl.Mcs'division_attribute!⇒McsattDivision,
* McshEngl.division--of--Mcs-atts!⇒McsattDivision,
description::
× Mcsh-creation: {2026-10-04}
· in ONE division all the-other attributes of an-attribute\a\ is the-complement of attribute\a\ ON this division.
name::
* McshEngl.Mcs_complement,
* McshEngl.McsattDivision'complement_of_att!⇒Mcs_complement,
* McshEngl.Mcs-complement!⇒Mcs_complement,
* McshEngl.Mcsattr'complement!⇒Mcs_complement,
* McshEngl.Mcs'complement_of_att!⇒Mcs_complement,
* McshEngl.Mcsattr.complement_of_att!⇒Mcs_complement,
* McshEngl.complement!⇒Mcs_complement,
* McshEngl.complement-of--Mcsattr!⇒Mcs_complement,
====== lagoSinagu:
* uo!=complement-of-att,
====== lagoGreek:
* McshElln.επίθετο.συμπληρωματικός!⇒Mcs_complement,
* McshElln.συμπληρωματικός!~AdjeElln!⇒Mcs_complement,
====== lagoTurkish:
* McshTurk.tamamlayıcı!⇒Mcs_complement,
======
"Of course! The term "complement" in mathematics (like the complement of a set or an angle) has interesting translations across languages, often rooted in the same Latin idea but adapted to each language's structure.
Here is a breakdown of "complement" in various world languages, focusing on the mathematical context.
### **Romance Languages**
These languages derive their terms directly from Latin ***complēmentum*** ("that which fills up").
* **Spanish:** el complemento
* *El complemento del conjunto A.* (The complement of set A.)
* **French:** le complément
* *Le complément d'un angle de 30° est 60°.*
* **Italian:** il complemento
* **Portuguese:** o complemento
* **Romanian:** complementul
### **Germanic Languages**
* **German:** das Komplement (formal, for sets, angles)
* *Das Komplement der Menge.*
* **Note:** In probability/statistics, *das Gegenereignis* ("counter-event") is often used for the complement of an event.
* **Dutch:** het complement
* **Swedish:** komplementet
* **Danish/Norwegian:** komplementet
### **Slavic Languages**
* **Russian:** дополнение (*dopolneniye*)
* *Дополнение множества.* (*Dopolneniye mnozhestva.*)
* Literally means "addition, supplement."
* **Polish:** dopełnienie
* **Czech:** doplněk
* **Serbo-Croatian:** komplement / комплемент, but also допуна / *dopuna*
### **Asian Languages**
* **Japanese:** 補集合 (*ho-shūgō*) for "complement of a set."
* 補 (*ho*) means "supplement." 集合 (*shūgō*) means "set."
* For angles: 余角 (*yo-kaku*) for "complementary angle."
* **Chinese (Mandarin):** 补集 (*bǔ jí*) for "complement set."
* 补 (*bǔ*) means "mend, repair, supplement." 集 (*jí*) means "set."
* Complementary angles: 余角 (*yú jiǎo*).
* **Korean:** 여집합 (*yeo-jiphap*) for "complement set."
* 여 (*yeo*) from 餘 meaning "remaining." 집합 (*jiphap*) means "set."
* **Hindi:** पूरक (*pūrak*)
* Derived from Sanskrit, meaning "that which fills" or "makes complete." Used for sets and angles.
* **Arabic:** المُتْـمَّة (*al-mutimma*)
* For sets: مكمل المجموعة (*mukammal al-majmū'a*).
### **Uralic & Other Languages**
* **Finnish:** komplementti (used in mathematics), but also **täydennys** ("the act of completing").
* **Hungarian:** komplementer (in set theory).
### **Key Linguistic Insight: Angles vs. Sets**
Many languages use **different words** for complementary angles vs. the complement of a set, even though the mathematical concept is the same.
* **English:** Complementary (angles) vs. Complement (of a set).
* **Japanese:** 余角 (*yokaku*) vs. 補集合 (*hoshūgō*).
* **Chinese:** 余角 (*yú jiǎo*) vs. 补集 (*bǔ jí*).
* **French:** Angles *complémentaires* vs. *complément* d'un ensemble.
### **Etymology**
The English word comes via Old French from Latin **complēmentum**, from **complēre** "to fill up, complete." This core meaning of "that which completes" is visible in almost all the translations above.
### **Summary Table**
| Language | Term (Mathematical Complement) | Key Notes |
| **Latin** | complēmentum | The source for many languages. |
| **Spanish** | el complemento | Direct inheritance. |
| **French** | le complément | Direct inheritance. |
| **German** | das Komplement | Formal math term; *Gegenereignis* in probability. |
| **Russian** | дополнение (dopolneniye) | Literally "addition/supplement." |
| **Arabic** | المُتْـمَّة (al-mutimma) | For angles; مكمل (mukammal) for sets. |
| **Mandarin** | 补集 (bǔ jí) | For sets. 余角 (yú jiǎo) for angles. |
| **Japanese** | 補集合 (ho-shūgō) | For sets. 余角 (yo-kaku) for angles. |
| **Hindi** | पूरक (pūrak) | Used for both sets and angles. |
This demonstrates how a fundamental mathematical concept is expressed through the unique lexical and semantic systems of languages worldwide."
[{2025-12-16 retrieved} https://chat.deepseek.com/a/chat/s/256283a7-7544-421a-95fe-d71336fbffa2]
description::
× Mcsh-creation: {2026-10-04}
name::
* McshEngl.Mcs_complement'generic_specific_tree,
generic-tree::
* McshEngl.Mcs_complement:generic,
===
* Mcsattr:generic,
* ...entity:generic,
specific-tree::
* McshEngl.Mcs_complement.specific,
===
* attributes-complement,
* parts-complement,
* specifics-complement,
description::
× Mcsh-creation: {2026-10-04}
· attributes-complement of Mcsattr is a-complement that makes-up all the-attributes of the-Mcs.
name::
* McshEngl.Mcs_complement.attributes_in_division,
* McshEngl.Mcs_complement.attributes,
* McshEngl.attributes-complement--of-Mcs,
* McshEngl.complement.attributes_of_Mcs,
====== lagoSinagu:
* uatro-a-Mes!=complement.attributes,
* uo-atro-a-Mes!=complement.attributes,
description::
× Mcsh-creation: {2026-10-04}
· parts-complement of att\a\ in a-division is the-complement-of-att\a\ in a-part-division.
name::
* McshEngl.Mcs_complement.parts_in_division,
* McshEngl.Mcs'parts_complement__of_att,
* McshEngl.Mcs_complement.parts,
* McshEngl.Mcs'parts_complement,
* McshEngl.complement.parts_of_Mcs,
* McshEngl.partial-complement,
* McshEngl.parts-complement--of-Mcs,
====== lagoSinagu:
* ujo-a-Mes!=complement.parts,
* uo-jo-a-Mes!=complement.parts,
description::
× Mcsh-creation: {2026-10-04}
· specific-complement-of-att\a\ IN a-specifics-division-of-a-Mcs\b\ is the-complement-of-att\a\ in the-specifics-division\b\.
· example:
· the-SystMolecules has a-specifics-division: pure, pureNo.
· the-specific-complement-of-pure is the-pureNo.
name::
* McshEngl.Mcs_complement.specifics_in_division,
* McshEngl.Mcs'specifics_complement__of_att,
* McshEngl.Mcs_complement.specifics,
* McshEngl.Mcs-specifics-complement,
* McshEngl.complement.specifics_of_Mcs,
* McshEngl.specific-complement--of-Mcs,
* McshEngl.specifics-complement--of-Mcs,
====== lagoSinagu:
* ugo-a-Mes!=complement.specifics,
* uo-go-a-Mes!=complement.specifics,
description::
× Mcsh-creation: {2026-10-04}
name::
* McshEngl.McsattDivision'generic_specific_tree,
generic-tree::
* McshEngl.McsattDivision:generic,
===
* Mcsattr:generic,
* ...entity:generic,
specific-tree::
* McshEngl.McsattDivision.specific,
===
* McsattDivision.McsdvsnTwo!@McshCor000002#idMcsattDvsnDhm,
* McsattDivision.McsdvsnTri!@McshCor000002#idMcsattDvsnThm,
* doing-att-division,
===
* McsattDivision.McsattPartDivision!@McshCor000002#idMcsattPrtdvn,
* McsattDivision.McsattSpecificsDivision!@McshCor000002#idMcsattWhlNSpcdvn,
description::
× Mcsh-creation: {2026-10-04}
· dichotomous-division is a-division with 2 members, the-one that has the-attribute and the-other that has not.
· it is the-simplest and clearest one.
name::
* McshEngl.dichotomous-division--Mcsattr!⇒McsdvsnTwo,
* McshEngl.McsdvsnTwo!=dichotomous-division--Mcsattr,
* McshEngl.Mcsattr.dichotomous_division!⇒McsdvsnTwo,
* McshEngl.Mcsattr.division.dichotomous!⇒McsdvsnTwo,
* McshEngl.McsattDivision.dichotomous!⇒McsdvsnTwo,
* McshEngl.division.dichotomous_Mcsattr!⇒McsdvsnTwo,
====== lagoGreek:
* McshElln.διχοτομική-διαίρεση!⇒McsdvsnTwo,
description::
× Mcsh-creation: {2026-10-04}
· like a-dichotomous-division we have clear division in 3 entities:
· past, present, future,
· male, maleNo-(female), maleBo-(both male and female).
[Humn1959Sinagu.2019-07-19]
* ordered--trichotomous-division,
* orderedNo-trichotomous-division,
name::
* McshEngl.McsattDivision.trichotomous!⇒McsdvsnTri,
* McshEngl.trihotomous-division--of-Mcs!⇒McsdvsnTri,
* McshEngl.McsdvsnTri!=trihotomous-division--of-Mcs,
====== lagoGreek:
* McshElln.τριχοτομική-διαίρεση!⇒McsdvsnTri,
description::
× Mcsh-creation: {2026-10-04}
· there-is-no "attributes-division",
because the-same entity, we see different views: generic-specific, whole-part. {2026-10-21}
· attributes-division of Mcs\a\ is a-division of its\a\ attributes.
name::
* McshEngl.attributes-division-of-Mcs,
* McshEngl.McsattDivision.attributes,
description::
× Mcsh-creation: {2026-10-04}
· doing-division--Mcsattr is a-dichotomous-division of a-Mcs's attributes in doing and doingNo.
name::
* McshEngl.division.doing_Mcsattr,
* McshEngl.Mcsattr.division.doing,
* McshEngl.Mcs_division.doing,
description::
× Mcsh-creation: {2026-10-04}
· parts-division--Mcsattr is a-division of a-Mcs's parts.
name::
* McshEngl.parts-division--Mcsattr!⇒McsdvsnPrts,
* McshEngl.McsdvsnPrts!=parts-division--Mcsattr,
* McshEngl.Mcs_division.parts!⇒McsdvsnPrts,
* McshEngl.Mcsattr.division.parts!⇒McsdvsnPrts,
* McshEngl.McsattDivision.part_attributes!⇒McsdvsnPrts,
description::
× Mcsh-creation: {2026-10-04}
· part-att of Mcs\a\ is an-att we perceive as internal|intrinsic.
name::
* McshEngl.part-Mcsattr!⇒McsattPart,
* McshEngl.McsattPart!=part-Mcsattr,
* McshEngl.externalNo-Mcsattr!⇒McsattPart,
* McshEngl.internal-Mcsattr!⇒McsattPart,
* McshEngl.intrinsic-Mcsattr!⇒McsattPart,
* McshEngl.Mcs'externalNo_attribute!⇒McsattPart,
* McshEngl.Mcs'internal_attribute!⇒McsattPart,
* McshEngl.Mcs'part!⇒McsattPart,
* McshEngl.Mcsattr.externalNo!⇒McsattPart,
* McshEngl.Mcsattr.internal!⇒McsattPart,
* McshEngl.Mcsattr.part!⇒McsattPart,
* McshEngl.Mcs-part-att!⇒McsattPart, {2019-04-08}
* McshEngl.Mcsattr.part_instance.part!⇒McsattPart,
====== lagoSinagu:
* atro-jo-a-Mes!⇒McsattPart,
description::
× Mcsh-creation: {2026-10-04}
· part-relation of Mcs\a\ is the-relation between the-Mcs\a\ and a-part of it\a\.
name::
* McshEngl.RltnMcsThenPart,
* McshEngl.McsattPart'part_relation!⇒RltnMcsThenPart,
* McshEngl.McsattPart'relation!⇒RltnMcsThenPart,
* McshEngl.McsattPart-relation!⇒RltnMcsThenPart,
* McshEngl.part-relation--of-Mcs!⇒RltnMcsThenPart,
* McshEngl.relation.part_of_Mcs!⇒RltnMcsThenPart,
* McshEngl.RltnPart!⇒RltnMcsThenPart,
====== lagoSinagu:
* ja!~ConjSngu!⇒RltnMcsThenPart,
* rao-jo!=RltnPart!⇒RltnMcsThenPart, {2023-07-21}
description::
× Mcsh-creation: {2026-10-04}
name::
* McshEngl.McsattPart'generic_specific_tree,
generic-tree::
* McshEngl.McsattPart:generic,
===
* Mcsattr:generic,
* ...entity:generic,
specific-tree::
* McshEngl.McsattPart.specific,
===
* part-list-McsattPart,
* part-instance-McsattPart,
* title-McsattPart,
* overview-McsattPart,
* description-McsattPart,
* name-McsattPart,
* definition-McsattPart,
* part-division-McsattPart,
description::
× Mcsh-creation: {2026-10-04}
· part-list-att of Mcs is a-set of part-att.
name::
* McshEngl.McsattPart.list,
* McshEngl.part-list-att--of-Mcs,
description::
× Mcsh-creation: {2026-10-04}
· part-instance--Mcs\a\-att is a-genericNo part-attribute.
name::
* McshEngl.Mcsattr.part_instance,
* McshEngl.McsattPart.instance,
* McshEngl.part-instance--Mcsattr,
description::
× Mcsh-creation: {2026-11-03}
·
name::
* McshEngl.title-Mcsattr!⇒McsattTitle,
* McshEngl.McsattTitle!=title-Mcsatt,
* McshEngl.Mcsattr.title!⇒McsattTitle,
* McshEngl.McsattPart.title!⇒McsattTitle,
description::
× Mcsh-creation: {2026-10-04}
· overview-of-Mcs is a-part-attribute which contains the-description and the-name attributes.
[Humn1959Sinagu.2018-11-03]
name::
* McshEngl.overview-of-Mcsattr!⇒McsattOverview,
* McshEngl.McsattOverview!=overview-of-Mcsattr,
* McshEngl.McsattPart.overview!⇒McsattOverview,
* McshEngl.Mcsattr.overview!⇒McsattOverview,
description::
× Mcsh-creation: {2026-10-04}
· description--Mcsattr is Mcs-TEXT that IDENTIFIES a-Mcs.
· a-definition UNIQUELY IDENTIFIES a-Mcs.
[Humn1959Sinagu.2017-12-22]
name::
* McshEngl.McsattPart.description!⇒McsattDescription,
* McshEngl.description-Mcsattr!⇒McsattDescription,
* McshEngl.McsattDescription!=description-Mcsattr,
* McshEngl.Mcsattr.description!⇒McsattDescription,
* McshEngl.Mcs/description!⇒McsattDescription,
* McshEngl.Mcs'description_attribute!⇒McsattDescription,
description::
× Mcsh-creation: {2026-10-04}
· our knowledge is-structured in 3 fundamental structures: the-whole-part-tree and the-generic-specific-tree and the-evolutionary-tree.
· every Mcs must-have 6 definitions: generic, specific, whole, part, parent, child.
[Humn1959Sinagu.{2023-04-12}]
===
· definition-att of Mcs is Mcs-TEXT that UNIQUELY IDENTIFY a-Mcs in the shortest way.
· a-Mcs has more than one definition because our knowledge is-structured at least in two fundamental structures: the-whole-part-tree and the-generic-specific-tree.
· every Mcs must-have 4 definitions: generic, specific, whole, part.
· description is TEXT that IDENTIFY a-Mcs.
· a-definition is formal if it is readable and by machines.
name::
* McshEngl.McsattPart.definition!⇒McsattDefinition,
* McshEngl.definition-Mcsattr!⇒McsattDefinition,
* McshEngl.McsattDefinition!=definition-att-of-Mcs,
* McshEngl.definition-att--of-Mcs!⇒McsattDefinition,
* McshEngl.Mcsattr.definition!⇒McsattDefinition,
* McshEngl.Mcs/definition!⇒McsattDefinition,
* McshEngl.definition-of-Mcs!⇒McsattDefinition,
* McshEngl.dfn-of-Mcs!⇒McsattDefinition,
====== lagoChinese:
* McshZhon.dìngyì-定义-(定義)!⇒McsattDefinition,
* McshZhon.定义-(定義)-dìngyì!⇒McsattDefinition,
====== lagoGreek:
* McshElln.ορισμός!ο!⇒McsattDefinition,
======
"Here is **“definition” grouped by etymology**, showing whether each term comes from **Latin/Greek scholarly tradition** or from **native lexical roots**.
---
## 1️⃣ Latin *definīre* → “to set bounds, delimit”
Spread mainly through **Romance languages** and later adopted by many others via academia.
* **English:** *definition*
* **French:** *définition*
* **Spanish:** *definición*
* **German:** *Definition*
➡️ These are **direct borrowings** (or near-borrowings) from Latin, often via French or scholarly usage.
---
## 2️⃣ Greek roots (native, not borrowed from Latin)
Greek does **not** use the Latin-derived word.
* **Greek:** *ορισμός* (*orismós*)
* from *ὁρίζω* = “to set a boundary, determine”
➡️ Interestingly, Greek expresses the **same core metaphor** (setting limits) but with **native Greek morphology**.
---
## 3️⃣ Semitic root “to make known / clarify”
Derived from roots meaning **explanation or clarification**, not boundary-setting.
* **Arabic:** *تعريف* (*taʿrīf*) ← root ع-ر-ف (“to know, recognize”)
* **Hebrew:** *הגדרה* (*hagdará*) ← root ג-ד-ר (“to fence, enclose”)
➡️ Note:
* Arabic emphasizes **making something known**
* Hebrew emphasizes **enclosing / bounding**, closer to Latin–Greek metaphor
---
## 4️⃣ Sino-Xenic (Classical Chinese scholarly compound)
Used across East Asia, originally from **Classical Chinese**.
* **Chinese:** 定义 (*dìngyì*) = “fix + meaning”
* **Japanese:** 定義 (*teigi*)
* **Korean:** 정의 (*jeong-ui*)
➡️ All three share the **same characters and concept**, adapted phonetically.
---
## 5️⃣ Native Finno-Ugric formations
Built from **indigenous verbs**, not borrowed.
* **Finnish:** *määritelmä* ← “to determine/specify”
* **Hungarian:** *meghatározás* ← “to delimit, set bounds”
➡️ Semantically close to Latin/Greek, but **independently formed**.
---
## 6️⃣ Turkic native root
Plain, everyday verb → noun.
* **Turkish:** *tanım* ← *tanımak* (“to recognize, identify”)
➡️ Focuses on **recognition**, not boundaries.
---
## 7️⃣ Dravidian native formation
Descriptive, non-borrowed structure.
* **Tamil:** *வரையறை* (*varaiyaṟai*)
* *varai* = boundary/limit
* *aṟai* = statement
➡️ Conceptually very close to **Greek and Latin**, but fully native.
---
## 🧠 Big Picture Insight
Across languages, **“definition” tends to mean one of three things**:
1. **Setting boundaries** → Latin, Greek, Hebrew, Tamil
2. **Making meaning fixed/explicit** → Chinese-based terms
3. **Making something known/recognized** → Arabic, Turkish
If you want, I can:
* map these metaphors visually
* compare **legal vs mathematical definitions** across cultures
* or analyze how this affects **legal drafting and interpretation** (useful given your interest in legal English)."
[{2025-12-20 retrieved} https://chatgpt.com/c/6946491d-b95c-8330-9378-2a56ccff6b79]
description::
× Mcsh-creation: {2026-10-04}
· generic-definition is a-definition FROM a-specific-concept.
· creates a-generic-concept.
name::
* McshEngl.McsattDefinition.generic,
* McshEngl.generic-McsattDefinition,
description::
× Mcsh-creation: {2026-10-04}
· specific-definition is a-definition FROM a-generic-concept.
· creates a-specific-concept.
name::
* McshEngl.McsattDefinition.specific,
* McshEngl.specific-McsattDefinition,
description::
× Mcsh-creation: {2026-10-04}
· whole-definition is a-definition FROM part-concepts.
· creates a-whole-concept.
name::
* McshEngl.McsattDefinition.whole,
* McshEngl.whole-McsattDefinition,
description::
× Mcsh-creation: {2026-10-04}
· part-definition is a-definition FROM a-whole-concept.
· creates a-part-concept.
name::
* McshEngl.McsattDefinition.part,
* McshEngl.part-McsattDefinition,
description::
× Mcsh-creation: {2026-10-04}
· creates a-parent-concept in the-evolutionary-tree.
name::
* McshEngl.McsattDefinition.parent,
* McshEngl.parent-McsattDefinition,
description::
× Mcsh-creation: {2026-10-04}
· creates a-child-concept in the-evolutionary-tree.
name::
* McshEngl.child-McsattDefinition,
* McshEngl.McsattDefinition.child,
description::
× Mcsh-creation: {2026-10-04}
· analytic-definition is any specific or part definition.
name::
* McshEngl.analytic-definition,
* McshEngl.McsattDefinition.analytic,
description::
× Mcsh-creation: {2026-10-04}
· synthetic-definition is any generic or whole definitions.
name::
* McshEngl.McsattDefinition.synthetic,
* McshEngl.synthetic-McsattDefinition,
description::
× Mcsh-creation: {2026-10-04}
· part-division--Mcsattr is a-division of the-part-attributes.
name::
* McshEngl.McsattPart.part_division!⇒McsattPartDivision,
* McshEngl.McsattPartDivision,
* McshEngl.part-division--Mcsattr!⇒McsattPartDivision,
* McshEngl.division.part_Mcsattr!⇒McsattPartDivision,
* McshEngl.Mcs'division.part!⇒McsattPartDivision,
* McshEngl.McsattDivisionPart!⇒McsattPartDivision,
* McshEngl.McsattPart.division!⇒McsattPartDivision,
* McshEngl.Mcsattr.part_division!⇒McsattPartDivision,
* McshEngl.partial-division--Mcsattr!⇒McsattPartDivision,
generic-tree::
* McshEngl.McsattPartDivision:generic,
===
* McsattDivision:generic,
* Mcsattr:generic,
* ...entity:generic,
description::
× Mcsh-creation: {2026-10-04}
· partNo--Mcsattr is the-complement of part-attribute.
name::
* McshEngl.McsattPartNo,
* McshEngl.partNo-Mcsattr!⇒McsattPartNo,
* McshEngl.Mcs'external_attribute!⇒McsattPartNo,
* McshEngl.Mcs'internalNo_attribute!⇒McsattPartNo,
* McshEngl.Mcsattr.external!⇒McsattPartNo,
* McshEngl.Mcsattr.internalNo!⇒McsattPartNo,
* McshEngl.Mcsattr.partNo!⇒McsattPartNo,
* McshEngl.external-Mcsattr!⇒McsattPartNo,
* McshEngl.extrinsic-Mcsattr!⇒McsattPartNo,
* McshEngl.intrinsicNo-Mcsattr!⇒McsattPartNo,
* environment--Mcsattr!⇒McsattPartNo, {2019-03-09}
* McshEngl.Mcsattr.part_instance.partNo!⇒McsattPartNo,
====== lagoSinagu:
* atro-joUgo-a-Mes!⇒McsattPartNo,
description::
× Mcsh-creation: {2026-10-04}
name::
* McshEngl.McsattPartNo'generic_specific_tree,
generic-tree::
* McshEngl.McsattPartNo:generic,
===
* Mcsattr:generic,
* Mcs:generic,
* concept:generic,
* RltnAttributeThenEntity:generic,
* ...entity:generic,
specific-tree::
* McshEngl.McsattPartNo.specific,
===
description::
× Mcsh-creation: {2026-10-04}
· on whole:
* whole--envt-att,
* wholeNo--envt-att,
description::
× Mcsh-creation: {2026-10-04}
· whole-att of Mcs\a\ is another Mcs\b\ which has as part the-Mcs\a\.
name::
* McshEngl.McsattWhole,
* McshEngl.Mcs-whole!⇒McsattWhole,
* McshEngl.Mcsattr.partNo.whole!⇒McsattWhole,
* McshEngl.Mcsattr.whole!⇒McsattWhole,
* McshEngl.whole-Mcsattr!⇒McsattWhole, {2019-03-09}
* McshEngl.whole-of-Mcs!⇒McsattWhole,
====== lagoSinagu:
* atro-co-a-Mes!=McsattWhole,
description::
× Mcsh-creation: {2026-10-04}
· whole-chain of Mcs\a\ is the-chain of whole-concepts of Mcs\a\ from parent-whole to most-whole-concept.
name::
* McshEngl.whole-chain--Mcsattr!⇒McsattWhole_chain,
* McshEngl.McsattWhole_chain!=whole-chain--Mcsattr,
* McshEngl.Mcsattr.whole_chain!⇒McsattWhole_chain,
* McshEngl.McsattWhole.whole_chain!⇒McsattWhole_chain,
description::
× Mcsh-creation: {2026-10-04}
· wholeNo = environment. {2026-04-23}
· wholeNo--Mcsattr is a-partNo-att which is not whole of this Mcs.
· a-wholeNo, partNo attribute.
name::
* McshEngl.environment-Mcsattr!⇒McsattEnvironment,
* McshEngl.McsattEnvironment!=environment-Mcsattr,
* McshEngl.Mcs'envt!⇒McsattEnvironment,
* McshEngl.Mcsattr.wholeNo!⇒McsattEnvironment,
* McshEngl.wholeNo-Mcsattr!⇒McsattEnvironment,
* Mcsattr.partNo.wholeNo!⇒McsattEnvironment,
* partNo.wholeNo_Mcsattr!⇒McsattEnvironment,
* wholeNo.partNo_Mcsattr!⇒McsattEnvironment,
====== lagoSinagu:
* atro-coUgo-a-Mes!⇒McsattEnvironment,
description::
× Mcsh-creation: {2026-10-04}
name::
* McshEngl.McsattEnvironment'generic_specific_tree,
generic-tree::
* McshEngl.McsattEnvironment:generic,
===
* Mcsattr:generic,
* ...entity:generic,
specific-tree::
* McshEngl.McsattEnvironment.specific,
===
* author-of-Mcs,
* evaluation-of-Mcs,
* referent-of-Mcs,
* supporter-of-Mcs,
description::
× Mcsh-creation: {2026-10-04}
· a-concept is a-brainin-model of entities\a\.
· a-structured-concept is a-computer-model of a-concept.
· archetype-of-a-structured-concept is the-set of entities\a\.
[Humn1959Sinagu.2018-01-07]
===
· referent-of-Mcs is the-entity that the-Mcs models.
· every concept models an-entity (its referent).
· the-referent of a-concept\a\ and the-referent of the-Mcs that models that concept\a\ are the-same.
name::
* McshEngl.archetype-Mcsattr!⇒McsattArcho,
* McshEngl.McsattArcho!=archetype--Mcsattr,
* McshEngl.Mcs'archetype!⇒McsattArcho,
* McshEngl.Mcsattr.archetype!⇒McsattArcho,
* McshEngl.Mcsattr.referent!⇒McsattArcho,
* McshEngl.Mcs'referent!⇒McsattArcho,
* McshEngl.referent-Mcsattr!⇒McsattArcho,
* McshEngl.McsattEnvironment.archetype!⇒McsattArcho,
whole-tree::
* McshEngl.McsattArcho//whole,
===
* environment--Mcsattr,
generic-tree::
* McshEngl.McsattArcho:generic,
===
* Mcsattr:generic,
* ...entity:generic,
description::
× Mcsh-creation: {2026-10-04}
· evaluation--Mcsattr is the-cons and pros of the-Mcs.
name::
* McshEngl.evaluation-Mcsattr!⇒McsattEvaluation,
* McshEngl.McsattEvaluation!=evaluation-Mcsattr,
* McshEngl.Mcsattr.evaluation!⇒McsattEvaluation,
* McshEngl.Mcsattr.wholeNo.evaluation!⇒McsattEvaluation,
* McshEngl.McsattEnvironment.evaluation!⇒McsattEvaluation,
description::
× Mcsh-creation: {2026-10-04}
· supporter-of-Mcs is the-entity (human, group of humans, machine) that consider this Mcs as true.
name::
* McshEngl.supporter-of-Mcsattr!⇒McsattSupporter,
* McshEngl.McsattSupporter!=supporter-of-Mcsattr,
* McshEngl.Mcsattr.holder!⇒McsattSupporter,
* McshEngl.Mcsattr.supporter!⇒McsattSupporter,
* McshEngl.Mcs'supporter!⇒McsattSupporter,
* McshEngl.McsattEnvironment.supporter!⇒McsattSupporter,
description::
× Mcsh-creation: {2026-10-04}
· author is the-supporter who created the-Mcs.
name::
* McshEngl.author-of-Mcsattr!⇒McsattAuthor,
* McshEngl.McsattAuthor!=author-of-Mcs,
* McshEngl.Mcs'author!⇒McsattAuthor,
* McshEngl.Mcs'creator!⇒McsattAuthor,
generic-tree::
* McshEngl.McsattAuthor:generic,
===
* Mcsattr:generic,
* ...entity:generic,
description::
× Mcsh-creation: {2026-10-04}
· meta-info--Mcsattr is a-Mcsattr that presents additional info about the-Mcs itself, like times visited, versions, ...
name::
* McshEngl.meta-info--Mcsattr!⇒McsattMeta,
* McshEngl.McsattMeta!=meta-info--Mcsattr,
* McshEngl.Mcsattr.meta_info!⇒McsattMeta,
* McshEngl.Mcsattr.wholeNo.meta_info!⇒McsattMeta,
* McshEngl.McsattEnvironment.meta_info!⇒McsattMeta,
description::
× Mcsh-creation: {2026-10-04}
· doing--Mcsattr is LISTS of a-Mcsattr which are doings|processes.
name::
* McshEngl.doing-Mcsattr!⇒McsattDoing,
* McshEngl.McsattDoing!=doing-Mcsattr,
* McshEngl.Mcsattr.doing!⇒McsattDoing,
* McshEngl.Mcsattr.doing_instance.doing!⇒McsattDoing,
description::
× Mcsh-creation: {2026-10-04}
· evoluting--Mcsattr is the-attribute that describes the-Mcs over time, its stages.
· evoluting comprises the-evoluting of the-Mcs itself and the-evoluting of its referent.
· everything is-born and die.
· evoluting is a-doing-attribute, not a-specific one because specifics behave like the-evolution of their generic.
name::
* McshEngl.evoluting-Mcsattr!⇒McsattEvoluting,
* McshEngl.McsattEvoluting!=evoluting-Mcsattr,
* McshEngl.Mcsattr.specific'evoluting!⇒McsattEvoluting,
description::
× Mcsh-creation: {2026-10-04}
· doingNo--Mcsattr is the-complement doing-att.
name::
* McshEngl.doingNo-Mcsattr!⇒McsattDoingNo,
* McshEngl.McsattDoingNo!=doingNo-Mcsattr,
* McshEngl.Mcsattr.doingNo!⇒McsattDoingNo,
* McshEngl.Mcsattr.doing_instance.doingNo!⇒McsattDoingNo,
description::
× Mcsh-creation: {2026-10-04}
· generic-att of Mcs\a\ is another Mcs\b\ whose\b\ all attributes are and attributes of Mcs\a\ but not the-opposite.
· the-Mcs\a\ is a-specific-of-Mcs\b\.
· the-referent of a-generic-of-Mcs is a-superset of the-referent-of-Mcs.
name::
* McshEngl.generic-of-Mcs!⇒McsattGeneric,
* McshEngl.McsattGeneric!=generic-of-Mcs,
* McshEngl.generic-att--of-Mcs!⇒McsattGeneric,
* McshEngl.Mcsattr.generic!⇒McsattGeneric,
* McshEngl.Mcs'generic_attribute!⇒McsattGeneric,
* McshEngl.Mcsattr.generic_instance.generic!⇒McsattGeneric,
====== lagoSinagu:
* atro-ko-a-Mes!=generic-att--of-Mcs,
description::
× Mcsh-creation: {2026-10-04}
· generic-chain of Mcs\a\ is the-chain of generic-concepts of Mcs\a\ from parent-generic to most-generic-concept.
name::
* McshEngl.generic-chain--Mcsattr!⇒Mcsgnch,
* McshEngl.Mcsgnch!=generic-chain--Mcsattr,
* McshEngl.generic-path--Mcsattr!⇒Mcsgnch,
* McshEngl.Mcsattr.generic_chain!⇒Mcsgnch,
* McshEngl.McsattGeneric'generic_chain!⇒Mcsgnch,
generic-tree::
* McshEngl.Mcsgnch:generic,
===
* Treenodepath:generic,
* ...entity:generic,
===
* Mcsattr:generic,
* ...entity:generic,
description::
× Mcsh-creation: {2026-10-04}
· specific-att of Mcs\a\ is another Mcs\b\ if all the-attributes of Mcs\a\ are and attributes of Mcs\b\ and not the-opposite.
· the-Mcs\a\ is a-generic-of-Mcs\b\.
· also, the-referent of a-specific is a-subset of the-referent of its generic.
name::
* McshEngl.specific-Mcsattr!⇒McsattSpecific,
* McshEngl.McsattSpecific!=specific-type--Mcsattr,
* McshEngl.Mcsattr.specific_type!⇒McsattSpecific,
* McshEngl.specific-type-att-of-Mcs!⇒McsattSpecific,
* McshEngl.specific-type-of-Mcs!⇒McsattSpecific,
* McshEngl.Mcsattr.generic_instance.specific_type!⇒McsattSpecific,
====== lagoSinagu:
* atro-koUanto-a-Mes!⇒McsattSpecific,
description::
× Mcsh-creation: {2026-10-04}
· individual-att of Mcs is a-specific-of-Mcs which has no other specifics.
name::
* McshEngl.McsattIndividual,
* McshEngl.individual-of-Mcsattr!⇒McsattIndividual,
* McshEngl.McsattIndividualindividual-of-Mcsattr,
* McshEngl.Mcsattr.individual!⇒McsattIndividual,
* McshEngl.individual-att--of-Mcsattr!⇒McsattIndividual,
* McshEngl.instance-of-Mcsattr!⇒McsattIndividual,
====== lagoSinagu:
* atro-koUgo-a-Mes!⇒McsattIndividual,
description::
× Mcsh-creation: {2026-10-04}
Specifics-division-of-Mcs\a\ is the-set of specific-concepts of Mcs\a\ on THE-SAME-ATTRIBUTE.
A-generic-concept can-have MANY specifics-divisions on DIFFERENT attributes.
For example, humans on 'tallness' are tall and tallNo.
The same humans on 'fatness' are fat and fatNo.
But it is a-mistake to say that humans are tall, tallNo and fat.
And this is the most common mistake in scientific-knowledge!
[Humn1959Sinagu.2017-11-15]
name::
* McshEngl.specifics-division--Mcsattr!⇒McsattSpecificsDivision,
* McshEngl.McsattSpecificsDivision!=specifics-division--Mcsattr,
* McshEngl.McsattDivisionSpecifics!⇒McsattSpecificsDivision,
* McshEngl.Mcsattr.division.specifics!⇒McsattSpecificsDivision,
* McshEngl.Mcsattr.specifics_division!⇒McsattSpecificsDivision,
* McshEngl.Mcs_division.specifics!⇒McsattSpecificsDivision,
* McshEngl.division.specifics_Mcsattr!⇒McsattSpecificsDivision,
* McshEngl.Sd!=specifics-division!⇒McsattSpecificsDivision, {2022-08-28}
* McshEngl.Specsdiv!=specifics-division!⇒McsattSpecificsDivision,
* McshEngl.specs-div!=specifics-division!⇒McsattSpecificsDivision,
* McshEngl.specs-division--Mcsattr!⇒McsattSpecificsDivision,
====== lagoGreek:
* McshElln.διαίρεση-ειδικών-εννοιών!⇒McsattSpecificsDivision,
generic-tree::
* McshEngl.McsattSpecificsDivision:generic,
===
* generic-tree,
* McsattDivision:generic,
description::
× Mcsh-creation: {2026-10-04}
Inheritedfrom--Mcs\a\-att is an-attribute-of-Mcs\a\ which is AND attribute of a-generic-concept of it\a\.
name::
* McshEngl.inherited-from--Mcsattr!⇒McsattInheritedFrom,
* McshEngl.McsattInheritedFrom!=inherited-from--Mcsattr,
* McshEngl.Mcsattr.inherited_from!⇒McsattInheritedFrom,
* McshEngl.Mcs'inherited_from__attribute!⇒McsattInheritedFrom,
* McshEngl.Mcsattr.inherited_from_instance.inherited_from!⇒McsattInheritedFrom,
description::
× Mcsh-creation: {2026-10-04}
InheritedfromNo--Mcs\a\-att is an-attribute-of-Mcs\a\ which is NOT AND attribute of a-generic-concept of it\a\.
name::
* McshEngl.inherited-fromNo--Mcsattr!⇒McsattInheritedFromNo,
* McshEngl.McsattInheritedFromNo!=inherited-fromNo--Mcsattr,
* McshEngl.Mcsattr.inherited_from.no!⇒McsattInheritedFromNo,
* McshEngl.Mcsattr.inherited_fromNo!⇒McsattInheritedFromNo,
* McshEngl.Mcsattr.own!⇒McsattInheritedFromNo,
* McshEngl.Mcsattr.inherited_from_instance.inherited_from.no!⇒McsattInheritedFromNo,
description::
× Mcsh-creation: {2026-10-04}
Inheritedto--Mcs\a\-att is an-attribute-of-Mcs\a\ which is AND attribute of a-specific-concept of it\a\.
name::
* McshEngl.inherited-to--Mcsattr!⇒McsattInheritedTo,
* McshEngl.McsattInheritedTo!=inherited-to--Mcsattr,
* McshEngl.Mcsattr.inherited_to!⇒McsattInheritedTo,
* McshEngl.Mcsattr.inherited_to_instance.inherited_to!⇒McsattInheritedTo,
description::
× Mcsh-creation: {2026-10-04}
InheritedtoNo--Mcs\a\-att is an-attribute-of-Mcs\a\ which is NOT AND attribute of a-specific-concept of it\a\.
name::
* McshEngl.Mcsattr.inherited_to.no!⇒McsattInheritedToNo,
* McshEngl.inherited-toNo--Mcsattr!⇒McsattInheritedToNo,
* McshEngl.McsattInheritedToNo!=inherited-toNo--Mcsattr,
* McshEngl.Mcsattr.inherited_toNo!⇒McsattInheritedToNo,
* McshEngl.Mcs'inherited_toNo__attribute!⇒McsattInheritedToNo,
description::
× Mcsh-creation: {2026-10-04}
· attribute-concept: title:"name of main_mind_name(Mmn)", name:"Mmd'name_with_underscores".
· specific-attribute-concept: title|name:"Mmn.name_with_underscores"
· title-of-Mcs is the-main-name-of-Mcs placed at the-top of its presentation.
"The-title is the-main-name of the-concept."
[Humn1959Sinagu.{2017-03-18}]
· attribute-title: "name-notation of Mmn" (Mmn = main-mind-name). Its name is "Mmn'name_notation".
· specific-title: "Mmn.name_with_underscores". Its name is the same, "Mmn.name_with_underscores".
name::
* McshEngl.title-of-Mcs!⇒Mcstitle,
* McshEngl.Mcstitle!=title-of-Mcs,
* McshEngl.Mcs-title!⇒Mcstitle,
* McshEngl.nameMcsTitle!⇒Mcstitle,
* McshEngl.McsnameTitle!⇒Mcstitle,
* McshEngl.Mcs/title!⇒Mcstitle,
* McshEngl.Mcs'title!⇒Mcstitle,
* McshEngl.McsApTitle!⇒Mcstitle,
* McshEngl.Mcsname.title!⇒Mcstitle,
* McshEngl.title-Mcsattr!⇒Mcstitle,
generic-tree::
* McshEngl.Mcstitle:generic,
===
* McsnameMind:generic,
* Mcsname:generic,
* Mcsattr:generic,
* ...entity:generic,
description::
× Mcsh-creation: {2026-10-28}
· attribute-title of Mcs is the-title of an-attribute-concept: "name-notation of Mmn", where Mmn is the-main-mind-name of the-owner of the-attribute.
· the-title gives the-name "Mmn'name_notation" (dashes become underscores).
· Mmn is the-owner in the-title; it is not always the-whole of the-presentation.
name::
* McshEngl.attribute-title-of-Mcs!⇒Mcstitleattr,
* McshEngl.Mcstitleattr!=attribute-title-of-Mcs,
* McshEngl.Mcstitle.attribute!⇒Mcstitleattr,
generic-tree::
* McshEngl.Mcstitleattr:generic,
===
* Mcstitle:generic,
description::
× Mcsh-creation: {2026-10-28}
· specific-title of Mcs is the-title of a-specific-concept: "Mmn.name_with_underscores", where Mmn is the-main-mind-name of its generic.
· the-title is also a-name of the-concept, written the-same: "Mmn.name_with_underscores".
name::
* McshEngl.specific-title-of-Mcs!⇒Mcstitlespec,
* McshEngl.Mcstitlespec!=specific-title-of-Mcs,
* McshEngl.Mcstitle.specific!⇒Mcstitlespec,
generic-tree::
* McshEngl.Mcstitlespec:generic,
===
* Mcstitle:generic,
description::
× Mcsh-creation: {2026-10-04}
· name of Mcs\a\ is any logo-name of it\a\.
[Humn1959Sinagu.2019-08-05]
name::
* McshEngl.name-of-Mcs!⇒Mcsname,
* McshEngl.Mcsname!=name-of-Mcs,
* McshEngl.Mcsattr.name!⇒Mcsname,
* McshEngl.Mcs-name!⇒Mcsname,
* McshEngl.Mcs/name!⇒Mcsname,
* McshEngl.Mcs'name!⇒Mcsname, {2020-04-30}
* McshEngl.name-att--of-Mcs!⇒Mcsname,
* McshEngl.nameMcs!⇒Mcsname,
description::
× Mcsh-creation: {2026-10-04}
· it is VERY IMPORTANT to be-consistent on the-names we use in order to increase communication.
name::
* McshEngl.name-notation--of-Mcs!⇒Mcsnotn,
* McshEngl.Mcsnotn!=name-notation--of-Mcs,
* McshEngl.Mcsname'name_notation!⇒Mcsnotn,
* McshEngl.Mcs'notation_of_name!⇒Mcsnotn,
* McshEngl.name'notation_of_Mcs!⇒Mcsnotn,
* McshEngl.Mcsname'naming_convension!⇒Mcsnotn,
* McshEngl.Mcsnamenttn!⇒Mcsnotn,
* McshEngl.Mcsname-notation!⇒Mcsnotn,
* McshEngl.Mcsname'notation!⇒Mcsnotn,
* McshEngl.naming-convension--of-Mcs!⇒Mcsnotn,
* McshEngl.notation-of--Mcs-name!⇒Mcsnotn,
description::
× Mcsh-creation: {2026-10-04}
name::
* McshEngl.Mcsnotn'generic_specific_tree,
generic-tree::
* McshEngl.Mcsnotn:generic,
===
* convention:generic,
* ...entity:generic,
specific-tree::
* McshEngl.Mcsnotn.specific,
===
* 2-words-names,
* no-space,
* attribute,
* capital,
* upper|lower-case,
* ! extra-info,
* !~ PoS,
* !⇒ main-name,
* != translation,
* {time},
* [info-resource],
* \reference,
description::
× Mcsh-creation: {2026-10-04}
· I use 2 words, at least, to name concepts.
· specifics: cellAnimal, cellBone, ...
· attributes: body'neck, body'torso, ...
· this method resolves ambiguities of one-word-names with many meanings and improves the-meaning of texts.
name::
* McshEngl.2-words-names--Mcs-notation!⇒McsnotnTwo,
* McshEngl.McsnotnTwo!=2-words-names--Mcs-notation,
* McshEngl.Mcsnotn.2_words_names!⇒McsnotnTwo,
* McshEngl.two-words-names--Mcs-notation!⇒McsnotnTwo,
description::
× Mcsh-creation: {2026-10-04}
· no spaces in multi-word names:
* human-language, Mcsattr,
* use char.45'-' or char.95'_' in programing-languages if '-' is not allowed,
* hyphenate compound-words when the-parts have obvious different concepts: structured-concept, keyboard,
* use more than one hyphen when combine compound-words: decentralized-crypto-chain--protocol,
[Humn1959Sinagu.2018-01-22]
· EXCEPTION: when the-name must denote a-character and we want to make it visible well. {2026-10-17}
name::
* McshEngl.McsnotnNospace,
* McshEngl.Mcsnotn.no_space!⇒McsnotnNospace,
description::
× Mcsh-creation: {2026-10-04}
· denote type of attributes of concepts:
* xxx'yyy or xxxAaYyy: yyy is attribute of xxx,
* xxx'yyy or xxxApYyy: yyy is part of xxx,
* xxx'yyy or xxxAeYyy: yyy is environment of xxx,
* xxx'yyy or xxxAwYyy: yyy is whole of xxx,
* xxx'yyy or xxxAgYyy: yyy is generic of xxx,
* xxx.yyy or xxxAsYyy or xxxYyy: yyy is specific of xxx,
[Humn1959Sinagu.2017-11-24, 2019-01-17]
===
* xxx'yyy or xxxAaYyy: yyy is attribute of xxx,
* xxx'pYyy or xxxApYyy: yyy is part of xxx,
* xxx'eYyy or xxxAeYyy: yyy is environment of xxx,
* xxx'wYyy or xxxAwYyy: yyy is whole of xxx,
* xxx'gYyy or xxxAgYyy: yyy is generic of xxx,
* xxx'sYyy or xxxAsYyy or xxxYyy: yyy is specific of xxx,
· this notation is very usefull when we SEARCH for a-concept, where we quickly find ALL related concepts.
· we can-use it in parallel with the-common-names of the-concepts.
name::
* McshEngl.attribute(')--Mcs-name-notation!⇒McsnotnAttr,
* McshEngl.McsnotnAttr!=attribute(')--Mcs-name-notation,
* McshEngl.'attribute__name_notation!⇒McsnotnAttr,
* McshEngl.Mcsnotn.'attribute!⇒McsnotnAttr,
* McshEngl.Mcsnotn.attribute(')!⇒McsnotnAttr,
* McshEngl.Mcsnotn.attribute!⇒McsnotnAttr,
description::
× Mcsh-creation: {2026-10-04}
· a-part-attribute of an-Mcs.
name::
* McshEngl.part(/)--Mcs-name-notation!⇒McsnotnPart,
* McshEngl.McsnotnPart!=part(/)--Mcs-name-notation,
* McshEngl./attribute.part__name_notation!⇒McsnotnPart,
* McshEngl.Mcsnotn./attribute.part!⇒McsnotnPart,
* McshEngl.Mcsnotn.attribute.part(/)!⇒McsnotnPart,
* McshEngl.Mcsnotn.part_attribute(/)!⇒McsnotnPart,
* McshEngl.Mcsnotn.whole/part!⇒McsnotnPart,
description::
× Mcsh-creation: {2026-10-04}
· a-whole-attribute of an-Mcs.
name::
* McshEngl.whole(//)--Mcs-name-notation!⇒McsnotnWhole,
* McshEngl.McsnotnWhole!=whole(//)--Mcs-name-notation,
* McshEngl.//attribute.whole__name_notation!⇒McsnotnWhole,
* McshEngl.Mcsnotn.//attribute.whole!⇒McsnotnWhole,
* McshEngl.Mcsnotn.attribute.whole(//)!⇒McsnotnWhole,
* McshEngl.Mcsnotn.whole_attribute(//)!⇒McsnotnWhole,
* McshEngl.Mcsnotn.part//whole!⇒McsnotnWhole,
description::
× Mcsh-creation: {2026-10-04}
· a-specific-attribute of an-Mcs.
name::
* McshEngl.specific(.)--Mcs-name-notation!⇒McsnotnSpecific,
* McshEngl.McsnotnSpecific!=specific(.)--Mcs-name-notation,
* McshEngl..attribute.specific__name_notation!⇒McsnotnSpecific,
* McshEngl.Mcsnotn..attribute.specific!⇒McsnotnSpecific,
* McshEngl.Mcsnotn..attribute_Sptr!⇒McsnotnSpecific,
* McshEngl.Mcsnotn.attribute.specific(.)!⇒McsnotnSpecific,
* McshEngl.Mcsnotn.specific_attribute(.)!⇒McsnotnSpecific,
* McshEngl.Mcsnotn.generic.specific!⇒McsnotnSpecific,
* McshEngl.generic.specific!⇒McsnotnSpecific,
description::
× Mcsh-creation: {2026-10-04}
· a-generic-attribute of an-Mcs.
name::
* McshEngl.generic(:)--Mcs-name-notation!⇒McsnotnGeneric,
* McshEngl.McsnotnGeneric!=generic(:)--Mcs-name-notation,
* McshEngl.Mcsnotn.:attribute.generic!⇒McsnotnGeneric,
* McshEngl.Mcsnotn.attribute.generic(:)!⇒McsnotnGeneric,
* McshEngl.Mcsnotn.generic_attribute(:)!⇒McsnotnGeneric,
* McshEngl.Mcsnotn.specific:generic!⇒McsnotnGeneric,
* McshEngl.specific:generic!⇒McsnotnGeneric,
description::
× Mcsh-creation: {2026-10-04}
· parent - child notation.
name::
* McshEngl.child(;)--Mcs-name-notation!⇒McsnotnChild,
* McshEngl.McsnotnChild!=child(;)--Mcs-name-notation,
* McshEngl.;child_attribute__name_notation!⇒McsnotnChild,
* McshEngl.Mcsnotn.;attribute.child!⇒McsnotnChild,
* McshEngl.Mcsnotn.attribute.child(;)!⇒McsnotnChild,
* McshEngl.Mcsnotn.child_attribute(;)!⇒McsnotnChild,
* McshEngl.parent;child!⇒McsnotnChild,
description::
× Mcsh-creation: {2026-10-04}
· child-parent notation.
name::
* McshEngl.parent(;;)--Mcs-name-notation!⇒McsnotnParent,
* McshEngl.McsnotnParent!=parent(;;)--Mcs-name-notation,
* McshEngl.;;parent_attribute__name_notation!⇒McsnotnParent,
* McshEngl.Mcsnotn.;;attribute.parent!⇒McsnotnParent,
* McshEngl.Mcsnotn.parent;child!⇒McsnotnParent,
* McshEngl.Mcsnotn.child;;parent!⇒McsnotnParent,
* McshEngl.Mcsnotn.attribute.parent_child!⇒McsnotnParent,
description::
× Mcsh-creation: {2026-10-04}
· first-capital ⇒ short-name. {2026-10-08}
· capital-inside ⇒ specific-concept:
- McsHitp, lagoSinagu,
· first-capital ⇒ initialism, many-words, instance:
- Mcsmgr, Mcs_mgr, Hitp, Athens, Systnode, sys_node,
[Humn1959Sinagu.{2026-08-27}]
· Webapi = many words name, first capital.
· lagoSinago = generic-specific name, first small.
[{2024-11-14} Humn1959Sinagu]
· first capital:
* initialisms: Hitp, Html,
* many-words: Webapi,
* instance-concepts: Earth, Athens,
* exception: short-names: net, ogn, Ogsm,
[Humn1959Sinagu.2018-01-22]
===
· ONE CASE everywhere:
· sentences begin with char.183'·', so we do-not-need capital-letters in the-beginning of a-sentence.
· exceptions:
* all capitals, for emphasis,
* specifics: xxxYyy,
[Humn1959Sinagu.2018-01-14]
name::
* McshEngl.capital--Mcs-name-notation!⇒McsnotnCapital,
* McshEngl.McsnotnCapital!=capital--Mcs-name-notation,
* McshEngl.Mcsnotn.capital!⇒McsnotnCapital,
* McshEngl.Mcsnotn.lower|upper_case!⇒McsnotnCapital,
* McshEngl.Mcsnotn.upper|lower_case!⇒McsnotnCapital,
description::
× Mcsh-creation: {2026-10-04}
- McsEll.σύστημα!το,
- McsEll.καλός!-ός-ή-ό,
· method of inflection:
name::
* McshEngl.Mcsnotn.! extra_info,
* McshEngl.extra-info(!)--Mcs-name-notation!⇒McsnotnExtrainfo,
* McshEngl.McsnotnExtrainfo!=extra-info(!)--Mcs-name-notation,
* McshEngl.! extra-info--name-notation!⇒McsnotnExtrainfo,
* McshEngl.Mcsnotn.! extra-info!⇒McsnotnExtrainfo,
* McshEngl.Mcsnotn.extra_info.!!⇒McsnotnExtrainfo,
description::
× Mcsh-creation: {2026-10-04}
- McshElln.ένας!~AdjeElln,
name::
* McshEngl.Mcsnotn.!~ PoS,
* McshEngl.Pos(!~)--Mcs-name-notation!⇒McsnotnPos,
* McshEngl.McsnotnPos!=Pos(!~)--Mcs-name-notation,
* McshEngl.part-of-speech(!~)--name-notation!⇒McsnotnPos,
* McshEngl.!~ PoS--name-notation!⇒McsnotnPos,
* McshEngl.Mcsnotn.!~ PoS!⇒McsnotnPos,
* McshEngl.Mcsnotn.PoS !~!⇒McsnotnPos,
description::
× Mcsh-creation: {2026-10-04}
· denotes the-main-name\a\ of a-sensorial-concept.
· AND instructs the-computer to search for it\a\.
name::
* McshEngl.Mcsnotn.!⇒main_mind_name,
* McshEngl.main-mind-name(!⇒)--Mcs-name-notation!⇒McsnotnMainMind,
* McshEngl.McsnotnMainMind!=main-mind-name(!⇒)--Mcs-name-notation,
* McshEngl.!⇒main-mind-name!⇒McsnotnMainMind,
* McshEngl.main-mind-name--name-notation-(!⇒)!⇒McsnotnMainMind,
* McshEngl.Mcsnotn.(!⇒)!⇒McsnotnMainMind,
* McshEngl.Mcsnotn.main_mind_name(!⇒)!⇒McsnotnMainMind,
description::
× Mcsh-creation: {2026-10-28}
· main-name for non-english names.
name::
* McshEngl.Mcsnotn.!⇨non_english_main,
* McshEngl.non_english_main(!⇨)--Mcs-name-notation!⇒McsnotnMainOther,
* McshEngl.McsnotnMainOther!=non_english_main(!⇨)--Mcs-name-notation,
* McshEngl.!⇨non_english_main!⇒McsnotnMainOther,
* McshEngl.Mcsnotn.!⇨non_english_main!⇒McsnotnMainOther,
description::
× Mcsh-creation: {2026-10-28}
· Id in current worldview.
name::
* McshEngl.Mcsnotn.!@Id,
* McshEngl.Id(!@)--Mcs-name-notation!⇒McsnotnId,
* McshEngl.McsnotnId!=Id(!@)--Mcs-name-notation,
* McshEngl.!@Id!⇒McsnotnId,
* McshEngl.Mcsnotn.!@Id!⇒McsnotnId,
description::
× Mcsh-creation: {2026-10-04}
· denotes translation to English.
name::
* McshEngl.Mcsnotn.!= translation!⇒McsnotnTranslation,
* McshEngl.translation(!=)--Mca-name-notation!⇒McsnotnTranslation,
* McshEngl.McsnotnTranslation!=translation(!=)--Mca-name-notation,
* McshEngl.!=translation--name-notation!⇒McsnotnTranslation,
* McshEngl.Mcsnotn.translation.!=!⇒McsnotnTranslation,
description::
× Mcsh-creation: {2026-10-04}
· @ denotes a-name of another worldview.
· !/ previous
· we know / denotes part-of in directories.
· !: previous abandoned because : is-used in name-value-pair.
· !⇨ previous
name::
* McshEngl.Mcsnotn.@ other_worldview!⇒McsnotnWorldviewOther,
* McshEngl.McsnotnWorldviewOther,
* McshEngl.other-worldview(@)--Mcs-name-notation!⇒McsnotnWorldviewOther,
* McshEngl.other-worldview(@)--Mcs-name-notation,
* McshEngl.@other-worldview--name-notation!⇒McsnotnWorldviewOther,
* McshEngl.other-worldview@--name-notation!⇒McsnotnWorldviewOther,
* McshEngl.Mcsnotn.@other_worldview!⇒McsnotnWorldviewOther,
* McshEngl.Mcsnotn.other_worldview@!⇒McsnotnWorldviewOther,
description::
× Mcsh-creation: {2026-10-04}
· the-info-resource of an-info.
name::
* McshEngl.[info-resource]--Mcs-name-notation!⇒McsnotnInfo,
* McshEngl.McsnotnInfo!=[info-resource]--Mcs-name-notation,
* McshEngl.Mcsnotn.[info_resource]!⇒McsnotnInfo,
* McshEngl.Mcsnotn.[info_resource]!⇒McsnotnInfo,
* McshEngl.Mcsnotn.left_right_square_brackets!⇒McsnotnInfo,
description::
× Mcsh-creation: {2026-10-04}
· the-reference of a-pronoun.
name::
* McshEngl.reference\\--Mcs-name-notation!⇒McsnotnReference,
* McshEngl.McsnotnReference!=reference\\--Mcs-name-notation,
* McshEngl.\reference\!⇒McsnotnReference,
* McshEngl.Mcsnotn.\reference\!⇒McsnotnReference,
* McshEngl.Mcsnotn.reverse_solidus!⇒McsnotnReference,
* McshEngl.Mcsnotn.\reference\!⇒McsnotnReference,
description::
× Mcsh-creation: {2026-10-04}
· I will-add zzz at the-end, 0 I use in language-families. {2026-10-10}
· when a-name has a-length smaller than a-fixed length I want to use,
then, then I add 0000s at the-end to match the-fixed length.
[Humn1959Sinagu.{2021-01-05}]
name::
* McshEngl.fixed-length--Mcs-name-notation!⇒McsnotnFixed,
* McshEngl.McsnotnFixed!=fixed-length--Mcs-name-notation,
* McshEngl.Mcsnotn.fixed_length!⇒McsnotnFixed,
description::
× Mcsh-creation: {2026-10-04}
· NAMES are the-semantic-units of THE-SENTENCES of our texts/speeches.
We create names using WORDS.
In-order-to distinguish names from words I am-using the-following NAME-NOTATION.
Also, in our computer-era, where computers create automatically name-indexes, the-following-notation puts together related concepts.
name::
* McshEngl.Mcsnotn.before_,
* McshEngl.Mcsnotn.before_{2017-11-21},
NAME-OF-CONCEPT with MANY WORDS::
• xxx-yyy
• xxx_yyy
• xxxyyy
example: human-language, human_language, humanlanguage.
This composite-name itself, does not convey any meaning from its sub-names.
Name of A-SPECIFIC-CONCEPT::
• xxx.yyy: the-specifc has as generic the-xxx with attribute the-yyy.
• xxxYyy: same.
example: language.human, languageHuman, Kaseluris.Nikos.1959.
Name of A-CONCEPT'S-ATTRIBUTE::
• xxx's-yyy: yyy is an-attribute of xxx.
• xxx'yyy: same.
example: human's-language, human'language (= language-of-human).
Name of A-PROCESS-CONCEPT::
If a-concept is a-process, I use to name it with an '-ing' ending.
example: doing, evoluting, encrypting, ...
{2013-08-28}
APHORISM::
bad-names bad-thinking, clear-names clear-thinking.
{2013-02-22}
description::
× Mcsh-creation: {2026-10-04}
· derived-name\b\ of Mcsname\a\ is a-name of an-attribute of the-concept with the-Mcsname\a\, that is-created from it\a\.
· according to Mcs-naming-convension it\b\ begins with the-Mcsname\a\ which is-called 'original-name'.
name::
* McshEngl.derived-name--of--Mcs-name!⇒Mcs_derived_name,
* McshEngl.Mcs_derived_name!=derived-name--of--Mcs-name,
* McshEngl.Mcsname'derived_name!⇒Mcs_derived_name,
* McshEngl.related-name--of--Mcs-name!⇒Mcs_derived_name,
description::
× Mcsh-creation: {2026-10-04}
name::
* McshEngl.Mcs_derived_name'generic_specific_tree,
generic-tree::
* McshEngl.Mcs_derived_name:generic,
===
* ...entity:generic,
specific-tree::
* McshEngl.Mcs_derived_name.specific,
===
* Mcs_derived_name.McsmmnDerived!@McshCor000002#idMcsattNamDzrMaindrvd,
description::
× Mcsh-creation: {2026-10-04}
· original-name--of--a-Mcsname\a\ is a-name\b\ of a-concept with attribute the-Mcsname\a\, if name\b\ is a-derived-name of name\a\.
name::
* McshEngl.original-name--of-Mcs-name!⇒Mcs_original_name,
* McshEngl.Mcs_original_name!=original-name--of-Mcs-name,
* McshEngl.Mcsname'original_name!⇒Mcs_original_name,
description::
× Mcsh-creation: {2026-10-04}
* overview--Mcsattr,
description::
× Mcsh-creation: {2026-10-04}
name::
* McshEngl.Mcsname'generic_specific_tree,
generic-tree::
* McshEngl.Mcsname:generic,
===
* Mcsattr:generic,
* ...entity:generic,
specific-tree::
* McshEngl.Mcsname.specific,
===
* mind-name,
* mindNo-name,
* main-name,
* Mcsname.Mcstitle!@McshCor000002#idMcsttl,
===
* English-name,
* EnglishNo-name,
===
* machine-name,
* machineNo-name,
description::
× Mcsh-creation: {2026-10-04}
* English-language:
- concept'attribute. /kónsepts-átribyyut/ {2020-04-30}
- attribute-of-concept.
- conceptual-attribute.
===
* Sinago-language:
- eniosAtro.
- enios-atro.
name::
* McshEngl.attribute-name-of-Mcs!⇒McsnameAttr,
* McshEngl.McsnameAttr!=attribute-name-of-Mcs,
* McshEngl.Mcsname.attribute!⇒McsnameAttr,
description::
× Mcsh-creation: {2026-10-04}
* English-language:
- concept.specific.
- conceptSpecific.
- specific-concept.
- specific-of-concept.
===
* Sinago-language:
- enio-specifico.
- enioSpecifico.
name::
* McshEngl.specific-attribute-name-of-Mcs!⇒McsnameAttrSpec,
* McshEngl.McsnameAttrSpec!=specific-attribute-name-of-Mcs,
* McshEngl.Mcsname.specific_attribute!⇒McsnameAttrSpec,
description::
× Mcsh-creation: {2026-10-04}
· mind-name of Mcs\a\ is a-name we use to refer to concept\a\ itself and not to one of its semu-concepts.
· its generic noun usually it is-used as mind-name.
[Humn1959Sinagu.2019-08-05]
name::
* McshEngl.mind-name-of-Mcs!⇒McsnameMind,
* McshEngl.McsnameMind!=mind-name-of-Mcs,
* McshEngl.mind-name--of-Mcs!⇒McsnameMind,
* McshEngl.Mcs'dezignator!⇒McsnameMind,
* McshEngl.dezignatorMcs!⇒McsnameMind,
* McshEngl.dezignator-of-Mcs!⇒McsnameMind,
* McshEngl.mindNameMcs!⇒McsnameMind, {2022-08-17}
* McshEngl.Mcsname.mind!⇒McsnameMind,
* McshEngl.nameMindMcs!⇒McsnameMind,
====== lagoGreek:
* McshElln.δηλωτής!ο!⇒McsnameMind,
description::
× Mcsh-creation: {2026-10-04}
name::
* McshEngl.McsnameMind'generic_specific_tree,
generic-tree::
* McshEngl.McsnameMind:generic,
===
* Mcsname:generic,
* ...entity:generic,
specific-tree::
* McshEngl.McsnameMind.specific,
===
* ID,
* McsnameMind.Mcsmmn!@McshCor000002#idMcsattNamDzrMain,
* McsnameMind.Mcstitle!@McshCor000002#idMcsttl,
description::
× Mcsh-creation: {2026-10-04}
· Mcs-main-mind-name is the-english most used name of the-concept\a\.
· the-formal (after !⇒) is unique in the-worldview.
· the-informal (before !⇒ and after !=) in second-line, is human readable.
· a-Mcs can-have many mind-names.
· main-name is its most used term mind-name.
· the related names of the-concept (part, specific) are created from the-main-name.
name::
* McshEngl.main-mind-name--of-Mcs!⇒Mcsmmn,
* McshEngl.Mcsmmn!=main-mind-name--of-Mcs,
* McshEngl.Mcsmainmindname!⇒Mcsmmn,
* McshEngl.Mcs_main_mind_name!⇒Mcsmmn,
* McshEngl.McsnameMindMain!⇒Mcsmmn,
* McshEngl.McsnameMainMind!⇒Mcsmmn,
* McshEngl.McsnameMind.main!⇒Mcsmmn,
* McshEngl.Mcs'mind_main_name!⇒Mcsmmn,
* McshEngl.Mcs-main-mind-name!⇒Mcsmmn, {2019-03-10}
* McshEngl.Mcs-mind-main-name!⇒Mcsmmn, {2019-03-10}
* McshEngl.main-mind-Mcsname!⇒Mcsmmn,
* McshEngl.Mcsname.main.mind!⇒Mcsmmn,
* McshEngl.Mcsname.mind.main!⇒Mcsmmn,
description::
× Mcsh-creation: {2026-10-04}
· derived-name--of--Mcs-main-name\a\ is a-derived-name of it\a\.
· the-main-mind-names of the-attributes (specific and not) of a-concept, are-derived.
name::
* McshEngl.derived-name--of--Mcs-main-name!⇒McsmmnDerived,
* McshEngl.McsmmnDerived!=derived-name--of--Mcs-main-name,
* McshEngl.Mcsmmn'derived_name!⇒McsmmnDerived,
* McshEngl.Mcsname.main'derived_name!⇒McsmmnDerived,
* McshEngl.McsnameMain'derived_name!⇒McsmmnDerived,
* McshEngl.related-name--of--Mcs-main-name!⇒McsmmnDerived,
generic-tree::
* McshEngl.McsmmnDerived:generic,
===
* Mcs_derived_name:generic,
* ...entity:generic,
description::
× Mcsh-creation: {2026-10-28}
· the-main-mind-names of the-attributes (specific and not) of a-concept, are-created of from text related to Mcsmmn of the-concept.
· it is-denoted in third|forth line with (!Attrbase).
name::
* McshEngl.Attrbase-of--Mcs-main-mind-name!⇒Mcsmmnbase,
* McshEngl.Mcsmmnbase!=Attrbase-of--Mcs-main-mind-name,
* McshEngl.Mcsmmn'Attrbase!⇒Mcsmmnbase,
description::
× Mcsh-creation: {2026-10-04}
· mainNo-mind-name of Mcs is any mind-name other than the-main-name.
· the-mainNo-mind-names, in the-list of names, present and the-main-name in the-form: * Mcs.mainNo-name!⇒main-name,
· this way the-derived-names of a-name\a\ are-stored once with only the-main-name of the-name\a\.
name::
* McshEngl.mainNo-mind-name--Mcs-name,
* McshEngl.McsnameMind.mainNo,
description::
× Mcsh-creation: {2026-10-28}
· Mcs-other-main-name is a-main-mind-name in another language, not english.
· it is-denoted as (!⇨).
name::
* McshEngl.Mcs-other-main-mind-name!⇒McsnameMindOthr,
* McshEngl.McsnameMindOthr!=Mcs-other-main-mind-name,
* McshEngl.McsnameMind.other!⇒McsnameMindOthr,
description::
× Mcsh-creation: {2026-10-04}
· synonyms of Mcs\a\ is the-set of all mind-names of Mcs\a\
description::
× Mcsh-creation: {2026-10-04}
· conceptary of worldview is the-set of all mind-names in one language.
· the-conceptary does-not-contain the-parts-of-speech that denote semu-concepts of a-concept.
name::
* McshEngl.dezigneptary-of-worldview, from 'dictionary'
* McshEngl.conceptary-of-worldview, from 'dictionary'
* McshEngl.McsnameMind.conceptary,
====== lagoGreek:
* McshElln.εννοιολόγιο!=conceptary, από 'λεξιλόγιο',
* McshElln.δηλοτολόγιο!=conceptary, από 'λεξιλόγιο',
description::
× Mcsh-creation: {2026-10-04}
· mindNo-name of Mcs\a\ is a-name not a-mind-name, ie a-name for the-semu-concepts of a-concept, such as noun (case-noun, adjective, adverb), verb, conjunction.
[Humn1959Sinagu.2019-08-05]
name::
* McshEngl.McsnameMindNo,
* McshEngl.Mcs'dezignatorNo!⇒McsnameMindNo,
* McshEngl.Mcs'mindNo_name!⇒McsnameMindNo,
* McshEngl.Mcs'semu_name!⇒McsnameMindNo,
* McshEngl.dezignatorNo-of-Mcs!⇒McsnameMindNo,
* McshEngl.mindNo-name-of-Mcs!⇒McsnameMindNo,
* McshEngl.McsnameSemo!⇒McsnameMindNo,
* McshEngl.semu-name--of-Mcs!⇒McsnameMindNo,
* McshEngl.Mcsname.mindNo!⇒McsnameMindNo,
====== lagoGreek:
* McshElln.μη-δηλωτής!⇒McsnameMindNo,
description::
× Mcsh-creation: {2026-07-02}
· an-Mcs can-have many main-names.
* main--mind-name(english):
* main_mind_name.formal, after !⇒
* main_mind_name.formalNo, before !⇒ and after !=
* main_mind_name.other, after !⇨
* main--argu-name,
* main--verb-name,
* main--Conj-name,
name::
* McshEngl.Mcs-main-name!⇒McsnameMain,
* McshEngl.McsnameMain!=Mcs-main-name, {2026-07-02}
* McshEngl.main-name--of-Mcs!⇒McsnameMain,
* McshEngl.mnnm-of-Mcs!⇒McsnameMain,
* McshEngl.Mcsname.main!⇒McsnameMain,
description::
× Mcsh-creation: {2026-10-29}
name::
* McshEngl.McsnameMain'generic_specific_tree,
generic-tree::
* McshEngl.McsnameMain:generic,
===
* Mcsname:generic,
* ...entity:generic,
specific-tree::
* McshEngl.McsnameMain.specific,
===
* McsnameMain.McshnameMain!@McshTchInf000009#idMcsHitpnameMain,
description::
× Mcsh-creation: {2026-07-02}
· not a-main-name.
name::
* McshEngl.Mcs-mainNo-name!⇒McsnameMainNo,
* McshEngl.McsnameMainNo!=Mcs-mainNo-name, {2026-07-02}
* McshEngl.mainNo-name--of-Mcs!⇒McsnameMainNo,
* McshEngl.Mcsname.mainNo!⇒McsnameMainNo,
description::
× Mcsh-creation: {2026-10-04}
· genericNo-name of Mcs is ANY genericNo-logo-name of it.
name::
* McshEngl.Mcs-synonym!⇒McsnameSyno,
* McshEngl.McsnameSyno!=Mcs-synonym, {2026-07-02}
* McshEngl.Mcsname.element!⇒McsnameSyno,
* McshEngl.Mcsname.genericNo!⇒McsnameSyno,
* McshEngl.Mcsname.individual!⇒McsnameSyno,
* McshEngl.Mcsname.instance!⇒McsnameSyno,
* McshEngl.Mcsname-element!⇒McsnameSyno,
* McshEngl.Mcsname-instance!⇒McsnameSyno,
* McshEngl.genericNo-name--of-Mcs!⇒McsnameSyno,
* McshEngl.name-element--of-Mcs!⇒McsnameSyno,
* McshEngl.name-instance--Mcsattr!⇒McsnameSyno,
* McshEngl.synonym-of-Mcs!⇒McsnameSyno,
* Mcsname, {2019-03-02}
* Mcsname, {2019-02-11}
description::
× Mcsh-creation: {2026-10-04}
· a-English-Mcsname has:
* title: 'name::' and
* list-elements: '* McshEngl.name' (old: '* Mcs.name')
name::
* McshEngl.English--Mcs-name,
* McshEngl.Mcsname.English,
description::
× Mcsh-creation: {2026-10-04}
· a-non-English-Mcsname has:
* title: 'name::' and
* a-subtitle: '====== langoName:' and
* list-elements: '* McsLag4.name', where Lag4 a-4-letter language-name,
=== old:
* title: 'name.Language::' and
* list-elements: '* McsLag.name', where Lag is the-3-letter-terminology-ISO-639-2-language-code,
name::
* McshEngl.Mcsname.EnglishNo,
* McshEngl.non-English--Mcs-name,
====== lagoGreek:
* McshElln.μη-Αγγλικό-όνομα-αισθητής-έννοιας,
description::
× Mcsh-creation: {2026-10-04}
· formal--Mcs-name is an-Mcs-name used most by machines.
· for example, "McsnameFrml".
· 1) formal-names are ONE word, short, at least locally unique, with underscores.
· 2) initializations have only first capital: "Html, Dbcnet".
name::
* McshEngl.formal--Mcs-name!⇒McsnameFrml,
* McshEngl.McsnameFrml!=formal--Mcs-name,
* McshEngl.machine--Mcs-name!⇒McsnameFrml,
* McshEngl.Mcsname.formal!⇒McsnameFrml,
* McshEngl.Mcsname.machine!⇒McsnameFrml,
* McshEngl.Mcs'formal_name!⇒McsnameFrml,
description::
× Mcsh-creation: {2026-10-04}
· formalNo--Mcs-name is an-Mcs-name used most by humans.
· for example, "non-formal-Mcsname".
· it contains hyphens(-), not underscores(_).
name::
* McshEngl.informal--Mcs-name!⇒McsnameFrmlNo,
* McshEngl.McsnameFrmlNo!=informal--Mcs-name,
* McshEngl.human-readable--Mcs-name!⇒McsnameFrmlNo,
* McshEngl.formalNo--Mcs-name!⇒McsnameFrmlNo,
* McshEngl.machineNo--Mcs-name!⇒McsnameFrmlNo,
* McshEngl.Mcsname.formalNo!⇒McsnameFrmlNo,
* McshEngl.Mcsname.machineNo!⇒McsnameFrmlNo,
* McshEngl.Mcs'informal_name!⇒McsnameFrmlNo,
description::
× Mcsh-creation: {2026-10-04}
· in literature there-is a-confusion and different understandings among the-concepts:
* wordary,
* namary,
* termary,
* conceptary,
· that is why we see indexes of words instead of names.
· also we see vicious-circle-definitions of nouns and verbs of the-SAME concept.
name::
* McshEngl.dictionary@literature,
* McshEngl.glossary@literature,
* McshEngl.lexicon@literature,
* McshEngl.terminology@literature,
* McshEngl.vocabulary@literature,
* McshEngl.Mcsname.dictionary,
description::
× Mcsh-creation: {2026-10-04}
· Mcs-text is TEXT comprised of Mcsname.
· it uses the-Mcsname-notation.
· the-goal of Mcs-text is to be MONOSEMANTIC by defining ALL the-names it uses, LIKE computer-language-texts.
[Humn1959Sinagu.2018-10-14]
===
· the-second goal is the-manager to understands the-text and display it in any language.
· monosemanticity is a-prerequisite for that.
· lagoSinago could-be-used for that.
[Humn1959Sinagu.{2021-03-18}]
name::
* McshEngl.Mcs_text, {2019-05-22}
* McshEngl.Mcs-text!⇒Mcs_text,
* McshEngl.Mcs'text!⇒Mcs_text,
* McshEngl.sensorial-concept--text!⇒Mcs_text,
* McshEngl.text-of-Mcs!⇒Mcs_text,
description::
× Mcsh-creation: {2026-10-04}
· time info is enclosed in {}.
=== time-point:
* {2005}
* {0005}
* {Bce0005}
* {Bce9999}
* {BpK1x010} ⭢ 10'000 years ago, after Bce9999 use only Bp,
* {BpK1x012} ⭢ 12'000 years ago,
* {BpK1x033} ⭢ 33'000 years ago,
* {BpK2x033} ⭢ 33 million years ago,
* {BpK3x033} ⭢ 33 billion years ago,
=== time-interval:
* {i2005..2010}
* {iBce0010..Bce0005}
* {iBpK1x033..BpK1x003}
* {i0...} ⭢ interval larger that millennium
* {i1m-2000} ⭢ interval-1m time-info: MILLENNIUM events {1001..2000}
* {i11-2000} ⭢ interval-11 time-info: early-millennium events,
* {i12-2000} ⭢ interval-12 time-info: middle-millennium events,
* {i13-2000} ⭢ interval-13 time-info: late-millennium events,
* {i1m-Bce2000} ⭢ interval-1m time-info: MILLENNIUM events {Bce1001..Bce2000}
* {i2c-2000} ⭢ interval-2c time-info: CENTURY {1901..2000}
* {i21-2000} ⭢ interval-21 time-info: early-century,
* {i3d-2000} ⭢ interval-3d time-info: DECADE {1991..2000}
* {i4y-2000} ⭢ interval-4y time-info: YEAR,
=== time-on-subject:
* {SoctEus-2000} ⭢ Eu time-info (uses main-name),
* {SoctEus-i2000..2060} ⭢ Eu time-info (uses main-name),
* {SoctEus-ic-2000} ⭢ Eu time-info (uses main-name),
===
name::
* McshEngl.Mcsh_time,
* McshEngl.Mcs'time!⇒Mcsh_time,
* McshEngl.time.Mcs!⇒Mcsh_time,
* McshEngl.Mcsh'data.time!⇒Mcsh_time,
* McshEngl.Mcsh'time_data!⇒Mcsh_time,
* McshEngl.Mcs_text'time!⇒Mcsh_time,
description::
× Mcsh-creation: {2026-10-04}
· Mcs-view is a-sensorial-concept-Mcs which is a-system of sensorial-concepts that we communicate.
---
· a-mind-view\a\ is a-brain construct that\a\ we do-not-know yet how exactly it is-formed.
· but we can-make a-sensorial model of it\a\, comprised of sensorial-concepts.
· in this site, these sensorial-concepts I am-using, I call sensorial-concepts-Mcs and the-sensorial mind-view, Mcs-view\b\.
· this\b\ sensorial view is the-input of language-mapping-method and anybody can-see.
· also this\b\ sensorial view is what anyone can-get if they decode correctly the-logo-view.
---
name::
* McshEngl.Mcs-view!⇒Mcsview, {2019-05-22}
* McshEngl.Mcsview!=Mcs-view,
* McshEngl.Mcs'view!⇒Mcsview,
* McshEngl.Mcs'conceptual_model!⇒Mcsview,
* McshEngl.McsAwView!⇒Mcsview,
* McshEngl.Mcsvw!⇒Mcsview, {2020-07-06}
* McshEngl.Mcsvw!=Mcs-view!⇒Mcsview,
* McshEngl.Mcs-subworldview!⇒Mcsview,
* McshEngl.concept-model--of--sensorial-concepts!⇒Mcsview,
* McshEngl.conceptual-model--of--sensorial-concepts!⇒Mcsview,
* McshEngl.conceptual_model.sensorial!⇒Mcsview,
* McshEngl.conceptual-modelAsMcs!⇒Mcsview,
* McshEngl.conceptual-system-of-Mcs!⇒Mcsview,
* McshEngl.conceptual_system.sensorial!⇒Mcsview,
* McshEngl.infoViewMcs!⇒Mcsview,
* McshEngl.model.004_Mcs_view!⇒Mcsview, {2020-08-04}
* McshEngl.model.Mcs_view!⇒Mcsview, {2020-08-04}
* McshEngl.model-of-sensorial-concepts!⇒Mcsview,
* McshEngl.modelConceptView!⇒Mcsview,
* McshEngl.modelConceptViewMcs!⇒Mcsview,
* McshEngl.modelInfoView.Mcs!⇒Mcsview,
* McshEngl.sensoconcept-model!⇒Mcsview, {2021-06-05}
* McshEngl.sensorial--conceptual-model!⇒Mcsview,
* McshEngl.sensorial--conceptual-system!⇒Mcsview,
* McshEngl.sensorial-concept-model!⇒Mcsview,
* McshEngl.sensorial-conceptual-model!⇒Mcsview,
* McshEngl.sensorial-concept--view!⇒Mcsview, {2020-11-10}
* McshEngl.sensorial-concept-view!⇒Mcsview,
* McshEngl.sensorial-mind-view!⇒Mcsview,
* McshEngl.sensorial-view!⇒Mcsview, {2020-05-06}
* McshEngl.subworldview-of-Mcs!⇒Mcsview,
* McshEngl.system-of-conceptsSensorial!⇒Mcsview,
* McshEngl.viewBrnSnsHumn!⇒Mcsview,
* McshEngl.viewMcs!⇒Mcsview,
* McshEngl.viewMindSensorial!⇒Mcsview,
* McshEngl.viewSensorial!⇒Mcsview,
* McshEngl.view-of-Mcs!⇒Mcsview,
* sensorial-brain-concept-view!⇒Mcsview,
* sensorial-mind-view--of-lagoHmnm!⇒Mcsview,
====== lagoGreek:
* McshElln.αισθητών-εννοιών--εννοιακό-μοντέλο!⇒Mcsview,
* McshElln.αισθητών-εννοιών--θεώρηση!⇒Mcsview,
* McshElln.εννοιακό-μοντέλο--αισθητών-εννοιών!⇒Mcsview,
* McshElln.θεώρηση--αισθητών-εννοιών!⇒Mcsview,
description::
× Mcsh-creation: {2026-10-04}
name::
* McshEngl.Mcsview'generic_specific_tree,
generic-tree::
* McshEngl.Mcsview:generic,
===
* model:generic,
* system:generic,
* whole:generic,
* ...entity:generic,
specific-tree::
* McshEngl.Mcsview.specific,
===
* Mcsview.Mcsdir!@McshCor000002#idMcsvDir,
* Mcsview.Mcswv!@McshCor000002#idMcswv,
* Mcsview.Mcsbase!@McshCor000002#idMcsbv,
===
* Mcsview.HmmdviewMindSenso!@McshLag000007#idLHmnmipt2,
description::
× Mcsh-creation: {2026-10-04}
· directory-Mcsview is a-Mcs-view that is-stored in a-computer-directory.
name::
* McshEngl.directory-view-of-Mcs!⇒Mcsdir,
* McshEngl.Mcsdir!=directory-view-of-Mcs,
* McshEngl.Mcs'dir_view!⇒Mcsdir,
* McshEngl.directory-view--of-Mcs!⇒Mcsdir,
* McshEngl.Mcs-dir-view!⇒Mcsdir,
* McshEngl.Mcsdv!⇒Mcsdir, {2020-06-17}
* McshEngl.directory-Mcsview!⇒Mcsdir,
* McshEngl.viewDirMcs!⇒Mcsdir,
====== lagoGreek:
* McshElln.φάκελος--αισθητών-εννοιών!=Mcsdv!⇒Mcsdir,
generic-tree::
* McshEngl.Mcsdir:generic,
===
* Mcsview:generic,
* model:generic,
* system:generic,
* ...entity:generic,
description::
× Mcsh-creation: {2026-10-04}
· Mcs-worldview is a-Mcs-view of an-entity (human, group-of-humans, organization-of-humans) with ALL their Mcs-views.
· an-Mcs-worldview is a-Mcs.
· an-Mcs-worldview is MONOSEMOUS, because the-Mcs-text it uses is monosemous.
· an-Mcs-worldview is SUBJECTIVE, it describes the-view about the-world of the-entity that supports it.
name::
* McshEngl.worldview-of-Mcs!⇒Mcswv,
* McshEngl.Mcswv!=worldview-of-Mcs,
* McshEngl.Mcs'world_view!⇒Mcswv,
* McshEngl.Mcs.worldview!⇒Mcswv,
* McshEngl.Mcs'worldview!⇒Mcswv,
* McshEngl.Mcs-worldview!⇒Mcswv, {2019-05-22}
* McshEngl.McsAsWorldview!⇒Mcswv,
* McshEngl.McsViewAsWorldview!⇒Mcswv,
* McshEngl.Mcsworldview!⇒Mcswv,
* McshEngl.McsWorld!⇒Mcswv, {2019-03-01}
* McshEngl.Mcsw!⇒Mcswv,
* McshEngl.modelConceptWorld!⇒Mcswv,
* McshEngl.modelConceptWorldMcs!⇒Mcswv,
* McshEngl.modelInfoWorldMcs!⇒Mcswv,
* McshEngl.sensorial-concept--pedia!⇒Mcswv,
* McshEngl.sensorial-concept--worldview!⇒Mcswv,
* McshEngl.sensorial-mind-worldview!⇒Mcswv,
* McshEngl.viewWorldMcs!⇒Mcswv,
* McshEngl.world_view.Mcs!⇒Mcswv,
* McshEngl.worldviewAsMcs!⇒Mcswv,
* McshEngl.worldviewMcs!⇒Mcswv,
* McshEngl.worldviewMindSensorial!⇒Mcswv,
* McshEngl.worldviewSensorialMind!⇒Mcswv,
====== lagoGreek:
* McshElln.αισθητών-εννοιών--κοσμοθεώρηση!⇒Mcswv,
* McshElln.κοσμοθεώρηση--αισθητών-εννοιών!⇒Mcswv,
description::
× Mcsh-creation: {2026-10-04}
· the-human|s that endorse this worlview.
description::
× Mcsh-creation: {2026-10-04}
· every Mcs-worldview is-stored in a-site in a root-directory, the-'dirMcs'.
name::
* McshEngl.Mcs'dirMiwMcs,
* McshEngl.Mcswv'dirMcsh, {2020-06-17}
* McshEngl.Mcswv'dirMiwMcs,
* McshEngl.Mcswv'root_directory,
* McshEngl.dirMcs,
* McshEngl.Mcswv'dirMcs,
description::
× Mcsh-creation: {2026-10-04}
name::
* McshEngl.Mcswv'generic_specific_tree,
generic-tree::
* McshEngl.Mcswv:generic,
===
* worldviewSensorial!@McshLag000003#idWldv003,
* worldviewMind:generic,
* Mcsview:generic,
* Mcs:generic,
* Mcsview:generic,
* worldview:generic,
* ...entity:generic,
specific-tree::
* McshEngl.Mcswv.specific,
===
* Mcswv.Mws!@Mcsh000000,
description::
× Mcsh-creation: {2026-10-04}
· Mcs-base-view is a-Mcs-view with a-set of Mcs-worldviews.
name::
* McshEngl.base-of-Mcs!⇒Mcsbase,
* McshEngl.Mcsbase!=base-of-Mcs,
* McshEngl.Mcs'base_view!⇒Mcsbase,
* McshEngl.Mcs-base-view!⇒Mcsbase,
* McshEngl.Mcsbv!⇒Mcsbase, {2020-06-17}
* McshEngl.Mcsb!⇒Mcsbase, {2020-06-17}
* McshEngl.base-view-of-Mcs!⇒Mcsbase,
* McshEngl.base_view.Mcs!⇒Mcsbase,
* McshEngl.baseMcs!⇒Mcsbase,
* McshEngl.baseviewMcs!⇒Mcsbase,
* McshEngl.baseview.Mcs!⇒Mcsbase,
* McshEngl.sensorial-concept--base!⇒Mcsbase,
* McshEngl.viewBaseMcs!⇒Mcsbase,
* McshEngl.worldview-baseMcs!⇒Mcsbase,
====== lagoGreek:
* McshElln.βάση--αισθητών-κοσμοθεωρήσεων!⇒Mcsbase,
generic-tree::
* McshEngl.Mcsbase:generic,
===
* Mcsview:generic,
* model:generic,
* system:generic,
* ...entity:generic,
description::
× Mcsh-creation: {2026-10-04}
· the-relation between the-Mcs and the-mind-concept that models.
name::
* McshEngl.Mcs'mind_relation,
description::
× Mcsh-creation: {2026-10-04}
· an-Mcs models a-mind-concept using the-Mcs-language.
name::
* McshEngl.Mcs_mind_concept,
* McshEngl.Mcs'mind_concept!⇒Mcs_mind_concept,
* McshEngl.mind-concept-of-Mcs,
* McshEngl.Mcs'mind_relation'mind_concept,
description::
× Mcsh-creation: {2026-10-04}
· the-relation between the-Mcs and the-semu-concepts a-language creates from it.
description::
× Mcsh-creation: {2026-10-04}
· the-relation between the-Mcs and the-names a-language creates from it.
description::
× Mcsh-creation: {2026-10-04}
· the-language we use to map mind-concepts to Mcs.
name::
* McshEngl.Mcs'language!⇒Mcslago,
* McshEngl.Mcslago!=Mcs'language,
* McshEngl.Mcs-language!⇒Mcslago,
specific-tree::
* Mcshlago!@McshTchInf000009,
* HtmlSfi,
* Xml,
description::
× Mcsh-creation: {2026-10-04}
· Mcs-manager is the-tools, computers, computer-networks, computer-programs, info-storage-entities, etc we use to manage Mcs.
· Mcsmgr manages from inception, worldviews and more accurately baseviews.
name::
* McshEngl.Mcs-manager!⇒Mcsmgr,
* McshEngl.Mcsmgr!=Mcs-manager, {2020-11-12}
* McshEngl.Mcs'manager!⇒Mcsmgr,
* McshEngl.Mcs-mngr!⇒Mcsmgr,
* McshEngl.Mcs-worldview-manager!⇒Mcsmgr,
* McshEngl.Mcs-tool!⇒Mcsmgr,
* McshEngl.Mcsm!⇒Mcsmgr, {2020-06-17}
* McshEngl.Mcsmanager!⇒Mcsmgr,
* Mcsmgr!=Mcs-manager!=Mcsmgr, {2025-08-08}
* McshEngl.Mcsmngr!⇒Mcsmgr,
* McshEngl.Mcswv'manager!⇒Mcsmgr,
* McshEngl.Mcswvm!⇒Mcsmgr,
* McshEngl.SCM!=sensorial-concept-manager!⇒Mcsmgr,
* McshEngl.sensorial-concept-manager!⇒Mcsmgr, {2020-06-25}
* McshEngl.worldview_manager.Mcs!⇒Mcsmgr,
=== OLD:
* McshEngl.Mcs-pgm!⇒Mcsmgr, {2017-10-15} //emphais on mcs,
* McshEngl.structured-concept-manager!⇒Mcsmgr, {2016-08-23}
* McshEngl.programModelConceptStructured!⇒Mcsmgr, {2016-08-23}
* McshEngl.programMcs!⇒Mcsmgr, {2016-08-23}
* McshEngl.concept-processor!⇒Mcsmgr, {2016-03-12} //in contrast 'word-processor',
* McshEngl.cbsmgr!⇒Mcsmgr, {2013-07-31}
* McshEngl.cbscms!⇒Mcsmgr, {2013-04-04}
* McshEngl.cbs-cms!⇒Mcsmgr, {2013-04-03}
* McshEngl.cmsCbs!⇒Mcsmgr, {2013-04-03}
* McshEngl.cms.cbs!⇒Mcsmgr, {2013-04-03}
* McshEngl.cbs-management-system!⇒Mcsmgr, {2013-03-30}
* McshEngl.cbsms!⇒Mcsmgr, {2013-03-30}
* McshEngl.prgCbs!⇒Mcsmgr, {2012-03-27}
* McshEngl.cbsPrg!⇒Mcsmgr, {2012-03-18}
* McshEngl.sbcMgr!⇒Mcsmgr, {2011-05-28}
* McshEngl.ConceptBrainualSensorialManager!⇒Mcsmgr, {2011-05-27}
* McshEngl.cbsManager!⇒Mcsmgr, {2011-05-27}
* McshEngl.SBViewManager!⇒Mcsmgr, {2011-01-29}
* SciMgr!⇒Mcsmgr, {2011-01-28}
* McshEngl.koncesto-program!⇒Mcsmgr, {2008-01-19}
* McshEngl.SCprogram!⇒Mcsmgr, {2008-01-13}
* McshEngl.KNBprogram!⇒Mcsmgr, {2007-12-19}
* McshEngl.KNprogram!⇒Mcsmgr, {2007-12-18}
* McshEngl.brainepto-base-purification-program!⇒Mcsmgr, {2007-12-08}
* McshEngl.bbpp!⇒Mcsmgr, {2007-12-08}
* McshEngl.brainepto-base-program!⇒Mcsmgr, {2007-12-01}
* McshEngl.brainepto-base-manager!⇒Mcsmgr, {2007-11-27}
* McshEngl.brainepto-base-management!⇒Mcsmgr, {2007-11-26}
* McshEngl.knowledge-system-management!⇒Mcsmgr, {2007-11-25}
* McshEngl.integruolo!⇒Mcsmgr, {2007-07-30} //I want to emphasize its integration function and NOT just the management which is more generic,
* McshEngl.knowledge-integrator!⇒Mcsmgr, {2007-06-22}
* McshEngl.brainepto-model--integrator!⇒Mcsmgr, {2007-01-30}
* McshEngl.model-breinepto--management!⇒Mcsmgr, {2006-06-01}
* McshEngl.mdbm!⇒Mcsmgr, {2006-06-01}
* McshEngl.Conceptual-Model-Management-System!⇒Mcsmgr, {2001-07-30}
* McshEngl.Concept-Base-Management-System!⇒Mcsmgr, {2001-06-20}
* McshEngl.scs-science-support-system!⇒Mcsmgr, {1999-08-27}
* McshEngl.scs-sss!⇒Mcsmgr, {1999-08-27}
* McshEngl.SCS!=structured-concept-system!⇒Mcsmgr,
* McshEngl.Knowledge-Management-System!⇒Mcsmgr, {1999-02-08}
* McshEngl.Structured-Concept-System-KMS!⇒Mcsmgr, {1997-11-09}
* McshEngl.scs-KMS!⇒Mcsmgr, {1997-11-09}
* McshEngl.scs-program!⇒Mcsmgr, {1997-11-09}
* McshEngl.scs_editor/browser!⇒Mcsmgr, {1997-10-05}
* McshEngl.structured-concept-system-creator-program!⇒Mcsmgr, {1997-05-09}
* McshEngl.scsc-program!⇒Mcsmgr, {1997-05-09}
* McshEngl.scs-creator!⇒Mcsmgr, {1997-05-06}
* McshEngl.scsc!⇒Mcsmgr, {1997-05-06}
* McshEngl.Science-Support-System!⇒Mcsmgr, {1990}
* McshEngl.SSS!=science-support-system!⇒Mcsmgr,
===
* McshEngl.structured-concept--knowledge-management-system!⇒Mcsmgr,
* McshEngl.SBC-program-(sensorial-brain-concept-program)!⇒Mcsmgr,
* McshEngl.sensorial-brain-concept-program-(SBC-program)!⇒Mcsmgr,
====== lagoGreek:
* McshElln.ΔΟΜΗΜΕΝΩΝ-ΕΝΝΟΙΩΝ-ΣΥΣΤΗΜΑ-ΔΙΑΧΕΙΡΙΣΗΣ-ΓΝΩΣΗΣ!⇒Mcsmgr, {1999-02-08}
* McshElln.ΠΡΟΓΡΑΜΑ-ΔΗΜΙΟΥΡΓΙΑΣ-ΣΥΣΤΗΜΑΤΩΝ-ΔΟΜΗΜΕΝΩΝ-ΕΝΝΟΙΩΝ!⇒Mcsmgr,
* McshElln.ΣΥΣΤΗΜΑ-ΔΟΜΗΜΕΝΩΝ-ΕΝΝΟΙΩΝ!⇒Mcsmgr,
===
* the-evolution of the-names for the-manager shows, in some degree, and the-evolution of the-concept.
description::
× Mcsh-creation: {2026-10-04}
· the-info the-manager stores and retrieves.
· the-goal of Mcsmgr is the-construction of base-views (set of world-views) because information is subjective and there-is no absolute truth info.
· in contrast, today {2020} we see the-construction of only ONE worldview:
- https://www.wolframalpha.com/tour/: "expert-level knowledge",
- https://en.wikipedia.org/wiki/Help:Editing: "Ideally, all information should be cited and verifiable by reliable sources."
- https://www.cyc.com/archives/service/cyc-knowledge-base: "Cyc has the world’s broadest and deepest common sense knowledge base (KB), by orders of magnitude."
name::
* McshEngl.Knlgbase.Mcsmgr,
* McshEngl.Mcsmgr'info,
* McshEngl.Mcsmgr'att006_info,
description::
× Mcsh-creation: {2026-10-04}
· user is any human or machine that uses the-system.
name::
* McshEngl.Mcsmgr'user,
* McshEngl.Mcsmgr'att013_user,
description::
× Mcsh-creation: {2026-10-04}
· one or more humans that support a-worldview.
name::
* McshEngl.Mcsmgr'author,
* McshEngl.Mcsmgr'user.author,
description::
× Mcsh-creation: {2026-10-04}
· a-human that reads the-base.
name::
* McshEngl.Mcsmgr'reader,
* McshEngl.Mcsmgr'user.reader,
description::
× Mcsh-creation: {2026-04-27}
· the-functions of the-manager.
name::
* McshEngl.Mcsmgr'doing!⇒Mcsmgrdoing,
* McshEngl.Mcsmgrdoing!=Mcsmgr'doing,
* McshEngl.Mcsmgrdong!⇒Mcsmgrdoing,
description::
× Mcsh-creation: {2026-10-04}
· the-first function the-manager must-have is to be-able to build a-consistent base.
name::
* McshEngl.Mcsmgr_building_base,
* McshEngl.Mcsmgr'building_base!⇒Mcsmgr_building_base,
* McshEngl.Mcsmgr'att001_building_base,
* McshEngl.McsmDoing.building_base,
* McshEngl.Mcsmgr'storing_base,
* McshEngl.Mcsmgrdong'building_base,
description::
× Mcsh-creation: {2026-10-04}
· the-method the-manager uses to gather info for its base.
· adding new concepts must-not-invalidate existing relations.
* directly by an-author.
* by collaboration.
* automatically from another machine.
* mechanical-learning techniques.
* natural-language-understanding.
* sensor support.
name::
* McshEngl.Mcsmgr_acquiring_base,
* McshEngl.Mcsmgr'acquiring_base!⇒Mcsmgr_acquiring_base,
* McshEngl.Mcsmgr'att024_acquiring_base,
* McshEngl.McsmDoing.adding_concepts,
* McshEngl.McsmDoing.acquiring_base,
description::
× Mcsh-creation: {2026-10-04}
· changing relations must-be-validated.
· changing the-names of Mcs, the-base must-be the-same.
· the-evolution of the-base must-show the-changes.
name::
* McshEngl.Mcsmgr_att026_changing_info,
* McshEngl.Mcsmgr'att026_changing_info!⇒Mcsmgr_att026_changing_info,
* McshEngl.Mcsmgr'changing_info!⇒Mcsmgr_att026_changing_info,
* McshEngl.Mcsmgr'changing_info,
* McshEngl.McsmDoing.changing_info,
description::
× Mcsh-creation: {2026-10-04}
· changing the-format of a-Mcs, to change this format in all other Mcs.
name::
* McshEngl.Mcsmgr'formating,
* McshEngl.Mcsmgr'att003_formating,
* McshEngl.McsmDoing.formating,
description::
× Mcsh-creation: {2026-10-04}
· this is THE-MOST IMPORTANT DOING the-manager MUST-HAVE.
· changing an-attribute in an-Mcs\a\, the-manager to make this change in all its\a\ specifics.
· generalizing attribute: make it and attribute of its generic.
name::
* McshEngl.Mcsmgr_generic_specific_managing,
* McshEngl.Mcsmgr'generic_specific_managing!⇒Mcsmgr_generic_specific_managing,
* McshEngl.Mcsmgr'att004_generic_specific_managing,
* McshEngl.McsmDoing.generic_specific_managing,
description::
× Mcsh-creation: {2026-10-04}
· whole-part-relations managing is the-second MOST IMPORTANT DOING the-manager MUST-HAVE.
name::
* McshEngl.Mcsmgr_whole_part_managing,
* McshEngl.Mcsmgr'whole_part_managing!⇒Mcsmgr_whole_part_managing,
* McshEngl.Mcsmgr'att005_whole_part_managing,
* McshEngl.McsmDoing.whole_part_managing,
description::
× Mcsh-creation: {2026-10-04}
· the-manager must validate the-relations among the-stored-concepts for incosistencies.
· on every editing the-system must validate the-new relations.
name::
* McshEngl.Mcsmgr_validating,
* McshEngl.Mcsmgr'validating!⇒Mcsmgr_validating,
* McshEngl.Mcsmgr'att009_validating!⇒Mcsmgr_validating,
* McshEngl.Mcsmgr'consistency_checking!⇒Mcsmgr_validating,
* McshEngl.McsmDoing.validating!⇒Mcsmgr_validating,
* McshEngl.Mcsmgr'integrating!⇒Mcsmgr_validating,
description::
× Mcsh-creation: {2026-10-04}
· IF current-cpt has as PART cpt-x,
THEN cpt-x has as WHOLE current-cpt.
name::
* McshEngl.Mcsmgr_validating.part,
* McshEngl.Mcsmgr'att015_part_validating,
description::
× Mcsh-creation: {2026-10-04}
· IF current-cpt has as WHOLE cpt-x,
THEN cpt-x has as PART current-cpt.
name::
* McshEngl.Mcsmgr_validating.whole,
* McshEngl.Mcsmgr'att016_whole_validating,
description::
× Mcsh-creation: {2026-10-04}
· IF current-cpt has as GENERIC cpt-y
THEN the-ATTRIBUTES of cpt-y are attributes of current-cpt. {1999-01-17}.
===
· IF current-cpt has as GENERIC cpt-y
THEN cpt-y has as SPECIFIC current-cpt. {1999-02-28}.
name::
* McshEngl.Mcsmgr_validating.generic,
* McshEngl.Mcsmgr'att017_generic_validating,
description::
× Mcsh-creation: {2026-10-04}
· IF current-cpt has as SPECIFIC cpt-y
THEN the-attributes of current-cpt are attributes of cpt-y. {1999-01-17}.
===
· IF current-cpt has as SPECIFIC cpt-y
THEN cpt-y has as GENERIC current-cpt. {1999-02-22}.
name::
* McshEngl.Mcsmgr_validating.specific,
* McshEngl.Mcsmgr'att018_specific_validating,
description::
× Mcsh-creation: {2026-10-04}
· IF current-cpt has as SIBLING cpt-y
THEN both concepts have a-common generic-concept. {1999-02-09}.
===
· IF current-cpt has as sibling cpt-y in relation to generic cpt-w
AND cpt-y has as sibling cpt-z in relation to generic cpt-w
THEN current-cpt has as sibling cpt-z. {1999-03-13}.
===
· IF current-cpt has as GENERIC cpt-y
THEN check if ALL the-specifics of cpt-y are siblings of current-cpt (except current!). {1999-04-17}.
name::
* McshEngl.Mcsmgr_validating.sibling,
* McshEngl.Mcsmgr'att019_sibling_validating,
description::
× Mcsh-creation: {2026-10-04}
· the-elements of a-specific-division must-have its specific-complements.
===
· the-elements of a-part-division must-have its part-complements.
name::
* McshEngl.Mcsmgr_validating.complement,
* McshEngl.Mcsmgr'att020_complement_validating,
description::
× Mcsh-creation: {2026-10-04}
· every concept must-have part, whole, generic, specific definitions.
name::
* McshEngl.Mcsmgr_validating.definition,
* McshEngl.Mcsmgr'att021_definition_validating,
description::
× Mcsh-creation: {2026-10-04}
· IF current-cpt has a-relation with cpt-y
THEN cpt-y must-have this relation with current-cpt.
name::
* McshEngl.Mcsmgr_validating.relation,
* McshEngl.Mcsmgr'att022_relation_validating,
description::
× Mcsh-creation: {2026-10-04}
· the-manager must-support the-consistent|inconsistent name-managing-mechanisms of the-natural-languages of its base.
· names help us to communicate our info.
· bad-names, bad communication.
· the-manager must-have under control the-names used in its info.
* it must validate the-names against the-naming conventions used in its base-view.
* it must find undefined names.
* it must can-change a-name in all cases used.
* ...
name::
* McshEngl.Mcsmgr_name_managing,
* McshEngl.Mcsmgr'name_managing!⇒Mcsmgr_name_managing,
* McshEngl.Mcsmgr'att010_name_managing,
* McshEngl.McsmDoing.name_managing,
description::
× Mcsh-creation: {2026-10-04}
· the-value of the-system depends on the-easiness of retrieving the-stored-base.
name::
* McshEngl.Mcsmgr_retrieving_base,
* McshEngl.Mcsmgr'retrieving_base!⇒Mcsmgr_retrieving_base,
* McshEngl.Mcsmgr'att002_retrieving_base,
* McshEngl.McsmDoing.retrieving_base,
* McshEngl.Mcsmgrdong'retrieving_base,
description::
× Mcsh-creation: {2026-10-04}
· the-presentation of the-system's-info is very important for the-reader.
· Mcsmgr presents its info per concept ubiquitously.
name::
* McshEngl.Mcsmgr'presenting,
* McshEngl.Mcsmgr'att011_presenting,
* McshEngl.McsmDoing.presenting,
* McshEngl.Mcsmgr'reading,
description::
× Mcsh-creation: {2026-10-04}
· the-manager must-have the-ability to navigate through its base.
· the-navigating must-be-easy and fast.
name::
* McshEngl.Mcsmgr'navigating,
* McshEngl.Mcsmgr'att012_navigating,
* McshEngl.McsmDoing.navigating,
description::
× Mcsh-creation: {2026-10-04}
· the-manager must be-able to compute the-translation of the-stored-info in all natural-languages and not just store the-translation.
name::
* McshEngl.Mcsmgr'translating,
* McshEngl.Mcsmgr'att007_translating,
* McshEngl.McsmDoing.translating,
description::
× Mcsh-creation: {2026-10-04}
· the-system must answer questions on the-stored-info.
· it must be-able to compute answers and not just retrieve stored-info.
name::
* McshEngl.Mcsmgr'questioning,
* McshEngl.Mcsmgr'att008_questioning,
* McshEngl.McsmDoing.questioning,
description::
× Mcsh-creation: {2026-10-04}
· the-manager must-can-make many computations (building or retrieving) on its base.
name::
* McshEngl.Mcsmgr'computing,
* McshEngl.Mcsmgr'att014_computing,
* McshEngl.McsmDoing.computing,
* McshEngl.Mcsmgr'inferencing,
* McshEngl.Mcsmgrdong'computing,
specific-tree::
* name-managing,
* questioning,
* translating,
* validating,
description::
× Mcsh-creation: {2026-10-04}
· the-manager must-have the-ability to store and present the-evolution of its base.
name::
* McshEngl.Mcsmgr_evoluting_managing,
* McshEngl.Mcsmgr'evoluting_managing!⇒Mcsmgr_evoluting_managing,
* McshEngl.Mcsmgr'att023_evoluting_managing,
* McshEngl.McsmDoing.evoluting_managing,
* McshEngl.Mcsmgrdong'evoluting_managing,
description::
× Mcsh-creation: {2026-10-04}
name::
* McshEngl.Mcsmgrdoing'generic_specific_tree,
generic-tree::
* McshEngl.Mcsmgrdoing:generic,
===
* ...entity:generic,
specific-tree::
* McshEngl.Mcsmgrdoing.specific,
===
* building-base,
* retrieving-base,
===
* building,
* computing,
* consistency-checking,
* formating,
* generic-specific-relations-management,
* inferencing,
* integrating,
* name-management,
* navigating,
* parent-child-relations-management,
* presenting,
* retrieving,
* questioning,
* storing,
* translating,
* validating,
* whole-part-relations-management,
===
* Mcsmgrdoing.McsmgrAAjdoing!@McshCor000002#idMcsmAajdong,
* Mcsmgrdoing.Mcshmgrdoing!@McshTchInf000009#idLMcshmngrdong,
description::
× Mcsh-creation: {2026-10-04}
· see Mcs'evoluting.
name::
* McshEngl.evoluting-of-Mcsmgr!⇒Mcsmgrevolg,
* McshEngl.Mcsmgrevolg!=evoluting-of-Mcsmgr,
* McshEngl.Mcsmgr'evoluting!⇒Mcsmgrevolg,
description::
× Mcsh-creation: {2026-04-27}
name::
* McshEngl.Mcsmgr'generic_specific_tree,
generic-tree::
* McshEngl.Mcsmgr:generic,
===
* KnlgMngr:generic,
* worldview-management-tool!@McshLag000003#idWldvatt002,
* Cptlmngr:generic,
* ...entity:generic,
specific-tree::
* McshEngl.Mcsmgr.specific,
===
* Webapp-Mcsmgr,
* Mcsmgr.Mcshmgr!@McshTchInf000009#idLMcshmngr,
* HtmlMgr-Mcsmgr!@McshCor000002#idMcsmHmljv,
* Mcsmgr.McsmgrAAj!@McshCor000002#idMcsmAaj,
* Mcsmgr.FvMcsmgr!@McshCor000002#idMcsmFlvw,
* Mcsmgr.McsmgrPaper!@McshCor000002#idMcsmPrst,
===
* Mws'management_tool!@Mcsh000000#idMwstool,
description::
× Mcsh-creation: {2026-10-04}
· McsmgrIdeal\a\ is an-Mcsmgr we have to build in order to have better worldviews and consequently a-better society.
· it must-be a-decentralized-system like IPFS.
· it must-be like a-web-app, so any machine can-work with it.
· it must-support many worldviews.
· it must-support all natural-languages.
· it must-support the-evolution of the-world and the-evolution of the-worldviews.
· on Mcsmgr attributes, I will-present its\a\ attributes.
name::
* McshEngl.McsmgrIdeal, {2021-03-24}
* McshEngl.Mcsmgr.ideal!⇒McsmgrIdeal,
* McshEngl.Mcsmgr.long_term!⇒McsmgrIdeal,
* McshEngl.ideal-Mcsmgr!⇒McsmgrIdeal,
* McshEngl.long-term-Mcsmgr!⇒McsmgrIdeal,
* McshEngl.needed-Mcsmgr!⇒McsmgrIdeal,
description::
× Mcsh-creation: {2026-10-04}
· synagonism-mw is a-MediaWiki-Skin that greatly improves page-READING by moving the-table-of-contents on the-left and showing the-position the-reader is-reading.
· I created this skin because I was-thinking to use MedaWiki (wikipedia's manager) as an-Mcsmgr for Html-Mcs.
· I abandoned this idea because I did-not-want to use the-PHP-language.
name::
* McshEngl.Mcsmgr.MediaWiki_!⇒McsmgrWiki,
* McshEngl.McsmgrWiki,
* McshEngl.Mcsmgr.MediaWiki!⇒McsmgrWiki,
* McshEngl.Mcsmgr.synagonism_mw!⇒McsmgrWiki,
* McshEngl.synagonism-mw--Mcsmgr!⇒McsmgrWiki,
addressWpg::
* http://synagonism-mw.sourceforge.net/,
* https://sourceforge.net/projects/synagonism-mw/,
description::
× Mcsh-creation: {2026-10-04}
· with my ToC-Chrome-extension I could-have an-Html-Mcs\a\ without the-need of a-special program to view it\a\.
· but with a-cost. It\a\ was-depended on Chrome-browser and a-source-editor.
· old webpage on synagonism.net.
· on chrome web store: https://chrome.google.com/webstore/detail/table-of-contents-crx/eeknhipceeelbgdbcmchicoaoalfdnhi.
· on GitHub: https://github.com/synagonism/CrxToc.
name::
* McshEngl.table-of-contents-Crx--Mcsmgr!⇒McsmgrCrxToc,
* McshEngl.McsmgrCrxToc!=table-of-contents-Crx--Mcsmgr,
* McshEngl.Mcsmgr.CrxToc!⇒McsmgrCrxToc,
* McshEngl.table-of-contents-Chrome-extension--Mcsmgr!⇒McsmgrCrxToc,
* McshEngl.Toc-Chrome-extension--Mcsmgr!⇒McsmgrCrxToc,
* McshEngl.Toc-Crx--Mcsmgr!⇒McsmgrCrxToc,
* McshEngl.crxToc-Mcsmgr!⇒McsmgrCrxToc,
description::
× Mcsh-creation: {2026-10-04}
· HtmlMgr is a-free java open-source BROWSER and a-wysiwyg and source EDITOR of html-files\a\ that contain structured-fragment-identifiers that denote the-structure of the-files\a\.
· quickly I stopped developing this project, when I realized that java is not the-appropriate language to manage html, BUT shows the-wysiwyg functionality needed.
· HtmlMgr was my first try to create a-senso-concept-Mcs in Html.
· I published it on SourceForge.
· the-last working version with AAj documentation, I published on GitHub.
· you can-download ("download raw file") the-whole directory from github, unzip it, and run it locally.
· you can also download it, here in synagonism.net.
name::
* McshEngl.Mcsmgr.HtmlMgr_,
* McshEngl.HtmlMgr-Mcsmgr,
* McshEngl.Mcsmgr.HtmlMgr,
* McshEngl.Mcsmgr.Sfi,
* McshEngl.McsmgrSfi,
* McshEngl.app.HtmlMgr,
addressWpg::
* https://github.com/synagonism/appHtmlMgr: last working version with AAj documentation,
* https://htmlmgr.sourceforge.net/,
* https://lists.w3.org/Archives/Public/public-html-comments/2010May/0027.html,
description::
× Mcsh-creation: {2026-10-04}
· AAj is my-java open-source Mcsmgr that uses Xml-Mcs.
· I worked on this project until {2010} when projects like wikipedia showed to me that a-worldview must be online.
· the-last working version 00.02.02-2010.06.20, with documentation viewable with my HtmlMgr, I published on GitHub.
· you can-download ("download raw file") the-whole directory from github, unzip it, and run it locally.
· you can also download it, here in synagonism.net.
name::
* McshEngl.Mcsmgr.AAj_!⇒McsmgrAAj,
* McshEngl.McsmgrAAj, {2021-03-22}
* McshEngl.AAj!⇒McsmgrAAj,
* McshEngl.AAj-Mcsmgr!⇒McsmgrAAj,
* McshEngl.AAj-SensorialConcept-ComputerSystem!⇒McsmgrAAj,
* McshEngl.AAj-SensorialConcept-System!⇒McsmgrAAj,
* McshEngl.AAj-Brainepto-Base-Purification-System!⇒McsmgrAAj,
* McshEngl.AAj-Knowledge-Integrator!⇒McsmgrAAj,
* McshEngl.KnlgMngr.003_AAj!⇒McsmgrAAj,
* McshEngl.KnlgMngr.AAj!⇒McsmgrAAj,
* McshEngl.Mcsmgr.AAj!⇒McsmgrAAj,
* McshEngl.app.AAj!⇒McsmgrAAj,
* McshEngl.jSCS!⇒McsmgrAAj,
* McshEngl.java-Brainepto-Model-Manager!⇒McsmgrAAj,
* McshEngl.java-Mental-Model-Management!⇒McsmgrAAj,
* McshEngl.java-Structured-Concept-Knowledge-Management-System!⇒McsmgrAAj,
* McshEngl.java-Structured-Concept-System!⇒McsmgrAAj,
* McshEngl.java-Science-Support-System!⇒McsmgrAAj,
description::
× Mcsh-creation: {2026-10-04}
· view-of-McsmgrAAj is a-system of McsAAj on any-entity of one author.
· quantity of concepts:
* Human-Body 4 concepts
* InfoTech 113 concepts
* Language 142 concepts
* Philosophy 41 concepts
* Society 2 concepts
* Source 1 concept
* SUM 303 concepts
* [https://synagonism.net/dirOtenet/jscs.html-{2000-06-19}]
name::
* McshEngl.McsmgrAAj'view,
* McshEngl.McsmgrAAj'subworldview,
description::
× Mcsh-creation: {2026-10-04}
· worldview-of-McsmgrAAj is the-system of McsAAj of ONE author.
description::
× Mcsh-creation: {2026-10-04}
· base-of-McsmgrAAj is the-set of its supported worldviews.
name::
* McshEngl.McsmgrAAj'base,
* McshEngl.McsmgrAAj'knowledge_base,
description::
× Mcsh-creation: {2026-10-04}
* https://github.com/synagonism/appAAj,
* https://synagonism.net/dirOtenet/jscs.html,
* https://synagonism.net/dirAAj2010/hSbc/aaj-sbccs.html,
description::
× Mcsh-creation: {2026-10-04}
* computer,
* program,
** viewer,
** editor,
** html-browser,
* base,
name::
* McshEngl.structure-of-McsmgrAAj!⇒McsmgrAAjsrtr,
* McshEngl.McsmgrAAjsrtr!=structure-of-McsmgrAAj,
* McshEngl.McsmgrAAj'structure!⇒McsmgrAAjsrtr,
description::
× Mcsh-creation: {2026-10-04}
· AAj-viewer
name::
* McshEngl.McsmgrAAj_viewer,
* McshEngl.McsmgrAAj'viewer!⇒McsmgrAAj_viewer,
* McshEngl.McsmgrAAj'structure'viewer!⇒McsmgrAAj_viewer,
description::
× Mcsh-creation: {2026-10-04}
* Program:
** About Program/Author,
** Exit,
* Retrieve-XKnowledgeBase:
** Back,
** History,
** Refresh,
** Information of Current XConcept,
** View All Tree-Structures,
** View Whole-Tree-Structure,
** View Part-Tree-Structure,
** View Generic-Tree-Structure,
** View Specific-Tree-Structure,
** View Specific-Complements,
** Find XConcept:
*** Find XConcept by Name,
*** Find XConcept by Related XConcepts,
*** Find XConcept by FormalID,
*** Find XConcept by Formal-Name,
*** Find Selected XConcept,
*** Open XConceptFile,
*** Find XConcept by Searching Xml-Files,
*** Find XConcept by FormalID/FormalName File-Lists,
** Find TxConcept-Terms of TxConcept-Name,
** Ask AAj a Question,
** Translate,
** XKnowledgeBase Statistics,
** XKnowledgeBase Author,
* Build-XKnowledgeBase:
** Integrate Current XConcept:
*** Total Integration,
*** Part Integration,
*** Whole Integration,
*** Generic Integration,
*** Specific Integration,
*** Environment Integration,
** Edit Source of XConcept,
** Manage Names,
** Update LgConcept-Terms,
** Override Selected Part,
** Generalize Selected Part,
** Make Part Inherited,
** Change SubWorldView,
** Add XConcept:
*** Add NEW XConcept to Current:
**** As PART,
**** As WHOLE,
**** As GENERIC,
**** As SPECIFIC,
**** As ENVIRONMENT,
**** As ATTRIBUTE,
*** Add EXISTING XConcept to Current:
*** Add UNRELATED XConcept,
** Delete XConcept:
*** Delete XConcept,
*** Delete Related XConcept:
**** Delete PART,
**** Delete WHOLE,
**** Delete GENERIC,
**** Delete SPECIFIC,
**** Delete DIMENSION,
**** Delete ENVIRONMENT,
*** Delete UNRELATED XConcept to Current
** Add Specific-Division ON Attribute,
** Manage Sinago-Terms,
** Create Sensorial-Worldview,
** Create Sensorial-SubWorldview,
** Set Author of XKnowledgeBase,
** Save Variables,
* Language:
** English Language,
** Greek Language,
** Esperanto Language,
** Sinago Language,
* Help:
** Help in Html,
** What is AAj,
** AAj Parts Tree,
** AAj Functions Tree,
name::
* McshEngl.McsmgrAAj_viewer'menu,
* McshEngl.McsmgrAAj'menu.viewer,
* McshEngl.McsmgrAAj'viewer'menu,
description::
× Mcsh-creation: {2026-10-04}
· AAj-editor
name::
* McshEngl.McsmgrAAj'editor,
* McshEngl.McsmgrAAj'Xml_editor,
* McshEngl.McsmgrAAj'structure'editor,
description::
× Mcsh-creation: {2026-10-04}
· AAj-browser
name::
* McshEngl.McsmgrAAj'browser,
* McshEngl.McsmgrAAj'Html_browser,
* McshEngl.McsmgrAAj'structure'browser,
description::
× Mcsh-creation: {2026-10-04}
· base-building,
· base-retrieving,
name::
* McshEngl.doing-of-McsmgrAAj!⇒McsmgrAAjdoing,
* McshEngl.McsmgrAAjdoing!=doing-of-McsmgrAAj,
* McshEngl.McsmgrAAj'doing!⇒McsmgrAAjdoing,
generic-tree::
* McshEngl.McsmgrAAjdoing:generic,
===
* Mcsmgrdoing:generic,
* ...entity:generic,
description::
× Mcsh-creation: {2026-10-04}
* accessing-base,
* navigating-base,
* presenting-base,
name::
* McshEngl.McsmgrAAjdoing.retrieving_base!⇒McsmgrAAjRetrieving,
* McshEngl.McsmgrAAjRetrieving!=McsmgrAAjdoing.retrieving_base,
* McshEngl.McsmgrAAj'doing.retrieving_base!⇒McsmgrAAjRetrieving,
* McshEngl.McsmgrAAj'retrieving_base!⇒McsmgrAAjRetrieving,
description::
× Mcsh-creation: {2026-10-04}
· AAj is a-local-system the-user must store in his computer.
name::
* McshEngl.McsmgrAAjRetrieving.accessing_base!⇒McsmgrAAjdoingAccessing,
* McshEngl.McsmgrAAj'retrieving.accessing_base!⇒McsmgrAAjdoingAccessing,
* McshEngl.McsmgrAAjdoingAccessing!=McsmgrAAj'retrieving.accessing_base,
* McshEngl.McsmgrAAj_accessing_base!⇒McsmgrAAjdoingAccessing,
* McshEngl.McsmgrAAj'accessing_base!⇒McsmgrAAjdoingAccessing,
* McshEngl.McsmgrAAj'doing.accessing_base!⇒McsmgrAAjdoingAccessing,
description::
× Mcsh-creation: {2026-10-04}
* user-interface,
* finding|searching,
* asking|inferring,
name::
* McshEngl.McsmgrAAjRetrieving.navigating_base!⇒McsmgrAAjdoingNavigating,
* McshEngl.McsmgrAAj'retrieving.navigating_base!⇒McsmgrAAjdoingNavigating,
* McshEngl.McsmgrAAjdoingNavigating!=McsmgrAAj'retrieving.navigating_base,
* McshEngl.McsmgrAAjdoing.navigating_base!⇒McsmgrAAjdoingNavigating,
* McshEngl.McsmgrAAj'doing.navigating_base!⇒McsmgrAAjdoingNavigating,
* McshEngl.McsmgrAAj'navigating_base!⇒McsmgrAAjdoingNavigating,
description::
× Mcsh-creation: {2026-10-04}
· the-program is a-global one, in Java terms. Now it can-present the user-interface in English, Greek, Sinago and Esperanto languages.
description::
× Mcsh-creation: {2026-10-04}
· the-system has a-SMART search function. It can-search related Mcs, for example, a) the-parts of an-Mcs or b) all the-Mcs of the-same kind.
· of course, it can-search ALL the-Mcs for its names and synonyms. It can-search for a-'word', part of a-word, and for a-'name' (one or more words that name an-entity).
name::
* McshEngl.McsmgrAAj'doing.searching,
* McshEngl.McsmgrAAj'finding,
* McshEngl.McsmgrAAj'searching,
description::
× Mcsh-creation: {2026-10-04}
· the-system can-answer "is specific of" and "is part of" questions.
name::
* McshEngl.McsmgrAAj'asking,
* McshEngl.McsmgrAAj'doing.asking,
* McshEngl.McsmgrAAj'inferring,
description::
× Mcsh-creation: {2026-10-04}
* table-of-contents,
* worldviews,
* help-sytem,
name::
* McshEngl.McsmgrAAjRetrieving.presenting_base!⇒McsmgrAAjdoingPresenting,
* McshEngl.McsmgrAAj'retrieving.presenting_base!⇒McsmgrAAjdoingPresenting,
* McshEngl.McsmgrAAj'retrieving.presenting_base,
* McshEngl.McsmgrAAjdoing.presenting_base!⇒McsmgrAAjdoingPresenting,
* McshEngl.McsmgrAAj'doing.presenting_base!⇒McsmgrAAjdoingPresenting,
* McshEngl.McsmgrAAj'presenting_base!⇒McsmgrAAjdoingPresenting,
description::
× Mcsh-creation: {2026-10-04}
· the-viewer displays one Mcs at a time AND all its first-level attributes.
· the-window is divided in two parts. On the-left, there is a-tree with the-table-of-contents of the-Mcs. On the-right, the-attributes of the-Mcs are-displayed.
description::
× Mcsh-creation: {2026-10-04}
· the-reader, when searches for an-Mcs, can-choose the-worldview he is intresting on or all of them.
description::
× Mcsh-creation: {2026-10-04}
· the-system displays its help\a\ in the-same format that displays the-stored knowledge.
· also it displays it\a\ in html-format through a-simple html-browser.
· on last version, I incorporated my HtmlMgr to display the-help-system.
description::
× Mcsh-creation: {2026-10-04}
· acquiring-base,
· adding-base,
· changing-base,
name::
* McshEngl.McsmgrAAjdoing.building_base!⇒McsmgrAAjBuilding,
* McshEngl.McsmgrAAjBuilding!=McsmgrAAjdoing.building_base,
* McshEngl.McsmgrAAj'doing.building_base!⇒McsmgrAAjBuilding,
* McshEngl.McsmgrAAj'building_base!⇒McsmgrAAjBuilding,
specific-tree::
* acquiring,
* adding,
* changing,
* validating,
description::
× Mcsh-creation: {2026-10-04}
· the-author adds its info to the-base.
name::
* McshEngl.McsmgrAAjBuilding.acquiring_info!⇒McsmgrAAjdoingAcquiring,
* McshEngl.McsmgrAAj'building.acquiring_info!⇒McsmgrAAjdoingAcquiring,
* McshEngl.McsmgrAAjdoingAcquiring!=McsmgrAAj'building.acquiring_info,
* McshEngl.McsmgrAAj_acquiring_base!⇒McsmgrAAjdoingAcquiring,
* McshEngl.McsmgrAAj'acquiring_base!⇒McsmgrAAjdoingAcquiring,
* McshEngl.McsmgrAAj'doing.acquiring_base!⇒McsmgrAAjdoingAcquiring,
description::
× Mcsh-creation: {2026-10-04}
* editor: the-program has a-simple XML-editor. Any author who knows XML can-use it. Also the-editor is a-tool to check if something goes wrong.
* integrating,
name::
* McshEngl.McsmgrAAjBuilding.adding_info!⇒McsmgrAAjdoingAdding,
* McshEngl.McsmgrAAj'building.adding_info!⇒McsmgrAAjdoingAdding,
* McshEngl.McsmgrAAjdoingAdding!=McsmgrAAj'building.adding_info,
* McshEngl.McsmgrAAj_adding_info!⇒McsmgrAAjdoingAdding,
* McshEngl.McsmgrAAj'adding_info!⇒McsmgrAAjdoingAdding,
* McshEngl.McsmgrAAj'doing.adding_info!⇒McsmgrAAjdoingAdding,
description::
× Mcsh-creation: {2026-10-04}
* name-managing: changing the-name of a-Mcs does-NOT-affect the-base.
name::
* McshEngl.McsmgrAAjBuilding.changing_info!⇒McsmgrAAjdoingChanging,
* McshEngl.McsmgrAAj'building.changing_info!⇒McsmgrAAjdoingChanging,
* McshEngl.McsmgrAAjdoingChanging!=McsmgrAAj'building.changing_info,
* McshEngl.McsmgrAAj_changing_info!⇒McsmgrAAjdoingChanging,
* McshEngl.McsmgrAAj'changing_info!⇒McsmgrAAjdoingChanging,
* McshEngl.McsmgrAAj'doing.changing_info!⇒McsmgrAAjdoingChanging,
description::
× Mcsh-creation: {2026-10-04}
· this is the-notable function my-system now has. It CHECKS the-part-whole and generic-specific relations among Mcs and FIXES them. What I mean: writing an-Mcs, you must-integrate it with the-existing base. Then my-system can-check for Mcs-relations violations such as:
* Part-Integration: the-attribute-cpts of the-current-cpt must-have as whole-cpt the-current-cpt. If not my-system fixes the-error.
* Whole-Integration: the-whole-cpts of the-current-cpt must-have as attribute-cpts the-current-cpt. If not my-system fixes the-error.
* Generic-Integration: the-attribute-cpts of the-generic-cpts of the-current-cpt must-be attribute-cpts of the-current-cpt. If not my-system fixes the-error.
* Specific-Integration: The-specific-cpts must-have as attribute-cpts the-attribute-cpts of the-current-cpt. Also a-specific of current-cpt must-have as generic the-current. If not my-system fixes the-error.
* Environment-Integration: an-environment-cpt with another 'object' must be environment-cpt also to that 'object' and any environment-cpt must be related at least to two objects. If not my-system fixes the-error.
name::
* McshEngl.McsmgrAAjBuilding.validating_base!⇒McsmgrAAjdoingIntegrating,
* McshEngl.McsmgrAAj'building.validating_base!⇒McsmgrAAjdoingIntegrating,
* McshEngl.McsmgrAAjdoingIntegrating!=McsmgrAAj'building.validating_base,
* McshEngl.McsmgrAAjdoing.integrating_base!⇒McsmgrAAjdoingIntegrating,
* McshEngl.McsmgrAAj'doing.integrating_base!⇒McsmgrAAjdoingIntegrating,
* McshEngl.McsmgrAAj'integrating_base!⇒McsmgrAAjdoingIntegrating,
* McshEngl.McsmgrAAj'validating_base!⇒McsmgrAAjdoingIntegrating,
description::
× Mcsh-creation: {2026-10-04}
· AAj evolution.
name::
* McshEngl.evoluting-of-McsmgrAAj!⇒McsmgrAAjevolg,
* McshEngl.McsmgrAAjevolg!=evoluting-of-McsmgrAAj,
* McshEngl.McsmgrAAj'evoluting!⇒McsmgrAAjevolg,
{2010-06-20}-AAj-v00.02.03::
* AddNewAttribute with XmlDefinition
* LAST VERSION.
{2010-01-02..2010-06-20}-AAj-v00.02.02::
* {2010-06-19}: HtmlMgr
- HtmlMgr is incorporated in AAj.
- DOCUMENTATION is written with LocDocs.
* {2010-01-02} b-concept and sbConcept well established in my mind.
{2009-08-08..2010-01-02}-AAj-v00.02.01::
* shorter versions.
* {2009-08-20} difference in definition and creation
{2000-11-09..2009-08-08}-AAj-v00.02.00::
* Natural-language management.
* {2006-11-21} Komuno-language word management.
* {2004-11-21} English to Greek translation: "Concept is called every hierarchy-node of a concept-model" to "έννοια ονομάζεται κάθε κόμβος από ένα εννοιακό-μοντέλο".
* {2004-10-31} TextToMeaning.
* {2001-09-13} meaning-(ci) to logos
{2000-02-21..2000-11-08}-AAj-v00.01.09::
* No saxon.
* Definition with "Vudetro"
{1999-04-25..2000-02-21}-AAj-v00.01.08::
* Internal-Cpt kb'names.
* {2000-01} AAj searches for the-selected-name in the-text.
{1999-03-14..1999-04-25}-AAj-v00.01.07::
* Many-KB One-line-Xml-Att New-Formal-Name Inline-Concepts
* {1999-04}-base: multiple worldviews are-supported.
{1999-02-21..1999-03-14}-AAj-v00.01.06::
* smart-search: I've added the 'smart' search facility.
{1999-02-16..1999-02-21}-AAj-v00.01.05::
* Add Attribute Concept.
{1999-02-10..1999-02-16}-AAj-v00.01.04::
* Fix integration errors.
{1999-02-09..1999-02-10}-AAj-v00.01.03::
* generic-specific integration.
{1999-02-07..1999-02-09}-AAj-v00.01.02::
* General integration.
{1999-01-19..1999-02-07}-AAj-v00.01.01::
* Whole-part integration.
{1999-01-17..1999-01-19}-AAj-v00.00.17::
* Editor-xt.
{1999-01-03..1999-01-17}-AAj-v00.00.16::
* Sax-ConRef-Editor.
{1999-01-01..1999-01-03}-AAj-v00.00.15::
* Help
{1998-01-09..1999-01-01}-AAj-v00.00.14::
* JDK1.2 update.
{1998-01-04..1998-01-09}-AAj-v00.00.13::
* XML-ZLF parent3
{1997-12-30..1998-01-04}-AAj-v00.00.12::
* MSXML
{1997-12-28..1997-12-30}-AAj-v00.00.11::
* TextPane-MouseListener.
{1997-12-27..1997-12-28}-AAj-v00.00.10::
* Open-Search
{1997-12-21..1997-12-27}-AAj-v00.00.09::
* ToolBar.
{1997-12-14..1997-12-21}-AAj-v00.00.08::
* AAj uses structured-concepts\a\ in XML-format, and the-aelfred-parser to read them\a\.
{1997-12-13..1997-12-14}-AAj-v00.00.07::
* Tree
{1997-12-12..1997-12-13}-AAj-v00.00.06::
* Global-program.
{1997-06-08..1997-12-12}-AAj-v00.00.05::
* Applet.
{1997-05-25..1997-06-08}-AAj-v00.00.04::
* Bean
{1997-05-24..1997-05-25}-AAj-v00.00.03::
* About-command.
{1997-05-12..1997-05-24}-AAj-v00.00.02::
* ClassViewer.
{1997-05-12}-AAj-v00.00.01::
* The beginning.
* my first java program (just a user interface).
description::
× Mcsh-creation: {2026-10-04}
· in order to pay my tuitions for the-university, I had to work.
· I was lucky, because in one of my jobs, where we created electronic-books, we used the-hypertext fulltext-search Folio-Views-program, DOS-version.
· it was the-best program I have-met so far, for what I wanted to do.
· I began to store Mcs (as with my-paper-system) but now the-concepts were linked and I could easily navigate among them and search for every word I wrote describing the-attributes of concepts.
· In {1994} I bought the-windows version of FolioViews.
· with this I have created an-Mcs-base with hundred thousands of concepts.
· the-system, is a-working one.
· but in a-few years, it was obvious to me that I had to write my own program to have the-functionality I needed to manage Mcs.
· so, in {1997} I began my-java-program-AAj.
· I still use Folio-Views today-{2021} and because of it and my experience with Mcsmgr I created my Mcs-theory.
· the-quantity of concepts I cleared in my mind was the-cause to further understand and new other concepts and so my Mcs-theory is becoming more clear day after day.
· FolioViews-base contains a very important characteristic.
· it contains the-EVOLUTION of my-Mcs-theory and the-evolution of my-Worldview.
· this happens because when I added an-attribute on an-Mcs, I added and the-date I wrote it, at least on the-majority of cases.
name::
* McshEngl.Mcsmgr.FolioViews_!⇒FvMcsmgr,
* McshEngl.FolioViews-Mcsmgr!⇒FvMcsmgr,
* McshEngl.FvMcsmgr!=FolioViews-Mcsmgr,
* McshEngl.Mcsmgr.FolioViews!⇒FvMcsmgr,
addressWpg::
* https://synagonism.net/dirOtenet/scsimpl.html,
* https://synagonism.net/dirAAj2010/hSbc/sbc-system.html#h0.11.2p5,
description::
× Mcsh-creation: {2026-10-04}
· working on my-paper-system for about 4 years, its limits became apparent to me.
· also I was then confident that only computers could help us to manage knowledge.
· so, in {1989} I went to George-Washington-University to study computers (information-management).
· in {1990} my first try with computers was a-word-processor (word-perfect).
· in a-week, it became obvious that a-word-procesor was not the right tool for me.
· the-same year, my second try was a-relational-database-program, the-DBASE-IV.
· I created a-complicated system of formalism to store concepts per author, per date, per source.
· I spent enough hours on this system for nothing!!!
[https://synagonism.net/dirAAj2010/hSbc/sbc-system.html#h0.11.2p4]
name::
* McshEngl.Mcsmgr.DBASE_IV_,
* McshEngl.DBASE-IV-Mcsmgr,
* McshEngl.Mcsmgr.DBASE_IV,
* McshEngl.McsmgrDBASEIV,
description::
× Mcsh-creation: {2026-10-04}
· the-need to manage my knowledge, led me to construct a-paper-system.
· I had dossiers for concrete sciences and I had independent paper-sheets for concrete concepts.
· apparently, with the-expansion of knowledge it was difficult to manage that knowledge.
name::
* McshEngl.Mcsmgr.papersheet_!⇒McsmgrPaper,
* McshEngl.McsmgrPaper,
* McshEngl.Mcsmgr.papersheet!⇒McsmgrPaper,
* McshEngl.papersheet-Mcsmgr!⇒McsmgrPaper,
description::
× Mcsh-creation: {2026-04-27}
* evaluation-of-Mcs,
* human-concept,
* referent-of-Mcs,
name::
* McshEngl.Mcs'environment,
* McshEngl.McsAeEnvironment,
description::
× Mcsh-creation: {2026-04-27}
* AI,
* conceptual-graph,
* knowledge-graph,
* mind-map,
* ontology,
* topic-map,
description::
× Mcsh-creation: {2026-10-04}
· Mcs is A-MODEL of human-concept\a\, not a-specific of it\a\.
· then there-is a-one-to-one relation between a-Mcs and a-human-concept.
name::
* McshEngl.Mcs_relation_to_cptMind,
* McshEngl.Mcs'relation_to_cptMind!⇒Mcs_relation_to_cptMind,
* McshEngl.Mcs'relation_to_human_concept!⇒Mcs_relation_to_cptMind,
* McshEngl.Mcs'relation_to__human_concept,
* McshEngl.McsAeRelation-to--human-concept,
* McshEngl.cnptMind'relation_to__sensorial_concept,
* McshEngl.human_concept'relation_to__sensorial_concept,
* McshEngl.relation-of-cnptMind-to-Mcs,
* McshEngl.relation-of--human-concept--to-Mcs,
* McshEngl.relation-of-Mcs-to--human-concept,
* McshEngl.Mcs'relation_to_human_concept,
description::
× Mcsh-creation: {2026-10-04}
· the-concept 'cnptMind|Mcs' has referent cptMinds|Mcs.
· the-concept 'entity' has referent anything.
· then cnptMind|Mcs is NOT the-same with entity.
· 'entity' is the-most-generic 'cnptMind|Mcs'.
[Humn1959Sinagu.{2022-10-12}]
===
· cnptMind|Mcs has referent anything (concept and conceptNo).
· entity has referent anything.
· then cnptMind|Mcs is the-same with entity.
[Humn1959Sinagu.{2022-08-26}]
===
· entity is the-most-generic-Mcs, then Mcs is a-specific of entity.
· entity by itself IS a-Mcs, then entity is a-specific of Mcs.
· how we can-solve this VICIOUS-CIRCLE?
· there-is-no specific and generic by itself.
· always we have a specifc and generic of a-Mcs\a\, in relation to an-attribute of it\a\.
· IN RELATION TO THEIR REFERENTS, a-Mcs is a-specific on entity because the-referent of Mcs is a-subset of the-referent of entity.
· the-referent of entity includes everything, concepts, structured-concepts, material-entities, anything.
· on the-other-hand, IN RELATION TO THEIR ATTRIBUTES, the-entity\b\ is a-human-construct to model anything.
· it\b\ is a-structured-concept like all other structured-concepts we create to model our environment.
· then, in relation to their attributes, the-entity is a-specific structured-concept and it has the-attributes of the-structured-concept.
[Humn1959Sinagu.2017-12-04]
name::
* McshEngl.Mcs_relation_to_entity,
* McshEngl.Mcs'relation_to_entity!⇒Mcs_relation_to_entity,
* McshEngl.McsAeRelation-to-entity,
* McshEngl.cnptMind'relation_to_entity,
* McshEngl.entity'relation_to_cptMind,
* McshEngl.entity'relation_to__sensorial_concept,
* McshEngl.relation-of-entity-to-Mcs,
* McshEngl.relation-of-entity-to-cnptMind,
* McshEngl.relation-of-Mcs-to-entity,
description::
× Mcsh-creation: {2026-10-04}
· a-sensorial-concept is similar to 'object' in Oop-object-oriented-programing.
· objects serve the-inheritance-mechanism in programing-languages, and sensorial-concepts serve the-inheritance-mechanism in natural-languages.
· in contrast, sensorial-concepts inherit FROM other sensorial-concepts and inherit TO others, but objects inherit from classes or prototypes-of-constructors.
name::
* McshEngl.Oop_relation_to__sensorial_concept,
* McshEngl.Oop'relation_to__sensorial_concept!⇒Oop_relation_to__sensorial_concept,
* McshEngl.Mcs'relation_to_object_oriented_programing!⇒Oop_relation_to__sensorial_concept,
* McshEngl.Mcs'relation_to_Oop,
* McshEngl.Mcs'relation_to_object_oriented_programing,
* McshEngl.McsAeRelation-to-Oop,
* McshEngl.relation-of-Oop-to-Mcs,
* McshEngl.relation-of-Mcs-to-Oop,
description::
× Mcsh-creation: {2026-10-04}
· today's texts are unmanageable.
· just look at society's laws!
· in order to manage the enormous quantity of current information we need technology.
· automated-information or artificial-intelligence can-not-be-achieved by managing secondary-information (texts) which are models of primary-information.
· primary-information is-stored in human-brains as conceptual-models.
· automated-information can-be-achieved by managing primary-information.
· structured-concepts are the building blocks of MODELS of primary-information.
· next, we need computer-programs to manage structured-concept-models.
[Humn1959Sinagu.2017-11-28]
name::
* McshEngl.evaluation-of-Mcs!⇒Mcsevaln,
* McshEngl.Mcsevaln!=evaluation-of-Mcs,
* McshEngl.Mcsevalg!⇒Mcsevaln,
* McshEngl.Mcs'evaluation!⇒Mcsevaln,
* McshEngl.McsAeEvaluation!⇒Mcsevaln,
description::
× Mcsh-creation: {2026-10-04}
· truthness is the-mapping-relation of Mcs with its referent.
· truthness is a-matter of degree.
name::
* McshEngl.Mcs'truthness,
* McshEngl.truthness-of-Mcs,
description::
× Mcsh-creation: {2026-10-04}
· info written in Mcs-format WILL-BE monosemantic.
· this will-be-achieved using the same method with programing-languages: ONE DEFINITION RULE.
· compilers refuse to continue if a-name is-undefined or it has more than one definitions.
· in an-Mcs-worldview we can-define everything except 2 fundamental concepts we must-take for granted, as axioms:
* sympan: the most whole concept, and
* entity: the most generic concept,
[Humn1959Sinagu.2018-03-12]
===
· monosemanticity of info is a-prerequisite of artificial-intelligence.
[Humn1959Sinagu.2018-12-30]
===
· monosemanticity is a-prerequisite for correct translations.
[Humn1959Sinagu.2018-12-31]
name::
* McshEngl.monosemanticity-of-Mcs,
* McshEngl.Mcs'monosemanticity,
description::
× Mcsh-creation: {2026-10-04}
· consistent-info is info with no contradictions.
· it will-be-achieved from structureness.
· computer-programs will-validate the clear relations of structured-concepts and their positions in the two fundamental structures of an-Mcs-worldview: the-whole-part-tree and the-generic-specific-tree.
[Humn1959Sinagu.2018-03-12]
name::
* McshEngl.consistency-of-Mcs,
* McshEngl.Mcs'consistency,
* McshEngl.Mcs'integration,
description::
× Mcsh-creation: {2026-10-04}
· complete-info is info with no wholes in its structure.
· like consistency it will-be-achieved from structureness.
name::
* McshEngl.completeness-of-Mcs,
* McshEngl.Mcs'completeness,
description::
× Mcsh-creation: {2026-10-04}
· a-Mcs is NOT 'objective', 'true', 'systematic', 'scientific', ...
· a-Mcs is the SUBJECTIVE view of a-brain (the-subject) with a degree of truth, but monosemantic, consistent, and complete info.
· with Mcs we create many Mcs-worldviews that model the same reality.
[Humn1959Sinagu.2019-01-05]
name::
* McshEngl.Mcs'subjectivity,
* McshEngl.subjectivity-of-Mcs,
description::
× Mcsh-creation: {2026-10-04}
· sensorial-concepts-Mcs demonstrate the-unity-of-science thesis in philosophy-of-science that says that "all the sciences form a unified whole".
· additionally, I argue that there-are two "unified wholes" for the-(same)-reality:
· one, with generic-specific-tree-structure and outermost node, the-entity and the-second with whole-part-tree-structure and outermost node the-Sympan and arguing that entity ≡ Sympan.
· in other words, Mcs demonstrate a-holistic-method to knowledge.
name::
* McshEngl.Mcs_unity_of_science,
* McshEngl.Mcs'unity_of_science!⇒Mcs_unity_of_science,
* McshEngl.unity-of-science,
description::
× Mcsh-creation: {2026-10-04}
* name-notation,
* syntax-notation []{}(),
* anafora: \a\
· valence of Hmmdsemuverb\a\ is the-quantity of its\a\ semu-arguments.
{2021-07-23}
* pronunnciation: /dúer/
* citation:
[{1989} Getmanova, Logic, p15]
* sentence:
· in other words, Mcs demonstrate a-holistic-method to knowledge.
* formal-info:
× name: info.
name::
* McshEngl.notation-of-Mcs!⇒Mcsnotation,
* McshEngl.Mcsnotation!=notation-of-Mcs,
* McshEngl.Mcs'notation!⇒Mcsnotation,
====== lagoGreek:
* McshElln.σημειογραφία-αισθητής-έννοιας!η!⇒Mcsnotation,
description::
× Mcsh-creation: {2026-10-04}
· any info from other worldviews about this Mcs.
name::
* McshEngl.info-resource--of-Mcs!⇒Mcsinfrsc,
* McshEngl.Mcsinfrsc!=info-resource--of-Mcs,
* McshEngl.Mcs'info_resource!⇒Mcsinfrsc,
description::
× Mcsh-creation: {2026-10-04}
· another concept with referent same-as the-referent of this Mcs.
name::
* McshEngl.Mcs_same_referent,
* McshEngl.Mcs'same_referent!⇒Mcs_same_referent,
* McshEngl.same-referent--Mcs,
* McshEngl.Mcs'info_resource'same_referent,
description::
× Mcsh-creation: {2026-10-04}
· same-referent, other-view
name::
* McshEngl.Mcs_same_referent_other_view,
* McshEngl.Mcs'same_referent_other_view!⇒Mcs_same_referent_other_view,
* McshEngl.same-referent-other-view--Mcs,
description::
× Mcsh-creation: {2026-10-04}
· same-referent, similar-view
name::
* McshEngl.Mcs_same_referent_similar_view,
* McshEngl.Mcs'same_referent_similar_view!⇒Mcs_same_referent_similar_view,
* McshEngl.same-referent-similar-view--Mcs,
description::
× Mcsh-creation: {2026-10-04}
· same-referent, same-view
name::
* McshEngl.Mcs_same_referent_same_view,
* McshEngl.Mcs'same_referent_same_view!⇒Mcs_same_referent_same_view,
* McshEngl.same-referent-same-view--Mcs,
description::
× Mcsh-creation: {2026-10-04}
· another concept with SIMILAR referent.
name::
* McshEngl.Mcs_similar_referent,
* McshEngl.Mcs'similar_referent!⇒Mcs_similar_referent,
* McshEngl.similar-referent--Mcs,
* McshEngl.Mcs'info_resource'similar_referent,
description::
× Mcsh-creation: {2026-10-04}
· we can-manage sensorial-concepts-Mcs because they are sensible unlike its counterparts brain-concepts.
· today, computer-programs can-do incredible jobs on them.
name::
* McshEngl.Mcs'doing!⇒Mcsdoing,
* McshEngl.Mcsdoing!=Mcs'doing,
* McshEngl.Mcsmng!⇒Mcsdoing,
* McshEngl.Mcs'managing!⇒Mcsdoing,
description::
× Mcsh-creation: {2026-10-04}
name::
* McshEngl.Mcsdoing'generic_specific_tree,
generic-tree::
* McshEngl.Mcsdoing:generic,
===
* ...entity:generic,
specific-tree::
* McshEngl.Mcsdoing.specific,
===
* automatedSemi,
* automatedNo,
===
* creating,
* editing,
* naming,
* Mcsdoing.Mcs_searching!@McshCor000002#idMcssrcg,
* validating,
description::
× Mcsh-creation: {2026-10-04}
· creating a-new-Mcs.
name::
* McshEngl.Mcsdoing.creating,
* McshEngl.Mcs-creating,
* McshEngl.Mcsmng.creating,
description::
× Mcsh-creation: {2026-10-04}
· editing an-existing-Mcs.
name::
* McshEngl.Mcsdoing.editing,
* McshEngl.Mcs-editing,
* McshEngl.Mcsmng.editing,
description::
× Mcsh-creation: {2026-10-04}
· because Mcs-knowledge is structured, we can-access ANY concept, directly from anywhere.
· this site demonstrates this feature.
name::
* McshEngl.Mcsdoing.searching!⇒Mcs_searching,
* McshEngl.Mcs_searching,
* McshEngl.Mcs'searching!⇒Mcs_searching,
* McshEngl.Mcsmng.searching!⇒Mcs_searching,
* McshEngl.searching-Mcs!⇒Mcs_searching,
description::
× Mcsh-creation: {2026-10-04}
* descending-order for timeline. {2020-12-17}.
* regexp searching. {2020-12-17}.
* on space to search exactly the-name. {2020-12-17}.
description::
× Mcsh-creation: {2026-10-04}
name::
* McshEngl.Mcs'searching'generic_specific_tree,
generic-tree::
* McshEngl.Mcs_searching:generic,
===
* Mcsdoing:generic,
* ...entity:generic,
specific-tree::
* McshEngl.Mcs_searching.specific,
===
* Mcs_searching.Hitpsearching!@McshTchInf000008#idLHitpscg,
description::
× Mcsh-creation: {2026-10-04}
· naming is a-very-important-doing on Mcs.
· we must-follow the-same-rules all over a-worldview.
name::
* McshEngl.Mcsdoing.naming,
* McshEngl.Mcsmng.naming,
* McshEngl.Mcs-naming,
description::
× Mcsh-creation: {2026-10-04}
· Mcs-validating is any doing of consistency checking among the-Mcs.
name::
* McshEngl.Mcsdoing.validating!⇒Mcs_validating,
* McshEngl.Mcs_validating,
* McshEngl.Mcs-validating!⇒Mcs_validating,
* McshEngl.Mcs-consistency-checking!⇒Mcs_validating,
* McshEngl.Mcs-integrating!⇒Mcs_validating,
* McshEngl.Mcsmng.validating!⇒Mcs_validating,
description::
× Mcsh-creation: {2026-10-04}
name::
* McshEngl.Mcs_validating'generic_specific_tree,
generic-tree::
* McshEngl.Mcs_validating:generic,
===
* ...entity:generic,
specific-tree::
* McshEngl.Mcs_validating.specific,
===
· part-validating,
· whole-validating,
· generic-validating,
· specific-validating,
· sibling-validating,
· relation-validating,
· definition-validating,
description::
× Mcsh-creation: {2026-10-04}
· a) IF cpt1 has as part cpt2
THEN cpt2 has as whole cpt1.
description::
× Mcsh-creation: {2026-10-04}
· a) IF cpt1 has as whole cpt2
THEN cpt2 has as part cpt1.
description::
× Mcsh-creation: {2026-10-04}
· a) IF cpt1 has as generic cpt2
THEN the-attributes of cpt2 are and attributes of cpt1.
· b) IF cpt1 has as generic cpt2
THEN cpt2 has as specific cpt1.
description::
× Mcsh-creation: {2026-10-04}
· a) IF cpt1 has as specific cpt2
THEN the-attributes of cpt1 are and attributes of cpt-2.
· b) IF cpt1 has as specific cpt2
THEN cpt-2 has as generic cpt1.
description::
× Mcsh-creation: {2026-10-04}
· a) IF cpt1 has as sibling cpt2 in relation to generic cpt3
THEN both cpt1 and cpt2 have cpt3 as generic.
· b) IF cpt1 has as sibling cpt2 in relation to generic cpt3 AND cpt2 has as sibling cpt4 in relation to generic cpt3
THEN cpt1 has as sibling cpt4.
· c) IF cpt1 has as generic cpt2
THEN all the-specifics of cpt2 in one division\a\, which\a\ includes cpt1, are siblings of cpt1, except cpt1.
description::
× Mcsh-creation: {2026-10-04}
· IF cpt1 has a-relation with cpt2,
THEN cpt2 must-have the-(same)-relation with cpt1.
description::
× Mcsh-creation: {2026-10-04}
· search for: {Mcs
· this journey began around {1985} from my need to improve my then very limited worldview to figure out how we can-improve our society!
name::
* McshEngl.evoluting-of-Mcs!⇒Mcsevolg,
* McshEngl.Mcsevolg!=evoluting-of-Mcs,
* McshEngl.Mcs'evoluting!⇒Mcsevolg,
* McshEngl.McsAdEvoluting!⇒Mcsevolg,
{2020-10-18}-McsHitp-paragraph::
· I added paragraph-McsHitp in index-files.
· until now the-index-files contained only section-Mcs.
===
* McshEngl.{Mcs'2020-10-18}-paragraph-Mcs,
{2020-04-24}-McsHitp-200'000-names::
· my-worldview now {2020-04-24} contains 200'000 names of 43'000 direct accessed sensorial-concepts-Mcs.
===
* McshEngl.{Mcs'2020-04-04}-200'000-names,
{2020-01-06}-McsHitp-Sympan≡entity::
· by realizing this, I realized that the-two tree-structures (whole-part and generic-specific) of our knowledge, model the-(same)-entity, our Universe.
===
* McshEngl.{2020-01-06}-Mcs-Sympan≡entity,
* McshEngl.{Mcs'2020-01-06}-Sympan≡entity,
{2017-11-17}-McsHitp-PUBLICATION::
· I published the-Mcs (this concept, McsHitp) in synagonism.net and github.
· since {2017-11-17} I started publishing my worldview on GitHub.
· since then the-evolution of my-worldview is PUBLIC.
===
* McshEngl.{Mcs'2017-11-17}-McsHitp-publication-GitHub,
{2017-06-05}-McsHitp-searching::
· I added this functionality on my-worldview which demonstrates THE-POWER of sensorial-concepts-Mcs over texts.
{2013}-Mcs-synagonism.net--Hitp-worldview::
· in {2013} I bought the-domain synagonism.net and I started building my online Hitp-worldview as a-system of sensorial-concepts-McsHitp.
===
* McshEngl.{Mcs'2013}-synagonism.net,
{2011}-Hitp-webpage-language::
· in {2011} I started developing my Hitp-webpage-dialect that automatically displays the-table-of-contents of the-page without the-need of a-browser-extension.
{2011}-Mcs-synagonism-mw::
· a-MediaWiki-skin.
{2010}-ToC-Chrome-extension--HtmlMgr--Html-worldview::
· in {2010} I created my Table-of-Contents-Chrome-extension which displays automatically the-table-of-contents of a-webpage with headings.
· at the-same time {2010} I wrote my HtmlMgr-program written in java, which manages webpages in a-wysiwyg manner.
· with the-HtmlMgr I began writing an-offline Html-worldview using Html-sensorial-concepts viewed with my ToC-Chrome-extention.
· for historical purpose I published it here.
===
* McshEngl.{Mcs'2010}-Html-worldview,
{2002-02-18}-GWCreator-Applet::
· I published my-GreekWordCreator-Applet that demonstrates the-word creation mechanism languages use to create their words.
===
* McshEngl.{Mcs'2002-02-18}-GWCreator-Applet,
{2001-04-18}-WordForms-Applet::
· I published my-WordForms-Applet that inflects Greek and English names.
===
* McshEngl.{Mcs'2001-04-18}-WordForms-Applet,
{1997..2010}-Mcs-java-manager-AAj::
· in {1997} I started writing my own sensorial-concept-management-program with the-new then java-language.
· I worked on this project until {2010} when projects like wikipedia showed to me that a-worldview must be online.
===
* McshEngl.{Mcs'1997..2010}-Mcs-java-manager,
{1994..1995}-MCS-analytical-synthetical-definition::
I eliminated the vicious-cycles in my definitions with the use of analytical (generic-to-specific | whole-to-part) and synthetical (specific-to-generic | part-to-whole) definitions.
We can-define a concept ONLY in one way.
We can-have many definition of one-concept but we can-not-mix-up different type of definitions.
===
* McshEngl.{Mcs'1994..1995}-analytical-synthetical-definition,
{1993-10}-Mcs-forcast::
· By the year 2000, we gonna have a system where someone can write a book in which all information will be structured.
· By the year 2010, we will see a structured-science.
· By the year 2033, we will see ALL sciencies structured.
[https://synagonism.net/dirOtenet/scsevolution.html]
{1992..today}-Mcs-FolioViews-worldview::
· I began to build my worldview with the-Folio-Views-2.1-(DOS)\a\ XYPERTEXT-program.
· in {1994} I bought the-Windows-version of it\a\ and until today-{2020} I hold on this program my offline-worldview with hundred of thousands sensorial-concepts.
===
* McshEngl.{Mcs'1992}-hypertext-FolioViews-worldview,
{1990}-Science-Support-System-papper::
with my 1990-Science-Support-System-papper at George-Washington-University for my Information-Management master's degree, I understood that only a-future computer-system could-manage a-worldview.
===
* McshEngl.{Mcs'1990}-Science-Support-System-papper,
{1985..1989}-Mcs-paper-worldview::
· I began to build my paper-worldview as a-system-of-sensorial-concepts.
· each dossier contained a-view on a-subject with each sensorial-concept represented with a-paper-sheet in a-dossier.
· I had access to these concepts with paper-indexes.
· as the-quantity of concepts increased, quickly become apparent the-unmanageability of the-project.
· since then I BELIEVED that the-then-new information-technology will solve the-problem of knowledge-management.
· I stopped working on my paper-worldview in {1989} when I went at George-Washington-University to get a-master's-degree in "information-Management".
===
* McshEngl.{Mcs'1985..1989}-paper-worldview,
{1985}-Mcs-Hellenic-Mathematical-Society::
I suggested to distinguish in any math-concept its a)name, b)semasia, c)symbol, and d)graphics.
===
* McshEngl.{Mcs'1985}-Hellenic-Mathematical-Society,
{1978}-picture-of-my-worldview::
this picture of me in {1978} (19 years young) shows how I perceived my then worldview.
Ioannina (Litharitsia), math-student at University-of-Ioannina.
===
* McshEngl.{Mcs'1978}-picture-of-my-worldview,
description::
× Mcsh-creation: {2026-04-27}
· whole-part-tree of Mcs.
name::
* McshEngl.Mcs'whole_part_tree,
whole-tree::
* McshEngl.Mcs//whole,
===
* view,
* dir-view,
* worldview,
* base,
===
* Mcs-view,
* Mcs-worldview,
* human-society,
* International-society,
* ...sympan//whole,
part-tree::
* McshEngl.Mcs/part,
===
* attribute-of-Mcs,
description::
× Mcsh-creation: {2026-10-04}
· structure-of-Mcs is the-att-complement of doing.
· bodies and relations of Mcs.
name::
* McshEngl.structure-of-Mcs!⇒Mcssrtr,
* McshEngl.Mcssrtr!=structure-of-Mcs,
* McshEngl.Mcs'structure!⇒Mcssrtr,
description::
× Mcsh-creation: {2026-04-27}
· generic-specific-tree of Mcs.
name::
* McshEngl.Mcs'generic_specific_tree,
generic-tree::
* McshEngl.Mcs:generic,
===
* concept:generic,
* infoSenso:generic,
* info:generic,
* infoBio:generic,
* model:generic,
* entity:generic (the-most-generic),
* ...entity:generic,
specific-tree::
* McshEngl.Mcs.specific,
===
* Mcs.McsPaper!@McshCor000002#idMcsPrst,
* digital-Mcs,
===
* Everipedia-Mcs,
* Mcs.Mcsh!@McshTchInf000009#idMcsHitp,
* Mcs.Fv_Mcs!@McshCor000002#idMcsHrtt,
* Mcs.DeConcept!@McshCor000002#idMcsDctc,
===
* Mcs.Fv_Mcs!@McshCor000002#idMcsHrtt,
* Mcs.McsAAj!@McshCor000002#idMcsXml,
* Mcs.McsHtml!@McshCor000002#idMcsHtml,
description::
× Mcsh-creation: {2026-10-04}
· my first try {1985..1989} to create sensorial-concepts was the-use of paper-sheets with one concept per sheet.
· the-dificulty to manage this system, made obvious to me that I needed a-digital solution.
· that is why I got a-master degree in information-management from George-Washington-University {1989..1992}.
name::
* McshEngl.Mcs.papersheet_!⇒McsPaper,
* McshEngl.McsPaper,
* McshEngl.Mcs.papersheet!⇒McsPaper,
* McshEngl.paper-Mcs!⇒McsPaper,
* McshEngl.papersheet-Mcs!⇒McsPaper,
* McshEngl.papersheet--senso-concept!⇒McsPaper,
description::
× Mcsh-creation: {2026-10-04}
· in this system, an-Mcs is a-set of 'levels' analogous to Html-headings. All Mcs have the-same format (name, definition, misc attributes, whole, specifice ...). The-program created automatically the-structure of the-Mcs and I had direct access to any Mcs by using formal-names. Also it is a-wysiwyg-editor.
· in {1990} my first try with computers was a word processor (word perfect). In a week, it became obvious that word procesor was not the right tool for me.
· the same year, my second try was a relational database program, the DBASE-IV. I created a complicated system of formalism to store concepts per author, per date, per source. I spent enough hours on this system for nothing!!!
· In order to pay my tuitions for the university, I had to work. I was lucky, because in one of my jobs, where we created electronic-books, we used the hypertext fulltext-search Folio-Views program. It was the best program I have met for what I wanted to do. I began to store sensorial-concepts (as with my paper-system) but now the concepts were linked and I could easily navigate among them and search for every word I wrote describing the attributes of concepts.
name::
* McshEngl.Mcs.hypertext_!⇒Fv_Mcs,
* McshEngl.FolioViews-Mcs!⇒Fv_Mcs,
* McshEngl.Fv_Mcs!=FolioViews-Mcs,
* McshEngl.FolioViews--senso-concept!⇒Fv_Mcs,
* McshEngl.Mcs.FolioViews!⇒Fv_Mcs,
* McshEngl.Mcs.hypertext!⇒Fv_Mcs,
* McshEngl.McsFv!⇒Fv_Mcs,
* McshEngl.hypertext-Mcs!⇒Fv_Mcs,
* McshEngl.McsFolioviews!⇒Fv_Mcs,
* McshEngl.McsHypertext!⇒Fv_Mcs,
description::
× Mcsh-creation: {2026-10-04}
· McsXml is an-Mcs written with the-Xml-language.
· the-FolioViews-system, is a-working one. But in a few years, it was obvious to me that I had to write my own program to have the functionality I needed to manage sensorial-concepts.
· so, in {1997} I began my java program, AAj.
· I still use Folio-Views today-{2021} and because of it and my experience with AAj I created my-theory-on-language. The quantity of concepts I cleared in my mind was the cause to further understand and new other concepts and so my language-theory is becoming more clear day after day. My-FolioViews-knowledge-base contains a very important characteristic. It contains the EVOLUTION of my-language-theory and the evolution of my-worldview. This happens because when I added an attribute on a-sensorial-concept, I added and the date I wrote it, at least on the majority of cases.
· result: it is amazing how different is your current worldview from your worldview some years ago, but you think you always hold the-last one!!!
· presentation of an-McsAAj:
name::
* McshEngl.Mcs.Xml_!⇒McsAAj,
* McshEngl.McsAAj,
* McshEngl.AAj-Mcs!⇒McsAAj,
* McshEngl.Mcs.Xml!⇒McsAAj,
* McshEngl.McsXml!⇒McsAAj,
* McshEngl.Xml-Mcs!⇒McsAAj,
* McshEngl.Xml--senso-concept!⇒McsAAj,
* McshEngl.x-concept!⇒McsAAj,
* McshEngl.x-cpt!⇒McsAAj,
* McshEngl.xConcept!⇒McsAAj,
* McshEngl.xcpt!⇒McsAAj,
* McshEngl.xml--sensorial-b-concept!⇒McsAAj,
* McshEngl.xml-concept!⇒McsAAj,
description::
× Mcsh-creation: {2026-10-04}
<!--
LastModified: 2000.06.11
Creation: 1997dec,
-->
<!ELEMENT CONCEPT (NAME, SYNONYMS?, DEFINITION, PARTS?, WHOLE?, GENERIC?, SUBGENERIC?, ENVIRONMENT?)>
<!ATTLIST CONCEPT FRnAME CDATA #REQUIRED>
<!ATTLIST CONCEPT LASTiNTfRnUMBER CDATA #REQUIRED>
<!ATTLIST CONCEPT INTEGRATED CDATA #REQUIRED>
<!ATTLIST CONCEPT CREATED CDATA #REQUIRED>
<!ATTLIST CONCEPT LASTMODIFIED CDATA #REQUIRED>
<!ATTLIST CONCEPT AUTHOR CDATA #REQUIRED>
<!ELEMENT NAME (#PCDATA)>
<!ATTLIST NAME CREATED CDATA #REQUIRED>
<!ATTLIST NAME LASTMODIFIED CDATA #REQUIRED>
<!ATTLIST NAME AUTHOR CDATA #REQUIRED>
<!-- a 'NAME' with parent 'SYNONYMS' is a SYNONYM -->
<!ELEMENT SYNONYMS (NAME)+>
<!ATTLIST SYNONYMS CREATED CDATA #REQUIRED>
<!ATTLIST SYNONYMS LASTMODIFIED CDATA #REQUIRED>
<!ATTLIST SYNONYMS AUTHOR CDATA #REQUIRED>
<!ELEMENT DEFINITION (#PCDATA)>
<!ATTLIST DEFINITION LASTMODIFIED CDATA #REQUIRED>
<!ATTLIST DEFINITION AUTHOR CDATA #REQUIRED>
<!ELEMENT PARTS (CPTEXT | CPTINT)+>
<!ATTLIST PARTS CREATED CDATA #REQUIRED>
<!ATTLIST PARTS LASTMODIFIED CDATA #REQUIRED>
<!ATTLIST PARTS AUTHOR CDATA #REQUIRED>
<!ELEMENT CPTEXT EMPTY>
<!ATTLIST CPTEXT FRnAME CDATA #REQUIRED>
<!ATTLIST CPTEXT GENERIC CDATA #REQUIRED>
<!ATTLIST CPTEXT CREATED CDATA #REQUIRED>
<!ATTLIST CPTEXT LASTMODIFIED CDATA #REQUIRED>
<!ATTLIST CPTEXT AUTHOR CDATA #REQUIRED>
<!ELEMENT CPTINT (NAME, SYNONYMS?, DEFINITION)>
<!ATTLIST CPTINT FRnAME CDATA #REQUIRED>
<!ATTLIST CPTINT GENERIC CDATA #REQUIRED>
<!ATTLIST CPTINT CREATED CDATA #REQUIRED>
<!ATTLIST CPTINT LASTMODIFIED CDATA #REQUIRED>
<!ATTLIST CPTINT AUTHOR CDATA #REQUIRED>
<!ELEMENT WHOLE (CPTEXT)+>
<!ATTLIST WHOLE CREATED CDATA #REQUIRED>
<!ATTLIST WHOLE LASTMODIFIED CDATA #REQUIRED>
<!ATTLIST WHOLE AUTHOR CDATA #REQUIRED>
<!-- an xConcept can have many generic -->
<!ELEMENT GENERIC (CPTEXT)+>
<!ATTLIST GENERIC CREATED CDATA #REQUIRED>
<!ATTLIST GENERIC LASTMODIFIED CDATA #REQUIRED>
<!ATTLIST GENERIC AUTHOR CDATA #REQUIRED>
<!ELEMENT SUBGENERIC (CPTEXT | CPTINT | DIVISION)+>
<!ATTLIST SUBGENERIC CREATED CDATA #REQUIRED>
<!ATTLIST SUBGENERIC LASTMODIFIED CDATA #REQUIRED>
<!ATTLIST SUBGENERIC AUTHOR CDATA #REQUIRED>
<!-- a DIVISION is a set of xConcepts that comprise the current xConcept
and are created after the division of the current xConcept on an attribute CRT
-->
<!ELEMENT DIVISION (CPTEXT)+>
<!ATTLIST DIVISION CRT CDATA #REQUIRED>
<!ATTLIST DIVISION CREATED CDATA #REQUIRED>
<!ATTLIST DIVISION LASTMODIFIED CDATA #REQUIRED>
<!ATTLIST DIVISION AUTHOR CDATA #REQUIRED>
<!ELEMENT ENVIRONMENT (CPTEXT)+>
<!ATTLIST ENVIRONMENT CREATED CDATA #REQUIRED>
<!ATTLIST ENVIRONMENT LASTMODIFIED CDATA #REQUIRED>
<!ATTLIST ENVIRONMENT AUTHOR CDATA #REQUIRED>
description::
× Mcsh-creation: {2026-10-04}
· McsHtml is an-Mcs written with the-Html-language.
· since {2007} I began to write sensorial-concepts-Mcs in html-format in order to publish my language-theory on the-web.
· in {2010-05-30} I published my-HtmlMgr that presents html-files with structured-fragment-identifiers, but I quickly realized that java is not the appropriate language to manage html.
· in {2010-10-23} Ι published my-Chrome-ToC-extention to help me read easily html-docs without the-need of a-special program.
· in {2013-04-14} I created my-lagoHitp to publish html-docs (with automated-ToC, id, link-previews), which work on ALL browsers and since then I begun to write Mcs in this format, McsHitp.
name::
* McshEngl.Mcs.Html_!⇒McsHtml,
* McshEngl.McsHtml,
* McshEngl.Html-Mcs!⇒McsHtml,
* McshEngl.Html--senso-concept!⇒McsHtml,
* McshEngl.Mcs.Html!⇒McsHtml,
description::
× Mcsh-creation: {2026-10-04}
name::
* McshEngl.McsHtml'generic_specific_tree,
generic-tree::
* McshEngl.McsHtml:generic,
===
* Mcs:generic,
* concept:generic,
* model:generic,
* ...entity:generic,
specific-tree::
* McshEngl.McsHtml.specific,
===
* {2013..today}-Hitp,
* {2011}-MediaWiki,
* {2011}-crxToc,
* {2010}-Sfi|HtmlMgr,
description::
× Mcsh-creation: {2026-10-04}
· McsSfi is an-McsHtml managed with my-HtmlMgr-program, that implements structured-fragment-identifiers.
name::
* McshEngl.McsHtml.Sfi|HtmlMgr!⇒McsSfi,
* McshEngl.Mcs-Html-with-structured-fragment-identifiers!⇒McsSfi,
* McshEngl.McsSfi!=Mcs-Html-with-structured-fragment-identifiers,
* McshEngl.LocDoc-McsHtml!⇒McsSfi,
* McshEngl.McsHtml.HtmlMgr!⇒McsSfi,
* McshEngl.McsHtml.LocDoc!⇒McsSfi,
* McshEngl.McsHtml.Sfi!⇒McsSfi,
* McshEngl.Sfi-McsHtml!⇒McsSfi,
* McshEngl.structured-fragment-identifier-Mcs!⇒McsSfi,
addressWpg::
* https://lists.w3.org/Archives/Public/public-html-comments/2010May/0027.html,
* https://htmlmgr.sourceforge.net/,
* https://synagonism.net/dirAAj2010/,
description::
× Mcsh-creation: {2026-10-04}
· fragment-identifier-(= URI fragment) is the-characters after #, in the-address of a-webpage\a\, that denotes a-portion of it\a\.
· structured-fragment-identifier is a-type of fragment-identifier I proposed in {2010} to denoted any part of an-Html-file.
· "LocDoc (= Locator-Document)" I then called an Html-file with Sfi.
· my HtmlMgr automatically created and managed Sfi.
· example:
<p class="h0">
<a name="h0"></a>
HtmlMgr (version: 2010.09.15-alpha)
<a class="hide">#h0#</a>
</p>
<h1>
<a name="h0.1"></a>
DESCRIPTION
<a class="hide">#h0.1 h1#</a>
</h1>
<p>
<a name="h0.3p2"></a>
I extend the concept of fragment-identifiers, ...
<a class="hide">#h0.3p2#</a>
</p>
· #h0.6.3p2: denotes paragraph-2, inside the-3rd h2-element which is inside the-6th h1-element of an-Html-file.
name::
* McshEngl.Sfi!=structured-fragment-identifier/McsSfi,
* McshEngl.structured_fragment_identifier/McsSfi,
* McshEngl.McsSfi'Sfi,
description::
× Mcsh-creation: {2026-10-04}
· McsCrxToc is an-McsHtml viewed with my-crxToc.
name::
* McshEngl.McsCrxToc,
* McshEngl.McsHtml.crxToc!⇒McsCrxToc,
* McshEngl.crxToc-Mcs!⇒McsCrxToc,
addressWpg::
* example: http://synagonism-mw.sourceforge.net/,
description::
× Mcsh-creation: {2026-10-04}
· McsWiki is an-McsHtml I experiment with using the-MediaWiki program of Wikipedia.
name::
* McshEngl.McsWiki,
* McshEngl.McsHtml.MediaWiki!⇒McsWiki,
description::
× Mcsh-creation: {2026-10-04}
· Đ-Mcs WILL-be the next implementation of a-structured-concept.
· it will-be-stored on the-decentralized-internet.
· it will-have an unmodifiable history.
· it will-have indisputable owner.
· with all the-pros of Hitp_Mcs.
[Humn1959Sinagu.2018-02-18]
name::
* McshEngl.Mcs.DeChain!⇒DeConcept,
* McshEngl.DeConcept, {2023-09-09}
* McshEngl.Agntchain-Mcs!⇒DeConcept,
* McshEngl.Dconcept!⇒DeConcept, {2019-04-25}
* McshEngl.McsAgnetchain!⇒DeConcept,
* McshEngl.Mcs.Agntchain!⇒DeConcept,
* McshEngl.Mcs.decentralized!⇒DeConcept,
* McshEngl.decentralized--sensorial-concept!⇒DeConcept,
* McshEngl.Đ-Mcs!⇒DeConcept,
description::
× Mcsh-creation: {2026-10-04}
· McsDefined is an-Mcs with a-definition explicit or implicit.
· today the-majority of texts contain implicit-definitions and thus polysemantic names.
· paper-texts is imposible to have-defined all its names.
name::
* McshEngl.McsDefined,
* McshEngl.Mcs.defined!⇒McsDefined,
* McshEngl.defined-Mcs!⇒McsDefined,
description::
× Mcsh-creation: {2026-10-04}
· McsDefinedNo is an-Mcs without a-definition.
name::
* McshEngl.McsDefinedNo,
* McshEngl.Mcs.definedNo!⇒McsDefinedNo,
* McshEngl.definedNo-Mcs!⇒McsDefinedNo,
* McshEngl.undefined-Mcs!⇒McsDefinedNo,
description::
× Mcsh-creation: {2026-10-04}
· definite-Mcs is a-Mcs identifiable WITH clear boundaries.
name::
* McshEngl.McsDefinite,
* McshEngl.Mcs.definite!⇒McsDefinite,
* McshEngl.definite-Mcs!⇒McsDefinite,
====== lagoSinagu:
* dio!⇒McsDefinite,
====== lagoGreek:
* McshElln.σαφής-αισθητή-έννοια!⇒McsDefinite,
====== lagoTurkish:
* McshTurk.kesin!⇒McsDefinite,
description::
× Mcsh-creation: {2026-10-04}
· definiteNo-Mcs is a-Mcs identifiable WITHOUT clear boundaries.
name::
* McshEngl.Mcs.definiteNo,
* McshEngl.definiteNo-Mcs,
* McshEngl.fuzzy-Mcs,
* McshEngl.indefinite-Mcs,
* McshEngl.vague-Mcs,
====== lagoSinagu:
* dioUgo,
====== lagoGreek:
* McshElln.ασαφής-αισθητή-έννοια!=McsDefinite,
====== lagoTurkish:
* McshTurk.belirsiz!=McsDefiniteNo,
description::
× Mcsh-creation: {2026-10-04}
· relative-Mcs is a-Mcs defined in relation to another one SAME Mcs.
· example: time relative to another time.
name::
* McshEngl.McsRelative,
* McshEngl.Mcs.relative!⇒McsRelative,
* McshEngl.rltv!⇒McsRelative,
* McshEngl.relative-Mcs!⇒McsRelative,
====== lagoSinagu:
* tio!⇒McsRelative,
====== lagoGreek:
* McshElln.Μεα.σχετική!⇒McsRelative,
* McshElln.έννοια-σχετική!⇒McsRelative,
* McshElln.σχετική-έννοια!⇒McsRelative,
description::
× Mcsh-creation: {2026-10-04}
· relativeNo-Mcs is a-Mcs NOT defined in relation to another one SAME Mcs.
name::
* McshEngl.Mcs.relativeNo,
* McshEngl.relativeNo-Mcs,
====== lagoSinagu:
* tioUgo!=relativeNo-Mcs,
This page was-visited times since {2017-11-17}
page-wholepath:: synagonism.net / worldviewSngu / dirCore / modelConceptSensorial-Mcs
SEARCH::
This page uses 'locator-names', names that when you find them, you find the-LOCATION of the-concept they denote.
LOCAL-SEARCH:
Type CTRL+F "CTRL+F "McshLag4.words-of-con", to go to the-LOCATION of the-concept.
GLOBAL-SEARCH:
Clicking on the-GREEN-BAR of a-page you have access to the-global--locator-names of my-site.
A-preview of the-description of a-global-name makes reading fast.
Abbreviations have no description.
webpage-versions::
• version.last.dynamic: ../../dirMcsh/dirCor/McshCor000002.last.html,
• version.previous: ../../dirMcs/dirCor/McsCor000002.last.html,
• version.5-0-0.2021-04-05 (4-91): ../../dirMiwMcs/filMcs.5-0-0.2021-04-05.html,
• version.4-0-0.2019-08-06 (3.65): ../../dirMiwMcs/FilMcs.4-0-0.2019-08-06.html,
• version.3-0-0.2017-11-26.last: ../../dirMiwMcs/FilMcs.3-0-0.2017-11-26.html,
• version.2-0-0.2017-11-21: ../../dirMiwMcs/filMcs.2-0-0.2017-11-21.html,
• version.1-0-0.2017-11-20: ../../dirMiwMcs/filMcs.1-0-0.2017-11-20.html,
• version.0-1-0.2017-11-17.published: ../../dirMiwMcs/filMcs.0-1-0.2017-11-17.html,
Comment here with a GitHub-account, or comment on X: @synagonism.