Re: whois++ response formats...

Rickard Schoultz <schoultz@admin.kth.se> Wed, 15 September 1993 15:19 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa05931; 15 Sep 93 11:19 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa05923; 15 Sep 93 11:19 EDT
Received: from ucdavis.ucdavis.edu by CNRI.Reston.VA.US id aa26696; 15 Sep 93 11:19 EDT
Received: by ucdavis.ucdavis.edu (4.1/UCD2.05) id AB18817; Wed, 15 Sep 93 07:51:17 PDT
X-Orig-Sender: ietf-wnils-request@ucdavis.edu
Received: from othello.admin.kth.se by ucdavis.ucdavis.edu (4.1/UCD2.05) id AA18656; Wed, 15 Sep 93 07:47:06 PDT
Received: from localhost.admin.kth.se by othello.admin.kth.se (5.65+bind 1.8+ida 1.4.2/4.0b) id AA23099; Wed, 15 Sep 93 16:48:06 +0200
Message-Id: <9309151448.AA23099@othello.admin.kth.se>
To: Martin Hamilton <M.T.Hamilton@lut.ac.uk>
Cc: ietf-wnils@ucdavis.edu
Subject: Re: whois++ response formats...
In-Reply-To: Your message of Tue, 14 Sep 93 09:33:40 +0100. <Pine.3.07.9309140940.E215-a100000@avarice>
Date: Wed, 15 Sep 1993 16:48:06 +0200
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Rickard Schoultz <schoultz@admin.kth.se>

> Here are the response formats I am using for responses that
> don't involve templates -- culled from the other whois++
> implementations.  Let me know if you disagree strongly with
> any of this stuff :-)

Martin,
 I think your set of responses are as good as any.  My opinion is that
we need a BNF (Peter?) for the FULL response, and use that to form the
responses from system commands.

If we start out with:

# FULL <hits>
# <template> <handle>
 <attribute>:<value>
 ...
# <template> <handle>
 <attribute>:<value>
 ...
...
#END

and apply it to the different responses:

>   version
>   # FULL 1
>    Version: LUT version 0.0
>   # END

This would add another line, with a questionmark on what the handle
should be:

# FULL 1
# VERSION version
 Version: 1.0a
# END

>   commands
>   # FULL 16
>   # command describe
>    Name: describe
>    Description: Describe Server
>   # command help
>    Name: help
>    Description: Help!
>   [...]

... follows the model.

>   constraints
>   # FULL 13
>     search
>     case
>     format
>     maxhits
>   [...]

Here we have the opportunity to tell about how we support different
constraints, so I think it too should follow the above model like:

constraints
# FULL 3
# CONSTRAINT MAXHITS
 Constraint:     maxhits
 Default-Value:  200
 Range:          1..n
 Description:    Maximum hits returned.
# CONSTRAINT FORMAT
 Constraint:     format
 Range:          full,abridged,handle,summary
 Description:    Selects output format.
# CONSTRAINT HOLD
 Constraint:     hold
 Description:    Keeps the connection open.
# END

> Ciao,
>
> Martin

-Rickard