Cart
[Home] [By Thread] [By Date] [Recent Entries]
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. len From: Jeff Greif [mailto:jgreif@a...] Sent: Wednesday, November 03, 2004 9:35 AM >> Why generate schemas dynamically? What's the advantage of an XML >> Schema language for this? Consider an application that consumes schemas, say, to generate forms for user input. (Based on a type in a schema, it generates a form.). Sometimes the type can be specialized to make things easier for the human entering the data, or for validation of the result.
|
