Low-Level Dependencies (migrated from T3Dv1 to T3Qv2)

The generated low-level dependencies serve (currently) exclusively for custom processing by third party tools for purposes such as slicing or markup of definitions related to a particular module definition (e.g. approved / locked definitions, etc.). That is the generated content for the low-level dependencies is only in an intermediate XML format and there is no HTML view for it (since it is roughly an abstracted version of the main view). Some form of HTML presentation may become available in future releases.

The low-level dependencies can be thought of as a blend between an abstracted version of the main view and a low-level version of the import view, featuring a compact representation of the low-level dependencies at the module definition (element) level - it contains all the module definitions and all the known elements referenced directly within each module definition.

The structure of the low-level dependencies intermediate representation features a list of all elements, where for each element the following pieces of information are available:

• A unique ID of the element so that it can be uniquely referenced
• The name of the element as per its identifier
• The top-level type of the element (e.g. type, function, altstep, etc.)
• Its definition start location (the line where the definition of the element starts)
• The name of the containing module where the element is defined
• The name of the file containing the module where the element is defined
• A list of the element IDs for all the elements referenced within the current element

Upon recursive resolution a dependency graph can be created for a set of related elements.

More details about the technical side of the low-level dependencies can be found in the technical documentation.