GENERIC-SPECIFIC-TREE of name_notation

description::
× Mcsh-creation: {2026-10-04}

name::
* McshEngl.name_notation'generic-specific-tree,
* McshEngl.name_notation'specific-generic-tree,

generic-tree::
* McshEngl.name_notation_Gntr,
===
* convention_Gntr,
* ...entity_Gntr,

specific-tree::
* McshEngl.name_notation.specific,
* McshEngl.name_notation_Sptr,
===
* 2-words-names,
* no-space,
* attribute,
* capital,
* upper|lower-case,
* ! extra-info,
* !~ PoS,
* !⇒ main-name,
* != translation,
* {time},
* [info-resource],
* \reference,

name_notation.2-words-names

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.name-notation.2-words-names,
* McshEngl.name_notation.2-words-names,
* McshEngl.2-words-names-notation,
* McshEngl.two-words-names-notation,

name_notation.no-space

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,
[HumnSngu.2018-01-22]

· EXCEPTION: when the-name must denote a-character and we want to make it visible well. {2026-10-17}

name::
* McshEngl.name-notation.no-space,
* McshEngl.name_notation.no-space,

name_notation.attribute

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,
[HumnSngu.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--name-notation,
* McshEngl.name-notation.'attribute,
* McshEngl.name-notation.attribute('),
* McshEngl.name_notation.attribute,

name_notation.capital

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, Sysnode, sys_node,
[humnSngu.{2026-08-27}]

· Webapi = many words name, first capital.
· lagoSinago = generic-specific name, first small.
[{2024-11-14} HumnSngu]

· first capital:
* initialisms: Hitp, Html,
* many-words: Webapi,
* instance-concepts: Earth, Athens,
* exception: short-names: net, ogn, Ogsm,
[HumnSngu.2018-01-22]

name::
* McshEngl.name-notation.capital,
* McshEngl.name_notation.capital,

name_notation.upper|lower-case

description::
× Mcsh-creation: {2026-10-04}
· 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,
[HumnSngu.2018-01-14]

name::
* McshEngl.name-notation.lower|upper-case,
* McshEngl.name-notation.upper|lower-case,
* McshEngl.name_notation.upper|lower-case,

name_notation.! extra-info

description::
× Mcsh-creation: {2026-10-04}
- McsEll.σύστημα!το,
- McsEll.καλός!-ός-ή-ό,
· method of inflection:

name::
* McshEngl.! extra-info--name-notation,
* McshEngl.name-notation.! extra-info,
* McshEngl.name-notation.extra-info.!,

name_notation.!~ PoS

description::
× Mcsh-creation: {2026-10-04}
- McshElln.ένας!~AdjeElln,

name::
* McshEngl.!~ PoS--name-notation,
* McshEngl.name-notation.!~ PoS,
* McshEngl.name-notation.PoS !~,

name_notation.!⇒ main-name

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.main_name__name_notation,
* McshEngl.main-name--name-notation!⇒main_name__name_notation,
* McshEngl.!⇒main_name__name_notation,
* McshEngl.main-name--name-notation-(!‍⇒)!⇒main_name__name_notation,
* McshEngl.name-notation.!‍⇒main-name!⇒main_name__name_notation,
* McshEngl.name-notation.main-name.!‍⇒!⇒main_name__name_notation,

name_notation.!= translation

description::
× Mcsh-creation: {2026-10-04}
· denotes translation to English.

name::
* McshEngl.!=translation--name-notation,
* McshEngl.name-notation.!= translation,
* McshEngl.name-notation.translation.!=,

name_notation.@ other-worldview

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.@other-worldview--name-notation,
* McshEngl.other-worldview@--name-notation,
* McshEngl.name-notation.@other-worldview,
* McshEngl.name-notation.other-worldview@,

name_notation.{time} (link)

name_notation.[info-resource]

description::
× Mcsh-creation: {2026-10-04}
· the-info-resource of an-info.

name::
* McshEngl.name-notation.[info-resource],
* McshEngl.name-notation.left-right-square-brackets,
* McshEngl.name_notation.[info-resource],

name_notation.\reference\

description::
× Mcsh-creation: {2026-10-04}
· the-reference of a-pronoun.

name::
* McshEngl.name-notation.\reference\,
* McshEngl.name-notation.reverse-solidus,
* McshEngl.name_notation.\reference\,

name_notation.fixed-length

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.
[HumnSngu.{2021-01-05}]

name::
* McshEngl.name-notation.fixed-length,
* McshEngl.name_notation.fixed-length,

name_notation.before.2017-11-21

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.name-notation.before.2017-11-21,
* McshEngl.name_notation.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}

GENERIC-SPECIFIC-TREE of Mcs_derived_name

description::
× Mcsh-creation: {2026-10-04}

name::
* McshEngl.Mcs_derived_name'generic-specific-tree,
* McshEngl.Mcs_derived_name'specific-generic-tree,

generic-tree::
* McshEngl.Mcs_derived_name_Gntr,
===
* ...entity_Gntr,

specific-tree::
* McshEngl.Mcs_derived_name.specific,
* McshEngl.Mcs_derived_name_Sptr,
===
* derived--main-name!@McshCor000002#idMcsattNamDzrMaindrvd,

GENERIC-SPECIFIC-TREE of nameMcsMind

description::
× Mcsh-creation: {2026-10-04}

name::
* McshEngl.nameMcsMind'generic-specific-tree,
* McshEngl.nameMcsMind'specific-generic-tree,

generic-tree::
* McshEngl.nameMcsMind_Gntr,
===
* ...entity_Gntr,

specific-tree::
* McshEngl.nameMcsMind.specific,
* McshEngl.nameMcsMind_Sptr,
===
* ID,
* main-name!@McshCor000002#idMcsattNamDzrMain,
* title!@McshCor000002#idMcsttl,

nameMcsMind.main

description::
× Mcsh-creation: {2026-10-04}
· 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.nameMcsMindMain,
* McshEngl.nameMcsMind.main!⇒nameMcsMindMain,
* McshEngl.Mcs'attAsNameAsMain!⇒nameMcsMindMain,
* McshEngl.Mcs'mind-main-name!⇒nameMcsMindMain,
* McshEngl.Mcs-mind-main-name!⇒nameMcsMindMain, {2019-03-10}
* McshEngl.main-mind-nameMcs!⇒nameMcsMindMain,
* McshEngl.main-mind-name--of-Mcs!⇒nameMcsMindMain,
* McshEngl.nameMcsMindMain!⇒nameMcsMindMain,
* McshEngl.nameMcs.mind.main!⇒nameMcsMindMain,

nameMcsMind.mainNo

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.nameMcsMind.mainNo,

nameMcsMind.synonyms

description::
× Mcsh-creation: {2026-10-04}
· synonyms of Mcs\a\ is the-set of all mind-names of Mcs\a\

name::
* McshEngl.nameMcsMind.synonyms,

nameMcsMind.conceptary

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.nameMcsMind.conceptary,
====== lagoGreek:
* McshElln.εννοιολόγιο!=conceptary, από 'λεξιλόγιο',
* McshElln.δηλοτολόγιο!=conceptary, από 'λεξιλόγιο',

environment::
* wordary,
* namary,

notation of nameMcsMain (link)

Mcsattr.Specsdiv.internal|external

description::
× Mcsh-creation: {2026-10-04}
* part-att,
* partNo-att,

name::
* McshEngl.Mcsattr.Specsdiv.part-instance,

Mcsattr.Specsdiv.generic

description::
× Mcsh-creation: {2026-10-04}
· on generic:
* generic-att,
* specific-att,

name::
* McshEngl.Mcsattr.Specsdiv.generic-instance,

Mcsattr.Specsdiv.doing-instance

description::
× Mcsh-creation: {2026-10-04}
· on doing:
* doing-att,
* doingNo-att,

name::
* McshEngl.Mcsattr.Specsdiv.doing-instance,

Mcsattr.Specsdiv.inherited-from-instance

description::
× Mcsh-creation: {2026-10-04}
· on inherited-from:
* inherited-from-att,
* inherited-fromNo-att,

name::
* McshEngl.Mcsattr.Specsdiv.inherited-from-instance,

Mcsattr.Specsdiv.inherited-to

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.
[HumnSngu.2020-01-11]
===
· on inherited-to:
* inherited-to-att,
* inherited-toNo-att,

name::
* McshEngl.Mcsattr.Specsdiv.inherited-to-instance,

complement-of-att of Mcsdivision

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.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,
* McshEngl.Mcsdivision'complement-of-att!⇒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]

GENERIC-SPECIFIC-TREE of Mcsdivision

description::
× Mcsh-creation: {2026-10-04}

name::
* McshEngl.Mcsdivision'generic-specific-tree,
* McshEngl.Mcsdivision'specific-generic-tree,

generic-tree::
* McshEngl.Mcs_division_Gntr,
===
* Mcsattr_Gntr,
* ...entity_Gntr,

specific-tree::
* McshEngl.Mcsdivision.specific,
* McshEngl.Mcs_division_Sptr,
===
* dichotomous-division!@McshCor000002#idMcsattDvsnDhm,
* trichotomous-division!@McshCor000002#idMcsattDvsnThm,
* doing-att-division,
===
* attributes-division!@McshCor000002#idMcsattPrtdvn,
* parts-division!@McshCor000002#idMcsattPrtdvn,
* specifics-division!@McshCor000002#idMcsattWhlNSpcdvn,

Mcsdivision.dichotomous

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,
* McshEngl.dichotomous-division--Mcsattr!⇒dichotomous_division__Mcsattr,
* McshEngl.Mcsattr.dichotomous-division!⇒dichotomous_division__Mcsattr,
* McshEngl.Mcsattr.division.dichotomous!⇒dichotomous_division__Mcsattr,
* McshEngl.Mcs'attAsDichotomous-division!⇒dichotomous_division__Mcsattr,
* McshEngl.Mcs'dichotomous-division-attribute!⇒dichotomous_division__Mcsattr,
* McshEngl.Mcs-division.dichotomous!⇒dichotomous_division__Mcsattr,
* McshEngl.Mcsdivision.dichotomous!⇒dichotomous_division__Mcsattr,
* McshEngl.division.dichotomous--Mcsattr!⇒dichotomous_division__Mcsattr,
====== lagoGreek:
* McshElln.διχοτομική-διαίρεση!=dichotomous_division__Mcsattr,

Mcsdivision.trichotomous

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).
[HumnSngu.2019-07-19]

