[
Lists Home |
Date Index |
Thread Index
]
We do it for some things. As one if forced to support more
and different target hosting environments, one does it more.
For example, we do:
1. XML model of metadata of databases. Then generate the
scripts to create tables for different database vendors.
This has some definite advantages.
2. Use metadata collectors (just a db) that gets metadata
from the application plus human annotation interface. Then
generate ERDs for customers that like these with all the
usual web page navigation and popup magic using a combination
of script, HTML and VML. Very popular item it turns out.
Intelligence aside, a report is a report is a report.
I could make the second one a web service but there is no
point really. There is nothing inherently dynamic or
frequent about them. Just push the button for every
version of the product after the metadatabase is updated,
and generate all of the little mini-apps. Old school.
len
From: Hunsberger, Peter [mailto:Peter.Hunsberger@STJUDE.ORG]
It's an after the fact rationalization, but; that's seems partly why we
have a metadata model that's not coded directly in XML: you want to be
free to produce multiple model representations as needed...
> Anyway, from the answers, I see that yes indeed we are far
> away from it...
Sigh, ain't it the truth!
Peter Hunsberger
|
