DCMS: Difference between revisions

From Cibernética Americana
Jump to navigationJump to search
← Older edit
No edit summary
No edit summary
 
(158 intermediate revisions by the same user not shown)
Line 1: Line 1:
<div style="background-color: black;"><br>
&nbsp;&nbsp; This is a trail of old speculative stories, <span class=plainlinks>[https://sameboat.network/DCMS DCMS]</span> as currently done is best described as drupal 7 fronting a lot of other stuff as mentioned in [[C-Liu]].
== 4720 Story ==
<div style="position: relative;right: 20px;background-color: grey;">
{{TOCright}}
</div>
<blockquote>
=== "D" CMS ===
Where D could be distributed, just D, recursively D, etc., but usually means domain or domains.
<blockquote>
=== Es War Einmal ... ===
<blockquote>
Some of these are historical/aspirational, rather than of immediate import. In the shorter term DCMS is the php, python and haskell code supporting people level services in early domain space.
*HL DCMS
** Provide a megamodule construct (Wiederhold, Wegner, Ceri, CACM 35 11 Nov 1992) with practical facilities now available
** Expose an Apache ISIS servant API using best of hackage java pkgs such as inline-java, java-bridge, etc. (AKA redvantis)
** GADT Framework for subsumption of drf, drupal, mediawiki, and wordpress relational schemes
*LL DCMS
**&laquo;MCS&raquo; / [[MCP|<span class="plainlinks" style="color: cyan;">MCP</span>]] and redvant integration.
**Ansible in the context of mcpcms to support MCP node low level provisioning.
**Reuse of existing <span style="background-color: pink>[[PHPCMS]]</span> (Drupal, WordPress, mediawiki).
* Notional
**A role in the Large Systems Revival relative to MCP analogous to these original Burroughs subsystems:  DMSII, possibly CANDE and NDLII/NAU.
**Mature apps are developed as literate artifacts in the WFL book metaphor.
**Early apps can start life, enter production in discrete subject CMSes (e.g. sameboats, tl:dr[n], <html><a title="Alt-rooted, won't work in the wild" href=https://pm-lets.principalsonly.org style="color: cyan;">poo domain</a></html> ), the admin server in django/mezzanine), migrate into the larger context as the driving case of development of our enterprise.
Explicit Non Goals
*Work other than access controls on these CMSes: any other cms, explicitly ecore, which is preserved for my personal use.
*Commercialization or use by others in any proximal stage of development, although it will be available and distributed with MCP.
</blockquote>
</blockquote>
</blockquote>
== Prior Intents ==
<blockquote>
<html><div style="color: gray; width: 1100px";></html>
<b>
<p>DCMS is, as indicated in the older material below, a generalization of CMS. In this I have in mind a certain aesthetic which is hard to convey but one can refer to examples in historical systems. First is the AS/400 architecture in which the entire user filespace could be accessed as a relational store. The generic quality of apps in the [[Burroughs MCP Architecture|MCP]] systems is a less clear but similar example. DCMS provides the reasoning support for finer level names than the domain name and is an umbrella term for all the support I provide for that.</p>
</b>
<html></div></html>
<html>
<div style="background-color: black; width: 1100px";>
<div style="position: relative; top: 10px; left:10px; background-image: url(https://meansofproduction.biz/images/liberty_leading_the_people.jpg); background-repeat: no-repeat; background-position: top left; width:1000px; height: 400px;"></html>
DCMS - Domain Content Management System.
DCMS - Domain Content Management System.
<br/>
<br/>
<blockquote>
<blockquote>
<b>ai-integration.biz</ab> is both a DNS domain and a commodity software project to provide semantic level bindings with a fanout of supporting toolchains based on a common core [[AII]]. There are these three distinct contexts:
Is a design concept of <b>ai-integration.biz</b> <font color="navy"> generalizing anything that could ''reasonably'' be construed to be a CMS:
<br><br>
<br/>
<ul>
<ul>
  <li> The subject design space.
  <li> A framework in which arbitrary NixOS packages can form an integral '''aii.biz''' domain application.
  <li> A running instance applied to this [[dominion]] available from the link of the same name in the left skin navigation dcms category.
  <li> A designation or namestyle by which the derivations used in WFL/DCP are distinguised from their original distributions. In this, the form DCMS-&lt;contentSpecifier&gt; is used where the convention is that &lt;contentSpecifier&gt; will be one or two latin characters if a generic category of actual CMSes is being modeled, or a name if a specific one is.
<li> A software distribution which can be applied to bind a different set of domains.
 
</ul>
:Example: '''DCMS-W''' would be the category of wiki CMSes but '''DCMS-wiki''' would be the mediawiki derivation ("EG") which you are working with now.
<li> '''DCMS-X''' is the special abstraction of DCMS realized in WFL/DCP as a dominion level subject, a concrete implementation of the LAMP abstraction based on our NixOS packages.
</ul></font>
</blockquote>
<br/>
<h4>Historical</h4>
DCMS was originally intended to be [[DMS III|implemented]] as the set of packages integrated by DCMS-X over [[:en:Unisys DMSII|DMS III]], but the later is more approriate to another of my projects.
*&laquo;DCP&raquo; inspired by the physical unit (Burroughs [http://www.freepatentsonline.com/4093981.html <span class="plainlinks" style="color: cyan;"> Data Communications Preprocessor</span>] (also Data Control Unit and Data Comm Processor) not the later same acronymed AI/ES here) using the distributed-process family of haskell modules on [[MCP|<span class="plainlinks" style="color: cyan;">MCP</span>]] nodes.
<html>
</div></div></html>
<br/><br />
</blockquote>
</blockquote>
==[http://juan.ai-integration.biz/everything/index.pl?node_id=1049 First notion of this]==
</div>
Retrieved from "https://eg.meansofproduction.biz/eg/index.php/DCMS"