|
|
1.1 root 1: % run this through LaTeX with the appropriate wrapper
2:
3: \chapter {Introduction}
4: This document is {\em The User's Handbook\/} for the
5: NYSERNet/PSI White Pages Pilot.
6: The goal of \thebook/ is to provide a user with enough information to be able
7: to make effective use of the white pages service.
8: In practical terms,
9: this means that \thebook/ provides information on how
10: to use the white pages from your host.
11:
12: The OSI Directory is used to provide the white pages service.
13: \thebook/ is not intended as a tutorial nor a detailed description
14: of the OSI Directory.
15: However,
16: in order to make effective use of the white pages,
17: it is necessary to understand some rudimentary Directory concepts.
18:
19: Your comments are welcome!
20: The OSI Directory is a new, complex technology.
21: Although \thebook/ attempts to be straight-forward it probably doesn't
22: succeed all the time.
23: If you have comments on this document, send them to the Internet
24: mailbox
25: \begin{quote}\begin{verbatim}
26: [email protected]
27: \end{verbatim}\end{quote}
28: so that \thebook/ can be improved.
29:
30: If you are interested in sharing about experiences with other users of the
31: white pages, drop a note to
32: \begin{quote}\begin{verbatim}
33: [email protected]
34: \end{verbatim}\end{quote}
35: and ask to be added to the
36: \begin{quote}\begin{verbatim}
37: [email protected]
38: \end{verbatim}\end{quote}
39: discussion group.
40:
41: \newpage
42:
43: \section* {Related Documentation}
44: In theory,
45: \thebook/ is the only reference needed by all but the most sophisticated of
46: users.
47: However,
48: if you're interested in finding out more about the NYSERNet/PSI White Pages
49: Pilot Project and the underlying mechanisms and technology,
50: there are a few documents you might want to look at.
51:
52: The white paper
53: {\em An Introduction to a NYSERNet White Pages Pilot Project\/}
54: introduces the goals and phases of the pilot project.
55: In addition,
56: site administrators are provided with a document called
57: {\em NYSERNet/PSI White Pages Pilot Project: Administrator's Guide},
58: or simply \theguide/.
59:
60: The research note {\em The Design of QUIPU\/} describes the design of the
61: software used for the pilot project,
62: whilst {\em Volume Five\/} of the ISODE User's Manual,
63: henceforth termed \volfive/,
64: describes the implementation of the software.
65:
66: Your site administrator has access to all of these documents and can provide
67: them to you as requested.
68:
69: \newpage
70:
71: \input{wp-intro}
72:
73: \input{dir-intro}
74:
75: \section {Where to turn for help}
76: The software supporting the pilot project is the QUIPU implementation
77: of the OSI Directory,
78: which is a part of the ISO Development Environment (ISODE).
79:
80: QUIPU was originally developed as a part of the INCA project
81: (under the auspices of the ESPRIT initiative of the EEC).
82: The Inca of Peru did not have writing.
83: Instead,
84: they stored information on strings,
85: carefully knotted in a specific manner with colored thread,
86: and attached to a larger rope.
87: Such a device was known as a {\em Quipu\/}
88: (pronounced {\em kwip-ooo}).
89: The encoding was obscure,
90: and could only be read by selected trained people:
91: the {\em Quipucamayocs}.
92: The Quipu was a key component of Inca society,
93: as it contained information about property and locations throughout
94: the extensive Inca empire.
95:
96: The pilot sponsors and the administrators of the participating organizations
97: form the {\em camayocs\/} for the pilot project.
98: There is a special mailing list
99: \begin{quote}\small\begin{verbatim}
100: [email protected]
101: \end{verbatim}\end{quote}
102: which each \camayoc/ belongs to.
103:
104: If you need help with the white pages service,
105: you should first contact your site administrator.
106: If you are unable to do so,
107: then you should contact another \camayoc/ or drop a note to the
108: \verb"wpp-camayocs" list.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.