--On Tuesday, November 16, 2004 12:58 PM +0100 Henry Story <[EMAIL PROTECTED]> wrote: > > Ok, so perhaps you would really like the model in which a Feed is a > subclass of Entry.
That is the normal approach for compound documents. But I still don't see a convincing reason. And I do favor short specs. 1. People have been working on compound documents without much success for at least fifteen years. To me, that indicates that they are either very hard or not very useful. 2. I have not seen a use case where a feed would be treated as an entry. If it is common, not just possible, for a feed to be an entry, then we need this. Otherwise, we don't. Show me the real world use cases. 3. Identity is not sufficient for something to be the same class. It is common for the same chemical to have multiple uses, each with different trademarks, packaging, production, and sales figures. From a business perspective, those identical chemicals must be treated as separate things, e.g. a dessert topping and a floor wax. wunder -- Walter Underwood Principal Architect, Verity
