This XML Schema allows to validate either complete VDL scripts, or specific VDL chunks. defines the type to be used for "lfn" elements. defines the type to be used for "use" elements. describe a tranformation or derivation with metadata. defines the three basic containers for parameters. defines the usable Condor universes. defines the usage of a logical filename. defines the legal namespaces of execution profiles. A textual representation of verbatim values. A simple element for text or files. Mixed content allowing only "lfn" in derivations. You can use either pure text or the "lfn" element. Mixed content allows mixing, but you should not mix. A list element containing simple elements. List of mixed content allowing only "lfn" in derivations. A "transformation" describes the specification of process environment with placeholders A "transformation" describes the specification of process environment with placeholders Each parameter is declared using the "declare" element, specifying the name and container type. A command line argument spec consists of an arbitrary number of namable chunks. "use" references a bound parameter. Each "profile" element declares one DAGMan, Condor, or Unix envronment variable. Mixed content allowing only "use" in transformations. Mixed content allowing only "use" in transformations. A "derivation" contains actual parameters. This element must occur, even if the list is empty. A "derivation" makes use of previous or outside transformations, and fills the placeholders with specific values. The "pass" element established the binding between an actual parameter with its named formal counterpart. The virtual data modification language. A VDL document consists of any number of "transformation" and "derivation" elements in arbitrary order.