structured-concept:
structured-concept-(Mcs)
(modelConceptStructured)

McsHitp-creation: {2017-09-27}

overview of Mcs-part

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.modelConceptStructured!⇒Mcs,
* Mcs.modelConceptStructured-(Mcs)!⇒Mcs,
* Mcs.Mcs,
* Mcs.Mcs'(modelConceptStructured)!⇒Mcs,
* Mcs.Mcs-(modelConceptStructured)!⇒Mcs,
* Mcs.structured-concept-(Mcs)!⇒Mcs,

name.Greek::
* McsEll.δομημένη-έννοια-(Μεδ),
* McsEll.Μεδ,
* McsEll.μοντέλο-δομημένης-έννοιας,
* McsEll.μοντέλοΕννοιαΔομημένη-(Μεδ),

attribute of Mcs

description::
· attribute-of-Mcs[a] is any Mcs[b] related with Mcs[a].

name::
* Mcs.attribute-of-Mcs!⇒Mcs'att,
* Mcs.Mcs'attribute!⇒Mcs'att,
* Mcs.Mcs-att!⇒Mcs'att,
* Mcs.McsAaAttribute!⇒Mcs'att,
* Mcs.Mcs'att,

Mcs-att.SPECIFIC

specific::
* part-att,
* partNo-att,
===
* generic-att,
* specific-att,
===
* inherited-from-att,
* inherited-fromNo-att,
===
* inherited-to-att,
* inherited-toNo-att,
===
* author-att,
* complement-of-att,
* definition-att,
* description-att,
* dichotomous-division--att,
* division-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,
* partial-division--att,
* specific-att,
* specific-chain--att,
* specific-division--att,
* supporter-att,
* title-att,
* whole-att,
* whole-chain--att,

Mcs-att.DIVISION

description::
· division--Mcs-att is the-SET of attributes of the-Mcs that make-up the-Mcs (= same referent) 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.division--Mcs-att,
* Mcs.Mcs'att.division,
* Mcs.Mcs'attAsDivision,
* Mcs.Mcs'division-attribute,

complement-of-att in division

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

name::
* Mcs.complement-of--Mcs-att,
* Mcs.Mcs'att'complement,

Mcs-att.division.SPECIFIC

specific::
* dichotomous-division,
* part-division,
* doing-division,
===
* partial-division,
* specific-division,

Mcs-att.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-att.division.PART

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

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

Mcs-att.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-att.PART (internal)

description::
· part--Mcs[a]-att is LISTS of part-instances-of-Mcs[a].

name::
* Mcs.externalNo--Mcs-att,
* Mcs.internal--Mcs-att,
* Mcs.intrinsic--Mcs-att,
* Mcs.Mcs'externalNo-attribute,
* Mcs.Mcs'internal-attribute,
* Mcs.Mcs'att.externalNo,
* Mcs.Mcs'att.internal,
* Mcs.Mcs'att.part,
* Mcs.Mcs'attAsExternalNo,
* Mcs.Mcs'attAsInternal,
* Mcs.Mcs'attAsPart,
* Mcs.part--Mcs-att,

Mcs-att.part-instance

description::
· part-instance--Mcs[a]-att is an-attribute we view as internal|intrincic to Mcs[a].

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

Mcs-att.title

description::
· title-of-Mcs is the-att that contains the-main-name of a-Mcs.

name::
* Mcs.Mcs'att.name.title,
* Mcs.Mcs'att.title,
* Mcs.McsApTitle,
* Mcs.title--Mcs-att,

generic-chain::
* name-attribute-of-Mcs,

Mcs-att.overview

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

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

Mcs-att.description

description::
· description--Mcs-att is Mcs-TEXT that IDENTIFIES a-Mcs.
· a-definition UNIQUELY IDENTIFIES a-Mcs.
[hmnSgm.2017-12-22]
===
Description--Mcs-att is TEXT that identifies the-Mcs informally.
The-definition identifies the-Mcs formally.

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

