sensorial-concept-(Mcs)
(modelConceptSensorial)

McsHitp-creation: {2017-09-27}

overview of Mcs

description::
· 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].
[hmnSgm.2017-11-14]
· the-goal of structured-concept creation is the-creation of MONOSEMANTIC, consistent, and complete information, readable by humans AND machines.
[hmnSgm.2018-03-05]

name::
* Mcs.filMcs.last.html,
* Mcs.dirCor/filMcs.last.html,
* Mcs.modelConceptSensorial!⇒Mcs, {2019-08-23}
* Mcs.modelConceptStructured!⇒Mcs,
* Mcs.modelConceptStructured!⇒Mcs,
* Mcs.Mcs,
* Mcs.Mcs'(modelConceptSensorial)!⇒Mcs, {2019-08-23}
* Mcs.Mcs-(modelConceptSensorial)!⇒Mcs,
* Mcs.concept.sensorial!⇒Mcs,
* Mcs.conceptSenso!⇒Mcs,
* Mcs.cptBrnSns!⇒Mcs,
* Mcs.cptSns!⇒Mcs,
* Mcs.sensorial-brain-concept!⇒Mcs,
* Mcs.sensorial-concept!⇒Mcs, {2019-08-23}
* Mcs.structured-concept!⇒Mcs,
====== langoKomo:
* McsKmo.Mes!=sensorial-concept,
* McsKmo.enioSenso!⇒Mes,
* McsKmo.modelo-enio-senso!⇒Mes,
====== langoGreek:
* McsEll.Μεα!=sensorial-concept,,
* McsEll.αισθητή-έννοια!⇒Μεα,
* McsEll.δομημένη-έννοια!⇒Μεα,
* McsEll.έννοια.αισθητή!⇒Μεα,
* McsEll.μοντέλο-δομημένης-έννοιας!⇒Μεα,
* McsEll.μοντέλοΕννοιαΑισθητή!⇒Μεα,

attribute of Mcs

description::
· attribute-of-Mcs[a] is one or more Mcs[b] related with Mcs[a].
[hmnSgm.2019-03-10]

name::
* Mcs.attribute-of-Mcs!⇒Mcs-att,
* Mcs.Mcs'attribute!⇒Mcs-att,
* Mcs.Mcs'att!⇒Mcs-att,
* Mcs.Mcs'characteristic!⇒Mcs-att,
* Mcs.Mcs'trait!⇒Mcs-att,
* Mcs.Mcs-att,
* Mcs.McsAaAttribute!⇒Mcs-att,
====== langoKomo:
* McsKmo.atro-a-Mes!=attribute-of-Mcs, {2019-10-20}
* McsKmo.enioSensosAtro, {2019-10-24}


====== langoGreek:
* McsEll.χαρακτηριστικό-Μεα!=attribute-of-Mcs,

attribute-relation of Mcs

description::
· attribute-relation is the-relation between a-concept[a] and an-attribute of it[a].

name::
* Mcs.Mcs'attribute-relation,
* Mcs.Mcs-att'attribute-relation,
* Mcs.attribute-relation--of-Mcs,
* Mcs.relation.attribute-of-Mcs,
* Mcs.am!~verbEngC1,
* Mcs.have!~verbEngC1,
* Mcs.of!~conj,
====== langoKomo:
* McsKmo.ro-atro!=relation.attribute,
* McsKmo.a!~conjKmo!=att-rel,
====== langoGreek:
* McsEll.σχέση-χαρακτηριστικού-Μεα,

attribute.SPECIFIC

specific::
=== alphabetically:
* author-att,
* complement-of-att,
* definition-att,
* description-att,
* dichotomous-division--att,
* division-att,
* doing-att,
* doingNo-att,
* environment-att,
* evaluation-att,
* evoluting-att,
* generic-att,
* generic-chain--att,
* inherited-from-att,
* inherited-fromNo-att,
* inherited-to-att,
* inherited-toNo-att,
* name-att,
* part-att,
* partNo-att,
* part-division--att,
* specific-att,
* specific-chain--att,
* specifics-division--att,
* supporter-att,
* title-att,
* whole-att,
* whole-chain--att,
* wholeNo-att,

attribute.specifics-division.internal|external

description::
* part-att,
* partNo-att,

name::
* Mcs.Mcs-att.specifics-division.part-instance,

attribute.specifics-division.generic

description::
· on generic:
* generic-att,
* specific-att,

name::
* Mcs.Mcs-att.specifics-division.generic-instance,

attribute.specifics-division.doing-instance

description::
· on doing:
* doing-att,
* doingNo-att,

name::
* Mcs.Mcs-att.specifics-division.doing-instance,

attribute.specifics-division.inherited-from-instance

description::
· on inherited-from:
* inherited-from-att,
* inherited-fromNo-att,

name::
* Mcs.Mcs-att.specifics-division.inherited-from-instance,

attribute.specifics-division.inherited-to-instance

description::
· on inherited-to:
* inherited-to-att,
* inherited-toNo-att,

name::
* Mcs.Mcs-att.specifics-division.inherited-to-instance,

attribute.division

description::
· 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::
* Mcs.Mcs-att.division!⇒Mcs-division,
* Mcs.Mcs'attAsDivision!⇒Mcs-division,
* Mcs.Mcs'division-attribute!⇒Mcs-division,
* Mcs.Mcs-division,
* Mcs.division--of--Mcs-atts!⇒Mcs-division,

complement-of-att of Mcs-division

description::
· in ONE division all the-other attributes of an-attribute[a] is the-complement of attribute[a] ON this division.

name::
* Mcs.Mcs-att'complement!⇒Mcs-complement,
* Mcs.Mcs'complement-of-att!⇒Mcs-complement,
* Mcs.Mcs-att.complement-of-att!⇒Mcs-complement,
* Mcs.Mcs-complement,
* Mcs.complement-of--Mcs-att!⇒Mcs-complement,
====== langoKomo:
* McsKmo.uo!=complement-of-att,

Mcs-complement.SPECIFIC in division

