Rocksolid Light

Welcome to RetroBBS

mail  files  register  newsreader  groups  login

Message-ID:  

Vini, vidi, Linux! -- Unknown source


devel / comp.databases.theory / Re: My proof that "anchor modeling" is plagiarism of my papers.

SubjectAuthor
o Re: My proof that "anchor modeling" is plagiarism of my papers.vldm10

1
Re: My proof that "anchor modeling" is plagiarism of my papers.

<840e3817-7fcc-4924-ad40-1cb94cb8aecbn@googlegroups.com>

  copy mid

https://www.rocksolidbbs.com/devel/article-flat.php?id=187&group=comp.databases.theory#187

  copy link   Newsgroups: comp.databases.theory
X-Received: by 2002:a05:6214:4b:: with SMTP id c11mr3815734qvr.18.1626168627112;
Tue, 13 Jul 2021 02:30:27 -0700 (PDT)
X-Received: by 2002:a05:6830:1bef:: with SMTP id k15mr2922945otb.362.1626168626789;
Tue, 13 Jul 2021 02:30:26 -0700 (PDT)
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!proxad.net!feeder1-2.proxad.net!209.85.160.216.MISMATCH!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.databases.theory
Date: Tue, 13 Jul 2021 02:30:26 -0700 (PDT)
In-Reply-To: <e5bdc50e-c38f-44a1-a785-62e3fd47aaa2@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=93.142.135.52; posting-account=GkmQDwoAAACufsQ7SBEEfQqOinAuwmaY
NNTP-Posting-Host: 93.142.135.52
References: <e5bdc50e-c38f-44a1-a785-62e3fd47aaa2@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <840e3817-7fcc-4924-ad40-1cb94cb8aecbn@googlegroups.com>
Subject: Re: My proof that "anchor modeling" is plagiarism of my papers.
From: vldm10@yahoo.com (vldm10)
Injection-Date: Tue, 13 Jul 2021 09:30:27 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
 by: vldm10 - Tue, 13 Jul 2021 09:30 UTC

