====== File Path ======

[[dido:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]

===== Discussion =====

A **File Path** identifies a location within a hierarchical file or resource naming structure.

A File Path consists conceptually of an ordered sequence of path components. A path component may identify a directory, container, intermediate location, or terminal [[dido:99_annexes:annex-b-terms-and-definitions:f:filename|Filename]].

For example:

><code>
reports/2026/quarterly/report.pdf
</code>

represents a hierarchy leading to the Filename:

><code>
report.pdf
</code>

The conceptual File Path does not prescribe a particular path separator or path syntax.

Different logical or physical environments may represent paths using constructs such as:

><code>
/
\
:
URI syntax
UNC syntax
container-specific syntax
</code>

A File Path may be absolute, relative, rooted, or otherwise contextual according to the applicable naming environment.

Although a hierarchical file structure has namespace-like characteristics, a File Path is distinct from a [[dido:99_annexes:annex-b-terms-and-definitions:n:namespace|Namespace]]. A Namespace establishes a naming and interpretation context, while a File Path identifies a location within a hierarchical naming structure.

===== Definition =====

//An ordered representation of a location within a hierarchical file or resource naming structure.//

===== Source =====

  * DIDO Solutions

===== Note =====

A File Path does not prescribe a particular filesystem, operating system, separator character, or encoding.

A File Path may include a Filename as its terminal component, but a File Path may also identify a directory or other intermediate location.

===== Example =====

The following conceptual File Path:

><code>
models/testing/test-definition.json
</code>

contains the ordered path components:

><code>
models
testing
test-definition.json
</code>

The final component is the Filename:

><code>
test-definition.json
</code>

The use of ''/'' in the example is illustrative and does not prescribe a particular logical representation.

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>