to solve BLI problems, 2.2.
concurrency must be analyzed and then proportional gravity must be applied
depending on HOW BLI problems' conditions (e.g. patterns) are; Not done yet,
still in R&D; to
design and engineer teleportation method (e.g. 2535769212965),
DNA's (2 ends of chromosome and telomeres of cell) must be matched, and then,
complex ion's space length must be matched for each (Bio Clock vs. Life Span)
e.g. specific numbers with defined environment only (also see:
4PP), and then code must
be attached to Network System Number, and then those numbers (i.e. Network
System Number + Teleportation Code) are convertible to be bio form, and then ...
; Not done yet, still in R&D;

e.g.
Driver's License Number is primary key in a table, Member Number is primary key
in a table, and National ID Number is primary key in a table; Those 3 primary
keys are together in 1 table as composite key; Invoice Number behaves like
transitive dependency e.g. Purchased Item's Model, Sale Person's ID, Store's
Location, and so on; By applying 3NF, Invoice Number should not be in a table
WHERE composite key exists; By applying 2NF, either Driver's License Number or
Member Number or National ID Number can define relational data; In some systems,
Driver's License Number and National ID Number can also be foreign key, because
member might not have Driver's License, because member might not have National
ID either; By applying 1NF, relationally recorded data can be retrieved by query
(i.e.SQL) because column is unique, row is unique, and so on;
In common, 4NF,
5NF, and 6NF are theoretical and they are not implemented;