description::
* attributes-complement,
* parts-complement,
* specifics-complement,

name::
* Mcs.Mcs-complement.specific,

Mcs-complement.attributes in division

description::
· attributes-complement of Mcs-att is a-complement that makes-up all the-attributes of the-Mcs.

name::
* Mcs.Mcs-complement.attributes,
* Mcs.attributes-complement--of-Mcs,
* Mcs.complement.attributes--of-Mcs,
====== langoKomo:
* McsKmo.uatro-a-Mes!=complement.attributes,

Mcs-complement.parts in division

description::
· parts-complement of att[a] in a-division is the-complement-of-att[a] in a-part-division.

name::
* Mcs.Mcs'parts-complement--of-att,
* Mcs.Mcs-complement.parts,
* Mcs.Mcs-parts-complement,
* Mcs.complement.parts--of-Mcs,
====== langoKomo:
* McsKmo.ulo-a-Mes!=complement.parts,

Mcs-complement.specifics in division

description::
· specifics-complement of att[a] in a-division is the-complement-of-att[a] in a-specifics-division.

name::
* Mcs.Mcs'specifics-complement--of-att,
* Mcs.Mcs-complement.specifics,
* Mcs.Mcs-specifics-complement,
* Mcs.complement.specifics--of-Mcs,
====== langoKomo:
* McsKmo.ugo-a-Mes!=complement.specifics,

Mcs-division.SPECIFIC

specific::
* dichotomous-division,
* trichotomous-division,
* doing-att-division,
===
* attributes-division,
* parts-division,
* specifics-division,

Mcs-division.dichotomous

description::
· 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::
* Mcs.dichotomous-division--Mcs-att,
* Mcs.division.dichotomous--Mcs-att,
* Mcs.Mcs-att.dichotomous-division,
* Mcs.Mcs-att.division.dichotomous,
* Mcs.Mcs'attAsDichotomous-division,
* Mcs.Mcs'dichotomous-division-attribute,
* Mcs.Mcs-division.dichotomous,

Mcs-division.trichotomous

description::
· like a-dichotomous-division we have clear division in 3 entities:
· past, present, future,
· male, maleNo-(female), maleBo-(both male and female).
[hmnSgm.2019-07-19]

name::
* Mcs.Mcs-division.trihotomous,
* Mcs.trihotomous-division--of-Mcs,

specific::
* ordered--trichotomous-division,
* orderedNo-trichotomous-division,

first-att of ordered--trichotomous-division

description::
·

name::
* Mcs.trichotomous-division'first-attribute,
====== langoKomo:
* McsKmo.atro-mido-anto,

middle-att of ordered--trichotomous-division

description::
·

name::
* Mcs.middle-att--of--trichotomous-division,
* Mcs.trichotomous-division'middle-attribute,
====== langoKomo:
* McsKmo.atro-mido,

third-att of ordered--trichotomous-division

description::
·

name::
* Mcs.trichotomous-division'third-attribute,
====== langoKomo:
* McsKmo.atro-mido-afto,

Mcs-division.attributes

description::
· attributes-division of Mcs[a] is a-division of its[a] attributes.

name::
* Mcs.attributes-division-of-Mcs,

Mcs-division.doing

description::
· doing-division--Mcs-att is a-dichotomous-division of a-Mcs's attributes in doing and doingNo.

name::
* Mcs.division.doing--Mcs-att,
* Mcs.Mcs-att.division.doing,
* Mcs.Mcs-division.doing,

Mcs-division.part-attributes

description::
· parts-division--Mcs-att is a-division of a-Mcs's parts.

name::
* Mcs.Mcs-division.parts,
* Mcs.Mcs-att.division.parts,
* Mcs.Mcs-division.parts,

attribute.part (internal)

description::
· part-att of Mcs[a] is an-att we perceive as internal|intrinsic.

name::
* Mcs.externalNo--Mcs-att!⇒Mcs-part,
* Mcs.internal--Mcs-att!⇒Mcs-part,
* Mcs.intrinsic--Mcs-att!⇒Mcs-part,
* Mcs.Mcs'externalNo-attribute!⇒Mcs-part,
* Mcs.Mcs'internal-attribute!⇒Mcs-part,
* Mcs.Mcs-att.externalNo!⇒Mcs-part,
* Mcs.Mcs-att.internal!⇒Mcs-part,
* Mcs.Mcs-att.part!⇒Mcs-part,
* Mcs.Mcs'attAsExternalNo!⇒Mcs-part,
* Mcs.Mcs'attAsInternal!⇒Mcs-part,
* Mcs.Mcs'attAsPart!⇒Mcs-part,
* Mcs.Mcs-part-att, {2019-04-08}
* Mcs.part--Mcs-att!⇒Mcs-part,
====== langoKomo:
* McsKmo.atro-jo-a-Mes!=part-att--of-Mcs,

part-relation

description::
· part-relation of Mcs[a] is the-relation between the-Mcs[a] and a-part of it[a].

name::
* Mcs.Mcs'part-relation,
* Mcs.part-relation--of-Mcs,
* Mcs.relation.part--of-Mcs,
====== langoKomo:
* McsKmo.ja!~conjKmo!=part-relation,
* McsKmo.ro-jo!=part-relation,

part.SPECIFIC

description::
* 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,

name::
* Mcs.Mcs-part.specific,

part.list

description::
· part-list-att of Mcs is a-set of part-att.

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

part.instance

description::
· part-instance--Mcs[a]-att is a-genericNo part-attribute.

name::
* Mcs.Mcs-att.part-instance,
* Mcs.Mcs-part.instance,
* Mcs.part-instance--Mcs-att,

part.title

description::
· title of Mcs is the-main-name-of-Mcs placed at the-top of its presentation.

name::
* Mcs.Mcs-name.title,
* Mcs.Mcs-att.title,
* Mcs.Mcs-part.title-of-Mcs,
* Mcs.McsApTitle,
* Mcs.title--Mcs-att,
* Mcs.title-of-Mcs,

part.overview

description::
· overview-of-Mcs is a-part-attribute which contains the-description and the-name attributes.
[hmnSgm.2018-11-03]

