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

Re: Access Control Draft

From: Jon Radoff <jradoff@novalink.com>
Date: Wed, 21 May 1997 16:06:38 -0400
Message-ID: <338355CE.3E35@novalink.com>
To: Jim Whitehead <ejw@ics.uci.edu>
CC: w3c-dist-auth@w3.org
> I'm not sure where this is headed.  HTTP already defines standard methods
> which are associated with resources, "read" is known as "GET", "write" is
> known as "PUT", and "delete" is known as "DELETE."  What is the benefit of
> giving these known, well-defined methods new names?  Or are you suggesting
> something similar to the AOLserver model, where they sometimes create
> pseudo methods for assigning access control rights.

The "methods" I'm talking about here aren't HTTP methods.  It
is probably closer to the AOLserver model in that there are
"security permission methods" such as read, mody, etc.
> Work on CORBA is outside the scope of activity of this working group, as
> specified in our charter.  But, I agree with you, once an interface
> standard has been developed, its packaging in various other formats (CORBA,
> RPC, etc.) is much easier.

I'm not proposing that we work on a CORBA spec;  simply that an
object-based approach with security methods would support this
type of encapsulation model.

I agree that we are probably drifing into too many areas of
proposed design, but I think it may be helpful to expose weaknesses
in going down particular paths with respect to the requirements.
We don't want a requirements document which is unworkable either
within our charter or from a techno-political standpoint.

Received on Thursday, 22 May 1997 12:55:04 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:01:15 UTC