Mcs.structured-concept (Mcs)
(ModelConceptStructured)

Cpt-created: {2017-09-27}

description 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::
* cpt.FilMcs.Last.html,
* cpt.dirCor/FilMcs.Last.html,
* cpt.ModelConceptStructured,
* cpt.ModelConceptStructured-(Mcs),
* cpt.Mcs,
* cpt.Mcs-(ModelConceptStructured),
* cpt.structured-concept,
* cpt.structured-concept-(Mcs),

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

title of Mcs-part

description::
Title-of-Mcs is the most used name of Mcs.

name::
* cpt.Mcs'title,
* cpt.McsApTitle,
* cpt.structured-concept'Title,
* cpt.Mcs-title,
* cpt.title-of-Mcs,

attribute of Mcs (Mcs-Att)

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

name::
* cpt.attribute-of-Mcs,
* cpt.Mcs'attribute,
* cpt.McsAaAttribute,
* cpt.structured-concept'Attribute,
* cpt.Mcs-Att,

Mcs-Att.SPECIFIC-CHAIN

Specific::
* Part-attribute,
* PartNo-attribute,
===
* Inheritedfrom-attribute,
* InheritedfromNo-attribute,
===
* Inheritedto-attribute,
* InheritedtoNo-attribute,
===
* Complement-attribute,
* Definition-attribute,
* Description-attribute,
* Dichotomous-division--attribute,
* Division-attribute,
* Environment-attribute,
* Generic-attribute,
* Generic-chain--attribute,
* Inheritedfrom-attribute,
* InheritedfromNo-attribute,
* Inheritedto-attribute,
* InheritedtoNo-attribute,
* Name-attribute,
* Part-attribute,
* PartNo-attribute,
* Partial-division--attribute,
* Specific-attribute,
* Specific-chain--attribute,
* Specific-division--attribute,
* Whole-attribute,
* Whole-chain--attribute,

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::
* cpt.division-attribute--of-Mcs,
* cpt.Mcs-AttAsDivision,
* cpt.Mcs'division-attribute,

complement-of-division Mcs-Att

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

name::
* cpt.complement-attribute--of-Mcs,
* cpt.Mcs-AttAsComplement,
* cpt.Mcs'complement-attribute,

Mcs-Att.division.SPECIFIC

Specific::
* Dichotomous-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::
* cpt.dichotomous-division--attribute--of-Mcs,
* cpt.divisionDichotomous--attribute--of-Mcs,
* cpt.Mcs-AttAsDichotomous-division,
* cpt.Mcs'dichotomous-division-attribute,

Mcs-Att.PART (internal)

description::
Part--Mcs-Att is an-attribute we view as internal|intrincic to Mcs.

name::
* cpt.externalNo-attribute--of-Mcs,
* cpt.internal-attribute--of-Mcs,
* cpt.intrinsic-attribute--of-Mcs,
* cpt.Mcs'externalNo-attribute,
* cpt.Mcs'internal-attribute,
* cpt.Mcs-AttAsExternalNo,
* cpt.Mcs-AttAsInternal,
* cpt.Mcs-AttAsPart,
* cpt.part-attribute--of-Mcs,

Mcs-Att.description

description::
· description--Mcs-Att is 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::
* cpt.description-attribute--of-Mcs,
* cpt.Mcs-AttAsDescription,
* cpt.Mcs'description-attribute,

Mcs-Att.name (Mcs-name)

description::
Name--Mcs-Att is any entity linguistic (word construct) or not we use to denote a-Mcs.

name::
* cpt.name-of-Mcs-part-att,
* cpt.Mcs-AttAsPart'sName,
* cpt.Mcs-AttAsName,
* cpt.Mcs-AttAsPartAsName,
* cpt.Mcs-AttAsName,
* cpt.Mcs'name,
* cpt.Mcs'name--part-attribute,

naming-convension of Mcs-name