name::
* Mcs.Mcs-part.overview,
* Mcs.Mcs-att.overview,
* Mcs.overview-of-Mcs,

part.description

description::
· description--Mcs-att is Mcs-TEXT that IDENTIFIES a-Mcs.
· a-definition UNIQUELY IDENTIFIES a-Mcs.
[hmnSgm.2017-12-22]

name::
* Mcs.description--Mcs-att,
* Mcs.Mcs-att.description,
* Mcs.Mcs-part.description,
* Mcs.Mcs'attAsDescription,
* Mcs.Mcs'description-attribute,

part.name

description::
· name of Mcs[a] is any logo-name of it[a].
[hmnSgm.2019-08-05]

name::
* Mcs.name-att--of-Mcs!⇒Mcs-name,
* Mcs.name-of-Mcs!⇒Mcs-name,
* Mcs.Mcs-att.name!⇒Mcs-name,
* Mcs.Mcs-name,
* Mcs.Mcs-part.name!⇒Mcs-name,
* Mcs.Mcs'attAsName!⇒Mcs-name,
* Mcs.Mcs'attAsPartAsName!⇒Mcs-name,

name-notation of Mcs-name

description::
· it is VERY IMPORTANT to be-consistent on the-names we use in order to increase communication.

name::
* Mcs.Mcs-name'naming-convension!⇒name-notation,
* Mcs.Mcs'name-notation!⇒name-notation,
* Mcs.Mcs-name'notation!⇒name-notation,
* Mcs.name-notation,
* Mcs.name-notation--of-Mcs!⇒name-notation,
* Mcs.naming-convension--of-Mcs!⇒name-notation,
* Mcs.notation-of--Mcs-name!⇒name-notation,

name-notation.no-space

description::
· no spaces in multi-word names:
* human-language, Mcs-att,
* 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.
[hmnSgm.2018-01-22]

name::
* Mcs.name-notation.no-space,

name-notation.attribute

description::
· 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.
[hmnSgm.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::
* Mcs.name-notation.attribute,

name-notation.capital

description::
· first capital:
* initialisms: Hitp, Html.
* instance-concepts: Earth, Athens.
* exception: short-names: net, ogn, ogm.
[hmnSgm.2018-01-22]

name::
* Mcs.name-notation.capital,

name-notation.case

description::
· 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.
[hmnSgm.2018-01-14]

name::
* Mcs.name-notation.case,

name-notation.!~

description::
· tilde char.126'~' denotes EXTRA information on a-name.
· type of name: verb, conjunction.
- McsEll.ένας!~adjvEll:ένας-μία-ένα,
· method of inflection:

name::
* Mcs.name-notation.!~,

name-notation.!⇒

description::
· denotes the-main-name of a-sensorial-concept.

name::
* Mcs.name-notation.!⇒,

name-notation.!=

description::
· denotes translation to English.

name::
* Mcs.name-notation.!=,

name-notation.before.2017-11-21

name::
* Mcs.name-notation.before.2017-11-21,

description::
· 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-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}

derived-name of name

description::
· derived-name[b] of Mcs-name[a] is a-name of an-attribute of the-concept with the-Mcs-name[a], that is-created from it[a].
· according to Mcs-naming-convension it[b] begins with the-Mcs-name[a] which is-called 'original-name'.

name::
* Mcs.derived-name--of--Mcs-name,
* Mcs.Mcs-name'derived-name,
* Mcs.related-name--of--Mcs-name,

specific::
* derived--main-name,

original-name of name

description::
· original-name--of--a-Mcs-name[a] is a-name[b] of a-concept with attribute the-Mcs-name[a], if name[b] is a-derived-name of name[a].

name::
* Mcs.Mcs-name'original-name,
* Mcs.original-name--of--a-Mcs-name,

WHOLE of name

description::
* overview--Mcs-att,

name::
* Mcs.Mcs-name'whole,

name.SPECIFIC

name::
* Mcs.Mcs-name.specific,
* Mcs.Mcs'attAsNameAsSpecific,

specific::
* dezignator-name,
* dezignatorNo-name,
* main-name,
* title,
===
* English-name,
* EnglishNo-name,
===
* machine-name,
* machineNo-name,

name.dezignator

description::
· dezignator of Mcs[a] is a-name we use to refer to concept[a] itself and not to one of its semaso-concepts.
· its generic noun usually it is-used as dezignator.
[hmnSgm.2019-08-05]

name::
* Mcs.Mcs'dezignator!⇒Mcs-dezignator,
* Mcs.Mcs-dezignator,
* Mcs.dezignator-of-Mcs!⇒Mcs-dezignator,

specific::
* ID,
* main-name,
* title,

dezignator.main

description::
· a-Mcs can-have many dezignators.
· main-name is its most used term dezignator.
· the related names of the-concept (part, specific) are created from the-main-name.

name::
* Mcs.main--Mcs-name!⇒Mcs-main-name,
* Mcs.main-name--of-Mcs!⇒Mcs-main-name,
* Mcs.Mcs-dezignator.main!⇒Mcs-main-name,
* Mcs.Mcs-name.main!⇒Mcs-main-name,
* Mcs.Mcs'attAsNameAsMain!⇒Mcs-main-name,
* Mcs.Mcs'main-name!⇒Mcs-main-name,
* Mcs.Mcs-main-name, {2019-03-10}

derived-name of main-name

description::
· derived-name--of--Mcs-main-name[a] is a-derived-name of it[a]

name::
* Mcs.derived-name--of--Mcs-main-name,
* Mcs.Mcs-name.main'derived-name,
* Mcs.Mcs-main-name'derived-name,
* Mcs.related-name--of--Mcs-main-name,

dezignator.mainNo

description::
· mainNo-dezignator of Mcs is any dezignator other than the-main-name.
· the-mainNo-dezignators, 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::
* Mcs.mainNo-dezignator--Mcs-name,
* Mcs.Mcs-dezignator.mainNo,

dezignator.synonyms

