|
After reading about this initiative I have the
following suggestions:
While I am not sure the exact specs for the API.
But what I think might be critical for success is that the query front end
interface be in a form of natural language,or a front end GUI, that is
similar by query by example based on the schema of modems.
It should be dynamic and ad hoc while delivering
responses from the query in both the OOdbms along with procedures used to
manipulate the data (methods).
I think it should be independent of any programming
language, However, Successful query structures should be able to be saved and
generate OO code (like Java) to implement the query within the code of the
application. This fits very nicely with UML based Java development.
The query should be a individual window (a visual
insight) for end user to the OOdbms without the need to have programming skills
to write code or API calls to obtain the Data pointers. Moreover, it could be
used by developers as simulation and prototyping method of devising complex and
effective querying. To be robust when later implemented directly in a
application.
Further, I think the OOdbms Schema and met should
be available in GUI format with proper documentation of the nature of the
classes being represented. This should serve as the basis for constructing any
query or Database manipulation of update, delete, and insert.
Great care must be provided in providing an option
of a direct path to query results to all query results of child classes of a
parent class that is the focus of the query process.
While these function might reside and operate on
top of an API. The API should be viewed as the backbone for the feature listed
above.
always
Schneur
----- Original Message -----
Sent: Saturday, August 05, 2000 1:19
AM
Subject: Fwd: OODB query interface
Hi all,
Carl has started a new initiative for the
creation of a new, OODBMS query
interface. Find his roundmail in the
attachment.
People, a query language is something that many of you have
asked for. Carls
approach is very interesting. It conbines advantages of a
real object oriented
architecture and a descriptive query language like
SQL.
Carl is working on commercial (closed) software. However, the
query interface
specification will be developed in a totally open manner.
Carl, and maybe
others, will probably implement the specification in
commercial software. But
if we decide to work on the specification, then we
have the chance to make the
specification real ozone-friendly (in contrast
to other specification like OQL
and JDO). And we will have the chance to
provide the first and hopefully the
best implementation of the
specification under an open source license.
So, if anybody is
interested in such a cool thing, then jump in and help with
the
specification and implementation.
Falko
----------
Forwarded Message ----------
Subject: OODB query interface
Date:
Fri, 4 Aug 2000 23:42:22 +0200
From: Carl.Rosenberger@t-online.de (Carl
Rosenberger)
Falko from www.ozone-db.org and I have decided to work
on a programming
language independant standard for a query interface to
OODBs. It will be
based on the approach described in the attached
HTML-file.
Our goals:
- promote OODBs
- a standard query
interface, simple and worthwhile to implement in contrary
to JDO
-
promote our own projects
The steps:
- find a name for the
API
- mail all our peers and direct contacts, if they like to participate
in the
first roundmail
- rough draft
- create a mailing list
-
"Call for experts" crossposting in newsgroups
- mail all DB vendors
-
mail to all magazines
- specification process
- publication of the
standard as above
Mails to magazines, vendors and publication will
include the names and
companies of all participants.
Would you be
interested in participating?
Regards,
Carl
Rosenberger
db4o - database for objects -
http://www.db4o.com
-------------------------------------------------------
--
______________________________________________________________________
Falko
Braeutigam
mailto:falko@smb-tec.com
SMB
GmbH
http://www.smb-tec.com
|