Re: The stupidest design I ever saw

> > > > "Formal Concept Analysis in Information Science" article by Uta Priss
> > > > http://upriss.org.uk/papers/arist.pdf
> > >
> > > 1. Identify all the cylindric sets
> > > 2. Connect nodes with the partial order relation
> >
> > I challenge anyone to follow the above steps and create the shown
> > hierarchy from the table, where the names of objects and classes are
> > simply identified by different letters (to prevent a user from
> > introducing knowledge not encoded in the table).
>
> Perhaps you could award $1000 to anyone who meets your challenge
> -- as I recall that would not cost you anything, Neo. ;-)

For you Dawn it is $1,000,000 :)

> > Now a friendly alien from Mars (named bill) arrives on Earth. He is capable of using his tools to dignose health problems and write prescriptions to cure various ailments. This alien is a doctor but he is not a human. To avoid such dilemmas start with a non-hierarcal arrangement of classes as shown below. (It is difficult for you and most other people to realize that there is an indirect, but no direct, relationship between classes human and doctor, which can be derived from the data below).
.
> Then we need to redefine our terms. If we had said that doctor is-a human, then we cannot say this alien is a doctor until we redefine that is-a relationship.
.
Perhaps you are one of the people for whom it is difficult to realize that there is an indirect/derivable, but no direct, relationship between classes human and doctor. Perhaps you prefer to setup initial data structures that will allow future dilemmas so that you can restructure shemas, migrate data and update related scripts/queries/code later. Received on Tue Apr 11 2006 - 16:51:52 CEST