description::
· synonyms of Mcs[a] is the-set of all dezignators of Mcs[a]

name::
* Mcs.Mcs-dezignator.synonyms,

dezignator.conceptary

description::
· conceptary of worldview is the-set of all dezignators in one language.

name::
* Mcs.conceptary-of-worldview,

environment::
* wordary,
* namary,

name.dezignatorNo

description::
· dezignatorNo of Mcs[a] is a-name not a-dezignator.
[hmnSgm.2019-08-05]

name::
* Mcs.Mcs'dezignatorNo,
* Mcs.dezignatorNo-of-Mcs,

name.individual

description::
· genericNo-name of Mcs is any genericNo-logo-name of it.

name::
* Mcs.Mcs-name.element,
* Mcs.Mcs-name.genericNo,
* Mcs.Mcs-name.individual,
* Mcs.Mcs-name.instance,
* Mcs.Mcs'name-element,
* Mcs.Mcs'name-instance,
* Mcs.Mcs-name, {2019-02-11}
* Mcs.genericNo-name--of-Mcs,
* Mcs.name-element--of-Mcs,
* Mcs.name-instance--Mcs-att,
* Mcs.nameMcs,
* Mcs'name, {2019-03-02}

name.English

description::
· a-English-Mcs-name has:
* title: 'name::' and
* list-elements: '* Mcs.name'

name::
* Mcs.English--Mcs-name,
* Mcs.Mcs-name.English,

name.EnglishNo

description::
· a-non-English-Mcs-name has:
* title: 'name.Language::' and
* list-elements: '* McsLag.name', where Lag is the-3-letter-terminology-ISO-639-2-language-code.

name::
* Mcs.Mcs-name.EnglishNo,
* Mcs.non-English--Mcs-name,

name.Greek::
* McsEll.μη-Αγγλικό-όνομα-δομημένης-έννοιας,

name.machine

description::
· formal--Mcs-name is an-Mcs-name used most by machines.
· for example, "Mcs-nameAsFormal".
· 1) machine-names begin with capitals: "Dtc-Net".
· 2) initializations have only first capital: "Html, Dbcnet".

name::
* Mcs.formal--Mcs-name,
* Mcs.machine--Mcs-name,
* Mcs.Mcs-name.formal,
* Mcs.Mcs-name.machine,
* Mcs.Mcs'attAsNameAsFormal,
* Mcs.Mcs'attAsNameAsMachine,

name.machineNo

description::
· formalNo--Mcs-name is an-Mcs-name used most by humans.
· for example, "non-formal-Mcs-name".

name::
* Mcs.formalNo--Mcs-name,
* Mcs.machineNo--Mcs-name,
* Mcs.Mcs-name.formalNo,
* Mcs.Mcs-name.machineNo,
* Mcs.Mcs'attAsNameAsFormalNo,
* Mcs.Mcs'attAsNameAsMachineNo,

name.dictionary

description::
· 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::
* Mcs.dictionary,
* Mcs.glossary,
* Mcs.lexicon,
* Mcs.terminology,
* Mcs.vocabulary,

part.definition

description::
· 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.
· description is TEXT that IDENTIFY a-Mcs.
· a-definition is formal if it is readable and by machines.

name::
* Mcs.definition--Mcs-att,
* Mcs.definition-att-of-Mcs,
* Mcs.definition-of-Mcs,
* Mcs.Mcs-att.definition,
* Mcs.Mcs-part.definition,
* Mcs.Mcs'attAsDefinition,

part.part-division

description::
· part-division--Mcs-att is a-division of the-part-attributes.

name::
* Mcs.division.part--Mcs-att,
* Mcs.Mcs'division.part,
* Mcs.Mcs-part.part-division,
* Mcs.Mcs-att.part-division,
* Mcs.Mcs'attAsPartial-division,
* Mcs.part-division--Mcs-att,

attribute.partNo (environment)

description::
· partNo--Mcs-att is the-complement of part-attribute.

name::
* Mcs.Mcs'external-attribute!⇒Mcs-envt-att,
* Mcs.Mcs'internalNo-attribute!⇒Mcs-envt-att,
* Mcs.Mcs'attAsExternal!⇒Mcs-envt-att,
* Mcs.Mcs'attAsInternalNo!⇒Mcs-envt-att,
* Mcs.Mcs'attAsPartNo!⇒Mcs-envt-att,
* Mcs.Mcs-att.environment!⇒Mcs-envt-att,
* Mcs.Mcs-att.external!⇒Mcs-envt-att,
* Mcs.Mcs-att.internalNo!⇒Mcs-envt-att,
* Mcs.Mcs-att.partNo!⇒Mcs-envt-att,
* Mcs.Mcs-envt-att,
* Mcs.environment--Mcs-att!⇒Mcs-envt-att, {2019-03-09}
* Mcs.external--Mcs-att!⇒Mcs-envt-att,
* Mcs.extrinsic--Mcs-att!⇒Mcs-envt-att,
* Mcs.intrinsicNo--Mcs-att!⇒Mcs-envt-att,
* Mcs.partNo--Mcs-att!⇒Mcs-envt-att,
====== langoKomo:
* McsKmo.atro-joUgo-a-Mes!=partNo-att--of-Mcs,

envt-att.specifics-division.whole

description::
· on whole:
* whole--envt-att,
* wholeNo--envt-att,

name::
* Mcs.Mcs-envt-att.specifics-division.whole,

attribute.whole

description::
· whole-att of Mcs[a] is another Mcs[b] which has as part the-Mcs[a].

name::
* Mcs.Mcs-att.partNo.whole!⇒Mcs-whole,
* Mcs.Mcs-att.whole!⇒Mcs-whole,
* Mcs.Mcs'attAsWhole!⇒Mcs-whole,
* Mcs.whole--Mcs-att, {2019-03-09}
* Mcs.whole-of-Mcs,
====== langoKomo:
* McsKmo.atro-co-a-Mes!=whole-att--of-Mcs,

attribute.whole-chain

description::
· whole-chain of Mcs[a] is the-chain of whole-concepts of Mcs[a] from parent-whole to most-whole-concept.

