In Part 3 - "https://reference.opcfoundation.org/Core/Part3/v105/docs/6.2.5":
All targets of forward hierarchical References from a TypeDefinitionNode shall have a BrowseName that is unique within the TypeDefinitionNode. The same restriction applies to the targets of forward hierarchical References from any InstanceDeclaration. This means that any InstanceDeclaration within the InstanceDeclarationHierarchy can be uniquely identified by a sequence of BrowseNames. This sequence of BrowseNames is called a BrowsePath.

• The last sentences assumes that a "BrowsePath" can only be constructed with "hierarchical References" which is not true.

In Part 4 - "https://reference.opcfoundation.org/Core/Part4/v104/docs/5.8.4" -> 5.8.4.2 -> Table 40 BrowsePath is defined as a Type:
browsePaths [] | BrowsePath | List of browse paths for which NodeIds are being requested. This structure is defined in-line with the following indented items.
startingNode | NodeId | NodeId of the starting Node for the browse path.
relativePath | RelativePath | The path to follow from the startingNode.
| The last element in the relativePath shall always have a targetName specified.
| This further restricts the definition of the RelativePath type.
| The Server shall return Bad_BrowseNameInvalid if the targetName is missing.
| The RelativePath structure is defined in 7.26.