Redvant: Difference between revisions

From Cibernética Americana
Jump to navigationJump to search
No edit summary
(48 intermediate revisions by the same user not shown)
Line 1: Line 1:
<html><style> .mw-headline {color: black !important;}</style></html>
<html><style> .mw-headline {color: black !important;}</style></html>
<div style="background-color: ivory; color: black;">
<div style="font-weight: 600;background-color: #fbfcf8; color: black;">
<blockquote><br>
<blockquote><br>
{{TOCleft}}
{{TOCleft}}
= Purpose =
The primary purpose of the <b>Redvant</b> moniker is to name the separation of some product lines from their domain space aspects. Products developed under its rubric can be compiled for operation strictly on the basis of the FOSS or COTS software upon which they are based without any integration with DS though in some cases this can gut the app if presentation of a DS feature was its  purpose. A non-DS application can then supply a new purpose. My <b>tl;dr</b> line and other apps sold on stores may thus have core function repurposed to such new apps without committing to DS ops.
However this separation is only in evidence at the time of it's application in such non DS development activity. Redvant exposition is largely or entirely in terms of its use in domain space and does not further comment on this separability .
= Pr&eacute;cis =
= Pr&eacute;cis =
<span class=plainlinks>
<span class=plainlinks>
Line 13: Line 19:
and "vant" is just from haskell-servant.
and "vant" is just from haskell-servant.
</div><br><span class=plainlinks>
</div><br><span class=plainlinks>
Use of Apache [https://isis.apache.org <font color=lime>ISIS</font>] or other fat DDD pkg is intended later in the development our overall DDD product line engineering (i.e. a 'redvantis'). Some enterprise users may prefer the java basing of ISIS or an ERP core and these future developments are anticipated after the foundational elements are established.
Use of Apache [https://isis.apache.org <font color=lime>ISIS</font>] or other fat DDD pkg is intended later in our overall DDD product line engineering (as 'redvantis'). Some enterprise users may prefer the java basing of ISIS or an ERP core and this is anticipated for later development.
</span>
</span>


Line 21: Line 27:


For pragmatic reasons, it is accounting oriented and doesn't address the full actual scope of use as implied by &sect; 2.2 below, which could be confusing.
For pragmatic reasons, it is accounting oriented and doesn't address the full actual scope of use as implied by &sect; 2.2 below, which could be confusing.
Later, there will coverage in the Docs DCMS volume.


== Scope ==
== Scope ==
Line 33: Line 41:
</span>
</span>


== Transacting ==
&sect; deleted see history.
== Accounting ==
== Accounting ==
 
&sect; deleted see history.
=== Principles ===
 
==== Abstraction and Unity ====
 
Ledgers are abstract entities realized differently in different packages but from the perspective of a single accounting ontology.
 
Unless qualified, 'ledger' means double entry accounting ledger, a fundamental concept conserved across all ledger implementations, the basis of their unification.
 
=== Packages ===
==== hledger ====
 
The user reference ledger, how individuals and groups  view their ledger. The hledger-web is not duplicated.
 
==== ledger ====
 
The plaintext reference ledger, how the system views all ledgers. AKA ledgercli, ledger c++, the original that was ported to hledger.
 
==== SQL-Ledger / LedgerSMB ====
 
The enterprise reference ledger, typical of a firms view of their ledger. Individuals don't normally view this package and it's interface is mod perl based.
 
== Transacting ==
==== django-oscar ====
 
Provides front end and tx'ing code. We introduce the notion of an ephemeral tx ledger, oriented to a single, possibly complex tx which is connected to the others. Like 'ledger' transaction, 'tx' is defined to be an abstract change to a ledger. The process of application of an real such change to persistent ledgers is called settlement.


= Sonstiges =
= Sonstiges =