Mcs-att.name

description::
· name--Mcs-att is a-Mcs-att with a-set of lists of Mcs-name-elements.
· every language has its own list.
[hmnSgm.2018-11-03]

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

naming-convension of name-att

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

1) no spaces in multi-word names:
* human-language, Mcs-att,
* use '-' or '_' 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]

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

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

4) ONE CASE everywhere:
· sentences begin with '·', 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.Mcs'att.name'naming-convension,
* Mcs.Mcs'name-notation,
* Mcs.Mcs'name'notation,
* Mcs.name-notation--of-Mcs,
* Mcs.naming-convension--of-Mcs,
* Mcs.notation-of--Mcs-name,

naming-convension before {time.2017-11-21}

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-att

description::
· derived-name--of--a-Mcs-name[a] is a-name of an-attribute of the-concept with the-Mcs-name[a].
· with the-Mcs-naming-convension it begins with the-Mcs-name[a] which is-called 'original-name'.

name::
* Mcs.derived-name--of--a-Mcs-name,
* Mcs.Mcs'att.name'derived-name,

original-name of name-att

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

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

WHOLE of name-att

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

name-att.SPECIFIC

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

specific::
* title,
===
* English--name-att,
* EnglishNo--name-att,
===
* machine--name-att,
* machineNo--name-att,

name-att.INSTANCE

description::
· name-element--of-Mcs is any entity linguistic (word construct) or not, a-language uses to denote a-Mcs.
[hmnSgm.2018-11-03]

name::
* Mcs.Mcs'att.name.element!⇒Mcs-name,
* Mcs.Mcs'att.name.instance!⇒Mcs-name,
* Mcs.Mcs'name!⇒Mcs-name,
* Mcs.Mcs'name-element!⇒Mcs-name,
* Mcs.Mcs'name-instance!⇒Mcs-name,
* Mcs.Mcs-name, {2019-02-11}
* Mcs.name-element--of-Mcs!⇒Mcs-name,
* Mcs.name-instance--Mcs-att!⇒Mcs-name,

name-att.ENGLISH

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

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

name-att.ENGLISH.NO

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'att.name.EnglishNo,
* Mcs.non-English--Mcs-name,

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

name-att.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'att.name.formal,
* Mcs.Mcs'att.name.machine,
* Mcs.Mcs'attAsNameAsFormal,
* Mcs.Mcs'attAsNameAsMachine,

name-att.MACHINE.NO

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'att.name.formalNo,
* Mcs.Mcs'att.name.machineNo,
* Mcs.Mcs'attAsNameAsFormalNo,
* Mcs.Mcs'attAsNameAsMachineNo,

name-att.MAIN

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

name::
* Mcs.main--Mcs-name,
* Mcs.Mcs'att.name.main,
* Mcs.Mcs'attAsNameAsMain,

name-att.MAIN.NO

description::
· mainNo-name is any name other than the-main-name.
· the-mainNo-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::
* Mcs.mainNo--Mcs-name,
* Mcs.Mcs'att.name.mainNo,
* Mcs.Mcs'attAsNameAsMainNo,

Mcs-att.definition

description::
· definition--Mcs-att is LISTS of definition-instances.
[hmnSgm.2019-01-13]

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

Mcs-att.definition-instance

description::
· definition-instance--Mcs-att is Mcs-TEXT that UNIQUELY IDENTIFY a-Mcs in the shortest way.
· a-Mcs has more than one definition-instances because our knowledge is-structured at least in two fundamental structures: the-whole-part-tree and the-generic-specific-tree.
[hmnSgm.2019-01-13]
===
· definition--Mcs-att is Mcs-TEXT that UNIQUELY IDENTIFY a-Mcs in the shortest way.
· on the other hand, description is TEXT that IDENTIFY a-Mcs.
[hmnSgm.2017-12-23]
===
· definition--Mcs-att is TEXT that UNIQUELY IDENTIFY a-Mcs in the shortest way.
· description does the-same in a longer way.
· a-definition is formal if it is readable and by machines.
[hmnSgm.2017-12-21]
===
Definition--Mcs-att is TEXT that UNIQUELY IDENTIFY the-Mcs in a formal way.
Formal here means readable by humans and machines.
In contrast, a-description identifies a-Mcs in an informal way.

