What you are talking about, imho, has to do with ease of use issues.
The ODMG standard is a 'technical' document that deals with how
to implement various thing in an ODMS (Object Data Management
System). It consists if a set of interfaces, specification languages,
and a query language. What I see solving the user problem is a module
in designer that lets the end user model business logic, etc.
Dan
On Thu, Jan 16, 2003 at 06:34:02PM -0500, Neil Tiffin wrote:
I think the goal should be a simple to understand method of modifying
the system behavior by non information systems professionals. An
object model (implemented well) is easy to explain to someone who is
not up on the latest OODB vs relational issues. One can talk about
purchase order objects, sales orders etc. In the relational world it
real easy to lose the abstraction because of the need to normalize
data.
There is no question that the relational model is useful, well
understood, effective and may even be the best technical solution.
But whatever you call it, I think an abstraction above the relational
database (or OODB) model is needed to make enterprise apps killer
apps. We need to deal with user customization at a higher level
(even thought the customization may flow down to this level in order
to work.) Unfortunately, the ODMG standard does not (based on my
limited review) help in this area. You really need to be technically
savvy to use it.
What is the current thought regarding end user (non-technical)
customization?
Neil
At 3:26 PM -0600 1/16/03, Jason Cater wrote:
>There's a fine line between bridging two worlds, and trying to emulate an
>OODBMS.
>
>-- Jason
>
>On Thursday 16 January 2003 03:23 pm, Daniel E Baumann wrote:
>> On Thu, Jan 16, 2003 at 02:30:43PM -0600, Jason Cater wrote:
>> > Since we are sharing articles that have bookmarked, here is an article
>> > from a respected relational theorist and practicioner:
>