DCMS: Difference between revisions
From Cibernética Americana
Jump to navigationJump to search
No edit summary |
|||
| (85 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
== | <div style="background-color: black;"> | ||
== 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> | |||
=== Design Intent === | |||
<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 | |||
**«MCS» / [[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 Usage == | ||
<blockquote> | |||
<html><div style="color: gray; width: 1100px";></html> | |||
<html><div style="width: 1100px";></html> | |||
<b> | <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> | <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> | ||
| Line 19: | 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 36: | 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. | ||
*«DCP» 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> | ||
<br/><br /> | <br/><br /> | ||
[http://juan.ai-integration.biz/everything/index.pl?node_id=1049 First notion of this] | </blockquote> | ||
==[http://juan.ai-integration.biz/everything/index.pl?node_id=1049 First notion of this]== | |||
</div> | |||
