Hi Mike and Mark,
Mike is claiming that ZNF already existed, before Gary (bG). He offers the
two links below, as evidence.
I logically disagree.
I say ZNF is one column of serial data, not column correlated. ZNF
only co-relates data symbols by: (1) source name and (2) chronological
sequence.
It is a time-based array. It has a very different ideological
geometry. That’s what makes it so primitive and universal (it’s like the
Universe is observing, contexting itself).
Below is what they say ZNF is (two links). I do not think they know what they are
talking about. Please interpret their writings for me. Thanks. -g
=====
GLD Notes: “One column of serial-data that is not column
correlated,” is the right and true definition of ZNF. If they start by saying
“Spreadsheet Design” or “It’s not normalized” and have the data
examples laid-out in a matrix form, then they do not have a clue.
Serial-data is an ideological tectonic shift, to any database specialist,
because it does not start with a matrix form. It will take us to explain it to
them. ZNF starts with a line form, from a single point. That
is a fairly primitive, ideological geometry.
From this line of serial-data, emerging from a single named-point, the
correlated matrix is created, in steps and stages, via MapReduction. This is
Big Data.
Keep in mind: Gary also created the idea of serial-data.
You must first understand serial-data, spewing from a named point, before you
can get ZNF. Flow.exe knows this.
Serial-data then leads to the ZNF logical linkage of it (0) to 1-2-3-#
Normalized Form data. The only co-relation that serial-data has is a line of
symbols, acquired in time, from a named source.
In short, ZNF logical allows us to bidirectionally link serial-data with
matrix-data. NOsql can now live well with SQL: it can be logically related
(automated).
Technical, that ZNF << to >> #NF is a very big thing to be able
to do. It is nice automation.
====
From: Michael Deines
Zero normal form has been defined already
|

