database
Click on the red underlined text to get to the source
... have recently become available on the Internet. However, these
freely-distributable databases are not accessible via a uniform
interface, and are not accessible from a single site. They are often
...
... interface, and are not accessible from a single site. They are often
small and incomplete individually, but would collectively provide an
interesting and useful database of English words. Examples include
the Jargon file [JARGON], the WordNet database ...
... database of English words. Examples include
the Jargon file [JARGON], the WordNet database [WORDNET], MICRA's
version ...
...
The webster protocol is not suitable for providing access to a large
number of separate dictionary databases, and extensions to the
current webster protocol were not felt to be a clean solution to the
dictionary database ...
... databases, and extensions to the
current webster protocol were not felt to be a clean solution to the
dictionary database problem.
The DICT protocol is designed to provide access to multiple
...
...
The DICT protocol is designed to provide access to multiple
databases. Word definitions can be requested, the word index can be
searched (using an easily extended set of algorithms), information
...
... about the server can be provided (e.g., which index search strategies
are supported, or which databases are available), and information
about a database can be provided (e.g., copyright, citation, or
...
... are supported, or which databases are available), and information
about a database can be provided (e.g., copyright, citation, or
distribution information). Further, the DICT protocol has hooks that
can be used to restrict access to some or all of the databases ...
... database can be provided (e.g., copyright, citation, or
distribution information). Further, the DICT protocol has hooks that
can be used to restrict access to some or all of the databases.
...
... This server is only an interface between programs and the dictionary
databases. It does not perform any user interaction or
presentation-level functions.
...
... command = cmd-word *<WS cmd-param>
cmd-word = atom
cmd-param = database / strategy / word
database = atom
...
...
DEFINE database word
...
...
This command will look up the specified word in the specified
database. All DICT servers MUST implement this command.
If the database ...
... database. All DICT servers MUST implement this command.
If the database name is specified with an exclamation point (decimal
code 33, "!"), then all of the databases will be searched until a
...
... If the database name is specified with an exclamation point (decimal
code 33, "!"), then all of the databases will be searched until a
match is found, and all matches in that database will be displayed.
...
... code 33, "!"), then all of the databases will be searched until a
match is found, and all matches in that database will be displayed.
If the database name is specified with a star (decimal code 42, "*"),
...
... match is found, and all matches in that database will be displayed.
If the database name is specified with a star (decimal code 42, "*"),
then all of the matches in all available databases will be displayed.
...
... If the database name is specified with a star (decimal code 42, "*"),
then all of the matches in all available databases will be displayed.
In both of these special cases, the databases will be searched in the
...
... then all of the matches in all available databases will be displayed.
In both of these special cases, the databases will be searched in the
same order as that printed by the "SHOW DB" command.
...
... following status code 151 give the word retrieved, the name of the
database (which is the same as the first column of the SHOW DB
command), and a short description for the database ...
... database (which is the same as the first column of the SHOW DB
command), and a short description for the database (which is the same
as the second column of the SHOW DB command). The short name is
...
... 550 Invalid database, use "SHOW DB" for list of databases
552 No match
150 n definitions retrieved - definitions follow
...
... 552 No match
150 n definitions retrieved - definitions follow
151 word database name - text follows
250 ok (optional timing information here)
...
...
For code 151, parameter 1 is the word retrieved, parameter 2 is the
database name (the first name as shown by "SHOW DB") from which the
definition has been retrieved, and parameter 3 is the the short
...
... DB") from which the
definition has been retrieved, and parameter 3 is the the short
database description (the second column of the "SHOW DB" command).
...
...
MATCH database strategy word
...
... query suggests).
If the database name is specified with an exclamation point (decimal
code 33, "!"), then all of the databases will be searched until a
...
... If the database name is specified with an exclamation point (decimal
code 33, "!"), then all of the databases will be searched until a
match is found, and all matches in that database will be displayed.
...
... code 33, "!"), then all of the databases will be searched until a
match is found, and all matches in that database will be displayed.
If the database name is specified with a star (decimal code 42, "*"),
...
... match is found, and all matches in that database will be displayed.
If the database name is specified with a star (decimal code 42, "*"),
then all of the matches in all available databases will be displayed.
...
... If the database name is specified with a star (decimal code 42, "*"),
then all of the matches in all available databases will be displayed.
In both of these special cases, the databases will be searched in the
...
... then all of the matches in all available databases will be displayed.
In both of these special cases, the databases will be searched in the
same order as that printed by the "SHOW DB" command.
...
... PZ85].
If no matches are found in any of the searched databases, then status
code 552 will be returned.
...
... matched words, one per line, in the form:
database word
This makes the responses directly useful in a DEFINE command.
...
... 550 Invalid database, use "SHOW DB" for list of databases
551 Invalid strategy, use "SHOW STRAT" for a list of strategies
552 No match
...
... A Note on Virtual Databases ...
...
The ability to search all of the provided databases using a single
command is given using the special "*" and "!" databases.
...
... search all of the provided databases using a single
command is given using the special "*" and "!" databases.
However, sometimes, a client ...
... client may want to search over some but not all
of the databases that a particular server provides. One alternative
is for the client to use the SHOW DB ...
... client to use the SHOW DB command to obtain a list of
databases and descriptions, and then (perhaps with the help of a
human), select a subset of these databases for an interactive search ...
... databases and descriptions, and then (perhaps with the help of a
human), select a subset of these databases for an interactive search.
Once this selection has been done once, the results can be saved, for
...
... configuration file.
Another alternative is for the server to provide "virtual" databases
which merge several of the regular databases into one. For example,
...
... Another alternative is for the server to provide "virtual" databases
which merge several of the regular databases into one. For example,
a virtual database may be provided which includes all of the
...
... which merge several of the regular databases into one. For example,
a virtual database may be provided which includes all of the
translating dictionaries, but which does not include regular
dictionaries or thesauri. The special "*" and "!" databases ...
... database may be provided which includes all of the
translating dictionaries, but which does not include regular
dictionaries or thesauri. The special "*" and "!" databases can be
considered as names of virtual databases which provide access to all
...
... dictionaries or thesauri. The special "*" and "!" databases can be
considered as names of virtual databases which provide access to all
of the databases. If a server implements virtual databases ...
... considered as names of virtual databases which provide access to all
of the databases. If a server implements virtual databases, then the
special "*" and "!" databases ...
... databases which provide access to all
of the databases. If a server implements virtual databases, then the
special "*" and "!" databases should probably exclude other virtual
...
... databases. If a server implements virtual databases, then the
special "*" and "!" databases should probably exclude other virtual
databases (since they merely provide information duplicated in other
...
... special "*" and "!" databases should probably exclude other virtual
databases (since they merely provide information duplicated in other
databases). If virtual databases ...
... databases (since they merely provide information duplicated in other
databases). If virtual databases are supported, they should be
listed as a regular database ...
... databases (since they merely provide information duplicated in other
databases). If virtual databases are supported, they should be
listed as a regular database with the SHOW DB ...
... databases). If virtual databases are supported, they should be
listed as a regular database with the SHOW DB command (although,
since "*" and "!" are required, they need not be listed).
...
... since "*" and "!" are required, they need not be listed).
Virtual databases are an implementation-specific detail which has
absolutely no impact on the DICT protocol. The DICT protocol views
virtual and non-virtual databases ...
... databases are an implementation-specific detail which has
absolutely no impact on the DICT protocol. The DICT protocol views
virtual and non-virtual databases the same way.
We mention virtual databases ...
... databases the same way.
We mention virtual databases here, however, because they solve a
problem of database selection which could also have been solved by
...
... We mention virtual databases here, however, because they solve a
problem of database selection which could also have been solved by
changes in the protocol. For example, each dictionary could be
assigned attributes, and the protocol could be extended to specify
...
... changes in the protocol. For example, each dictionary could be
assigned attributes, and the protocol could be extended to specify
searches over databases with certain attributes. However, this
needlessly complicates the parsing and analysis that must be
performed by the implementation. Further, unless the classification
...
...
system is extremely general, there is a risk that it would restrict
the types of databases that can be used with the DICT protocol
(although the protocol has been designed with human-language
...
... (although the protocol has been designed with human-language
databases in mind, it is applicable to any read-only database
application, especially those with a single semi-unique alphanumeric
key and textual data).
...
... language
databases in mind, it is applicable to any read-only database
application, especially those with a single semi-unique alphanumeric
key and textual data).
...
...
Displays the list of currently accessible databases, one per line, in
the form:
...
... the form:
database description
The textual body of the database ...
... database description
The textual body of the database list is terminated with a CRLF
period CRLF ...
... CRLF sequence. All DICT servers MUST implement this command.
Note that some databases may be restricted due to client domain or
...
... user authentication (see the AUTH and SASLAUTH commands in
sections 3.11 and 3.12). Information about these databases is not
available until authentication is performed. Until that time, the
...
... authentication is performed. Until that time, the
client will interact with the server as if the additional databases
did not exist.
...
... Response code 110 requires a special parameter. Parameter 1
must be the number of databases available to the user.
...
...
SHOW INFO database
...
...
Displays the source, copyright, and licensing information about the
specified database. The information is free-form text and is
suitable for display to the user in the same manner as a definition.
The textual body of the information is terminated with a CRLF ...
... Displays local server information written by the local administrator.
This could include information about local databases or strategies,
or administrative information such as who to contact for access to
databases ...
... local databases or strategies,
or administrative information such as who to contact for access to
databases requiring authentication. All DICT servers MUST implement
this command.
...
... encodings.
In the future, after significant experience with large databases in
various languages has been gained, and after evaluating the need for
...
...
Authentication may make more dictionary databases available for the
current session. For example, there may be some publicly
...
... current session. For example, there may be some publicly
distributable databases available to all users, and other private
databases available only to authenticated users ...
... distributable databases available to all users, and other private
databases available only to authenticated users. Or, a server may
require authentication ...
... results of successful AUTH authentication: more dictionary databases
may become available for the current session.
...
... dict://<user>;<auth>@<host>:<port>/d:<word>:<database>:<n>
dict://<user>;<auth>@<host>:<port ...
... dict://<user>;<auth>@<host>:<port>/m:<word>:<database>:<strat>:<n>
The "/d" syntax specifies the DEFINE command (section 3.2), whereas
...
...
Some or all of "<user>;<auth>@", ":<port>", "<database>", "<strat>",
and "<n>" may be omitted.
...
... port>" is omitted, the default port (2628) SHOULD be used. If
"<database>" is omitted, "!" SHOULD be used (see section 3.2). If
"<strat>" is omitted, "." SHOULD be used (see section 3.3).
...
...
This protocol was designed so that flat text databases can be used
with a server after a minimum of analysis and formatting. Our
experience is that merely constructing an index for a database ...
... databases can be used
with a server after a minimum of analysis and formatting. Our
experience is that merely constructing an index for a database may be
sufficient to make it useful with a DICT server. The ability to
serve preformatted text is especially important since freely-
...
... sufficient to make it useful with a DICT server. The ability to
serve preformatted text is especially important since freely-
available databases are often distributed as flat text files without
any semantic mark-up information (and often contain "ASCII ...
... precludes the automation of even simple formatting).
However, given a database with sufficient mark-up information, it may
be possible to generate output in a variety of different formats
(e.g., simple HTML ...
... indicates the response has defined arguments that must be provided.
* 110 n databases present - text follows
* 111 n strategies available - text follows
112 database ...
... databases present - text follows
* 111 n strategies available - text follows
112 database information follows
113 help text follows
114 server information follows
...
... 130 challenge follows
* 150 n definitions retrieved - definitions follow
* 151 word database name - text follows
* 152 n matches found - text follows
210 (optional timing and statistical information here)
...
... 531 Access denied, use "SHOW INFO" for server information
532 Access denied, unknown mechanism
550 Invalid database, use "SHOW DB" for list of databases
...
... 550 Invalid database, use "SHOW DB" for list of databases
551 Invalid strategy, use "SHOW STRAT" for a list of strategies
552 No match
...
... 551 Invalid strategy, use "SHOW STRAT" for a list of strategies
552 No match
554 No databases present
555 No strategies available
...
... S: 113 Help text follows
S: DEFINE database word look up word in database
S: MATCH database strategy word match word in database ...
... database word look up word in database
S: MATCH database strategy word match word in database using strategy
S: [ more server-dependent help text ]
...
... database
S: MATCH database strategy word match word in database using strategy
S: [ more server-dependent help text ]
S: .
...
... S: 110 1 database present: list follows
S: free "Free database"
S: .
S: 250 Command complete
...
... S: 110 2 databases present: list follows
S: free "Free database"
S: licensed "Local licensed database"
...
... Miller, G.A. (1990), ed. WordNet: An On-Line Lexical Database. International Journal of Lexicography. Volume 3, Number 4. <URL:http://www.cogsci.princeton.edu/~wn/> ...