name::
* McshEngl.Mcs_trichotomous_division,
* McshEngl.Mcs-division.trihotomous!⇒Mcs_trichotomous_division,
* McshEngl.trihotomous-division--of-Mcs!⇒Mcs_trichotomous_division,
* McshEngl.Mcsdivision.trichotomous!⇒Mcs_trichotomous_division,
====== lagoGreek:
* McshElln.τριχοτομική-διαίρεση!=Mcs_trichotomous_division,

Mcsdivision.attributes

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.Mcsdivision.attributes,

Mcsdivision.part-attributes

description::
× Mcsh-creation: {2026-10-04}
· parts-division--Mcsattr is a-division of a-Mcs's parts.

name::
* McshEngl.Mcs-division.parts,
* McshEngl.Mcsattr.division.parts,
* McshEngl.Mcsdivision.part-attributes,

part-relation of Mcspart

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.Mcspart'relation!⇒RltnMcsThenPart,
* McshEngl.Mcspart-relation!⇒RltnMcsThenPart,
* McshEngl.part-relation--of-Mcs!⇒RltnMcsThenPart,
* McshEngl.relation.part--of-Mcs!⇒RltnMcsThenPart,
* McshEngl.RltnPart!⇒RltnMcsThenPart,
* McshEngl.Mcspart'part-relation!⇒RltnMcsThenPart,
====== lagoSinagu:
* ja!~ConjSngu!=RltnMcsThenPart,
* rao-jo!=RltnPart!=RltnMcsThenPart, {2023-07-21}

