1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
|
<pre>Network Working Group P. Hoffman
Request for Comments: 4156 VPN Consortium
Category: Historic August 2005
<span class="h1">The wais URI Scheme</span>
Status of This Memo
This memo defines a Historic Document for the Internet community. It
does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2005).
Abstract
This document specifies the wais Uniform Resource Identifier (URI)
scheme that was originally specified in <a href="./rfc1738">RFC 1738</a>. The purpose of
this document is to allow <a href="./rfc1738">RFC 1738</a> to be made obsolete while keeping
the information about the scheme on standards track.
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
URIs were previously defined in <a href="./rfc2396">RFC 2396</a> [<a href="./rfc2396" title=""Uniform Resource Identifiers (URI): Generic Syntax"">RFC2396</a>], which was updated
by <a href="./rfc3986">RFC 3986</a> [<a href="./rfc3986" title=""Uniform Resource Identifier (URI): Generic Syntax"">RFC3986</a>]. Those documents also specify how to define
schemes for URIs.
The first definitions for many URI schemes appeared in <a href="./rfc1738">RFC 1738</a>
[<a href="./rfc1738" title=""Uniform Resource Locators (URL)"">RFC1738</a>]. Because that document has been made obsolete, this
document copies the wais URI scheme from it to allow that material to
remain on standards track.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Scheme Definition</span>
The WAIS URL scheme is used to designate WAIS databases, searches, or
individual documents available from a WAIS database. The WAIS
protocol is described in <a href="./rfc1625">RFC 1625</a> [<a href="./rfc1625" title=""WAIS over Z39.50-1988"">RFC1625</a>]. Although the WAIS
protocol is based on Z39.50-1988, the WAIS URL scheme is not intended
for use with arbitrary Z39.50 services.
Historical note: The WAIS protocol was not widely implemented and
almost no WAIS servers are in use today.
<span class="grey">Hoffman Historic [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc4156">RFC 4156</a> The wais URI Scheme August 2005</span>
A WAIS URL takes one of the following forms:
wais://<host>:<port>/<database>
wais://<host>:<port>/<database>?<search>
wais://<host>:<port>/<database>/<wtype>/<wpath>
If :<port> is omitted, the port defaults to 210. The first form
designates a WAIS database that is available for searching. The
second form designates a particular search. <database> is the name of
the WAIS database being queried.
The third form designates a particular document, within a WAIS
database, to be retrieved. In this form <wtype> is the WAIS
designation of the type of the object. Many WAIS implementations
require that a client know the "type" of an object prior to
retrieval; the type is returned along with the internal object
identifier in the search response. The <wtype> is included in the
URL in order to give the client interpreting the URL adequate
information to actually retrieve the document.
The <wpath> of a WAIS URL consists of the WAIS document-id. The WAIS
document-id should be treated opaquely; it may only be decomposed by
the server that issued it.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Security Considerations</span>
Many security considerations for URI schemes are discussed in
[<a href="./rfc3986" title=""Uniform Resource Identifier (URI): Generic Syntax"">RFC3986</a>]. There are no security considerations listed in [<a href="./rfc1625" title=""WAIS over Z39.50-1988"">RFC1625</a>],
but it should be noted that there is no privacy nor authentication
specified in the WAIS protocol.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Informative References</span>
[<a id="ref-RFC1738">RFC1738</a>] Berners-Lee, T., Masinter, L., and M. McCahill, "Uniform
Resource Locators (URL)", <a href="./rfc1738">RFC 1738</a>, December 1994.
[<a id="ref-RFC2396">RFC2396</a>] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifiers (URI): Generic Syntax", <a href="./rfc2396">RFC 2396</a>,
August 1998.
[<a id="ref-RFC3986">RFC3986</a>] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66,
<a href="./rfc3986">RFC 3986</a>, January 2005.
[<a id="ref-RFC1625">RFC1625</a>] St. Pierre, M., Fullton, J., Gamiel, K., Goldman, J.,
Kahle, B., Kunze, J., Morris, H., and F. Schiettecatte,
"WAIS over Z39.50-1988", <a href="./rfc1625">RFC 1625</a>, June 1994.
<span class="grey">Hoffman Historic [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc4156">RFC 4156</a> The wais URI Scheme August 2005</span>
Author's Address
Paul Hoffman
VPN Consortium
127 Segre Place
Santa Cruz, CA 95060
US
EMail: paul.hoffman@vpnc.org
<span class="grey">Hoffman Historic [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc4156">RFC 4156</a> The wais URI Scheme August 2005</span>
Full Copyright Statement
Copyright (C) The Internet Society (2005).
This document is subject to the rights, licenses and restrictions
contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
<a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf-
ipr@ietf.org.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
Hoffman Historic [Page 4]
</pre>
|
