Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #45899

RE: Using ACLs in JSON

Path csiph.com!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!newsfeed.xs4all.nl!newsfeed1.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail
Return-Path <carlosnepomuceno@outlook.com>
X-Original-To python-list@python.org
Delivered-To python-list@mail.python.org
X-Spam-Status OK 0.023
X-Spam-Evidence '*H*': 0.95; '*S*': 0.00; 'skip:[ 20': 0.04; 'syntax': 0.04; 'json': 0.07; 'logic': 0.09; 'wrong,': 0.09; 'python': 0.11; 'itself.': 0.14; '"1.0",': 0.16; 'clear.': 0.16; 'reasonably': 0.16; 'skip:[ 40': 0.16; 'restrictions': 0.19; 'addition,': 0.20; 'seems': 0.21; 'example': 0.22; 'to:name :python-list@python.org': 0.22; "aren't": 0.24; 'documented': 0.24; 'received:65.55.116': 0.24; 'sort': 0.25; "i've": 0.25; 'header:In-Reply-To:1': 0.27; 'record': 0.27; 'idea': 0.28; 'skip:- 40': 0.29; 'wondering': 0.29; '[1]': 0.29; "i'm": 0.30; 'url:mailman': 0.30; 'compatible': 0.32; 'url:python': 0.33; 'fri,': 0.33; 'role': 0.34; 'date:': 0.34; 'sense': 0.34; 'but': 0.35; 'google': 0.35; 'there': 0.35; 'accessible': 0.36; 'url:listinfo': 0.36; 'doing': 0.36; 'url:org': 0.36; 'should': 0.36; 'integration': 0.37; 'application': 0.37; 'email addr:python.org': 0.37; 'security,': 0.38; 'to:addr:python-list': 0.38; 'subject:': 0.39; 'to:addr:python.org': 0.39; 'url:mail': 0.40; 'deleting': 0.60; 'hope': 0.61; 'email addr:gmail.com': 0.63; 'more': 0.64; 'different': 0.65; 'email name:python-list': 0.65; 'below.': 0.71; 'viewed': 0.74; '"required":': 0.84; "it'd": 0.84; 'subject:Using': 0.84; '2013': 0.98
X-TMN [zaNkQxFuF+3o6oKCVDIYOp9to7L1XREU]
X-Originating-Email [carlosnepomuceno@outlook.com]
From Carlos Nepomuceno <carlosnepomuceno@outlook.com>
To "python-list@python.org" <python-list@python.org>
Subject RE: Using ACLs in JSON
Date Fri, 24 May 2013 19:13:15 +0300
Importance Normal
In-Reply-To <6e35fb87-6c6b-4fcc-a99c-199af8b1a4c1@k3g2000vbn.googlegroups.com>
References <6e35fb87-6c6b-4fcc-a99c-199af8b1a4c1@k3g2000vbn.googlegroups.com>
Content-Type text/plain; charset="iso-8859-1"
Content-Transfer-Encoding quoted-printable
MIME-Version 1.0
X-OriginalArrivalTime 24 May 2013 16:13:15.0942 (UTC) FILETIME=[98EFDC60:01CE5899]
X-BeenThere python-list@python.org
X-Mailman-Version 2.1.15
Precedence list
List-Id General discussion list for the Python programming language <python-list.python.org>
List-Unsubscribe <http://mail.python.org/mailman/options/python-list>, <mailto:python-list-request@python.org?subject=unsubscribe>
List-Archive <http://mail.python.org/pipermail/python-list/>
List-Post <mailto:python-list@python.org>
List-Help <mailto:python-list-request@python.org?subject=help>
List-Subscribe <http://mail.python.org/mailman/listinfo/python-list>, <mailto:python-list-request@python.org?subject=subscribe>
Newsgroups comp.lang.python
Message-ID <mailman.2070.1369411998.3114.python-list@python.org> (permalink)
Lines 58
NNTP-Posting-Host 2001:888:2000:d::a6
X-Trace 1369411998 news.xs4all.nl 15936 [2001:888:2000:d::a6]:43663
X-Complaints-To abuse@xs4all.nl
Xref csiph.com comp.lang.python:45899

Show key headers only | View raw


Not exactly what you want but you may consider Google ACL XML[1].

If there aren't any system integration restrictions you can do what you think it's best... for now.


[1] https://developers.google.com/storage/docs/accesscontrol#applyacls


----------------------------------------
> Date: Fri, 24 May 2013 01:18:06 -0700
> Subject: Using ACLs in JSON
> From: peter.h.m.brooks@gmail.com
> To: python-list@python.org
>
> I'm designing a system that should allow different views to different
> audiences. I understand that I can use application logic to control
> the access security, but it seems to me that it'd make more sense to
> have this documented in the data-stream so that it's data-driven.
>
> I was wondering if there was any standard way of doing this in JSON.
> Alternatively, is there a better way of organising this in Python
> that's compatible with JSON?
>
> I've put an example of the sort of thing that I mean below. The idea
> is that this object is accessible for viewing or deleting by the role
> 'HR' and available for change only to the owner of the record itself.
> In addition, the record can be viewed by those with the role
> 'manager'. The syntax may be wrong, but I hope that my intention is
> reasonably clear.
>
> Is there an existing practice or standard for doing this sort of
> thing?
>
> {
> "title" : "Example Schema",
> "type" : "object",
> "version" : "1.0",
> "properties": {
> "firstname" : {
> "type": "string"
> },
> "lastname" : {
> "type": "string"
> },
> "age" : {
> "description" : "Age in years",
> "type": "integer",
> "minimum": 0
> }
> },
> "ACL-view": ["HR","Manager",["firstname","lastname"]],
> "ACL-change": ["firstname","Lastname"],
> "ACL-delete": ["HR"],
> "required": ["firstname","lastname"]
> }
> --
> http://mail.python.org/mailman/listinfo/python-list 		 	   		  

Back to comp.lang.python | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Using ACLs in JSON Peter Brooks <peter.h.m.brooks@gmail.com> - 2013-05-24 01:18 -0700
  RE: Using ACLs in JSON Carlos Nepomuceno <carlosnepomuceno@outlook.com> - 2013-05-24 19:13 +0300
    Re: Using ACLs in JSON Peter Brooks <peter.h.m.brooks@gmail.com> - 2013-05-24 12:08 -0700
      RE: Using ACLs in JSON Carlos Nepomuceno <carlosnepomuceno@outlook.com> - 2013-05-25 00:12 +0300
  Re: Using ACLs in JSON Michael Torrie <torriem@gmail.com> - 2013-05-24 10:42 -0600
    Re: Using ACLs in JSON Peter Brooks <peter.h.m.brooks@gmail.com> - 2013-05-24 12:06 -0700

csiph-web