Whois++ constraints

Mark Prior <mrp@itd.adelaide.edu.au> Thu, 08 April 1993 06:31 UTC

Received: from aggie.ucdavis.edu by ucdavis.ucdavis.edu (5.61/UCD2.04) id AA07347; Wed, 7 Apr 93 23:31:24 -0700
Received: from ucdavis.ucdavis.edu by aggie.ucdavis.edu (5.61/UCD2.04) id AA18352; Wed, 7 Apr 93 22:59:20 -0700
Received: by ucdavis.ucdavis.edu (5.61/UCD2.04) id AA06022; Wed, 7 Apr 93 22:51:38 -0700
Sender: ietf-wnils-request@ucdavis.ucdavis.edu
Received: from jarrah.itd.adelaide.edu.au by ucdavis.ucdavis.edu (5.61/UCD2.04) id AA05953; Wed, 7 Apr 93 22:48:41 -0700
Received: by jarrah.itd.adelaide.edu.au with SMTP (5.61+IDA+MU/UA-5.26) id AA05714; Thu, 8 Apr 1993 15:16:08 +0930
Message-Id: <9304080546.AA05714@jarrah.itd.adelaide.edu.au>
To: Peter Deutsch <peterd@bunyip.com>
Cc: ietf-wnils@ucdavis.ucdavis.edu
Subject: Whois++ constraints
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Thu, 08 Apr 1993 15:16:06 +0930
From: Mark Prior <mrp@itd.adelaide.edu.au>

Can we please agree to change the syntax for the constaints before our
respective servers are released.

I would suggest the following syntax

<keyword> [ "=" <value> ] { "," <keyword> [ "=" <value> ] }

Having "," as a separator allows an implementation that doesn't support
all the options to easily skip over constraints it doesn't understand
by just skipping up to the next ",".

I would also like to transform the constraints "full", "handle",
"abridged", and "summary" into "format=(full|handle|abridged|summary)".
This will allow us to easily add formats, such as mime, later on
without extending the keywords into infinity.