Re: Demo: Things in Hierarchies (w/o RM/SQL)

> I wonder, would it help to stem the tide if the more experienced
> practitioners here would just posit a real-world problem to be solved
> (rather than cats and dogs, parent-child, etc.) Given an interesting
> enough problem, that may take quite a while to address, if it can be
> addressed at all with Neo's stuff. OLTP with 1000 TPS requirement?
> DataWarehousing with lots of summary reports, each different...
> maybe 80 per day,

A limited methodology (ie RM) will be more efficient than a more general methodology (ie Thing Model, the foundation for XDb1 & 2) when both are applied to an application within the limited methodology's scope. For years, RMers have propogated the falsity that RM is the most general/generic methodology. I am here to prove them wrong with examples outside RM's ideal scope.

RM is analogous to a set of fixed size wrenches. TM is analogous to an adjustable wrench. Each has it's advantages and disadvantages.

In my estimation, TM is geared towards AI-type applications. Are you game? Received on Sat Nov 06 2004 - 19:54:08 CET