Re: Resiliency To New Data Requirements

From: Jay Dee <ais01479_at_aeneas.net>
Date: Wed, 09 Aug 2006 03:35:38 GMT
Message-ID: <eKcCg.45806$vl5.34673@tornado.ohiordc.rr.com>

Neo wrote:

>>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?

Adjective? Class? Noun? Neo, they're variables.

What makes any variable an adjective or a noun or an index or an accumulator or a cache or a list or a queue or a tree or a pointer or a hash or a _____? How would any application know what its variables are? (Androids, I don't know about.) Received on Tue Aug 08 2006 - 22:35:38 CDT