Universal information management
How – Universal Information Management
Universal information addresses
When information is managed or processed in different applications or processes, some interpretation and translation may be required to make data from one process work with data from another process.
On the Internet of Entities, universal information addresses facilitate data to be:
- defined universally
- identified universally
- interpreted universally
- queried universally
- managed universally and
- related universally (both in data relations as well in related meaning)
The Internet Protocol for the Internet of Entities is the Uniform Entity and Transaction Protocol, or UETP in short. The Internet of Entities and UETP work with universal information addresses that consist of two building blocks:
- The U3ID (UETP Universally Unique Identifier). The U3ID is an identifier for an entity (an entity can represent anyone or anything that 'can be') and at the same time is the entity's virtual address, similar like an IP address or telephone number.
- The USEN (UETP Semantic Extension Number). The USEN is an identifier for specified meaning in the 1LANGUAGE open dictionary, with support in a large variety of languages.
Below, we demonstrate how we can combine U3IDs (entity identifiers) with USENs (meaning) to universally manage information.
U3ID + USEN: defining, identifying and interpreting information
When we create an U3ID identifier, which can distinctively identify anything, like a person, product, rule, event and so on, there is no further information than just the identifier (technically, the U3ID can contain meaning and structure, but that is beyond this point of introduction).
The identifier itself is just a universally unique combination of letters and numbers, there is no meaning of the entity. We can add meaning to the identifier by adding USENs (with meaning) to the U3ID.
| To which it pertains | Meaning |
|---|---|
| U3ID | USEN |
| This person | First name |
| That car | Driving speed in km/h |
| This rule | Height restriction in meters |
You basically could see the USEN as an extension number with a very specific meaning. With USENs, we can say that the identifier classifies as a person, with a certain first name, date of birth, shoe size, ownership situation and much more characteristics. Likewise, a product entity can be classified as a product, with a specific color, production date, etc.
The combination of U3IDs and USENs help us to universally identify specific entities and provide them with meaning that can be interpreted universally in the right context.
U3ID + USEN + USEN: Managing information
The ability to declare, define and query information is not enough. There is also a need for the management of data. Where is the data stored, who may have access, what access tokens need to be provided to use the data, what are the user rights to the data? By adding an additional USEN to the data, universally identifiable and meaningful information can be management in a universal manner.
| To which it pertains | Meaning | Managing it |
|---|---|---|
| U3ID | USEN | USEN |
| This person | First name | URL |
| That car | Driving speed in km/h | Public key |
| This rule | Height restriction in meters | Created by |
U3ID + USEN + U3ID: Meaningfully relating entities
Entities typically do not exist in isolation, they tend to relate to other entities. The relationship between entities can be described as a meaningful concept by a USEN. Information addresses with the structure U3ID + USEN + U3ID facilitate for such relational descriptions. As a result, self-emerging concepts (like a group of cells becoming tissue, groups of tissue becoming organs and groups of organs becoming a human body) can also be meaningfully created and interpreted in their inter-relational composition.
| Entity | Relates meaningfully to | Entity |
|---|---|---|
| U3ID | USEN | U3ID |
| This book | to own / owner | This person |
| This book | to author / author | This author |
| That car | to produce / producer | This producer |
USEN + USEN + USEN: Relating meaning
Additionally, with a combination of USENs, we can relate meaning with meaning in a meaningful way. Suppose we have defined an entity in relation to another entity as being a client. Now, someone with access rights to that data, is looking for a customer rather than for a client. If the term customer is not providing any results, it may be worthwhile looking for synonyms of customer. When looking at synonyms of the concept 'customer', the concept 'client' may come up and can be suggested as a search term that does render a helpful response.
Likewise, if someone wants to know whether something is purple and looks for the concept purple, another higher class concept like color may provide more information, possibly stating that its status is red.
Relating meaning with meaning can make artificial intelligence a lot more efficient than it is today, as it has to discover context by applying large amounts of information and lots of calculations, while it frequently still makes guesses about context.
| Meaning | Relates meaningfully to | Meaning |
|---|---|---|
| USEN | USEN | USEN |
| Client | Synonym | Customer |
| Up | Antonym | Down |
| Color | Hyponym / Hypernym | Purple |