!!! Overview 
The [{$pagename}] represents the [EDirectory] Syntax [SYN_PATH 15|X-NDS_SYNTAX] which is a [Component Syntax].

We have also seen this represented as: 
* LDAP Name: Tagged Name and String 
* Path 
* 

!! LDAP Format 
Typically attributes based on [{$pagename}] syntax may be retrieved as a String.

The [Component Syntax] layout is defined as three Fields:
* [VolumeName Field]
* [NameSpaceType Field]
* [Path Field]

An [Example] format would be similar to:
{{{ 
VolumeName"#"NameSpaceType"#"Path
}}}

!! Data Structure and Format 
API Data Structure 
{{{ 
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 Path 
}}} Binary: 
{{{ 
taggedNameAndString :: = SEQUENCE { 
objectName LDAPDN, 
number uint32, 
string LDAPString 
} 
}}} 

!! [Matching Rules] 
* [EQUALITY]
* [SUBSTR]
* [APPROXIMATE] — Not currently supported through LDAP !!! Remarks 
Attributes using this syntax can set size limits. !! Our Comments 
Interestingly, although the attribute shows in the schema to be of type 2.16.840.1.113719.1.1.5.1.15 which shows as "path", Novell shows this component name should be path and not path.xml. 

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 in[DirXML-EntitlementRef] is used on others with no programmatic method to determine which it which. 

Refer to the individual Fields for more details:
* [VolumeName Field]
* [NameSpaceType Field]
* [Path Field]

!! Syntax Details
* [OID]: [2.16.840.1.113719.1.1.5.1.15] 
* [X-NDS_SYNTAX]: 15 
!! More Information 
There might be more information for this subject on one of the following:[{ReferringPagesPlugin before='*' after='\n' }]