Difference between revisions of "DCMS"

From Cibernética Americana
 
(12 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
<div style="background-color: black;">
 
<div style="background-color: black;">
== 4717 Story ==
+
== 4720 Story ==
 
<div style="position: relative;right: 20px;background-color: grey;">
 
<div style="position: relative;right: 20px;background-color: grey;">
 
{{TOCright}}
 
{{TOCright}}
 
</div>
 
</div>
 
<blockquote>
 
<blockquote>
=== Pr&eacute;cis: ===
+
=== "D" CMS ===
 +
 
 +
Where D could be distributed, just D, recursively D, etc., but usually means domain or domains.
 
<blockquote>
 
<blockquote>
==== Design Intent ====
+
=== Design Intent ===
  
 
<blockquote>
 
<blockquote>
Explicit Design Goals
+
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  
 
*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
 
** GADT Framework for subsumption of drf, drupal, mediawiki, and wordpress relational schemes
** Provide a megamodule construct (Wiederhold, Wegner, Ceri, CACM 35 11 Nov 1992)
 
** Provide a complete Apache ISIS API using best of hackage java category
 
 
*LL DCMS
 
*LL DCMS
**&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.
+
**&laquo;MCS&raquo; / [[MCP|<span class="plainlinks" style="color: cyan;">MCP</span>]] and redvant integration.
**An Ansible/Django/Python based system to support MCP deployment and low level admin.
+
**Ansible in the context of mcpcms to support MCP node low level provisioning.
**Reuse of (nearly) unmodified existing CMS, specifically <span style="background-color: pink>[[PHPCMS]]</span> (Drupal, WordPress, mediawiki), and ecore.
+
**Reuse of existing <span style="background-color: pink>[[PHPCMS]]</span> (Drupal, WordPress, mediawiki).
*A role in the Large Systems Revival relative to MCP analogous to these original Burroughs subsystems:  DMSII, possibly CANDE and NDLII/NAU.
+
* Notional
*Mature apps are developed as literate artifacts in the WFL book metaphor.
+
**A role in the Large Systems Revival relative to MCP analogous to these original Burroughs subsystems:  DMSII, possibly CANDE and NDLII/NAU.
*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.
+
**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
 
Explicit Non Goals
  
*Work other than access controls on these CMSes: any other cms, explicitly ecore, which is preserved for my privilege level.
+
*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.
 
*Commercialization or use by others in any proximal stage of development, although it will be available and distributed with MCP.
  
 
</blockquote>
 
</blockquote>
  
==== "D" CMS ====
 
 
Where D can be domain(s), distributed, dominion, just D, etc., as different aspects of the generalization are considered.
 
  
 
</blockquote>
 
</blockquote>
 
</blockquote>
 
</blockquote>
== Early Pr&eacute;cis ==
+
 
 +
== Prior Usage ==
  
 
<blockquote>
 
<blockquote>
Line 50: Line 51:
 
<html>
 
<html>
 
<div style="background-color: black; width: 1100px";>
 
<div style="background-color: black; width: 1100px";>
<div style="position: relative; top: 10px; left:10px; background-image: url(/images/liberty_leading_the_people.jpg); background-repeat: no-repeat; background-position: top left; width:1000px; height: 400px;"></html>
+
<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/>
Line 67: Line 68:
 
<h4>Historical</h4>
 
<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.
 
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>
 
<html>
 
</div></div></html>
 
</div></div></html>

Latest revision as of 09:13, 28 March 2022

4720 Story

"D" CMS

Where D could be distributed, just D, recursively D, etc., but usually means domain or domains.

Design Intent

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
    • «MCS» / MCP and redvant integration.
    • Ansible in the context of mcpcms to support MCP node low level provisioning.
    • Reuse of existing PHPCMS (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], poo domain ), 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.


Prior Usage

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


DCMS - Domain Content Management System.

Is a design concept of ai-integration.biz generalizing anything that could reasonably be construed to be a CMS:

  • A framework in which arbitrary NixOS packages can form an integral aii.biz domain application.
  • A designation or namestyle by which the derivations used in WFL/DCP are distinguised from their original distributions. In this, the form DCMS-<contentSpecifier> is used where the convention is that <contentSpecifier> 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.
    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.
  • 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.


Historical

DCMS was originally intended to be implemented as the set of packages integrated by DCMS-X over DMS III, but the later is more approriate to another of my projects.

  • «DCP» inspired by the physical unit (Burroughs Data Communications Preprocessor (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 nodes.



First notion of this