Re: request for new forms submission consensus

• Mail folder: WWW Talk Oct 93-present
• Next message: Tony Sanders: "log file format for HTTP/1.0 requests"
• Previous message: Ari Luotonen: "AA BUGS and test page"
• In-reply-to: Marc Andreessen: "Re: request for new forms submission consensus"
• Reply: Tony Sanders: "Re: request for new forms submission consensus "

Message-id: <199310131353.AA05195@library.ucsf.edu>
From: dcmartin@library.ucsf.edu (David C. Martin)
Organization: UCSF Center for Knowledge Management
Email: dcmartin@ckm.ucsf.edu
Phone: 415/476-6111
Fax: 415/476-4653
To: Dave_Raggett <dsr@hplb.hpl.hp.com>
Cc: www-talk@nxoc01.cern.ch
In-reply-to: Your message of Tue, 12 Oct 1993 17:17:24 -0700
	<9310130017.AA20763@wintermute.ncsa.uiuc.edu> 
Subject: Re: request for new forms submission consensus 
Date: Wed, 13 Oct 1993 06:49:34 PDT
Sender: dcmartin@library.ucsf.edu

Dave_Raggett writes:

> I recommend instead, the SELECT tag as in:
> 
>     <SELECT NAME="what-to-do">
>         <LI>Read A Book
>         <LI>Take A Walk
>         <LI>Buy A Bagel
>         <LI>Watch TV
>     </SELECT>
> 
> You use <SELECT SEVERAL NAME="what-to-do"> if several selections are
> possible simultaneously.

You could also indicate it by:

     <SELECT NAME="what-to-do">
         <XC>Read A Book
         <XC>Take A Walk
         <XC>Buy A Bagel
         <XC>Watch TV
     </SELECT>

Where <XC> is an exclusive choice.  Seems more appropriate, if you're
inclined to that mechanism, since the method of choosing is in the
context of exclusivity is static, not dynamic (e.g. non-selectability).

dcm