This XML Schema allows to validate either complete VDL scripts, or VDL "chunk" elements that are used with parameter files and command line arguments. 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. describe a tranformation or derivation with metadata. defines the type to be used for "lfn" elements. defines the type to be used for "lfn" constants in transformations. defines the type to be used for "use" elements. defines the type to be used for "executable" and pre/post scripts. 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. List of mixed content allowing only "lfn" in derivations. Each element in a list may have an optional index for sparse vectors. 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 "transformation" describes the specification of process environment with placeholders A "transformation" describes the specification of process environment with placeholders The parameter list to the "transformation" can contain any number of parameter declarations, which are placeholder for parameter passing. Each parameter is declared using the "declare" element, specifying the name and container type. For default values in transformations and derivation passed values. The only mandatory part is the spec of an executable, or another transformation to invoke. Temporary declarations only provide bindings between parameter and temp. lfns. No other container types are allowed. Mixed content allowing only "use" in transformations. A transformation is either simple or a compound transformation. A compound transformation consists of one or more calls to other transformations. Each invoked transformation will be passed the required argument list. The "pass" element established the binding between an actual parameter with its named formal counterpart. The container type of the formal arg must match the chosen content container. Mixed content allowing only "use" in transformations. A lists consists of zero or more "i" items. Each element in a list may have an optional index for sparse vectors. Mixed content allowing only "use" in transformations. A simple transformation consists of an executable with optional command line arguments. Any application must contain an executable, but may also feature DAGMan pre- and postscripts. An optional DAGMan prescript to run in scheduler universe. The name of the executable itself. An optional DAGMan postscript to run in scheduler universe. A command line argument spec consists of an arbitrary number of namable chunks. A "chunk" describes an arbitrary, namable piece of a parameter file or command line arg for an executable. Each chunk may contain an arbitrary number of variable references "use", explicit logical filenames "lfn" and rendering instructions "br". "use" references a bound parameter. "br" is a whitespace mark-up tag for chunk rendering. visual markup Experimental feature, very unsure about this! 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. For default values in transformations and derivation passed values. The virtual data modification language. A VDL document consists of any number of "transformation" and "derivation" elements in arbitrary order.