name::
* Mcs.definition-instance--Mcs-att,
* Mcs.Mcs'att.definition-instance,

Mcs-att.partial-division

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

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

Mcs-att.PART.NO (environment)

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

name::
* Mcs.environment--Mcs-att,
* Mcs.external--Mcs-att,
* Mcs.extrinsic--Mcs-att,
* Mcs.intrinsicNo--Mcs-att,
* Mcs.Mcs'att.environment,
* Mcs.Mcs'external-attribute,
* Mcs.Mcs'internalNo-attribute,
* Mcs.Mcs'att.external,
* Mcs.Mcs'attAsExternal,
* Mcs.Mcs'att.internalNo,
* Mcs.Mcs'attAsInternalNo,
* Mcs.Mcs'att.partNo,
* Mcs.Mcs'attAsPartNo,
* Mcs.partNo--Mcs-att,

specific::
* whole,
* wholeNo,

Mcs-att.WHOLE

description::
Whole--Mcs[a]-att is LISTS of whole-instances-of-Mcs[a].

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

Mcs-att.WHOLE-INSTANCE

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

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

Mcs-att.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,

Mcs-att.WHOLE.NO

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,

Mcs-att.wholeNo.SPECIFIC

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

archetype of Mcs-envt

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-o-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.archetype--Mcs-att,
* Mcs.Mcs'archetype,
* Mcs.Mcs'att.archetype,
* Mcs.Mcs'att.referent,
* Mcs.Mcs'attAsArchetype,
* Mcs.Mcs'referent,
* Mcs.referent--Mcs-att,

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

generic-chain::
* Mcs-att,

Mcs-att.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,

Mcs-att.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,

Mcs-att.AUTHOR

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

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

Mcs-att.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,

Mcs-att.DOING

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

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

Mcs-att.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.

name::
* Mcs.evoluting--Mcs-att,
* Mcs.Mcs'att.evoluting,
* Mcs.Mcs'att.specific.evoluting,

Mcs-att.DOING.NO

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

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

Mcs-att.GENERIC

description::
· generic--Mcs-att is one or more lists of generic-elements--of-Mcs.

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

Mcs-att.GENERIC-INSTANCE

description::
· generic-element--Mcs[a] is another Mcs[b] whose[b] attributes are and attributes of Mcs[a] but not the-opposite.
· the-referent of a-generic-element-of-a-Mcs is a-superset of the-referent of the-Mcs.
[hmnSgm.2018-11-03]

name::
* Mcs.generic-instance--Mcs-att,
* Mcs.Mcs'att.generic-element,
* Mcs.Mcs'att.generic-instance,
* Mcs.Mcs'attAsGeneric-instance,
* Mcs.Mcs'generic-instance,

Mcs-att.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,

Mcs-att.SPECIFIC

description::
· specific--Mcs-att is a-set of lists with specific-elements--of-Mcs.
[hmnSgm.2018-11-03]

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

Mcs-att.SPECIFIC-INSTANCE

description::
· specific-element--of-Mcs[a] is another Mcs[b] if the-attributes of Mcs[a] are and attributes of Mcs[b] and not the-opposite.
· also, the-referent of a-specific is a-subset of the-referent of its generic.

name::
* Mcs.specific-element--Mcs-att,
* Mcs.specific-instance--Mcs-att,
* Mcs.Mcs'att.specific-element,
* Mcs.Mcs'att.specific-instance,
* Mcs.Mcs'attAsSpecific-instance,
* Mcs.Mcs'specific-instance,