Dana ponedjeljak, 23. prosinca 2019. u 14:50:24 UTC+1 korisnik vldm10 napisao je:
> In my post dated December 9, 2019, in thread „The relational model is a wrong
> theory“, I wrote the following facts:
> -------------------------------------------------------------------------------------
> You can also see two identifiers:
> 1. The Identifier of an entity.
> 2. The identifier of the state of an entity.
>
> Note that my identifier of state is actually a surrogate key. But when I link it to
> the corresponding identifier of the entity, then it is a very strong and complete
> link. So I have always two identifiers: the identifier of the entity and the
> identifier of an state of the entity.
> --
> Identifiers of entities they are in database and they are in the real world also.
> Because they exist in databases and in the real world, the identifiers of entities
> are not surrogates.
> -------------------------------------------------------------------------------------
> Now I will explain how authors of "anchor modeling" plagiarized my paper:
> They plagiarized my identifier of an entity and they link all changes to their key.
> This is exactly what I did. In fact I did more. I associate all changes related to
> this entity to the identifier of the entity which is in the database, more precisely I associate all these changes to some memory. But I have also the identifier of
> the entity in the real world. For example I have a small book, which I call
> „passport“ and the identifier of the entity is in the passport.
> The authors od "anchor modeling" call their key - „anchor key“.
> -------------------------------------------------------------------------------------
> This „anchor key“ is a surrogate key which is very bad database solution.
> My identifier of an entity is in the real world and in the database. So my
> identifier of an entity is:
> 1. The identifier of the entity in the real world.
> 2. The identifier of an entity is in the database.
> 3. This my identifier is not surrogate key.
> 4. My Identifier of the entity can work in data warehouse much better then an anchor.
> 5. „Anchor key“ is a special case of my key. If you delete my key from the real world
> and keep only my key in database, you will have „anchor key“.
> That is one reason why my solution to this problem is much more general than "anchor
> modeling".
> -------------------------------------------------------------------------------------
> This means that "anchor modeling" is only one case, that is, a special case from my
> general solution. It also means that the authors of "anchor modeling" plagiarized my
> main ideas, which were presented to this group and discussed in detail, five years
> before the authors of "anchor modeling" presented their plagiarism.
> My second identifier (that is the identifier of an state of an entity) was deleted by
> authors of "anchor modeling". However they left all changes of an entity and bound
> them to "anchor", which is a copy of my solution.
> In my opinion, this is one of the greatest plagiarism in history.
> ----------------------------------------
> What are we talking about here?
> ----------------------------------------
> This is a problem known from ancient Greece and is known as the Ship of Theseus.
> According to Wikipedia: „In the metaphysics of identity, the ship of Theseus is a thought experiment that raises the question of whether an object that has had all of
> its components replaced remains fundamentally the same object. The concept is one of
> the oldest in Western philosophy, having been discussed by the likes of Heraclitus
> and Plato by ca. 500-400 BC and later by Aristotle ."
> Later, many philosophers discussed and tried to solve this problem. For example,
> Thomas Hobbes, John Locke and Noam Chomsky.
> We who work with databases may set the following question: How does a person (or an
> entity) who has changed some attributes of his or her identity, for us, remain the
> same person?
>
> I solved this problem as an effective procedure with the help of my two identifiers
> and with the help of some other mentioned new solutions. I also found a procedure
> that binds all changes to an identifier of entity and this is exactly what the
> authors of „anchor modeling“ plagiarized for the process of changes and connecting
> these changes to "anchor").
> This my solution to the problem, which has not been solved for 2500 years, has been
> gradually plagiarized by the authors of "anchor modeling". Then they plagiarized my
> scientific results and declared it as their scientific results.
> The problem mentioned above, has not been solved for 2500 years. I solved this
> problem long before 2005, but presented it to this user group in 2005. The authors of
> "anchor modeling" gradually plagiarized my scientific papers. In December 2009, the
> authors of "anchor modeling" published their first work. The authors of "anchor
> modeling" published their second paper in DKE in December 2010. After my critique of
> errors and plagiarism of the authors of "anchor modeling" on this user group, they
> published their second paper, in which they plagiarized the most significant of my
> results. I have presented in this thread some of these plagiarism.
> Following my public criticisms of plagiarism published in the first paper of "anchor
> modeling", presented on this user group, the authors of "anchor modeling" published
> their second paper in the journal DKE, Editor-in-Chief Peter Chen.
> This time, they introduce "identifiers" on the most complex concept, that is the
> identifier of the relationship. You can see this in Definition 16 in their paper
> published in DKE.
> Of course, these complex identifies are solved in my papers from 2005.
>
> In their second paper, section 4.5, the authors of "anchor modeling" „introduce“
> "states".
> Let me note, that this nonchalant introduction to these basic concepts(identifiers
> and states) presented by authors of "anchor modeling" is one of the greatest
> plagiarism in history.
> Notice that states and identifiers are fundamental concepts for the beginnings of a
> completely new database theory. These two concepts significantly influence the
> fundamental things in Logic, Semantics, Meaning, and Theory of Thoughts. For example:
>
> 1. I am not speaking about Truth and Meaning.
> 2. I am speaking about truth and meaning in the past, in the present and in the
> future and what is the most important my database can do it very precisely.
>
> I also want to present that authors of "anchor modeling" gradually and carefully
> introduce plagiarism, so this is hard to notice this plagiarism.
>
> ------------------------------------------------------------------------------------
> In Brazil, the first paper from "anchor modeling" received the first prize, the
> honorary president of the congress was Peter Chen.
> The second paper (that is, the repair of the first, award-winning paper) was
> published in the scientific journal DKE, where Editor-in-Chief is Peter Chen.
> -------------------------------------------------------------------------------------
>
> Please note that I have been explaining my papers in detail on this user group since
> 2005.
>
> Vladimir Odrljin

The authors of “anchor modeling“ use „identity“ as the main term. However, this is a term that is not defined. Since „identity“ is not a defined term at all, the use of this term as a main term in procedures with data has no sense.
Of course, we do not use undefined terms in science. Undefined terms in science are nonsense. That is why the basic term in “ancor modeling“ is nonsense. This nonsense is called „identity“.
This phenomenon began to move from „object-oriented programming“ to database theory. This has been started by „scientists“ who do not understand database theory. In „object-oriented programming (OOP is a shortcut), the term „object identity“ was introduced. However, the notion of the identity of a real object from the real world has nothing to do with the identity of an object from object-oriented programming. In DB theory there are not only real objects, but there are also „images“ of real objects in human memory and in DB memory. These three objects (an object from the real world, „images“ of real objects in human memory, and DB memory from human memory, are connected. This connection between „the real world object“ and „the abstract world object“ in human memory is something that belongs to the most complex areas. This part, the authors of „anchor modeling“ did not understand. They inserted the idea of identity from the OOP into the DB – which is a great mistake and nonsense.

„anchor modeling“ was named the best paper at the most important database conference in the world. However, their main term „identity“ is not defined.


Click here to read the complete article
1
server_pubkey.txt

rocksolid light 0.9.81
clearnet tor