name::
* Mcs.Mcs-att.whole-chain,
* Mcs.Mcs'attAsWhole-chain,
* Mcs.whole-chain--Mcs-att,

attribute.wholeNo

description::
· wholeNo--Mcs-att is a-partNo-att which is not whole of this Mcs.

name::
* Mcs.Mcs-att.partNo.wholeNo,
* Mcs.Mcs-att.wholeNo,
* Mcs.Mcs'attAsWholeNo,
* Mcs.wholeNo--Mcs-att,
====== langoKomo:
* McsKmo.atro-coUgo-a-Mes!=partNo.wholeNo-att--of-Mcs,

attribute.wholeNo.SPECIFIC

specific::
* author-of-Mcs,
* evaluation-of-Mcs,
* referent-of-Mcs,
* supporter-of-Mcs,

attribute.wholeNo.archetype

description::
· 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].
[hmnSgm.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::
* Mcs.Mcs'archetype,
* Mcs.Mcs-att.archetype,
* Mcs.Mcs-att.referent,
* Mcs.Mcs'attAsArchetype,
* Mcs.Mcs'referent,
* Mcs.archetype--Mcs-att,
* Mcs.referent--Mcs-att,

whole-chain::
* environment--Mcs-att,

generic-chain::
* Mcs-att,

attribute.wholeNo.evaluation

description::
· evaluation--Mcs-att is the-cons and pros of the-Mcs.

name::
* Mcs.evaluation--Mcs-att,
* Mcs.Mcs-att.evaluation,
* Mcs.Mcs-att.wholeNo.evaluation,

attribute.wholeNo.supporter

description::
· supporter-of-Mcs is the-entity (human, group of humans, machine) that consider this Mcs as true.

name::
* Mcs.Mcs-att.holder,
* Mcs.Mcs-att.supporter,
* Mcs.Mcs'supporter,
* Mcs.supporter-of-Mcs,

attribute.author

description::
· author is the-supporter who created the-Mcs.

name::
* Mcs.author-of-Mcs,
* Mcs.Mcs'author,
* Mcs.Mcs'creator,

attribute.wholeNo.meta-info

description::
· meta-info--Mcs-att is a-Mcs-att that presents additional info about the-Mcs itself, like times visited, versions, ...

name::
* Mcs.Mcs-att.meta-info,
* Mcs.Mcs-att.wholeNo.meta-info,
* Mcs.meta-info--Mcs-att,

attribute.doing

description::
· doing--Mcs-att is LISTS of a-Mcs-att which are doings|processes.

name::
* Mcs.doing--Mcs-att,
* Mcs.Mcs-att.doing,

attribute.evoluting

description::
· evoluting--Mcs-att 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::
* Mcs.evoluting--Mcs-att,
* Mcs.Mcs-att.evoluting,
* Mcs.Mcs-att.specific.evoluting,

attribute.doingNo

description::
· doingNo--Mcs-att is the-complement doing-att.

name::
* Mcs.doingNo--Mcs-att,
* Mcs.Mcs-att.doingNo,

attribute.generic

description::
· 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::
* Mcs.generic-att--of-Mcs,
* Mcs.generic-of-Mcs,
* Mcs.Mcs-att.generic,
* Mcs.Mcs'attAsGeneric-attribute,
* Mcs.Mcs'generic-attribute,
====== langoKomo:
* McsKmo.atro-ko-a-Mes!=generic-att--of-Mcs,

attribute.generic-chain

description::
· generic-chain of Mcs[a] is the-chain of generic-concepts of Mcs[a] from parent-generic to most-generic-concept.

name::
* Mcs.generic-chain--Mcs-att,
* Mcs.Mcs-att.generic-chain,
* Mcs.Mcs'attAsGeneric-chain,

attribute.specific

description::
· 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::
* Mcs.Mcs-att.specific,
* Mcs.Mcs'attAsSpecific,
* Mcs.specific--Mcs-att,
* Mcs.specific-att-of-Mcs,
* Mcs.specific-of-Mcs,
====== langoKomo:
* McsKmo.atro-koUanto-a-Mes!=specific-att--of-Mcs,

attribute.individual

description::
· individual-att of Mcs is a-specific-of-Mcs which has no other specifics.

name::
* Mcs.Mcs-att.individual,
* Mcs.individual-att--of-Mcs,
* Mcs.individual-of-Mcs,
* Mcs.instance-of-Mcs,
====== langoKomo:
* McsKmo.atro-koUgo-a-Mes!=individual-att--of-Mcs,

attribute.specifics-division

description::
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!
[hmnSgm.2017-11-15]

name::
* Mcs.division.specifics--Mcs-att,
* Mcs.Mcs-att.division.specifics,
* Mcs.Mcs-att.specifics-division,
* Mcs.Mcs-division.specifics,
* Mcs.Mcs'attAsSpecifics-division,
* Mcs.specifics-division--Mcs-att,

attribute.specific-chain

description::
Specific-chain-of-Mcs[a] is the-chains of the-specific-concepts of Mcs[a] from child-specifics to instance-specifics.

name::
* Mcs.specific-chain--Mcs-att,
* Mcs.Mcs-att.specific-chain,
* Mcs.Mcs'attAsSpecific-chain,
* Mcs.Mcs'specific-chain--attribute,

attribute.inherited-from

description::
Inheritedfrom--Mcs[a]-att is an-attribute-of-Mcs[a] which is AND attribute of a-generic-concept of it[a].

name::
* Mcs.inherited-from--Mcs-att,
* Mcs.Mcs-att.inherited-from,
* Mcs.Mcs'attAsInherited-from,
* Mcs.Mcs'inherited-from--attribute,

attribute.inherited-from.no

description::
InheritedfromNo--Mcs[a]-att is an-attribute-of-Mcs[a] which is NOT AND attribute of a-generic-concept of it[a].

name::
* Mcs.inherited-fromNo--Mcs-att,
* Mcs.Mcs-att.inherited-fromNo,
* Mcs.Mcs'attAsInherited-fromNo,

attribute.inherited-to

description::
Inheritedto--Mcs[a]-att is an-attribute-of-Mcs[a] which is AND attribute of a-specific-concept of it[a].

name::
* Mcs.inherited-to--Mcs-att,
* Mcs.Mcs-att.inherited-to,
* Mcs.Mcs'attAsInherited-to,

attribute.inherited-to.no

description::
InheritedtoNo--Mcs[a]-att is an-attribute-of-Mcs[a] which is NOT AND attribute of a-specific-concept of it[a].

name::
* Mcs.inherited-toNo--Mcs-att,
* Mcs.Mcs-att.inherited-toNo,
* Mcs.Mcs'attAsInherited-toNo,
* Mcs.Mcs'inherited-toNo--attribute,

text of Mcs

description::
· Mcs-text is TEXT comprised of Mcs-names.
· it uses the-Mcs-name-notation.
· the-goal of Mcs-text is to be MONOSEMANTIC by defining ALL the-names it uses, LIKE computer-language-texts.
[hmnSgm.2018-10-14]

name::
* Mcs.Mcs'text!⇒Mcs-text,
* Mcs.Mcs-text, {2019-05-22}
* Mcs.structured-concept--text!⇒Mcs-text,
* Mcs.text-of-Mcs!⇒Mcs-text,

manager of Mcs-envt

description::
· Mcs-manager is the-tools, computer-programs, info-storage-entities, etc we use to manage Mcs.

name::
* Mcs.Mcs'manager!⇒Mcs-mngr,
* Mcs.Mcs-manager!⇒Mcs-mngr,
* Mcs.Mcs-mngr,
* Mcs.Mcs-tool!⇒Mcs-mngr,

DOING of Mcs-mngr

name::
* Mcs.Mcs-mngr'doing!⇒Mcs-mngr-doing,
* Mcs.Mcs-mngr-doing,

doing.formating of Mcs-mngr

description::
· changing the-format of a-Mcs, to change this format in all other Mcs.

name::
* Mcs.Mcs-mngr-doing.formating,

doing.generic-specific-managing of Mcs-mngr

description::
· this is THE-MOST IMPORTANT DOING the-manager MUST-HAVE.
· changing an-attribute in a-generic-Mcs[a], the-manager to make this change in all its[a] specifics.

name::
* Mcs.Mcs-mngr-doing.generic-specific-managing,

doing.whole-part-managing of Mcs-mngr

description::
·

name::
* Mcs.Mcs-mngr-doing.whole-part-managing,

evaluation of Mcs-envt

description::
· 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.
[hmnSgm.2017-11-28]

name::
* Mcs.Mcs'evaluation,
* Mcs.McsAeEvaluation,

monosemanticity of Mcs

description::
· 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 a-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.
[hmnSgm.2018-03-12]
===
· monosemanticity of info is a-prerequisite of artificial-intelligence.
[hmnSgm.2018-12-30]
===
· monosemanticity is a-prerequisite for correct translations.
[hmnSgm.2018-12-31]

name::
* Mcs.monosemanticity-of-Mcs,
* Mcs.Mcs'monosemanticity,

consistency of Mcs

description::
· 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 a-Mcs-worldview: the-whole-part-tree and the-generic-specific-tree.
[hmnSgm.2018-03-12]

name::
* Mcs.consistency-of-Mcs,
* Mcs.Mcs'consistency,

completeness of Mcs

description::
· complete-info is info with no wholes in its structure.
· like consistency it will-be-achieved from structureness.

name::
* Mcs.completeness-of-Mcs,
* Mcs.Mcs'completeness,

subjectivity of Mcs

description::
· 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.
[hmnSgm.2019-01-05]

name::
* Mcs.Mcs'subjectivity,
* Mcs.subjectivity-of-Mcs,

ENVIRONMENT of Mcs

name::
* Mcs.Mcs'environment,
* Mcs.McsAeEnvironment,

specific::
* evaluation-of-Mcs,
* human-concept,
* referent-of-Mcs,

related-tech of Mcs

name::
* Mcs.Mcs'related-tech,

specific::
* AI,
* conceptual-graph,
* knowledge-graph,
* mind-map,
* ontology,
* topic-map,

relation to human-concept of Mcs

description::
· 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::
* Mcs.human-concept'relation-to--structured-concept,
* Mcs.Mcs'relation-to--human-concept,
* Mcs.McsAeRelation-to--human-concept,
* Mcs.relation-of--human-concept--to-Mcs,
* Mcs.relation-of-Mcs-to--human-concept,

relation to entity of Mcs

description::
· 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.
[hmnSgm.2017-12-04]

name::
* Mcs.entity'relation-to--structured-concept,
* Mcs.Mcs'relation-to-entity,
* Mcs.McsAeRelation-to-entity,
* Mcs.relation-of-entity-to-Mcs,
* Mcs.relation-of-Mcs-to-entity,

relation to object-oriented-programing of Mcs

description::
· a-structured-concept is similar to 'object' in Oop-object-oriented-programing.
· objects serve the-inheritance-mechanism in programing-languages, and structured-concepts serve the-inheritance-mechanism in natural-languages.
· in contrast, structured-concepts inherit FROM other structured-concepts and inherit TO others, but objects inherit from classes or prototypes-of-constructors.

name::
* Mcs.Oop'relation-to--structured-concept,
* Mcs.Mcs'relation-to-Oop,
* Mcs.McsAeRelation-to-Oop,
* Mcs.relation-of-Oop-to-Mcs,
* Mcs.relation-of-Mcs-to-Oop,

WHOLE of Mcs

whole-chain::
* Mcs-view,
* Mcs-worldview.Synagonism,
...
* Sympan,

name::
* Mcs.Mcs'whole,
* Mcs.McsAwWhole,

view of Mcs

description::
· Mcs-view is a-Mcs with one or more structured-concepts that we communicate.

name::
* Mcs.Mcs'view!⇒Mcs-view,
* Mcs.Mcs'conceptual-model!⇒Mcs-view,
* Mcs.McsAwView!⇒Mcs-view,
* Mcs.Mcsm!⇒Mcs-view,
* Mcs.Mcsv!⇒Mcs-view,
* Mcs.Mcsv-(Mcs-view)!⇒Mcs-view,
* Mcs.McsView!⇒Mcs-view,
* Mcs.Mcs-view, {2019-05-22}
* Mcs.conceptual-model--of--structured-concepts!⇒Mcs-view,
* Mcs.conceptual-modelAsMcs!⇒Mcs-view,
* Mcs.model-of-structured-concepts!⇒Mcs-view,
* Mcs.modelConceptualMcs!⇒Mcs-view,
* Mcs.modelInfoView.Mcs!⇒Mcs-view,
* Mcs.structured-concept--knowledge!⇒Mcs-view,
* Mcs.structured-concept--view!⇒Mcs-view,
* Mcs.view-of-Mcs!⇒Mcs-view,

nameGreek::
* McsEll.δομημένων-εννοιών--εννοιακό-μοντέλο,
* McsEll.δομημένων-εννοιών--θεώρηση,
* McsEll.εννοιακό-μοντέλο--δομημένων-εννοιών,
* McsEll.θεώρηση--δομημένων-εννοιών,

specific::
* directory-McsView,
* world-McsView,
* base-McsView,

directory of Mcs (McsDir)

description::
· directory-McsView is a-McsView that is-stored in a-computer-directory.

name::
* Mcs.directory-McsView,
* Mcs.Mcs'directory,
* Mcs.McsAwDirectory,
* Mcs.Mcsd,
* Mcs.Mcsd-(Mcs-directory),
* Mcs.McsDir,
* Mcs.McsViewAsDirectory,

worldview of Mcs

description::
· Mcs-worldview is a-McsView of an-entity (human, group-of-humans, organization-of-humans) with ALL their Mcs-views.
· a-Mcs-worldview is a-Mcs.
· a-Mcs-worldview is MONOSEMOUS, because the-Mcs-text it uses is monosemous.
· a-Mcs-worldview is SUBJECTIVE, it describes the-view about the-world of the-entity that supports it.

name::
* Mcs.Mcs.worldview!⇒Mcs-worldview,
* Mcs.McsAsWorldview!⇒Mcs-worldview,
* Mcs.Mcs'worldview!⇒Mcs-worldview,
* Mcs.McsViewAsWorldview!⇒Mcs-worldview,
* Mcs.McsWorldview!⇒Mcs-worldview,
* Mcs.McsWorld!⇒Mcs-worldview, {2019-03-01}
* Mcs.Mcsw!⇒Mcs-worldview,
* Mcs.Mcs-worldview, {2019-05-22}
* Mcs.ModelInfoWorldAsMcs!⇒Mcs-worldview,
* Mcs.structured-concept--pedia!⇒Mcs-worldview,
* Mcs.structured-concept--worldview!⇒Mcs-worldview,
* Mcs.worldview.Mcs!⇒Mcs-worldview,
* Mcs.worldviewAsMcs!⇒Mcs-worldview,

nameGreek::
* McsEll.δομημένων-εννοιών--κοσμοθεώρηση,
* McsEll.κοσμοθεώρηση--δομημένων-εννοιών,

generic-chain::
* McsView,
* Mcs,

dirMiwMcs of McsWorld

description::
· every Mcs-worldview is-stored in a-site in a root-directory 'dirMiwMcs'.

name::
* Mcs.Mcs'dirMiwMcs,
* Mcs.McsWorld'dirMiwMcs,

base of Mcs

description::
Mcs-base is a-McsView with many Mcs-worldviews.

name::
* Mcs.Mcs'base!⇒Mcs-base,
* Mcs.Mcs-base,
* Mcs.structured-concept--base!⇒Mcs-base,

DOING of Mcs

name::
* Mcs.Mcs'doing,

specific::
* managing-Mcs,
* searching-Mcs,

searching Mcs

description::
· because Mcs-knowledge is structured, we can-access ANY concept, directly from anywhere.
· this site demonstrates this feature.

name::
* Mcs.Mcs'searching,
* Mcs.searching-Mcs,

specific::
* McsHitp-searching,

EVOLUTING of Mcs

name::
* Mcs.Mcs'evoluting,
* Mcs.McsAdEvoluting,

{time.2017-11-17}::
=== Mcs-PUBLICATION:
I published the-Mcs (this concept, McsHitp) in synagonism.net and github.

{time.1994-1995}::
=== 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.

{time.1985}::
=== Hellenic Mathematical Society:
I suggested to distinguish in any math-concept its a)name, b)semasia, c)symbol, and d)graphics.

