W3C home > Mailing lists > Public > public-rww@w3.org > November 2012

Re: [Owncloud] Permissions & CRUDS

From: Melvin Carvalho <melvincarvalho@gmail.com>
Date: Tue, 6 Nov 2012 23:58:28 +0100
Message-ID: <CAKaEYhLcxmvrs-RBL_bNtMXZQgTDC0r6YL5jVF2F8jXLOozdug@mail.gmail.com>
To: Thomas Tanghus <thomas@tanghus.net>
Cc: "owncloud@kde.org Mailinglist" <owncloud@kde.org>, public-rww <public-rww@w3.org>
On 6 November 2012 22:45, Thomas Tanghus <thomas@tanghus.net> wrote:

> We ended up in a discussion which kind of touches the fundamentals of
> ownCloud
> in https://github.com/owncloud/core/issues/151#issuecomment-10116749
>
> The Share API has a clear definition at
> https://github.com/owncloud/core/blob/master/lib/public/share.php#L50
>

Thanks for pointing this out, this is very interesting.

The W3C Read Write Web Community group is hoping to standarize in this
space based on traditional HTTP verbs.

Currently we have the concept of a collection (like a directory) and that
of a URL with the following 4 masks

1. READ
2. WRITE

3. CONTROL
4. APPEND

The first 2 are like owncloud

I think CONTROL is the same as SHARE, what it means is you can alter the
access control

And APPEND may be similar to UPDATE

I could be wrong but we may assume that WRITE access implies DELETE

Would you see any value here in trying to find a standard paradigm across
the whole web?


>
> I have used those for defining permissions for non-file objects like
> calendars
> and addressbooks.
>
> For me it would make sense to use those consts as a basis for the CRUDS
> paradigm.
>
> Comments?
>
> --
> Med venlig hilsen / Best Regards
>
> Thomas Tanghus
> _______________________________________________
> Owncloud mailing list
> Owncloud@kde.org
> https://mail.kde.org/mailman/listinfo/owncloud
>
Received on Tuesday, 6 November 2012 22:58:55 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 6 November 2012 22:58:56 GMT