On Monday 21 Feb 2005 9:08 pm, Ramanraj K wrote:
Nagarjuna G. wrote:
just wanted to make a minor correction in the account that gnoware
is
different from GNOWSYS. you mentioned gnoware, where it should be GNOWSYS.
Oops ;)
Gnow these :)
GNOWSYS is an acronym for Gnowledge Networking and Organizing SYStem
and
a pun on gnosis as well.
http://www.gnowledge.org/GNOWSYS/Programs/Data/ObjectType/G/GNOWSYS/viewObje...
GNOWARE is the name of a GNU/Linux distro ( www.gnoware.org )
GNOWLEDGE at http://web.gnowledge.org/ gives more info about the
things
to gnow.
Part of the argument during our travel together, was that oop is not suitable for gnowledge like services. oop serves computer programs themselves well, but the same is not suitable for modeling the real world. An elaborate discussion about that is available at: http://www.geocities.com/tablizer/oopbad.htm
I gave a look at the tablizer site mentioned above. Using TOP (table oriented programming) everywhere is not possible either. In fact one of the reasons why GNOWSYS is an OODBMS and not a RDBMS is because I found a limitation of not being able to add objects independently. second: the structure is not available to me today, I want it emerge, and emerge in multiple ways, while working with the database. TOP requires that before populating the data you need table very well defined. Changing schema is not possible. third: the structure of all my assertions and compositions is not known, and the semantics of composition is not known to be valid a priori. GNOWSYS is developed to take care of these problems. GNOWSYS also supports flexible design of n-adic relations. At the same time, GNOWSYS can take care of both functions as well as objects in its base. In fact it is a hybrid system, that satisfies all needs, giving the power of a traditional db. The basis vocabulary of GNOWSYS consists of terms and predicates, on one hand and classes and functions on the other. The former is for declarative knowledge and the later for procedural knowledge.
Nagarjuna