description::
· it is VERY IMPORTANT to be-consistent in 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 xxxAwYyy: yyy is whole of xxx.
* xxx'yyy or xxxAeYyy: yyy is environment 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]
===
* xxx'yyy or xxxAaYyy: yyy is attribute of xxx.
* xxx'pYyy or xxxApYyy: yyy is part of xxx.
* xxx'wYyy or xxxAwYyy: yyy is whole of xxx.
* xxx'eYyy or xxxAeYyy: yyy is environment 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::
* cpt.Mcs'name-notation,
* cpt.Mcs-name'notation,
* cpt.name-notation--of-Mcs,
* cpt.naming-convension--of-Mcs,
* cpt.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}

Mcs-name.SPECIFIC

name::
* cpt.Mcs-name.specific,
* cpt.Mcs-nameAsSpecific,

Specific::
* Formal--Mcs-name,
* FormalNo--Mcs-name,

Mcs-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::
* cpt.formal-Mcs-name,
* cpt.machine-Mcs-name,
* cpt.Mcs-name.formal,
* cpt.Mcs-name.machine,
* cpt.Mcs-nameAsFormal,
* cpt.Mcs-nameAsMachine,

Mcs-name.MachineNo

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

name::
* cpt.formalNo-Mcs-name,
* cpt.machineNo-Mcs-name,
* cpt.Mcs-name.formalNo,
* cpt.Mcs-name.machineNo,
* cpt.Mcs-nameAsFormalNo,
* cpt.Mcs-nameAsMachineNo,

Mcs-Att.definition

description::
· definition--Mcs-Att is 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::
* cpt.definition-attribute--of-Mcs,
* cpt.Mcs-AttAsDefinition,
* cpt.Mcs'definition-attribute,

Mcs-Att.partial-division

description::
Parital-division--Mcs-Att is a-division of the-part-attributes.

name::
* cpt.divisionPartial-attribute--of-Mcs,
* cpt.Mcs-AttAsPartial-division,
* cpt.Mcs'partial-division--attribute,
* cpt.partial-division--attribute--of-Mcs,

Mcs-Att.PART-NO (external)

description::
PartNo--Mcs-Att is the-complement of part-attributes.

name::
* cpt.external-attribute--of-Mcs,
* cpt.extrinsic-attribute--of-Mcs,
* cpt.intrinsicNo-attribute--of-Mcs,
* cpt.Mcs'external-attribute,
* cpt.Mcs'internalNo-attribute,
* cpt.Mcs-AttAsExternal,
* cpt.Mcs-AttAsInternalNo,
* cpt.Mcs-AttAsPartNo,
* cpt.partNo-attribute--of-Mcs,

Mcs-Att.WHOLE

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

name::
* cpt.Mcs'whole-attribute,
* cpt.Mcs-AttAsWhole,
* cpt.whole-attribute--of-Mcs,

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::
* cpt.Mcs'whole-chain--attribute,
* cpt.Mcs-AttAsWhole-chain,
* cpt.whole-chain--attribute--of-Mcs,

Mcs-Att.WHOLE-NO (Environment)

description::
WholeNo--Mcs-Att is a-partNo-att which is not whole of this Mcs.

name::
* cpt.environment-attribute--of-Mcs,
* cpt.Mcs'environment-attribute,
* cpt.Mcs'wholeNo-attribute,
* cpt.Mcs-AttAsEnvironment,
* cpt.Mcs-AttAsWholeNo,
* cpt.wholeNo--Mcs-Att,

Mcs-Att.GENERIC

description::
Generic--Mcs[a]-att is another Mcs[b] whose[b] attributes are and attributes of Mcs[a] but not the-opposite.

name::
* cpt.generic-concept--of-Mcs,
* cpt.generic-attribute--of-Mcs,
* cpt.Mcs-AttAsGeneric,
* cpt.Mcs'generic-attribute,

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::
* cpt.Generic-chain--attribute--of-Mcs,
* cpt.Mcs-AttAsGeneric-chain,
* cpt.Mcs-generic-chain-attribute,

