Difference between revisions of "ES/S Identity Prefix"
(→Format) |
(→Extensible Services / Server for Business) |
||
| (18 intermediate revisions by the same user not shown) | |||
| Line 3: | Line 3: | ||
[[File:Essb_58_example.png|350px|thumb|A common view of prefixes are on printable labels]] | [[File:Essb_58_example.png|350px|thumb|A common view of prefixes are on printable labels]] | ||
| − | 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. | ||
=== Benefits === | === Benefits === | ||
| Line 56: | Line 61: | ||
! Type | ! Type | ||
! Description | ! Description | ||
| + | |- | ||
| + | | Unprefixed | ||
| + | | User, Register, Round, Correlator, Excuse, Relation, DME, File | ||
| + | | | ||
| + | |- | ||
| + | | S | ||
| + | | Singleton Identifier | ||
| + | | Identifies a Person (User) against a System | ||
| + | |- | ||
| + | | R | ||
| + | | Realm Identifier | ||
| + | | Identifies a Group of Persons (Group of Users) against a System | ||
| + | |- | ||
| + | | 7 | ||
| + | | Entity (ESS.Entity) | ||
| + | | Entity as inherited from ES/S Core | ||
| + | |- | ||
| + | | 19 | ||
| + | | Person (ESSB.Person) | ||
| + | | A Natural person, usually used to refer to employees | ||
| + | |- | ||
| + | | 32 | ||
| + | | Data Catalog (ESSB.DataCatalog) | ||
| + | | A (Dynamic) stucturable Data Catalog, used to store and access large referencive books, for example international Standards | ||
| + | |- | ||
| + | | 44 | ||
| + | | Customer Reference (ESSB.CustomerReference ) | ||
| + | | A Reference used to identify Correspondence of a Customer, comes alonside factures and other documents. | ||
| + | |- | ||
| + | | 53 | ||
| + | | Item (ESSB.RegisteredItem) | ||
| + | | A Item, primarily a known item that can be ordered multiple times. | ||
| + | |- | ||
| + | | 54 | ||
| + | | Item (ESSB.VolatileItem) | ||
| + | | A Item that is volatile, for a single use case or only produced once. | ||
| + | |- | ||
| + | | 55 | ||
| + | | Offer (ESSB.Offering) | ||
| + | | A Volatile, non-binding prefacture bill, used to offer services in a legal manner | ||
|- | |- | ||
| 57 | | 57 | ||
| Line 68: | Line 113: | ||
| Order (ESSB.PostfactureOrder) | | Order (ESSB.PostfactureOrder) | ||
| A Postfactured Order, for example a bill for services or delivered goods, that have sent out before payments have occured | | A Postfactured Order, for example a bill for services or delivered goods, that have sent out before payments have occured | ||
| + | |- | ||
| + | | 71 | ||
| + | | StructuredIndex (ESSB.StructuredIndex ) | ||
| + | | A Structured Index Set, used to structure large sets of items and groups of a project | ||
|- | |- | ||
| 72 | | 72 | ||
| Project (ESSB.Project) | | Project (ESSB.Project) | ||
| A Project, for example a collection of tasks or roadmaps to achieve orders | | A Project, for example a collection of tasks or roadmaps to achieve orders | ||
| + | |- | ||
| + | | 62 | ||
| + | | Prefacture/Offering (ESSB.PreFacture) | ||
| + | | A Prefacture Receipt, also known as Offer, used to offer Services legally binding or non-binding. | ||
| + | |- | ||
| + | | 68 | ||
| + | | Facture Receipt (ESSB.FactureReceipt) | ||
| + | | A Facture Receipt, also known as Invoice. | ||
| + | |- | ||
| + | | 82 | ||
| + | | FinanceEntry (ESSB.FinanceEntryBooking) | ||
| + | | A Finance entry, used to keep tracks of pending payments and/or due refunds | ||
| + | |- | ||
| + | | 91 | ||
| + | | Cash Register (ESSB.CashRegister) | ||
| + | | A Cash Register, that has stores transactional data and controls access to cash values | ||
| + | |- | ||
| + | | 94 | ||
| + | | Volatile Debitor Account (ESSB.VolatileDebitor) | ||
| + | | A Volatile debitors account, for the purpose of tracking pending payment states | ||
|} | |} | ||
==== 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;" | ||
| Line 93: | Line 164: | ||
=== Customizability === | === Customizability === | ||
| − | Most distributions allow for extension or forking of data types. This mechanisms include addressing of unallocated prefixes. The prefix length is not limited, however included identities are generally 2-digits. | + | Most distributions allow for extension or forking of data types. This mechanisms include addressing of unallocated prefixes. The prefix length is not limited, however included identities (compatibility layer) are generally 2-digits, while recent innovations use variable length or unsectioned prefixing. |
Latest revision as of 06:58, 27 July 2024
Contents
General
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.
Benefits
The benefits of using a prefixed identity scheme are obviously achieving direct adressability both electronically and manually. A lone datasets provides the exact usage type of following identity suffixes and can be addressed without further information on any process, no matter if on paper or transmitted digitally.
Format
Due to compatibility with legacy systems and legacy hardware, the vast majority of resources for enterprise applications uses digits only. Some identites can include alphabetic characters, or multidimensional prefixing (ES/S Identity Chain). The products that solely rely on in-place programming and integrated scripting environments, like ES/S-A take advantage of alphabetic prefixes.
List of common prefixes
Extensible Services / Server
| Prefix | Type | Description |
|---|---|---|
| 1 | User Identity | Used for System Identities (most commonly users or robots) |
| 7 | System Identity Approval Permission | This identity is used pan-system wide exclusively to control programmed permissions |
Extensible Services / Server for Automation
| Prefix | Type | Description |
|---|---|---|
| CS/CSES | Complex Service | Used to identify complex typed system assets (CTSA) |
| AS/ASES | Primitive Service | Used to identify primitive typed system assets (PTSA) |
Extensible Services / Server for Business
| Prefix | Type | Description |
|---|---|---|
| Unprefixed | User, Register, Round, Correlator, Excuse, Relation, DME, File | |
| S | Singleton Identifier | Identifies a Person (User) against a System |
| R | Realm Identifier | Identifies a Group of Persons (Group of Users) against a System |
| 7 | Entity (ESS.Entity) | Entity as inherited from ES/S Core |
| 19 | Person (ESSB.Person) | A Natural person, usually used to refer to employees |
| 32 | Data Catalog (ESSB.DataCatalog) | A (Dynamic) stucturable Data Catalog, used to store and access large referencive books, for example international Standards |
| 44 | Customer Reference (ESSB.CustomerReference ) | A Reference used to identify Correspondence of a Customer, comes alonside factures and other documents. |
| 53 | Item (ESSB.RegisteredItem) | A Item, primarily a known item that can be ordered multiple times. |
| 54 | Item (ESSB.VolatileItem) | A Item that is volatile, for a single use case or only produced once. |
| 55 | Offer (ESSB.Offering) | A Volatile, non-binding prefacture bill, used to offer services in a legal manner |
| 57 | Customer (ESSB.DefaultCustomer) | A Customer Data set, commonly used to identify a companies customers |
| 58 | Order (ESSB.PrefactureOrder) | A Prefactured Order, for example a online shop order, that have been paid for while before or while ordering |
| 59 | Order (ESSB.PostfactureOrder) | A Postfactured Order, for example a bill for services or delivered goods, that have sent out before payments have occured |
| 71 | StructuredIndex (ESSB.StructuredIndex ) | A Structured Index Set, used to structure large sets of items and groups of a project |
| 72 | Project (ESSB.Project) | A Project, for example a collection of tasks or roadmaps to achieve orders |
| 62 | Prefacture/Offering (ESSB.PreFacture) | A Prefacture Receipt, also known as Offer, used to offer Services legally binding or non-binding. |
| 68 | Facture Receipt (ESSB.FactureReceipt) | A Facture Receipt, also known as Invoice. |
| 82 | FinanceEntry (ESSB.FinanceEntryBooking) | A Finance entry, used to keep tracks of pending payments and/or due refunds |
| 91 | Cash Register (ESSB.CashRegister) | A Cash Register, that has stores transactional data and controls access to cash values |
| 94 | Volatile Debitor Account (ESSB.VolatileDebitor) | A Volatile debitors account, for the purpose of tracking pending payment states |
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.
| Prefix | Type | Description |
|---|---|---|
| K | Network Process Fingerprint | A Network Process Fingerprint is used to identitfy a exact resource copy that was sent to a client device over a network like the internet. |
Pan-Organizational Use
Between branches or accros different legal entities, all identities can be chained. Secondly, any ES/S-Compatible identity has a unique checksum (Starting with CR) that can verify if a identity really belongs to a specific organization. These checksums are calculated from the organizational identifier key.
Customizability
Most distributions allow for extension or forking of data types. This mechanisms include addressing of unallocated prefixes. The prefix length is not limited, however included identities (compatibility layer) are generally 2-digits, while recent innovations use variable length or unsectioned prefixing.
