blob: 434744ebc1a6080b1c3ef38aa3069ce2f9cc8302 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
|
The permissions
===============
Permission's names
------------------
The proposal here is to specify a naming scheme for permissions
that allows the system to be as stateless as possible. The current
current specification includes in the naming of permissions either
the name of the bound binding when existing and the level of the
permission itself. Doing this, there is no real need for the
framework to keep updated a database of installed permissions.
The permission names are [URN][URN] of the form:
urn:AGL:permission:<api>:<level>:<hierarchical-name>
where "AGL" is the NID (the namespace identifier) dedicated to
AGL (note: a RFC should be produced to standardize this name space).
The permission names are made of NSS (the namespace specific string)
starting with "permission:" and followed by colon separated
fields. The 2 first fields are <api> and <level> and the remaining
fields are gouped to form the <hierarchical-name>.
<api> ::= [ <pname> ]
<pname> ::= 1*<pchars>
<pchars> ::= <upper> | <lower> | <number> | <extra>
<extra> ::= "-" | "." | "_" | "@"
The field <api> can be made of any valid character for NSS except
the characters colon and star (:*). This field designate the api
providing the permission. This scheme is used to deduce binding requirements
from permission requirements. The field <api> can be the empty
string when the permission is defined by the AGL system itself.
The field <api> if starting with the character "@" represents
a transversal permission not bound to any binding.
<level> ::= 1*<lower>
The field <level> is made only of letters in lower case.
The field <level> can only take some predefined values:
"system", "platform", "partner", "tiers", "owner", "public".
<hierarchical-name> ::= <pname> 0*(":" <pname>)
The field <hierarchical-name> is made <pname> separated by
colons. The names at left are hierarchically grouping the
names at right. This hierarchical behaviour is intended to
be used to request permissions using hierarchical grouping.
Permission's level
------------------
[URN]: https://tools.ietf.org/rfc/rfc2141.txt "RFC 2141: URN Syntax"
|