GENERIC of Mcs

generic-chain::
* information,
* model,
* entity,

name::
* Mcs.Mcs'generic,
* Mcs.McsAgGeneric,

Mcs.SPECIFIC

name::
* Mcs.Mcs.specific,
* Mcs.McsAsSpecific,

specific::
* Everipedia-Mcs,
* Hitp-Mcs,
* FolioViews-Mcs,
* chain-Mcs,

Mcs.Hitp (McsHitp)

description::
· Hitp-Mcs is a-Mcs written with my Hitp-web-language.
· the current concept (Mcs) is a-Hitp-Mcs.

name::
* Mcs.Hitp-Mcs!⇒McsHitp,
* Mcs.Hitp--structured-concept!⇒McsHitp,
* Mcs.Hitp-structured-concept!⇒McsHitp,
* Mcs.Mcs.Hitp!⇒McsHitp,
* Mcs.Mcs.web!⇒McsHitp,
* Mcs.McsAsHitp!⇒McsHitp,
* Mcs.McsHitp,
* Mcs.modelConceptStructuredHitp!⇒McsHitp,
* Mcs.structured-concept.Hitp!⇒McsHitp,
* Mcs.web-Mcs!⇒McsHitp, {2018-02-18}
* Mcs.web--structured-concept!⇒McsHitp, {2018-02-18}

