[
Lists Home |
Date Index |
Thread Index
]
As a means to create a consumable document for others to
generate instances of say, queries, sure. The dynamic
aspects of the generation are merely convenient. Note
that VisualStudio.Net autogenerates schemas for datasets.
Good for data dictionary work.
len
From: Peter Hunsberger [mailto:peter.hunsberger@gmail.com]
Sent: Wednesday, November 03, 2004 10:05 AM
On Wed, 3 Nov 2004 10:00:17 -0600, Bullard, Claude L (Len)
<len.bullard@intergraph.com> wrote:
> I won't go quite that far. I may need to create a schema for
> others to inspect because I don't want to open up an ODBC
> connection for them to my metadata tables. In that case,
> providing an XML Schema for them to consume or its analog
> (the mammals are relentless reinovators), makes sense.
> I agree that in the environment I work in, modeling in
> XML Schema isn't very useful.
Exactly, that's why I questioned whether an XML schema was ever the
best "model".... I might have a need for XML schema to travel with
certain instance data, but do I need them otherwise?
|
