Re: Resiliency To New Data Requirements

> And we've arrived at an impasse: you're interpreted a design, decided that some attributes are "classifications" rather than "adjectives" and that others are not "nouns" and cobbled together a dbd design that represents your reinterpretation of whatever it was being represented.

The general form of the following Tutorial D script ...

sage += relation {tuple { name 'Bob' };
jerk += relation {tuple { name 'Neo' } } ; state += relation {tuple { name 'Bob', state 'on' }, ... } ;

... seems to be:
X1 += relation { tuple{...}, ... };

In general, how would an application (ie an andriod) know to interpret X1 as an adjective (vs a class) in some cases and a noun in others cases? Received on Mon Aug 07 2006 - 16:13:19 CEST