summaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authorJosé Bollo <jose.bollo@iot.bzh>2017-01-31 16:08:47 +0100
committerJosé Bollo <jose.bollo@iot.bzh>2017-01-31 16:11:49 +0100
commit0c6c12370b8f2b467f64e08b96b21b20e7ee15ee (patch)
treea0a057e64c55bc3934f81275b8558f59b3b02031 /docs
parent1d4de11a907e41c06063a2cd5028dc4101690f50 (diff)
Improves names
The name binding is related to an internal concept of the binder. The term API is more generic. Dont forget that an API can be provided by more than one binding (but only one at a given time). Change-Id: I91b2f3d96de6aace5fcb434cf64df7e8ed61630f Signed-off-by: José Bollo <jose.bollo@iot.bzh>
Diffstat (limited to 'docs')
-rw-r--r--docs/permissions.md16
1 files changed, 8 insertions, 8 deletions
diff --git a/docs/permissions.md b/docs/permissions.md
index 300a719..434744e 100644
--- a/docs/permissions.md
+++ b/docs/permissions.md
@@ -14,17 +14,17 @@ framework to keep updated a database of installed permissions.
The permission names are [URN][URN] of the form:
- urn:AGL:permission:<binding>:<level>:<hierarchical-name>
+ 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 <binding> and <level> and the remaining
+fields. The 2 first fields are <api> and <level> and the remaining
fields are gouped to form the <hierarchical-name>.
- <binding> ::= [ <pname> ]
+ <api> ::= [ <pname> ]
<pname> ::= 1*<pchars>
@@ -32,12 +32,12 @@ fields are gouped to form the <hierarchical-name>.
<extra> ::= "-" | "." | "_" | "@"
-The field <binding> can be made of any valid character for NSS except
-the characters colon and star (:*). This field designate the binding
-providing the permission. It is use to deduce binding requirements
-from permission requirements. The field <binding> can be the empty
+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 <binding> if starting with the character "@" represents
+The field <api> if starting with the character "@" represents
a transversal permission not bound to any binding.
<level> ::= 1*<lower>