W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > October to December 1997

RE: ACL Draft

From: Paul Leach <paulle@microsoft.com>
Date: Fri, 24 Oct 1997 11:53:12 -0700
Message-ID: <771E1FEEEE41D111A95900805FFE658712AD6A@RED-MSG-51.dns.microsoft.com>
To: "'hep@netscape.com'" <hep@netscape.com>
Cc: w3c-dist-auth@w3.org, "'Larry Masinter'" <masinter@parc.xerox.com>
I sent off the previous post slightly incomplete... corrected below:

> ----------
> From: 	Paul Leach
> Sent: 	Friday, October 24, 1997 10:31 AM
> To: 	'hep@netscape.com'
> Cc: 	w3c-dist-auth@w3.org; 'Larry Masinter'
> Subject: 	RE: ACL Draft
> 
> >   Do you use Windows NT?  Have you looked
> > at its API for access control (or did you design it)?  It seems quite
> > complex to me, although I believe I understand the need for the
> > complexity.
> > The UI for setting access control on files seems reasonably intuitive,
> > however, at least to me.  It appears that your UI designer chose not to
> > expose all of the underlying functionality, and got a pretty good
> result.
> > 
> To the contrary. Our usability studies show that most users have a very
> hard
> time with ACL editing. And the functionality that isn't exposed through
> the
> UI in effect does not exist.
> 
> As to the API, there's a difference between complex/baroque encodings and
> complex concepts. A baroque encoding
> 
A boroque encoding can be overcome with a good UI (and/or a nicer API).
Complex concepts can't (well -- are much much harder).

Paul
Received on Friday, 24 October 1997 14:55:49 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:43:44 GMT