Mcs-att.SPECIFIC-DIVISION

description::
Specific-division-of-Mcs[a] is the-set of specific-concepts of Mcs[a] on THE-SAME-ATTRIBUTE.
A-generic-concept can-have MANY specific-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.specific--Mcs-att,
* Mcs.Mcs'att.division.specific,
* Mcs.Mcs'att.specific-division,
* Mcs.Mcs'attAsSpecific-division,
* Mcs.specific-division--Mcs-att,

Mcs-att.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,

Mcs-att.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,

Mcs-att.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,

Mcs-att.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,

Mcs-att.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-envt

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.structured-text,
* Mcs.text-of-Mcs,

tool of Mcs-envt

description::
Mcs-tool is any computer-program we use to manage Mcs.

name::
* Mcs.Mcs'tool,
* Mcs.tool-of--Mcs-envt,
* Mcs.McsAeTool,

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,

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 (McsView)

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

name::
* Mcs.conceptual-model--of--structured-concepts,
* Mcs.conceptual-modelAsMcs,
* Mcs.model-of-structured-concepts,
* Mcs.modelConceptualMcs,
* Mcs.modelInfoView.Mcs,
* Mcs.Mcs'view,
* Mcs.Mcs'conceptual-model,
* Mcs.McsAwView,
* Mcs.Mcsm,
* Mcs.Mcsv,
* Mcs.Mcsv-(Mcs-view),
* Mcs.McsView,
* Mcs.view-of-Mcs,

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 (McsWorld)

description::
· Mcs-worldview is a-McsView of an-entity (human, group-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.McsAsWorldview,
* Mcs.Mcs'worldview,
* Mcs.McsViewAsWorldview,
* Mcs.McsWorldview,
* Mcs.McsWorld,
* Mcs.Mcsw,
* Mcs.Mcsw-(Mcs-worldview),
* Mcs.ModelInfoWorldAsMcs,
* Mcs.structured-worldview,
* Mcs.worldview.Mcs,
* Mcs.worldviewAsMcs,

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

generic-chain::
* McsView,
* Mcs,

base of Mcs (McsBase)

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

name::
* Mcs.base-McsView,
* Mcs.Mcs'base,
* Mcs.McsAwBase,
* Mcs.structured-pedia, {2019-01-06}
* Mcs.Mcsb,
* Mcs.Mcsb-(Mcs-base),
* Mcs.McsViewAsBase,

DOING of Mcs

name::
* Mcs.Mcs'doing,

searching Mcs

description::
· any McsHitp can-be-searched DIRECTLY from any other Mcs by clicking on the left search-tab or on the green top bar.

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

to-do::
* {2019-02-02} automatically to search for the-concept's main-name, the-name after (!⇒).

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

WHOLE of McsHitp

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

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,
* Mcs.McsHitp.FileNo,
* Mcs.McsHitpAsfileNo,

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,
* Mcs.Hitp-structured-concept.Paragraph,
* Mcs.McsHitp.P,
* 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.Hitp-structured-concept.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.Hitp-structured-concept.list,
* Mcs.list--Hitp-structured-concept,
* Mcs.list-McsHitpP,
* Mcs.McsHitpP.list,

McsHitp.EVOLUTING

name::
* Mcs.McsHitp.evoluting,

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

Mcs.CHAIN

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.chain-Mcs!⇒McsChain,
* Mcs.decentralized--structured-concept!⇒McsChain,
* Mcs.McsChain,
* Mcs.Mcs.chain!⇒McsChain,
* Mcs.Mcs.decentralized!⇒McsChain,
* Mcs.Đ-Mcs!⇒McsChain,

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
• twitter: @synagonism
• edit on github: https://github.com/synagonism/Mcsw/blob/master/dirCor/filMcs.last.html,

webpage-versions::
• version.last.dynamic: filMcs.last.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