ES/S Identity Prefix - Revision history

Wikiadmin: /* Extensible Services / Server for Business */

2024-07-27T06:58:59Z

‎Extensible Services / Server for Business

Wikiadmin: /* Extensible Services / Server for Business */

2023-09-13T00:17:17Z

‎Extensible Services / Server for Business

Wikiadmin: /* Extensible Services / Server for Business */

2023-09-10T03:17:53Z

‎Extensible Services / Server for Business

Wikiadmin: /* Extensible Services / Server for Business */

2023-07-24T16:18:23Z

‎Extensible Services / Server for Business

Wikiadmin: /* Extensible Services / Server for Business */

2023-07-01T03:52:42Z

‎Extensible Services / Server for Business

Wikiadmin: /* Extensible Services / Server for Business */

2023-07-01T01:36:04Z

‎Extensible Services / Server for Business

Wikiadmin: /* Extensible Services / Server for Business */

2023-06-27T02:17:51Z

‎Extensible Services / Server for Business

Wikiadmin: /* Extensible Services / Server for Web Services */

2023-06-21T15:37:22Z

‎Extensible Services / Server for Web Services

Wikiadmin: /* Extensible Services / Server for Business */

2023-06-21T15:35:49Z

‎Extensible Services / Server for Business

Wikiadmin: /* General */

2023-06-21T15:24:38Z

‎General

@@ Line 65: / Line 65: @@
 | User, Register, Round, Correlator, Excuse, Relation, DME, File
+|
 |-
 | 7

@@ Line 73: / Line 73: @@
 | Person (ESSB.Person)
 | A Natural person, usually used to refer to employees
 |-
 | 44

@@ Line 101: / Line 101: @@
 | Order (ESSB.PostfactureOrder)
 | A Postfactured Order, for example a bill for services or delivered goods, that have sent out before payments have occured
 |-
 | 72

@@ Line 121: / Line 121: @@
 | Cash Register (ESSB.CashRegister)
 | A Cash Register, that has stores transactional data and controls access to cash values
 |}

@@ Line 105: / Line 105: @@
 | Project (ESSB.Project)
 | A Project, for example a collection of tasks or roadmaps to achieve orders
 |-
 | 68

@@ Line 85: / Line 85: @@
 | Item (ESSB.VolatileItem)
 | A Item that is volatile, for a single use case or only produced once.
 |-
 | 57

@@ Line 105: / Line 105: @@
 | Facture Receipt (ESSB.FactureReceipt)
 | A Facture Receipt, also known as Invoice.
 |-
 | 91

← Older revision		Revision as of 15:37, 21 June 2023
Line 112:		Line 112:

	==== Extensible Services / Server for Web Services ====		==== Extensible Services / Server for Web Services ====
		+
		+	ES/S-W generally makes no broad use of prefixes, because there is no necessity to identify automatically managed resources that face virtually no human interaction.

	{\| class="wikitable" style="float:center; margin:0 0 0.5em 1em;"		{\| class="wikitable" style="float:center; margin:0 0 0.5em 1em;"

← Older revision		Revision as of 15:24, 21 June 2023
Line 4:		Line 4:

	All ES/S Compatible Systems, but especially the ones used in complex enterprise applications make use of prefixed identities. This is used to clarify and allocate the identity space a company uses internally. The idea behind is to uniquely allocate prefixes to a specific dataset type or enumeration, that for example, can be a customer, a project or a task.		All ES/S Compatible Systems, but especially the ones used in complex enterprise applications make use of prefixed identities. This is used to clarify and allocate the identity space a company uses internally. The idea behind is to uniquely allocate prefixes to a specific dataset type or enumeration, that for example, can be a customer, a project or a task.
		+
		+	The resulting number, alongside with its prefix and unqiue serial number is called ESSID.
		+	ESSID's are used by every ES/S System established, in a sophisticated and commodating way.

	Most systems used alongside database systems use non prefixed auto-incrementing counters, that do not reset upon entry deletion. The ES/S Systems differ somewhat that all available space is used at any time. This behaviour maximizes disburse of storage expenses and merchantability of the complete organization. The space filling can be deactivated and is linked closely with checksum creation to ensure no confusions are made during data maintenance.		Most systems used alongside database systems use non prefixed auto-incrementing counters, that do not reset upon entry deletion. The ES/S Systems differ somewhat that all available space is used at any time. This behaviour maximizes disburse of storage expenses and merchantability of the complete organization. The space filling can be deactivated and is linked closely with checksum creation to ensure no confusions are made during data maintenance.