description::
· HitpMcs-language is a-concept-language that maps mind-concepts to HitpMcs.
· the-first application of HitpMcs-lago is my-HitpMcs-WorldView published in the-current site.
· IF this project\a\ will work, THEN it\a\ will-prove that we must-move from TEXTS to CONCEPTS in-order-to manage our knowledge. {2021-11-19}
· the biggest problem of current {2026} AI (LLM) is garbage-in garbage-out\b\: writing structured validated knowledge with McshLago will-help to solve it\b\. {2026-05-03}
name::
* McsEngl.McsTchInf000009.last.html//dirTchInf//dirMcs!⇒McshLago,
* McsEngl.dirMcs/dirTchInf/McsTchInf000009.last.html!⇒McshLago,
* McsEngl.Hitp-concept--language!⇒McshLago,
* McsEngl.Hitp-Mcs--format!⇒McshLago,
* McsEngl.Hitp-Mcs--language!⇒McshLago,
* McsEngl.HitpCpt-language!⇒McshLago,
* McsEngl.HitpMcs-format!⇒McshLago,
* McsEngl.HitpMcs-language!⇒McshLago,
* McsEngl.Mcsh--concept-language!⇒McshLago,
* McsEngl.Mcsh-format!⇒McshLago,
* McsEngl.Mcsh-lag!⇒McshLago,
* McsEngl.Mcsh-lagCnpt!⇒McshLago,
* McsEngl.Mcsh-language!⇒McshLago,
* McsEngl.Mcshl!⇒McshLago,
* McsEngl.McshLago!=HitpMcs-language,
* McsEngl.McshLago!=McsTchInf000009,
* McsEngl.lagCnpt.007-HitpMcs!⇒McshLago,
* McsEngl.lagCnpt.HitpMcs!⇒McshLago,
* McsEngl.lagHcpt!⇒McshLago,
* McsEngl.lagHitpCpt!⇒McshLago,
* McsEngl.lagHitpMcs!⇒McshLago,
* McsEngl.lagHmcs!⇒McshLago,
* McsEngl.lagMcsh!=McshLago,
* McsEngl.lagMcsHitp!=McshLago,
* McsEngl.lagoMcsh!⇒McshLago, {2025-01-27}
name::
* McsEngl.McshLago'user,
description::
· a-human that uses the-language.
description::
· mind-concepts[a] are subjective models of humans environment, constructed by the-mind.
· anything we perceive is a-mind-concept[a].
· mind-concepts have attributes which are also mind-concepts.
· systems of mind-concepts are mind-concepts.
· mind-concepts are-NOT the-units of information.
· information|knowledge is mind-concepts.
· human-languages have rules to give them[a] names.
· human-languages map mind-concepts into logo-(text|speech).
· logos are whole-part-systems of sentences which map relations or doings of mind-concepts and describe attributes of mind-concepts.
· the-semantic-units of sentences are names of semo-concepts.
name::
* McsEngl.McshLago'input,
description::
· the-output of McshLago is a-HitpDoc that denotes an-Mcs.
· it is also a-webpage and a-webapp.
· I call it HitpMcs, HitpMcs, Mcsh, McshApp.
· a-HitpMcs is a-model of a-mind-concept.
· it is-written in Html, Css, and JavaScript code.
name::
* McsEngl.McshApp!=output-of-McshLago,
* McsEngl.McshDoc!⇒McshApp,
* McsEngl.McshLago'output!⇒McshApp,
* McsEngl.McshWebApp!⇒McshApp,
description::
· HitpMcs is an-Mcs written with my McshLago-web-language.
· the current concept (McshLago) is an-HitpMcs.
name::
* McsEngl.Hitp--sensorial-concept!⇒Mcsh,
* McsEngl.Hitp-Mcs!⇒Mcsh,
* McsEngl.Hitp-concept!⇒Mcsh,
* McsEngl.Hitp-cpt!⇒Mcsh,
* McsEngl.Hitp-sensorial-concept!⇒Mcsh,
* McsEngl.HitpMcs!⇒Mcsh,
* McsEngl.Hitppage.sensorial-concept!⇒Mcsh,
* McsEngl.Hmcs!⇒Mcsh, {2021-03-10},
* McsEngl.Mcs.Hitp!⇒Mcsh,
* McsEngl.Mcs.web!⇒Mcsh,
* McsEngl.McsAsHitp!⇒Mcsh,
* McsEngl.Mcsh!=Hitp-Mcs, {2021-03-22}
* McsEngl.McshApp'Mcs!⇒Mcsh,
* McsEngl.mcsHitp!⇒Mcsh,
* McsEngl.mcsHtml.Hitp!⇒Mcsh,
* McsEngl.modelConceptStructuredHitp!⇒Mcsh,
* McsEngl.sensorial-concept.Hitp!⇒Mcsh,
* McsEngl.web-Mcs!⇒Mcsh, {2018-02-18},
* McsEngl.web--sensorial-concept!⇒Mcsh, {2018-02-18},
description::
× HitpMcs-creation: {2025-06-05},
· the-languages of names that are-indexed:
name::
* McsEngl.Mcsh'language-of-names,
* McsEngl.Mcsh'name-language,
* McsEngl.McshLago'language-of-names,
* McsEngl.name-language--of-McshLago,
description::
· any type of data used.
description::
* list-data,
* name-value-data,
* table-data,
* text-data,
* time-data,
* tree-data,
description::
· all sentences begin with char.183'·'.
· if text is a-quotation, it is-enclosed with char.34'"' and contains its source.
name::
* McsEngl.McshText,
* McsEngl.Mcsh'data.text!⇒McshText,
* McsEngl.Mcsh'text-data!⇒McshText,
name::
* McsEngl.McshTime,
* McsEngl.Mcsh'data.time!⇒McshTime,
* McsEngl.Mcsh'time-data!⇒McshTime,
description::
· the-items of a-list begin with char.42'*'.
name::
* McsEngl.McshList,
* McsEngl.Mcsh'array-data!⇒McshList,
* McsEngl.Mcsh'data.list!⇒McshList,
* McsEngl.Mcsh'list-data!⇒McshList,
description::
· name-value-data begin with char.215'×'.
× aType: [string, object]
× bRequired: true
× nSince: 2.0
× sParent: root
[hmnSngo.{2020-12-28}]
name::
* McsEngl.McshNvd!=name-value-data--of-Mcsh,
* McsEngl.Mcsh'data.name-value!⇒McshNvd,
* McsEngl.Mcsh'name-value-data!⇒McshNvd,
description::
· example:
<div id="idTable">
<p>table-title::
</p>
<table>
<tr>
<td>row11</td>
<td>row12</td>
</tr>
<tr>
<td>row21</td>
<td>row22</td>
</tr>
</table>
<a class="clsHide" href="#idTable"></a></div>
name::
* McsEngl.McshTable,
* McsEngl.Mcsh'data.table!⇒McshTable,
* McsEngl.Mcsh'table-data!⇒McshTable,
description::
· see McshLago'evoluting.
name::
* McsEngl.evoluting-of-Mcsh,
* McsEngl.Mcsh'evoluting,
description::
· a-mcshFile is a-HitpMcs which is a-webpage.
· the current Mcs is an-example of an-mcshFile.
name::
* McsEngl.Mcsh-file!⇒mcshFile,
* McsEngl.McshAsfile!⇒mcshFile,
* McshFile, {2021-03-24},
* McsEngl.McshHeader!⇒mcshFile,
* McsEngl.Mcsh.Header!⇒mcshFile,
* McsEngl.Mcsh.File!⇒mcshFile,
* McsEngl.mcshFile, {2025-08-09}
* McsEngl.filMcs!⇒mcshFile,
* McsEngl.file-Mcsh!⇒mcshFile,
* McsEngl.header-Mcsh!⇒mcshFile,
* McsEngl.webpage-Mcsh!⇒mcshFile,
description::
· mcshFile-title is a-header-Html-element which includes a-h1-element with the-text of the-title.
name::
* McsEngl.mcshFile'att001-title,
* McsEngl.mcshFile'title,
* McsEngl.title-of-mcshFile,
description::
· relative: McsTchInf000009.last.html,
· absolute: https://synagonism.net/dirMcs/dirTechInf/McsTchInf000009.last.html,
· IF we name them as filMcs000000.last.html, THEN we can-change its main-name without changing its file-name.
· also this way we can-store 1-million file-concepts per directory or using and a-letter eg filMcsA000000.last.html, 26 millions. {2021-03-28}.
name::
* McsEngl.mcshFile'att002-file-name,
* McsEngl.mcshFile'file-name,
description::
× HitpMcs-creation: {2026-04-29},
· non File HitpMcs.
name::
* McsEngl.fileNo-Mcsh!⇒mcshFileNo,
* McsEngl.Mcsh.FileNo!⇒mcshFileNo,
* McsEngl.McshAsfileNo!⇒mcshFileNo,
* McshFileNo, {2019-03-07},
* McsEngl.mcshFileNo, {2025-08-09}
specific::
* section-HitpMcs,
** H1-HitpMcs,
** H2-HitpMcs,
** H3-HitpMcs,
** H4-HitpMcs,
** H5-HitpMcs,
** H6-HitpMcs,
* P-HitpMcs,
description::
· an-McsHitpSection uses the-section-Html-element and one of its H1...H6-heading-elements.
· the-current-Mcs is an-McsHitpSectionH3.
· the-text of its heading-element contains its title.
· the-whole-concept is-stored inside the-heading-element.
· the-first inner-elements are the-paragraph-Html-elements description and name.
name::
* McsEngl.Mcsh.001-section!⇒mcshSection,
* McsEngl.Mcsh.section!⇒mcshSection,
* McsEngl.mcshSection, {2025-08-09}
* McsEngl.section-Mcsh!⇒mcshSection,
description::
· there-are 2 types of mcshP:
* a-text mcshP and
* a-list mcshP,
[hmnSngo.2017-12-17]
name::
* McsEngl.paragraph-Mcsh!⇒mcshP,
* McsEngl.Mcsh.paragraph!⇒mcshP,
* McsEngl.Mcsh.P!⇒mcshP,
* McsEngl.mcshFileNo.paragraph!⇒mcshP,
* McsEngl.mcshP, {2025-08-09}
description::
· the-title of a-mcshP ends with '::'
name::
* McsEngl.mcshP'att001-title,
* McsEngl.mcshP'title,
* McsEngl.title-of-mcshP,
description::
· after the-title, I put one or more names as:
* McsLag4.name,
· since {2020-10-18} these names are-indexed with the-Mcsh'manager.
name::
* McsEngl.mcshP'att002-name,
* McsEngl.mcshP'name,
* McsEngl.name-of-mcshP,
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.
[hmnSngo.2017-12-17]
name::
* McsEngl.Mcsh.text,
* McsEngl.text--Hitp-sensorial-concept,
* McsEngl.text-mcshP,
* McsEngl.mcshP.text,
* McsEngl.mcshPText,
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.
[hmnSngo.2017-12-17]
name::
* McsEngl.Mcsh.list,
* McsEngl.list--Hitp-sensorial-concept,
* McsEngl.list-mcshP,
* McsEngl.mcshP.list,
* McsEngl.mcshPList,
description::
× HitpMcs-creation: {2025-08-09},
· FolioViews-Mcsh is an-Hitp-Mcs converted from FolioViews-Mcs.
· address:
name::
* McsEngl.FolioViews-Mcsh,
* McsEngl.FolioViewsMcsh,
* McsEngl.Mcsh.FolioViews,
* McsEngl.McshFolioViews,
* McsEngl.mcshFv,
description::
· a-system of HitpMcs.
name::
* McsEngl.Mcsh'view!⇒McshView,
* McsEngl.Mcsh-view!⇒McshView,
* McsEngl.McshApp'view!⇒McshView,
* McsEngl.McshView,
* McsEngl.McshLago'output-view!⇒McshView,
* McsEngl.view.Mcsh!⇒McshView,
description::
· the-outermost and generic-most HitpMcs of ONE user.
name::
* McsEngl.Mcsh'WorldView!⇒McshWorldView,
* McsEngl.Mcsh-WorldView!⇒McshWorldView,
* McsEngl.McshApp'WorldView!⇒McshWorldView,
* McsEngl.McshWorldView,
* McsEngl.Mcshwview!⇒McshWorldView,
* McsEngl.McshLago'output-WorldView!⇒McshWorldView,
* McsEngl.WorldView.Mcsh!⇒McshWorldView,
specific-tree-of-McshWorldView::
* modelWorldSynagonism,
description::
· the-set of HitpMcs-WorldViews mapped.
name::
* McsEngl.Mcsh'baseview!⇒McshBase,
* McsEngl.Mcsh-baseview!⇒McshBase,
* McsEngl.McshApp'base!⇒McshBase,
* McsEngl.Mcshbview!⇒McshBase,
* McsEngl.McshBase,
* McsEngl.baseMcsh!⇒McshBase,
* McsEngl.baseview.Mcsh!⇒McshBase,
* McsEngl.McshLago'output-baseview!⇒McshBase,
description::
× HitpMcs-creation: {2025-10-14},
· McshApp, the-output of McshLago, is an-app and it has functions:
* search the-names of its texts.
* find the-codepoints of its characters.
* double-clicking selects names, not words, and query them.
* includes other sub-apps with various functions.
· McshManager includes the-above functions and has more from additional programs.
name::
* McsEngl.McshApp'doing,
description::
× HitpMcs-creation: {2025-10-21},
· McshApp-command I call the-functions on its Menu.
name::
* McsEngl.McshApp'command!⇒McshCmnd,
* McsEngl.McshApp-command!⇒McshCmnd,
* McsEngl.McshCmnd!=McshApp'command,
description::
× HitpMcs-creation: {2025-10-22},
· McshManager indexes the-names of concepts of McshFiles.
· name-search-command searches these indexes and suggest names and preview the-first suggestion.
name::
* McsEngl.McshApp'name-search-command,
* McsEngl.McshCmnd.name-search-command,
* McsEngl.name-search-command-in-McshApp,
description::
× HitpMcs-creation: {2025-10-21},
· DoubleClicking on content, selects the-clicked NAME\a\, not word, query it\a\, and preview the-first suggestion.
· if http is-clicked, it opens this address in a-new tab.
· the-language on which searches, is the-one selected in the-search-tab.
· we can-change the-language and after clicking, but selected first the-language the-process is faster.
· double-click selects the-name to THE-RIGHT of clicking word.
name::
* McsEngl.DoublClicking-in-McshApp,
* McsEngl.McshApp'DoublClicking,
* McsEngl.McshCmnd.DoublClicking,
description::
× HitpMcs-creation: {2025-10-22},
· query-selection-command queries the-selection and preview the-first suggestion.
· if http-address is-selected, it opens this address in a-new tab.
· Ctrl+q does also the-same command.
name::
* McsEngl.McshApp'query-selection,
* McsEngl.McshCmnd.query-selection,
* McsEngl.query-selection-command-in-McshApp,
description::
× HitpMcs-creation: {2025-10-22},
· selection-codepoints-command displays the-Unicode-codepoints of the-selected characters in my site.
· Ctrl+0 is its shortcut.
name::
* McsEngl.McshApp'selection-codepoints,
* McsEngl.McshCmnd.selection-codepoints,
* McsEngl.selection-codepoints-command-in-McshApp,
description::
× HitpMcs-creation: {2025-05-24},
· McshSite is a-website with McshApps.
name::
* McsEngl.McshLago'site!⇒McshSite,
* McsEngl.McshSite!=website-with-McshApps,
description::
× HitpMcs-creation: {2025-05-25},
* root-server-directory
** configMcs.json
** dirMcs: root McshSite dir
*** namidx.txt: contains McshDocs to index
*** oMcs_Hash.json: contains the-hashes of last McshDocs automatically
*** sftp.json: contains the-changed files to upload automatically
*** dirSubjectA: contains McshDocs on subjectA
**** McshSbjA000.files: dir with extra files of McshDoc
**** McshSbjA000.last.html: McshDoc-html-file
*** dirSubjectB: contains McshDocs on subjectB
*** ...
*** Mcsmgr: dir for all needed files except NamIdx-files
**** fileFntUbuntuMonoRegular.ttf: for McshCss
**** fileIcnFa463.woff2: for McshCss
**** mHitp.css: for McshCss
**** mMcsh.js: for McshJsb
**** mNamidx.mjs: create McshName-indexes locally
**** mSftp.mjs: uploads changed files
**** mUtil.mjs: utils on creating
**** mWatch.mjs: watch for changes, create indexes and uploads
*** dirNamidx: NamIdx-files.
**** namidx.lagRoot.json: the-languages and the-indexes of them.
**** dirLagNam1: dir of namidx-files of lagNam1.
***** namidx.lagNam100.json: McshNames that begin on 'other' chars.
***** namidx.lagNam101.json: McshNames that begin with char-01.
***** namidx.lagNam102_0.json
***** namidx.lagNam102_1.json
**** dirLagNam2
description::
× HitpMcs-creation: {2025-05-25},
·
name::
* McsEngl.McsDir!=directory-of-McshSite,
* McsEngl.McshSite'directory!⇒McshDir,
description::
× HitpMcs-creation: {2025-05-25},
· http-server root directory.
· contains configMcs.json and dirMcs.
description::
· base-dir is the-directory that holds the-knowledge-base-(the-set of WorldViews).
· dirMcs//website.
· website/dirMcs.
· old-name: dirMiwMcs.
name::
* McsEngl.McshDir.base,
* McsEngl.McshDir.root,
* McsEngl.base-dir-of-McshMngr,
* McsEngl.dirMcs,
* McsEngl.dirMcsh,
description::
× HitpMcs-creation: {2025-05-25},
· McshApp-html-files are-stuctured per subject-dirs.
· also these subject-dirs contain and the-directories of McshApp-html-files\a\ that contain extra files of them\a\.
description::
× HitpMcs-creation: {2025-05-25},
· contains all the-extra files needed to run the-site except namidx-files and configMcs.json.
description::
× HitpMcs-creation: {2025-05-25},
× whole: McshManager,
· contains:
- namidx.lagRoot.json file,
- dirLagLlll directories of languages which contain
- namidx.lagLlll00.json files
name::
* McsEngl.McshDir.namidx,
* McsEngl.dirNamidx-of-McshSite,
description::
· HitpMcs-manager is the-Mcs-manager we need to manage HitpMcs-language.
· with HitpMcs-manager I have online Html-Mcs on any browser with many advantanges.
· but I need the-Wysiwyg-editor I had in HtmlMgr and the great functions I had in AAj.
· {2026} I changed editing HitpMcs-files from jEdit to Visual-Studio-Code.
· now, I'm using Vscode extensions, keybindings, and tasks to automate my work.
· today {2024} I manage my HitpMcs-site as:
* I have my site locally in C:\xampp\htdocs\dWstSgm\dirMcs
* I open the-terminal and go to dirMcs
* I run 'node Mcsmgr/mWatch.mjs pwd'
* I open my site locally on browser: http://localhost/dWstSgm/dirMcs/Mcs000000.last.html
* I made changes in my editor (jEdit) and automatically updated online, on file save.
* when I feel important, I update my github repo.
name::
* McsEngl.KnlgMngr.027-HitpMcs!⇒McshMngr,
* McsEngl.KnlgMngr.HitpMcs!⇒McshMngr,
* McsEngl.HitpMcs-manager!⇒McshMngr,
* McsEngl.Mcsh'manager!⇒McshMngr,
* McsEngl.Mcsh-manager!⇒McshMngr,
* McsEngl.Mcshlmgr!⇒McshMngr, {2023-11-02},
* McsEngl.McshManager!⇒McshMngr,
* McsEngl.Mcsmgr.Hitp!⇒McshMngr,
* McsEngl.McsmgrHitp!⇒McshMngr,
* McsEngl.Mcshmgr!⇒McshMngr, {2021-11-08},
* McsEngl.McshMgr!⇒McshMngr, {2025-01-28}
* McsEngl.McshMngr!=HitpMcs-language--manager, {2025-05-24}
* McsEngl.McshLago'manager!⇒McshMngr,
* McsEngl.Mhlm!=HitpMcs-Language--Manager!⇒McshMngr,
generic-tree-of-McshMngr::
* Hitp-manager,
description::
┬ WebSite/
├── aPages.json,
├── configMcs.json,
└─┬ dirMcs/
├── Mcsqnt.root.json,
├── Mcs000000.last.html,
├─┬ dirVIEW/
│ ├── Mcsqnt.json,
│ └── McsView000000.last.html,
├─┬ dirNamidx/
│ ├─┬ dirLang/
│ │ └── namidx.lagSPEC.json,
│ ├── abbreviation.html,
│ └── namidx.lagRoot.json,
└─┬ Mcsmgr/
├── mWatch.mjs,
├── mNamidx.mjs,
├── mNamidxFile.mjs,
├── mSftp.mjs,
├── mMcsNew.mjs,
├── validator.js,
├── namidx.txt,
└── sftp.json,
name::
* McsEngl.McshMngr'dir!⇒McshMngrDir,
* McsEngl.McshMngrDir,
description::
· any file the-system uses
name::
* McsEngl.McshMngr'file!⇒McshMngrFile,
* McsEngl.McshMngrFile,
* McsEngl.McshMngrFile!=McshMngr'file,
specific-tree-of-McshMngrFile::
* McsView000000.last.html,
* mMcsh.js//Mcsmgr//dirMcs,
* mHitp.css//Mcsmgr//dirMcs,
* namidx.lagRoot.json//dirNamidx//dirMcs,
* Mcs000000.last.html//dirMcs,
* namdix.mjs//Mcsmgr//dirMcs,
* namdix.txt//dirMcs,
* mSftp.mjs//Mcsmgr//dirMcs,
description::
· name-index-files are array-json-files that contain INDICES of the-names of sensorial-concepts, orderd per Unicode-code-point, per language.
· each name is an-array of the-name AND the-Url of the-concept with this name.
[
[";lagEngl01ei","A..B",2032,"2021-11-08"],
["AA@EuvocStat","dirStn/McsStn000020.last.html#idEuoStatglsrAA"],
...
]
name::
* McsEngl.McshMngrFile.namidx.lag.json!⇒McshIndexFile,
* McsEngl.McshIndexFile,
* McsEngl.index-file-of-McshLago!⇒McshIndexFile,
* McsEngl.name-Url-Mcshfile!⇒McshIndexFile,
* McsEngl.name-index-content-file!⇒McshIndexFile,
* McsEngl.name-index-json-file!⇒McshIndexFile,
* McsEngl.name-index-name-Url-file!⇒McshIndexFile,
* McsEngl.name-index-lag-McshMngrFile!⇒McshIndexFile,
* McsEngl.namidx.content-McshMngrFile!⇒McshIndexFile,
* McsEngl.namidx.json-McshMngrFile!⇒McshIndexFile,
* McsEngl.namidx.name-Url-McshMngrFile!⇒McshIndexFile,
* McsEngl.namidx.lag.json-file!⇒McshIndexFile,
* McsEngl.namidx.lag-McshMngrFile!⇒McshIndexFile,
* McsEngl.namidx-file//McshMngr!⇒McshIndexFile,
* McsEngl.namidx-json-file//McshMngr!⇒McshIndexFile,
* McsEngl.namidxjson-McshMngrFile!⇒McshIndexFile,
specific-tree-of-McshIndexFile::
* reference-McshIndexFile,
* referenceNo-McshIndexFile,
description::
· a-reference-namidx.lag-file does-not-contain names-of-Mcs but references to other namind-files.
· when a-namind-file is too big, takes long time to be-downloaded.
· then we divide it to smaller easily downloaded files and the-original file is-becoming a-reference-file.
· the-name of a-reference-namind-file ends in 'namidx.lag..._0.json'.
· the-first element contain info about the-file:
a) the-name of the-file,
b) names from (included) to (not included),
c) quantity of names,
d) date,
e) comment.
[
[";lagEngl03si_2_0",";char..chas",163141,"2021-03-25","codepoint order"],
["lagEng03si_2_1","char..char.2",11366],
["lagEng03si_2_2","char.2..char.7",11973],
["lagEng03si_2_3","char.7..char.Α",8939],
...
["lagEng03si_2_14","char.n..chas",18303]
]
name::
* McsEngl.McshIndexFile.reference,
* McsEngl.McshMngrFile.namidx.lagSPEC.reference,
* McsEngl.McshIndexRefrFile,
* McsEngl.lagHitp'namidx.lag-file.reference,
* McsEngl.lagHitp'reference-namind.lag-file,
* McsEngl.namidx.lagSPEC.reference-McshMngrFile,
* McsEngl.reference-namidx.lag-McshMngrFile,
description::
· a-referenceNo-namidx.lag-file is a-json-file that contains ordered names-of-Mcs, per codepoint, and their addresses.
· all languages have and the-namidx.lagLang00.json file which contains the-names that begin without a-letter of that language.
· the-first element contain info about the-file:
a) the-name of the-file,
b) names from (included) to (not included),
c) quantity of names,
d) date.
[
[";lagEngl01ei",";A..B",1723,"2021-03-25"],
["AA!/EuvocStat","dirStn/McsStn000020.last.html#idEuoStatglsrAA"],
["AAj!⇒McsmgrAAj","dirCor/McsCor000002.last.html#idMcsmAaj"],
...
]
name::
* McsEngl.McshMngrFile.namidx.lagSPEC.referenceNo,
* McsEngl.McshIndexFile.referenceNo,
* McsEngl.McshIndexRefrNoFile,
* McsEngl.lagHitp'namidx.lag-file.referenceNo,
* McsEngl.lagHitp'referenceNo-namind.lag-file,
* McsEngl.namidx.lagSPEC.referenceNo-McshMngrFile,
* McsEngl.referenceNo-namidx.lag-McshMngrFile,
description::
· the-names of concepts are-indexed.
· they are-stored in files hierarchically.
· namidx.lagRoot.json contains the-root-files from ALL languages.
· for each language, the-root files are its letter files.
· also all languages have and the-namidx.lagLang00.json file which contains the-names that begin without a-letter of that language.
· as time passes, these files are-divided into smaller easily
downloaded files, creating a-tree-structure by creating one reference and two or more referenceNo namidx.lag-files.
· also contains the-quantity of names per letter, per language.
× sPath: namidx.lagRoot.json//dirNamidx//dirMcs,
× sContent:
[
[";lagAGGR",";letter",256492,"2021-03-25","per letter"],
["lagElln",";Greek",4256],
["lagElln00","letterNo",0],
["lagElln01alfa","Α",527],
["lagElln02vita","Β",51],
["lagElln03yama","Γ",99],
...
["lagEngl",";English",252236],
["lagEngl00","letterNo",489],
["lagEngl01ei","A",1723],
["lagEngl02bi","B",1881],
...
["lagSngo",";Sinago",403],
["lagSngo00","letterNo",0],
["lagSngo01po","P",0],
["lagSngo02fo","F",0],
["lagSngo03tho","Θ",0],
...
]
name::
* McsEngl.McshMngrFile.namidx.lagRoot.json,
* McsEngl.McshIndexFile.lagRoot,
* McsEngl.McshIndexRootFile,
* McsEngl.namidx.lagRoot.json-McshMngrFile,
description::
· dirMcs/namidx.txt is a-text-file that contains the-names of the-concept-files to be-indexed and the-language on which to work.
· with mWatch.mjs, this process is-automated: on any change in an-HitpMcs-file, it is-reidexed and uploaded.
// COMMENT the-lines with '//'
//lagAGGR;all-languages
lagEngl;English
//lagElln;Greek
//lagSngo;Sinago
//
//dirCor/McsCor000000.last.html
dirCor/McsCor000002.last.html
name::
* McsEngl.McshMngrFile.namidx.txt,
* McsEngl.McshIndexFiletxt,
* McsEngl.namidx.txt-McshMngrFile,
description::
× HitpMcs-creation: {2025-09-27},
· mMcsh.js contains the-JavaScript code of an-McshDoc.
name::
* McsEngl.McshMngrFile.mMcsh.js!⇒mMcshjs,
* McsEngl.mMcsh.js!⇒mMcshjs,
* McsEngl.mMcshjs,
description::
× HitpMcs-creation: {2025-09-27},
· the-main containers are:
1) top: contains the-title and icons.
2) main: the-content and info of the-page.
3) menu: left menu container.
4) width: right width container.
5) preview: preview info.
name::
* McsEngl.mMcshjs'container!⇒McshCntr,
* McsEngl.McshCntr!=container-of-mMcshjs,
description::
× HitpMcs-creation: {2025-09-27},
· it is a-div-html-element and contains the menu, home, title, search, and width subcontainers.
· name: oEltCnrTopDiv//oEltBody.
· subcontainers: oEltCnrTopTitleP, oEltCnrTopWidthIcnI, oEltCnrTopHomeIcnI, oEltCnrTopSearchIcnI, oEltCnrTopMenuIcnI.
name::
* McsEngl.McshCntr.top,
* McsEngl.oEltCnrTopDiv//oEltBody,
description::
× HitpMcs-creation: {2025-09-27},
· it is a-div-html and contains the-main webpage content and info subcontainers.
· name: oEltCnrMainDiv//oEltBody.
description::
× HitpMcs-creation: {2025-09-27},
·
name::
* McsEngl.McshCntr.main.content,
* McsEngl.McshCntr.content,
description::
× HitpMcs-creation: {2025-09-27},
· name: oEltCnrMainInfoDiv//oEltCnrMainDiv//oEltBody.
name::
* McsEngl.McshCntr.main.info!⇒mcshcntrInfo,
* McsEngl.McshCntr.info!⇒mcshcntrInfo,
* McsEngl.mcshcntrInfo!=info-container-of-mMcsh.js,
* McsEngl.oEltCnrMainInfoDiv!⇒mcshcntrInfo,
description::
× HitpMcs-creation: {2025-09-27},
· //oEltCnrMainInfoDiv//oEltCnrMainDiv//oEltBody.
description::
× HitpMcs-creation: {2025-09-27},
· //oEltCnrMainInfoDiv//oEltCnrMainDiv//oEltBody.
description::
× HitpMcs-creation: {2025-09-27},
· oEltTabContentDiv//oEltCnrMainInfoDiv//oEltCnrMainDiv//oEltBody.
name::
* McsEngl.mcshcntrInfo.oEltTabContentDiv,
description::
× HitpMcs-creation: {2025-09-27},
· oEltTabTocDiv//oEltTabContentDiv//oEltCnrMainInfoDiv//oEltCnrMainDiv//oEltBody.
name::
* McsEngl.mcshcntrInfo.TabContent.Toc,
* McsEngl.oEltTabTocDiv,
description::
× HitpMcs-creation: {2025-09-27},
· oEltTabSearchDiv//oEltTabContentDiv//oEltCnrMainInfoDiv//oEltCnrMainDiv//oEltBody.
name::
* McsEngl.mcshcntrInfo.TabContent.Search,
* McsEngl.oEltTabSearchDiv,
description::
× HitpMcs-creation: {2025-09-27},
· name: oEltCnrPreviewDiv//oEltBody.
description::
· mNamidx.mjs is a-Node.js-program that creates the-name-index-files of HitpMcs-files in dirMcs/namidx.txt and uploads the-changed files.
× RUN: dirMcs> node Mcsmgr/mNamidx.mjs pwd ALONE,
name::
* McsEngl.McshMngrFile.mNamidx.mjs,
* McsEngl.McshIndexFilemjs,
* McsEngl.McshMngr'mNamidx.mjs,
* McsEngl.mNamidx.mjs-McshMngrFile,
* McsEngl.mNamidx.mjs//Mcsmgr//dirMcs,
addressWpg::
* dirMcs/Mcsmgr/mNamidx.mjs,
* https://github.com/synagonism/McsWorld/blob/master/dirMcs/Mcsmgr/mNamidx.mjs,
algo::
* reads the-McsHitpFiles to be-indexed and the-languages to work-with from namidx.txt,
* reads the-root namidx-lag-files and the-quantity of names of concepts from namidx.lagRoot.json.
* create oNamidxRoot with {file : index}.
* for each[a] McsHitpFile, for each language
- REMOVE the-names of this file[a], from ALL namidx.lag-files,
- READ the-file[a] and store temporarilly its name-Urls,
- ADD the name-Urls in namidx.lag-files.
issue::
* names:
- they must not contain \ " tab, we use " \ instead.
* McsEngl.HitpLago'problem-on-names,
* McsEngl.McshLago'problem-on-names,
* McsEngl.problem-on-names--of-McshLago|lagHitp,
structure::
* aFileMcsIn: Mcs-files to reindex,
* aLagALL: the-languages on which to create indexes,
* aMcsQnt: Mcs-files with quantity of Mcs,
* oSetFileUp: changed locally files we want to upload,
* oFileNijRoot_Letter: root-namidx-files with letters of stored names,
* oNamidxjsonNamUrl,
* oNamidxQntnam: namidx and quantity of names that contain,
* fCreateOFileNij_Index(aIn),
* fRemoveNamUrl,
* fStoreNULetter,
* fStoreNUCodepoint,
* fRemoveArrayDupl,
* fWriteJsonQuantDate,
* fDateYMD,
* fWriteJsonArray,
* fCompare,
* fObjvalRKey,
* fComputeQntName,
* fComputeQntMcs,
description::
· it returns the-current-date as yyyy-mm-dd.
name::
* McsEngl.fDateYMD//mNamidx.mjs//McshMngr,
* McsEngl.mNamidx.mjs/fDateYMD,
description::
· DOING: it removes the-name-Urls from namidx-files per language
· INPUT:
- oFilenamidxIndexIn: object {lagElln01alfa: 'Α'} with the-namidx-files from which the-names will-be-removed
- sFilMcsRmvIn: the-Mcsfile whose names will-be-removed
- sLagIn: the-lag whose names will-be-removed
name::
* McsEngl.fRemoveNamUrl//mNamidx.mjs//McshMngr,
* McsEngl.mNamidx.mjs/fRemoveNamUrl,
description::
· mSftp.mjs is a-Node.js-program that sftp the modified local-files to a-remote-site.
· mNamidx.mjs outputs the-sftp.txt-file with the modified local-files.
× sPath: mSftp.mjs//Mcsmgr//dirMcs,
name::
* McsEngl.McshMngrFile.mSftp.mjs,
* McsEngl.McshMngr'mSftp.mjs,
* McsEngl.mSftp.mjs//Mcsmgr//dirMcs,
addressWpg::
* dirMcs/Mcsmgr/mSftp.mjs,
* https://github.com/synagonism/McsWorld/blob/master/dirMcs/Mcsmgr/mSftp.mjs,
description::
· mWatch.mjs watches for file changes, creates name-indices, and uploads the-files.
· to change the-languages on index-creation, we change the-variable aLagALL in mNamidx.mjs.
× RUN: dirMcs> node Mcsmgr/mWatch.mjs pwd
name::
* McsEngl.McshMngrFile.mWatch.mjs,
* McsEngl.McshMngr'mWatch.mjs,
* McsEngl.dirMcs/Mcsmgr/mWatch.mjs,
* McsEngl.mWatch.mjs//Mcsmgr//dirMcs,
addressWpg::
* dirMcs/Mcsmgr/mWatch.mjs,
* https://github.com/synagonism/McsWorld/blob/master/dirMcs/Mcsmgr/mWatch.mjs,
description::
· mMcsNew.mjs creates a-new HitpMcs-file.
- updates aPages.json
- creates McsDir000000.txt
- indexes new file
- uploads new and modified files
× RUN: node Mcsmgr\mMcsNew.mjs pwd
name::
* McsEngl.McshMngrFile.mMcsNew.mjs,
* McsEngl.McshMngr'mMcsNew.mjs,
* McsEngl.dirMcs/Mcsmgr/mMcsNew.mjs,
* McsEngl.mMcsNew.mjs//Mcsmgr//dirMcs,
addressWpg::
* dirMcs/Mcsmgr/mMcsNew.mjs,
description::
· sftp.json is a-json-file that contains a-json-array of the-files we have to upload because we have-changed them locally.
· this file is-created automatically with mNamidx.mjs when we reindex the-changed Mcs-files.
name::
* McsEngl.McshMngrFile.sftp.json,
* McsEngl.sftp.json-McshMngrFile,
description::
· cptqnt-McshMngrFiles are files that contain the-quantity of sensorial-concepts of a-WorldView.
name::
* McsEngl.McshMngrFile.cptqnt,
* McsEngl.cptqnt-McshMngrFile,
description::
× HitpMcs-creation: {2026-04-29},
· on {2026-04} I switched editing from jEdit to VSCode.
· my project tasks.json.
· my user keybindings.json,
· my user-input-extension that asks for user input in keybindings.json.
name::
* McsEngl.McshMngr'VSCode!⇒McshVscode,
* McsEngl.McshMngr'Visual-Studio-Code!⇒McshVscode,
* McsEngl.McshVscode!=McshMngr'Visual-Studio-Code,
description::
* Alt+F2: search for Chinese names.
* Ctrl+F2: search for Greek names.
* Ctrl+0: displays the-codepoint of selected character.
* F2: search for English names.
* Shift+F2: search for Sinago names.
description::
· any tech (machine, tool) used.
· web-browser, viewer of concepts.
· Visual-Studio-Code, editor.
· NodeJs, editor utilities.
· LLM, validator.
name::
* McsEngl.McshMngr'doing,
generic-tree-of-McshMngr'doing::
* Mcsmgr'doing,
description::
* my most needed tool is the-manager of classification-trees: generic-specific, whole-part, parent-child.
* a-WYSIWYG editor.
* search: if CONTAINS '.*' to do regular-expression search on names that begin with whatever entered eg 'verbEnglC.*fought' to search for 'fought' inside the-names begining with 'verbEnglC'. {2023-07-17}.
* Ctrl+Q: to query the-highlighted text. {2025-08-28}
=== DONE:
* hitp.js: to be-organized in modules. {2021-04-01} {done.2021-05-02},
* mcshFile-name: from filMcsName.last.html to filMcs000000.last.html. {2021-03-31} {done.2021-04-28}.
* Mcs-name: from * Mcs.name, to * McsEngl.name, so all names have the-same format: * McsLang.name, {2021-03-30} {done}.
name::
* McsEngl.McshMngr'todo,
* McsEngl.McshLago'todo,
* McsEngl.todo.McshMngr,
* McsEngl.todo.McshLago,
description::
· searching for ANY HitpMcs from anywhere in the-base, is the-notable function of my McshMngr.
· the-manager creates indexes of the-names of the-concepts with its related addresses with the-mNamidx.mjs-program.
· these namidx.lag-files are-stored in dirLANG//dirNamidx//dirMcs.
· PROBLEMS.
name::
* McsEngl.McshSearching,
* McsEngl.McshlSearching,
* McsEngl.McshMngr'searching,
* McsEngl.McshLago'searching,
* McsEngl.searching-of-McshMngr,
description::
· when an-referenceNo-index-file is too big and takes time to load, we can-split it:
1) on lagRoot we set the-reference: ["lagEngl19es","S",21445] >> ["lagEngl19es_0","S",21445],
2) we create the-reference: lagEngl19es_0,
3) we create the-referenceNo: lagEngl19es_1, lagEngl19es_2,
name::
* McsEngl.McshMngr'searching'splitting-index-files,
* McsEngl.McshLago'splitting-index-files,
* McsEngl.splitting-index-files--on-McshLago,
description::
× HitpMcs-creation: {2026-04-29},
· evolution of searching function.
{2021-01-02}-McshMngr-search-exact::
· TODO: typing space to display only the-exact name AND the ones with !: !⇒ != !~ after it.
{2019-03-05}-McshMngr-search-MainName::
· DONE: automatically search for the-concept's main-name, the-name after (!⇒).
{2019-02-02}-McshMngr-search-MainName::
· TODO: automatically to search for the-concept's main-name, the-name after (!⇒).
description::
× HitpMcs-creation: {2025-01-28},
1) create dir "dirMcs\dirNamidx\dirLagLLLL" locally and online,
2) on file "dirNamidx\namidx.lagRoot.json" add the new language. Define what letters an-index-file will-hold based on its writting-system.
3) on "Mcsmgr\mMcsh.js", add new language as option for searching, AND upload this file.
4) on "Mcsmgr\mNamidx.mjs", add the-new language for searching.
5) add macro "hitp-name-Language.bsh" and "syntax-lagLlll.bsh",
name::
* McsEngl.McshMngr'add-new-language,
* McsEngl.add-new-language--in-McshMngr,
* McsEngl.McshLago'add-new-language--in-McshMngr,
description::
=== DeepSeek:
"Conclusion
The McshLago format is a bold R&D‑grade knowledge representation system that successfully implements a functional, monosemantic concept language within standard HTML. Its interactive features, multi‑language support, and rigorous internal linking are noteworthy achievements. However, as a format for publishing structured knowledge on the web, it currently operates in a silo that modern crawlers, assistive technologies, and linked‑data tools cannot fully penetrate.
By adopting the phased recommendations above—particularly the implementation of JSON‑LD and semantic HTML5 landmarks—McshLago could preserve its conceptual power while becoming a genuine participant in the Semantic Web ecosystem. The format's underlying philosophy is sound; the next frontier is interoperability."
[{2026-04-29 retrieved} https://chat.deepseek.com/a/chat/s/d8bedaa3-a1d8-4a0a-a05c-e38afd4f6faf]
=== ChatGPT:
"Verdict
McshLago is a serious and coherent personal knowledge-representation system. Its biggest strength is that it treats concepts, names, attributes, and relations as first-class objects. Its biggest weakness is that the semantics are too dependent on custom visual conventions and custom tooling.
The best next step is not to abandon the format, but to formalize it: write a small grammar, define canonical HTML mappings, and generate JSON-LD/RDF exports automatically. That would move McshLago from “custom HTML knowledge pages” toward a genuinely interoperable structured-concept language."
[{2026-04-29 retrieved} https://chatgpt.com/c/69f20f18-4e20-83eb-885e-77323d5dfb93]
=== Claude:
"Bottom line
The underlying idea is good and you've clearly used the system productively for years — that's strong evidence it works for its primary user. The format suffers from the classic single-author-system problems: notational accretion, implicit conventions, tight coupling to one toolchain, and an unclear position relative to standards. The path from "personal knowledge tool" to "format others use" runs through a formal grammar, a sigil reference, and an explicit comparison with SKOS/RDF. None of those require redesigning what you have — they're additions that would let the design stand on its own merits."
[{2026-04-29 retrieved} https://claude.ai/chat/ee73dbc3-803f-4751-a9ae-8ef9716528f1]
description::
× HitpMcs-creation: {2021-03-09},
· creation of current concept.
name::
* McsEngl.evoluting-of-McshLago,
* McsEngl.McshLago'evoluting,
generic-tree-of-McshLago'evoluting::
* lagoHitp-evoluting,
{2026-04}-Visual-Studio-Code::
· I started using VSCode for editing. Also I created the validator.js. All editing now is from inside VSCode.
{2021-11-17}-HitpMcs'space-on-searching::
· "name " searches for "name", "name'xxx", "name.xxx", "name!xxx"
{2021-11-17}-HitpMcs'codepoint-finding::
· Shift+1 displays the-codepoint of a-selected-character.
{2021-11-14}-HitpMcs'Chinese-indices::
· I added 123 Chinese root name-indices.
{2021-05-25}-HitpMcs'modules::
· hitp.js to mHitp.js with ECMAScript-modules.
{2021-04-04}-HitpMcs'4-letter-language::
· I use 4 letters to denote languages.
· also in names: from * Mcs. to * McsEngl.
· mNamidx.mjs works for lagAGGR.
{2020-10-18}-HitpMcs'indexes-paragraph-Mcs::
· paragraph-HitpMcs added in index-files.
* McsEngl.{2020-10-18}-HitpMcs'indexes-paragraph-Mcs,
{2018-10-16}-HitpMcs'uses-Mcs-instead-cpt-in-names::
· I am-using '* Mcs.' instead of '* cpt.' in the-list of names.
* McsEngl.{2018-10-16}-HitpMcs'uses-Mcs-instead-cpt-in-names,
{2018-09-15}-HitpMcs'search-scalability::
- lagHitp.17.2018-09-15.search-scalability,
- Arrow-keys on search. {2017-11-10},
- No type-ahead. {2017-10-17},
- Underline hovering links. {2017-10-17},
* McsEngl.{2018-09-15}-HitpMcs'search-scalability,
{2017-06-05}-HitpMcs'searching::
- lagHitp'v16 with searching.
- structured-concept-searching: with this operation it is-demonstrated THE-POWER of structured-concepts.
* McsEngl.{2017-06-05}-HitpMcs'searching,
description::
× HitpMcs-creation: {2026-04-29},
· whole part relations.
name::
* McsEngl.McshLago'whole-part-tree,
* McsEngl.McshLago'part-whole-tree,
whole-tree-of-McshLago::
*
* ... Sympan.
description::
× HitpMcs-creation: {2026-04-29},
· generic specific relations.
name::
* McsEngl.McshLago'generic-specific-tree,
* McsEngl.McshLago'specific-generic-tree,
generic-tree-of-McshLago::
* concept-language,
* ... entity.
this webpage was-visited times since {2021-03-09}
page-wholepath: synagonism.net / worldviewSngo / dirTchInf / McshLago
SEARCH::
· this page uses 'locator-names', names that when you find them, you find the-LOCATION of the-concept they denote.
⊛ GLOBAL-SEARCH:
· clicking on the-green-BAR of a-page you have access to the-global--locator-names of my-site.
· use the-prefix 'McshLago' for sensorial-concepts related to current concept 'Hitp-concept--language'.
⊛ LOCAL-SEARCH:
· TYPE CTRL+F "McsLag4.words-of-concept's-name", to go to the-LOCATION of the-concept.
· a-preview of the-description of a-global-name makes reading fast.
webpage-versions::
• version.last.dynamic: McsTchInf000009.last.html,
• version.1-0-0.2021-04-09: (0-16) ../../dirMiwMcs/dirTchInf/filMcsLagMcsh.1-0-0.2021-04-09.html,
• filMcsLagMcsh.0-1-0.2021-03-09.last.html: draft creation,