DCMS: Difference between revisions

From Cibernética Americana
Jump to navigationJump to search
No edit summary
No edit summary
Line 10: Line 10:
Explicit Design Goals
Explicit Design Goals


*HL DCMS [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]] nodes.
*HL DCMS  
** GADT Framework for subsumption of drupal, mediawiki, and wordpress relational schemes
** GADT Framework for subsumption of drupal, mediawiki, and wordpress relational schemes
** Provide a megamodule construct (Wiederhold, Wegner, Ceri, CACM 35 11 Nov 1992)
** Provide a megamodule construct (Wiederhold, Wegner, Ceri, CACM 35 11 Nov 1992)
** Provide a complete Apache ISIS API using best of hackage java category
** Provide a complete Apache ISIS API using best of hackage java category
*LL DCMS
*LL DCMS
**[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]] nodes.
**An Ansible/Django/Python based system to support MCP deployment and low level admin.
**An Ansible/Django/Python based system to support MCP deployment and low level admin.
**Reuse of (nearly) unmodified existing CMS, specifically these: Drupal, WordPress, mediawiki, ecore, and mezzanine.
**Reuse of (nearly) unmodified existing CMS, specifically these: Drupal, WordPress, mediawiki, ecore, and mezzanine.