manager of McsHitp

description::
· McsHitp-manager is the-programs we need to manage McsHitp.

name::
* Mcs.McsHitp'manager,
* Mcs.McsHitp-manager!⇒McsHitp'manager,

generic-chain::
* Hitp-manager,

WHOLE of McsHitp

whole::
* Mcs-worldview.Synagonism,
* Mcs-base,

EVOLUTING of McsHitp

name::
* Mcs.McsHitp'evoluting,

generic-chain::
* Hitp-evoluting,

{time.2018-10-16}::
· I am-using '* Mcs.' instead of '* cpt.' in the-list of names.

McsHitp.SPECIFIC

specific::
* File-McsHitp,
* FileNo-McsHitp,

McsHitp.FILE

description::
· a-McsHitpFile is a-McsHitp which is a-webpage.

name::
* Mcs.file-McsHitp,
* Mcs.header-McsHitp,
* Mcs.McsHitp.Header,
* Mcs.McsHitp.File,
* Mcs.McsHitpAsheader,
* Mcs.McsHitpAsfile,
* Mcs.McsHitpFile,

title of McsHitpFile

description::
· McsHitpFile-title is a-header-Html-element which includes a-h1-element with the-text of the-title.

name::
* Mcs.McsHitpFile'title,
* Mcs.title-of-McsHitpFile,

