Gloss of "External Name"

While the principle name space used by the FDL consists of Abstract Identifiers, a relatively small number of identifiers must be maintained that make sense outside the FDL process in order to identify FDL entities outside the FDL process. When connected to the FDL, Clients can refer to abstract ids and communicate them via the FDL to other connected clients. But in order for clients to communicate identifiers outside the FDL, one must have a concrete substitute that can be later resolved when connected to the FDL. For example, one person may wish to tell another person via e-mail how to find an object in the FDL (from which many other objects can be found); to do so the first person simply needs to have the FDL attach a concrete name to the object, and communicate it to the second person, who then requests the object associated (perhaps temporarily) with the received concrete name. External names are bound to Objects or Closed Maps via Name Server objects. IF YOU CAN SEE THIS go to http://www.cs.cornell.edu/Info/People/sfa/Nuprl/Shared/Xindentation_hack_doc.html