GENERIC-SPECIFIC-TREE of Mcspart

description::
× Mcsh-creation: {2026-10-04}

name::
* McshEngl.Mcspart'generic-specific-tree,
* McshEngl.Mcspart'specific-generic-tree,

generic-tree::
* McshEngl.Mcspart_Gntr,
===
* Mcsattr_Gntr,
* ...entity_Gntr,

specific-tree::
* McshEngl.Mcspart.specific,
* McshEngl.Mcspart_Sptr,
===
* part-list--part-att,
* part-instance--part-att,
* title--part-att,
* overview--part-att,
* description--part-att,
* name--part-att,
* definition--part-att,
* part-division--part-att,

Mcspart.list

description::
× Mcsh-creation: {2026-10-04}
· part-list-att of Mcs is a-set of part-att.

name::
* McshEngl.Mcspart.list,
* McshEngl.part-list-att--of-Mcs,

Mcspart.instance

description::
× Mcsh-creation: {2026-10-04}
· part-instance--Mcs\a\-att is a-genericNo part-attribute.

name::
* McshEngl.Mcsattr.part-instance,
* McshEngl.Mcspart.instance,
* McshEngl.part-instance--Mcsattr,

Mcspart.title (link)

Mcspart.overview

description::
× Mcsh-creation: {2026-10-04}
· overview-of-Mcs is a-part-attribute which contains the-description and the-name attributes.
[HumnSngu.2018-11-03]

