RE: One more possible hole in UI?

personally I prefer a separate element to encode the
semantic difference rather than using an attribute.

Using the "password semantics" do do encryption etc is valid
--
the problem with a name like "password" is people then ask
"can I use this thing only for passwords ?"
(of course that is always the problem with naming anything--
>>>>> "Kelly" == Kelly Campbell <camk@channelpoint.com> writes:

    Kelly> I would prefer the first choice. I think
    Kelly> passwords should have different semantics than
    Kelly> plain text fields. That would allow passwords to
    Kelly> have further security constraints besides what is
    Kelly> echoed to the user. For example, in the
    Kelly> submission protocol, some type of encryption
    Kelly> scheme could be added for the password data when
    Kelly> not using SSL or something, or access to the
    Kelly> password data could be restricted for client-side
    Kelly> java scripts, etc. If you remove the semantic
    Kelly> notion of it being a password field, you lose
    Kelly> this ability.

    Kelly> An alternative to 1) or 2) could be something
    Kelly> like this: 3) <textbox type="password"
    Kelly> style="echo-char: '#'">...</textbox>

    Kelly> What do you think?

    Kelly> -Kelly -- Kelly A. Campbell Software Engineer
    Kelly> <camk@channelpoint.com> ChannelPoint, Inc.
    Kelly> <camk@merlotxml.org> Colorado Springs, Co.


    >> -----Original Message----- From: T. V. Raman
    >> [mailto:tvraman@almaden.ibm.com] Sent: Friday, March
    >> 23, 2001 12:41 PM To: Berin Loritsch Cc:
    >> tvraman@almaden.ibm.com; XForms Mailing List Subject:
    >> Re: One more possible hole in UI?
    >> 
    >> 
    >> the two choices I am presently considering are: 1)
    >> Have a <password>...</password> element analogous to
    >> textbox
    >> 
    >> 2) (preference as of last two days) <textbox
    >> echo="*">...</textbox> (default value of echo echoes
    >> chars as you type --echo ="*" displays '*' echo ="#"
    >> displays '#'
    >> 
    >> Since you say you're implementing this, what would
    >> your preference be?
    >> 
    >> By the way, I'll respond to the other half of your
    >> first note in the next couple of days-- >>>>> "Berin"
    >> == Berin Loritsch <bloritsch@apache.org> writes:
    >> 
    Berin> "T. V. Raman" wrote:
    >> >> coming in the next draft.
    >> 
    Berin> (Password textbox issue)
    >>
    Berin> Is there any way to get a feel for the current
    Berin> discussion on this?  Is this going to be a CSS
    Berin> style element?
    >>
    Berin> The reason I ask is that I am writing a server
    Berin> side form processing system based on the XForms
    Berin> spec, and if I have to augment the current XForms
    Berin> with current needs--I want to do so in a fashion
    Berin> that is closest to what the end spec is going to
    Berin> be.
    >> 
    >> -- 
    >> Best Regards, --raman
    >> ------------------------------------------------------------
    >> 
    >> IBM Research: Human Language Technologies Phone: 1
    >> (408) 927 2608 Fax: 1 (408) 927 3012 Email:
    >> tvraman@us.ibm.com WWW:
    >> http://www.cs.cornell.edu/home/raman PGP:
    >> http://cs.cornell.edu/home/raman/raman.asc Snail: IBM
    >> Almaden Research Center, 650 Harry Road San Jose
    >> 95120
    >> 

-- 
Best Regards,
--raman
------------------------------------------------------------

IBM Research: Human Language Technologies
Phone:        1 (408) 927 2608
Fax:        1 (408) 927 3012
Email:        tvraman@us.ibm.com
WWW:      http://www.cs.cornell.edu/home/raman
PGP:          http://cs.cornell.edu/home/raman/raman.asc 
Snail:        IBM Almaden Research Center,
              650 Harry Road
              San Jose 95120

Received on Friday, 23 March 2001 15:13:42 UTC