#### Significance of Typed and Untyped Entry Names

Next are the static declarations for the lowest layer of objects that make up the global name (distinguished name) of the CDS directory entry you want to read. These lowest-level objects contain the string values for each part of the name. Remember that the first three parts of the name (excluding the global prefix /.../, which is not represented) constitute the cell name, as follows:

/C=US/O=OSF/OU=DCE/

In this example, assume that GDS is being used as the cell's global directory service, so the cell name is represented in X.500 format, and each part of it is typed in the object representation; for example, DS_A_COUNTRY_NAME is the DS_ATTRIBUTE_TYPE in the Country_String_Object. If you were using DNS, the cell name might be something like the following:

osf.org.dce

In this case the entire string osf.org.dce would be held in a single object whose DS_ATTRIBUTE_TYPE would be DSX_TYPELESS_RDN.

DSX_TYPELESS_RDN is a special type that marks a name piece as not residing in an X.500 namespace. If the object resides under a typed X.500 name, as is the case in the declared object structures, then it serves as a delimiter for the end of the cell name GDS looks up, and the beginning of the name that is passed to a CDS server in that cell, assuming that the cell has access to GDS; if not, such a name cannot be resolved. In the following name, the untyped portion is at the beginning:

/.../osf.org.dce/hosts/zenocrate/self

In this case the name is passed immediately by XDS via the local CDS (and the GDA) to DNS for resolution of the cell name. Thus, the typing of entry names determines which directory service a global directory entry name is sent to for resolution.

####