Lists Home |
Date Index |
On Wed, 3 Nov 2004 09:46:39 -0600, Bullard, Claude L (Len)
> If I already have a database with the metadata in it needed to
> generate an application, why would I need a schema too?
> That I might need (likely will need) multiple tables to do that isn't
> that big a deal.
> I might need a schema when I want to expose the
> constraints and metadata to an external user(s) (eg, doesn't
> want to consume my database tables). If there is a
> dynamic aspect to the transaction that I need to
> communicate, then dynamically generating a schema
> is a good idea particularly if it only governs
> a limited set of instances or just one.
> OTW, a property bag is a property bag is a property bag.
Or as Burak just wrote on the "Describing hierarchies with XML" thread:
> [Singing the song of OO abstraction] "Model common things only once."
The fact is, the best model isn't always (ever? :-) an XML schema...