name::
* McshEngl.OVERVIEW-of-Mcs,
* McshEngl.Mcspart.overview,
* McshEngl.Mcsattr.overview,
* McshEngl.overview-of-Mcs,

Mcspart.description

description::
× Mcsh-creation: {2026-10-04}
· description--Mcsattr is Mcs-TEXT that IDENTIFIES a-Mcs.
· a-definition UNIQUELY IDENTIFIES a-Mcs.
[HumnSngu.2017-12-22]

name::
* McshEngl.description--Mcsattr,
* McshEngl.Mcsattr.description,
* McshEngl.Mcspart.description,
* McshEngl.Mcs'attAsDescription,
* McshEngl.Mcs'description-attribute,

Mcspart.name (link)

Mcspart.definition

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.
[HumnSngu.{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.definition-att-of-Mcs!⇒definitionMcs,
* McshEngl.definitionMcs!=definition-att-of-Mcs,
* McshEngl.definition-att--of-Mcs!⇒definitionMcs,
* McshEngl.Mcsattr.definition!⇒definitionMcs,
* McshEngl.Mcspart.definition!⇒definitionMcs,
* McshEngl.Mcs'attAsDefinition!⇒definitionMcs,
* McshEngl.definition--Mcsattr!⇒definitionMcs,
* McshEngl.definition-of-Mcs!⇒definitionMcs,
* McshEngl.dfn-of-Mcs!⇒definitionMcs,
====== lagoChinese:
* McshZhon.dìngyì-定义-(定義)!=definitionMcs,
* McshZhon.定义-(定義)-dìngyì!=definitionMcs,
====== lagoGreek:
* McshElln.ορισμός!ο!=definitionMcs,
======
"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]

Mcspart.part-division

description::
× Mcsh-creation: {2026-10-04}
· part-division--Mcsattr is a-division of the-part-attributes.

name::
* McshEngl.division.part--Mcsattr!⇒Mcspartdivi,
* McshEngl.Mcspartdivi!=division.part--Mcsattr,
* McshEngl.Mcs'division.part!⇒Mcspartdivi,
* McshEngl.Mcspart.part-division!⇒Mcspartdivi,
* McshEngl.Mcsattr.part-division!⇒Mcspartdivi,
* McshEngl.Mcs'attAsPartial-division!⇒Mcspartdivi,
* McshEngl.part-division--Mcsattr!⇒Mcspartdivi,
* McshEngl.partial-division--Mcsattr!⇒Mcspartdivi,

generic-tree::
* McshEngl.Mcspartdivi_Gntr,
===
* Mcs_division_Gntr,
* Mcsattr_Gntr,
* ...entity_Gntr,

GENERIC-SPECIFIC-TREE of McspartNo

description::
× Mcsh-creation: {2026-10-04}

name::
* McshEngl.McspartNo'generic-specific-tree,
* McshEngl.McspartNo'specific-generic-tree,

generic-tree::
* McshEngl.McspartNo_Gntr,
===
* Mcsattr_Gntr,
* RltnAttributeThenEntity_Gntr,
* ...entity_Gntr,

specific-tree::
* McshEngl.McspartNo.specific,
* McshEngl.McspartNo_Sptr,
===

Mcsattr.whole-chain

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.Mcsattr.whole-chain,
* McshEngl.Mcs'attAsWhole-chain,
* McshEngl.whole-chain--Mcsattr,
* McshEngl.Mcs_whole.whole-chain,

GENERIC-SPECIFIC-TREE of Mcsenvt

description::
× Mcsh-creation: {2026-10-04}

name::
* McshEngl.Mcsenvt'generic-specific-tree,
* McshEngl.Mcsenvt'specific-generic-tree,

generic-tree::
* McshEngl.Mcsenvt_Gntr,
===
* Mcsattr_Gntr,
* ...entity_Gntr,

specific-tree::
* McshEngl.Mcsenvt.specific,
* McshEngl.Mcsenvt_Sptr,
===
* author-of-Mcs,
* evaluation-of-Mcs,
* referent-of-Mcs,
* supporter-of-Mcs,

Mcsenvt.archetype

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\.
[HumnSngu.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!⇒Mcsarcho,
* McshEngl.Mcsarcho!=archetype--Mcsattr,
* McshEngl.Mcs'archetype!⇒Mcsarcho,
* McshEngl.Mcsattr.archetype!⇒Mcsarcho,
* McshEngl.Mcsattr.referent!⇒Mcsarcho,
* McshEngl.Mcs'attAsArchetype!⇒Mcsarcho,
* McshEngl.Mcs'referent!⇒Mcsarcho,
* McshEngl.referent--Mcsattr!⇒Mcsarcho,
* McshEngl.Mcsenvt.archetype!⇒Mcsarcho,

whole-tree::
* environment--Mcsattr,

generic-tree::
* McshEngl.Mcsarcho_Gntr,
===
* Mcsattr_Gntr,
* ...entity_Gntr,

Mcsenvt.evaluation

description::
× Mcsh-creation: {2026-10-04}
· evaluation--Mcsattr is the-cons and pros of the-Mcs.

name::
* McshEngl.evaluation--Mcsattr,
* McshEngl.Mcsattr.evaluation,
* McshEngl.Mcsattr.wholeNo.evaluation,
* McshEngl.Mcsenvt.evaluation,

Mcsenvt.supporter

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.Mcsattr.holder,
* McshEngl.Mcsattr.supporter,
* McshEngl.Mcs'supporter,
* McshEngl.supporter-of-Mcs,
* McshEngl.Mcsenvt.supporter,

Mcsenvt.meta-info

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.Mcsattr.meta-info,
* McshEngl.Mcsattr.wholeNo.meta-info,
* McshEngl.meta-info--Mcsattr,
* McshEngl.Mcsenvt.meta-info,

Mcsattr.evoluting

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,
* McshEngl.Mcsattr'evoluting,
* McshEngl.Mcsattr.specific'evoluting,

Mcsattr.generic-chain

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!⇒Mcsgenchn,
* McshEngl.Mcsgenchn!=generic-chain--Mcsattr,
* McshEngl.Mcsattr.generic-chain!⇒Mcsgenchn,

generic-tree::
* McshEngl.Mcsgenchn_Gntr,
===
* tree_node_chain_Gntr,
* Mcsattr_Gntr,

Mcsattr.individual

description::
× Mcsh-creation: {2026-10-04}
· individual-att of Mcs is a-specific-of-Mcs which has no other specifics.

name::
* McshEngl.Mcsattr.individual,
* McshEngl.individual-att--of-Mcs,
* McshEngl.individual-of-Mcs,
* McshEngl.instance-of-Mcs,
====== lagoSinagu:
* atro-koUgo-a-Mes!=individual-att--of-Mcs,

Mcsattr.specifics-division

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!
[HumnSngu.2017-11-15]

name::
* McshEngl.specifics-division--Mcsattr!⇒Mcsspecdiv,
* McshEngl.Mcsspecdiv!=specifics-division--Mcsattr,
* McshEngl.Mcsattr.division.specifics!⇒Mcsspecdiv,
* McshEngl.Mcsattr.specifics-division!⇒Mcsspecdiv,
* McshEngl.Mcs-division.specifics!⇒Mcsspecdiv,
* McshEngl.Mcs'attAsSpecifics-division!⇒Mcsspecdiv,
* McshEngl.division.specifics--Mcsattr!⇒Mcsspecdiv,
* McshEngl.Sd!=specifics-division!⇒Mcsspecdiv, {2022-08-28}
* McshEngl.specifics-division--Mcsattr!⇒Mcsspecdiv,
* McshEngl.Specsdiv!=specifics-division!⇒Mcsspecdiv,
* McshEngl.specs-div!=specifics-division!⇒Mcsspecdiv,
* McshEngl.specs-division--Mcsattr!⇒Mcsspecdiv,
====== lagoGreek:
* McshElln.διαίρεση-ειδικών-εννοιών!=Mcsspecdiv,

generic-tree::
* McshEngl.Mcsspecdiv_Gntr,
===
* generic-tree,
* Mcs_division_Gntr,

user.author of Mcsmgr

description::
× Mcsh-creation: {2026-10-04}
· one or more humans that support a-worldview.

name::
* McshEngl.Mcsmgr'author,
* McshEngl.Mcsmgr'user.author,

user.reader of Mcsmgr

description::
× Mcsh-creation: {2026-10-04}
· a-human that reads the-base.

name::
* McshEngl.Mcsmgr'reader,
* McshEngl.Mcsmgr'user.reader,

GENERIC-SPECIFIC-TREE of Mcsmgrdong

description::
× Mcsh-creation: {2026-10-04}

name::
* McshEngl.Mcsmgrdong'generic-specific-tree,
* McshEngl.Mcsmgrdong'specific-generic-tree,

generic-tree::
* McshEngl.Mcsmgrdong_Gntr,
===
* ...entity_Gntr,

specific-tree::
* McshEngl.Mcsmgrdong.specific,
* McshEngl.Mcsmgrdong_Sptr,
===
* 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,
===
* AAj'doing!@McshCor000002#idMcsmAajdong,
* Mcshmgr'doing!@McshTchInf000009#idLMcshmngrdong,

building-base of Mcsmgr

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'att001-building-base,
* McshEngl.McsmDoing.building-base,
* McshEngl.Mcsmgr'storing-base,
* McshEngl.Mcsmgrdong'building-base,

retrieving-base of Mcsmgr

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'att002-retrieving-base,
* McshEngl.McsmDoing.retrieving-base,
* McshEngl.Mcsmgrdong'retrieving-base,

computing of Mcsmgr

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,

evoluting-managing of Mcsmgr

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'att023-evoluting-managing,
* McshEngl.McsmDoing.evoluting-managing,
* McshEngl.Mcsmgrdong'evoluting-managing,

Mcs of McsMgrWiki (link)

Mcs of McsmgrCrxToc (link)

Mcs of HtmlMgr (link)

Mcs of McsMgrAAj (link)

view of 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,

worldview of McsMgrAAj

description::
× Mcsh-creation: {2026-10-04}
· worldview-of-McsMgrAAj is the-system of McsAAj of ONE author.

name::
* McshEngl.McsMgrAAj'worldview,

base of McsMgrAAj

description::
× Mcsh-creation: {2026-10-04}
· base-of-McsMgrAAj is the-set of its supported worldviews.

name::
* McshEngl.McsMgrAAj'base,
* McshEngl.McsMgrAAj'knowledge-base,

info-resource of McsMgrAAj

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,

name::
* McshEngl.McsMgrAAj'info-resource,

structure of McsMgrAAj

description::
× Mcsh-creation: {2026-10-04}
* computer,
* program,
** viewer,
** editor,
** html-browser,
* base,

name::
* McshEngl.McsMgrAAj'structure,

DOING of McsMgrAAj

description::
× Mcsh-creation: {2026-10-04}
· base-building,
· base-retrieving,

name::
* McshEngl.McsMgrAAj'doing,

generic-tree::
* McshEngl.AAj'doing_Gntr,
===
* Mcsmgrdong_Gntr,
* ...entity_Gntr,

evoluting of McsMgrAAj

description::
× Mcsh-creation: {2026-10-04}
· AAj evolution.

name::
* McshEngl.evoluting-of-McsMgrAAj,
* McshEngl.McsMgrAAj'evoluting,

{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).

Mcs of FvMcsMgr (link)

Mcs of McsMgrPaper (link)

Mcs-worldview of McsMgrPaper (link)

same-referent-other-view of Mcs

description::
× Mcsh-creation: {2026-10-04}
· same-referent, other-view

name::
* McshEngl.Mcs'same-referent-other-view,
* McshEngl.same-referent-other-view--Mcs,

same-referent-similar-view of Mcs

description::
× Mcsh-creation: {2026-10-04}
· same-referent, similar-view

name::
* McshEngl.Mcs'same-referent-similar-view,
* McshEngl.same-referent-similar-view--Mcs,

same-referent-same-view of Mcs

description::
× Mcsh-creation: {2026-10-04}
· same-referent, same-view

name::
* McshEngl.Mcs'same-referent-same-view,
* McshEngl.same-referent-same-view--Mcs,

GENERIC-SPECIFIC-TREE of Mcs'searching

description::
× Mcsh-creation: {2026-10-04}

name::
* McshEngl.Mcs'searching'generic-specific-tree,
* McshEngl.Mcs'searching'specific-generic-tree,

generic-tree::
* McshEngl.Mcs'searching_Gntr,
===
* Mcsmng_Gntr,
* ...entity_Gntr,

specific-tree::
* McshEngl.Mcs'searching.specific,
* McshEngl.Mcs'searching_Sptr,
===
* McsHitp-searching!@McshTchInf000008#idLHitpscg,

Mcs'searching'TODO

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}.

name::
* McshEngl.Mcs'searching'todo,

GENERIC-SPECIFIC-TREE of Mcs_validating

description::
× Mcsh-creation: {2026-10-04}

name::
* McshEngl.Mcs_validating'generic-specific-tree,
* McshEngl.Mcs_validating'specific-generic-tree,

generic-tree::
* McshEngl.Mcs_validating_Gntr,
===
* ...entity_Gntr,

specific-tree::
* McshEngl.Mcs_validating.specific,
* McshEngl.Mcs_validating_Sptr,
===
· part-validating,
· whole-validating,
· generic-validating,
· specific-validating,
· sibling-validating,
· relation-validating,
· definition-validating,

Mcs_validating.part

description::
× Mcsh-creation: {2026-10-04}
· a) IF cpt1 has as part cpt2
THEN cpt2 has as whole cpt1.

name::
* McshEngl.Mcs-validating.part,
* McshEngl.Mcs_validating.part,

Mcs_validating.whole

description::
× Mcsh-creation: {2026-10-04}
· a) IF cpt1 has as whole cpt2
THEN cpt2 has as part cpt1.

name::
* McshEngl.Mcs-validating.whole,
* McshEngl.Mcs_validating.whole,

Mcs_validating.generic

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.

name::
* McshEngl.Mcs-validating.generic,
* McshEngl.Mcs_validating.generic,

Mcs_validating.specific

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.

name::
* McshEngl.Mcs-validating.specific-attr,
* McshEngl.Mcs_validating.specific,

Mcs_validating.sibling

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.

name::
* McshEngl.Mcs-validating.sibling,
* McshEngl.Mcs_validating.sibling,

Mcs_validating.relation

description::
× Mcsh-creation: {2026-10-04}
· IF cpt1 has a-relation with cpt2,
THEN cpt2 must-have the-(same)-relation with cpt1.

name::
* McshEngl.Mcs-validating.relation,
* McshEngl.Mcs_validating.relation,

Sfi of McsSfi

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,

manager of McsSfi (link)

manager of McsCrxToc (link)

manager of McsWiki (link)