Mcs-Att.SPECIFIC

description::
Specific--Mcs[a]-att 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::
* cpt.specific-attribute--of-Mcs,
* cpt.specific-concept--of-Mcs,
* cpt.Mcs-AttAsSpecific,
* cpt.Mcs'specific-attribute,

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::
* cpt.DivisionSpecific-attribute--of-Mcs,
* cpt.Mcs-AttAsSpecific-division,
* cpt.Mcs-specific-division-attribute,
* cpt.Specific-division--attribute--of-Mcs,

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::
* cpt.specific-chain--attribute--of-Mcs,
* cpt.Mcs-AttAsSpecific-chain,
* cpt.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::
* cpt.inherited-from--attribute--of-Mcs,
* cpt.Mcs-AttAsInheritedfrom,
* cpt.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::
* cpt.inherited-fromNo-attribute--of-Mcs,
* cpt.Mcs-AttAsInheritedfromNo,
* cpt.Mcs'inherited-fromNo--attribute,

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::
* cpt.inherited-to--attribute--of-Mcs,
* cpt.Mcs-AttAsInherited-to,
* cpt.Mcs'inherited-to--attribute,

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::
* cpt.inherited-toNo--attribute--of-Mcs,
* cpt.Mcs-AttAsInherited-toNo,
* cpt.Mcs'inherited-toNo--attribute,

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]

name::
* cpt.archetype-of-Mcs,
* cpt.structured-concept'Archetype,
* cpt.Mcs'archetype,
* cpt.McsAeArchetype,

tool of Mcs-envt

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

name::
* cpt.Mcs'tool,
* cpt.structured-concept'Tool,
* cpt.Tool-of--Mcs-envt,
* cpt.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::
* cpt.Mcs'evaluation,
* cpt.structured-concept'Evaluation,
* cpt.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]

name::
* cpt.monosemanticity-of-Mcs,
* cpt.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::
* cpt.consistency-of-Mcs,
* cpt.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::
* cpt.completeness-of-Mcs,
* cpt.Mcs'completeness,

WHOLE of Mcs

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

name::
* cpt.Mcs'whole-chain,
* cpt.McsAwWhole-chain,
* cpt.structured-concept'Whole-chain,

view of Mcs (Mcsv)

description::
Mcs-view is many structured-concepts that we communicate.

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

Όνομα::
* ενν.Δομημένων-εννοιών--εννοιακό-μοντέλο,
* ενν.Δομημένων-εννοιών--θεώρηση,
* ενν.Εννοιακό-μοντέλο--δομημένων-εννοιών,
* ενν.Θεώρηση--δομημένων-εννοιών,

Specific::
* Directory-Mcsv,
* World-Mcsv,
* Base-Mcsv,

Mcsv.DIRECTORY (Mcsd)

description::
Directory-Mcsv is a-Mcsv that is-stored in a-computer-directory.

name::
* cpt.directory-Mcsv,
* cpt.Mcs'directory,
* cpt.McsAwDirectory,
* cpt.structured-concept'Directory,
* cpt.Mcs-directory,
* cpt.Mcsd,
* cpt.Mcsd-(Mcs-directory),
* cpt.McsvAsDirectory,

Mcsv.WORLDVIEW (Mcsw)

description::
Mcs-worldview is a-Mcsv of an-entity (human, group-of-humans) with ALL their Mcs-views.

name::
* cpt.Mcs'worldview,
* cpt.McsAwWorldview,
* cpt.structured-concept'Worldview,
* cpt.Mcs-worldview,
* cpt.McsvAsWorldview,
* cpt.McsWorldview,
* cpt.Mcsw,
* cpt.Mcsw-(Mcs-worldview),
* cpt.ModelInfoWorldAsMcs,
* cpt.worldview-Mcsv,
* cpt.worldviewAsMcs,

Όνομα::
* ενν.Δομημένων-εννοιών--κοσμοθεώρηση,
* ενν.Κοσμοθεώρηση--δομημένων-εννοιών,

