We have also seen this represented as:
The Component Syntax layout is defined as three Fields:
An Example format would be similar to:
VolumeName"#"NameSpaceType"#"Path
typedef struct { nuint32 nameSpaceType; pnstr8 volumeName; pnstr8 path; } Path_T;
Various AttributeTypes use each field to hold various data.
Transfer Format:
uint32 Length uint32 Name Space unicode Volume Align4 unicode PathBinary:
taggedNameAndString :: = SEQUENCE { objectName LDAPDN, number uint32, string LDAPString }
I suppose that the component is really based on the component number and not the name. This activity makes programmatic deciphering of the attributes really hard as "path" is used in some attributes and "path.xml" {as inDirXML-EntitlementRef is used on others with no programmatic method to determine which it which.
Refer to the individual Fields for more details: