defines the tri-state transfer modes.
defines the usage of a logical filename.
narrowly defines a string subset safe in most file systems as file name (excluding path).
defines an ASCII-restricted set of identifiers for graph nodes (jobs, daxes, dags).
describes restriction on a version number.
defines the valid architecture types.
defines the valid OS types.
defines the attribute set decribing system information.
defines the legal namespaces of execution profiles.
defines metadata
defines notifications.
type of the ubiquitous profile element.
defines just a filename.
logical filename representation. Add "executable" attribute yourself.
type for job-like uses elements that refers either to data or to executables.
type for transformation uses elements that refers either to data or to executables.
common elements in job, dag, and dax nodes.
Arguments on the commandline, text interrupted by filenames
Job-level metadata
Execution environment specific data to be passed to lower levels.
stand-in for "file", linkage is "input" fixed.
stand-in for "file", linkage is "output" fixed.
stand-in for "file", linkage is "output" fixed.
very simple notifications.
data or executable catalog entry type.
file- and executable-level metadata
abstract DAG in XML.
A dependency must not be used before all the jobs it references were declared. It is suggested to keep all jobs, all deps and all lfns together, a total of three sections.
workflow-level metadata
very simple workflow-level notifications (no warrantees).
Optional list of all data files used. The new extension is a kind of included replica catalog.
Optional list of all executables. The new extension is a kind of included transformation catalog.
repeatable simple notification forwarded to job instantiation.
An aggregation of executables as its own item.
A job component is one of a true job, an included DAG, or an included DAX. The recursive "adag" is an unsupported place-holder.
Job specification in terms of a logical transformation.
An already concrete workflow, stored mostly as file reference.
A workflow to be planned, stored mostly as file reference.
List of dependencies.
parent node refering to a job.