Mcsv.BASE (Mcsb)

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

name::
* cpt.base-Mcsv,
* cpt.Mcs'base,
* cpt.McsAwBase,
* cpt.structured-concept'Base,
* cpt.Mcs-base,
* cpt.Mcsb,
* cpt.Mcsb-(Mcs-base),
* cpt.McsvAsBase,

ENVIRONMENT of Mcs

name::
* cpt.Mcs'environment,
* cpt.McsAeEnvironment,
* cpt.structured-concept'Environment,

Specific::
* Human-concept,

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::
* cpt.human-concept'Relation-to--structured-concept,
* cpt.Mcs'relation-to--human-concept,
* cpt.McsAeRelation-to--human-concept,
* cpt.relation-of--human-concept--to-Mcs,
* cpt.relation-of-Mcs-to--human-concept,
* cpt.structured-concept'Relation-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::
* cpt.entity'relation-to--structured-concept,
* cpt.Mcs'relation-to-entity,
* cpt.McsAeRelation-to-entity,
* cpt.relation-of-entity-to-Mcs,
* cpt.relation-of-Mcs-to-entity,
* cpt.structured-concept'relation-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::
* cpt.Oop'relation-to--structured-concept,
* cpt.Mcs'relation-to-Oop,
* cpt.McsAeRelation-to-Oop,
* cpt.relation-of-Oop-to-Mcs,
* cpt.relation-of-Mcs-to-Oop,
* cpt.structured-concept'relation-to-Oop,

GENERIC of Mcs

Generic-chain::
* Information,
* Model,
* Entity,

name::
* cpt.Mcs'generic-chain,
* cpt.McsAgGeneric-chain,
* cpt.structured-concept'Generic-chain,

Mcs.SPECIFIC

name::
* cpt.Mcs.specific,
* cpt.McsAsSpecific,
* cpt.structured-concept.Specific,

Specific::
* Hitp-Mcs,
* FolioViews-Mcs,
* Đ-Mcs,

Mcs.Hitp (McsHitp)

description::
Hitp-Mcs is a-Mcs written with my Hitp-web-language.
Hitp represents title-content-tree-documents.
A-Hitp-Mcs has as TITLE its main-name and CONTENT an-ordered-list of its attributes which are also Hitp-Mcss.

name::
* cpt.Hitp-Mcs,
* cpt.Hitp--structured-concept,
* cpt.Mcs.Hitp,
* cpt.McsAsHitp,
* cpt.McsHitp,
* cpt.ModelConceptStructuredHitp,
* cpt.structured-concept.Hitp,
* cpt.structured-concept.web,
* cpt.web-Mcs, {2018-02-18}
* cpt.web--structured-concept, {2018-02-18}

WHOLE of McsHitp

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

McsHitp.SPECIFIC

Specific::
* File-McsHitp,
* FileNo-McsHitp,

McsHitp.FILE

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

McsHitp.FILE-NO

name::
* cpt.fileNo-McsHitp,
* cpt.McsHitp.FileNo,
* cpt.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::
* cpt.paragraph-McsHitp,
* cpt.Hitp-structured-concept.Paragraph,
* cpt.McsHitp.P,
* cpt.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::
* cpt.Hitp-structured-concept.Text,
* cpt.text--Hitp-structured-concept,
* cpt.text-McsHitpP,
* cpt.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::
* cpt.Hitp-structured-concept.List,
* cpt.list--Hitp-structured-concept,
* cpt.list-McsHitpP,
* cpt.McsHitpP.List,

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::
* cpt.Dcec-Mcs,
* cpt.decentralized--structured-concept,
* cpt.Mcs.chain,
* cpt.Mcs.decentralized,
* cpt.structured-concept.decentralized,
* cpt.Đ-Mcs,

Mcs.EVOLUTING

name::
* cpt.Mcs.evoluting,
* cpt.McsAsEvoluting,
* cpt.structured-concept.Evoluting,

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

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 "cpt.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