On Jun 9, 2009, at 11:49 AM, Alex Miller wrote:
Did you guys kill off the command-line vdb tool? Seems like that
was one possible direction for importing physical metadata and
potentially to add views within a lightweight tool.
We could still go this direction, except for a) it's not really that
lightweight, b) it does nothing to allow for integration with metadata
from other products, and c) I don't believe it even supported views,
just access to multiple physical sources.
Another possibly crazy idea that I would seriously consider these
days is using an embedded dsl / builder in a language like Groovy to
define vdb metadata. You could take the groovy script itself as the
vdb definition or even run it to produce a compiled vdb. If you
were clever enough, the dsl could be extensible to allow metadata
creation with new metamodels. But this is probably only a valid
solution if you expect a developer or other suitably precise user to
be the target.
I believe the developer audience you mentioned is a serious concern,
and as with your first suggestion, this also provides no type of
standard with which to leverage any sort of interoperability with
other products.