Abstract

Abstract This paper is based on the author's experience of designing a white pages user interface to the X.500 Directory. The paper examines two issues. First, a number of problems arose during the design process which are perceived as being due to inadequacies in the 1988 protocol and service interface. In cases where these issues have been addressed in the 1992/3 standard, the proposed remedies are noted. Second, whilst access to an X.500 directory service is by protocols which have been standardised, the environment in which it runs can vary in many ways: hardware and network infrastructure; directory information tree structure; naming policies; access policies; data coverage and management; effort required for system management. However, new users of the Directory have no knowledge of this lack of uniformity, and often, quite reasonably, expect a fully populated Directory with all information accessible at high-speed. The paper suggests a range of approaches to help the directory user cope with this diversity: some of the recommendations require service agreements and coordination, whilst others have implications for user interface design.

Full Text
Published version (Free)

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call