McsHitp.FILE.NO

name::
* Mcs.fileNo-McsHitp!⇒McsHitpFileNo,
* Mcs.McsHitp.FileNo!⇒McsHitpFileNo,
* Mcs.McsHitpAsfileNo!⇒McsHitpFileNo,
* Mcs.McsHitpFileNo, {2019-03-07}

specific::
* H1-McsHitp,
* H2-McsHitp,
* H3-McsHitp,
* H4-McsHitp,
* H5-McsHitp,
* H6-McsHitp,
* P-McsHitp,

McsHitp.P

description::
· there-are 2 types of McsHitpP:
* a-text McsHitpP and
* a-list McsHitpP.
[hmnSgm.2017-12-17]

name::
* Mcs.paragraph-McsHitp!⇒McsHitpP,
* Mcs.McsHitp.paragraph!⇒McsHitpP,
* Mcs.McsHitp.P!⇒McsHitpP,
* Mcs.McsHitpFileNo.paragraph!⇒McsHitpP,
* Mcs.McsHitpP,

title of McsHitpP

description::
· the-title of a-McsHitpP ends with '::'

name::
* Mcs.McsHitpP'title,
* Mcs.title-of-McsHitpP,

McsHitpP.TEXT

description::
· a-text--Hitp-structured-concept is comprised of:
* a-title that ends with '::' and
* a-list of sentences that begin with '·' and end with '.'.
· examples are the-description structured-concepts.
[hmnSgm.2017-12-17]

name::
* Mcs.McsHitp.text,
* Mcs.text--Hitp-structured-concept,
* Mcs.text-McsHitpP,
* Mcs.McsHitpP.text,

McsHitpP.LIST

description::
· a-list--Hitp-structured-concept is comprised of:
* a-title that ends with '::' and
* a-list of names that begin with '*'.
· examples are the-name structured-concepts.
[hmnSgm.2017-12-17]

name::
* Mcs.McsHitp.list,
* Mcs.list--Hitp-structured-concept,
* Mcs.list-McsHitpP,
* Mcs.McsHitpP.list,

Mcs.Dchain

description::
· Đ-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.
[hmnSgm.2018-02-18]

name::
* Mcs.Dchain-Mcs!⇒Dconcept,
* Mcs.Dconcept {2019-04-25},
* Mcs.McsDchain!⇒Dconcept,
* Mcs.Mcs.Dchain!⇒Dconcept,
* Mcs.Mcs.decentralized!⇒Dconcept,
* Mcs.decentralized--structured-concept!⇒Dconcept,
* Mcs.Đ-Mcs!⇒Dconcept,

Mcs.definite

description::
· definite-Mcs is a-Mcs identifiable WITH clear boundaries.

name::
* Mcs.Mcs.definite,
* Mcs.definite-Mcs,
====== langoKomo:
* McsKmo.dio,

Mcs.definiteNo

description::
· definiteNo-Mcs is a-Mcs identifiable WITHOUT clear boundaries.

name::
* Mcs.Mcs.definiteNo,
* Mcs.definiteNo-Mcs,
====== langoKomo:
* McsKmo.dioUgo,

Mcs.relative

description::
· relative-Mcs is a-Mcs defined in relation to another one SAME Mcs.
· example: time relative to another time.

name::
* Mcs.Mcs.relative,
* Mcs.relative-Mcs,
====== langoKomo:
* McsKmo.tio!=relative-Mcs,

Mcs.relativeNo

description::
· relativeNo-Mcs is a-Mcs NOT defined in relation to another one SAME Mcs.

name::
* Mcs.Mcs.relativeNo,
* Mcs.relativeNo-Mcs,
====== langoKomo:
* McsKmo.tioUgo!=relativeNo-Mcs,

meta-info

This page was-visited times since {2017-11-17}

page-wholepath: synagonism.net / Mcs-worldview / dirCore / modelConceptStructured

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 "Mcs.words-of-concept's-name", to go to the-LOCATION of the-concept.
GLOBAL-SEARCH:
Clicking on the-green-TITLE 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.

footer::
• author: Kaseluris.Nikos.1959
• email:
 imgMail
• edit on github: https://github.com/synagonism/Mcsw/blob/master/dirCor/filMcs.last.html,
• twitter: @synagonism

webpage-versions::
• version.last.dynamic: filMcs.last.html,
• version.4-0-0.2019-08-06 (3.65): FilMcs.4-0-0.2019-08-06.html,
• version.3-0-0.2017-11-26.last: FilMcs.3-0-0.2017-11-26.html,
• version.2-0-0.2017-11-21: filMcs.2-0-0.2017-11-21.html,
• version.1-0-0.2017-11-20: filMcs.1-0-0.2017-11-20.html,
• version.0-1-0.2017-11-17.published: filMcs.0-1-0.2017-11-17.html,

support (link)

comments

comments powered by Disqus