From e7c522b6068670173a519639b5fa96f831631323 Mon Sep 17 00:00:00 2001 From: Kegsay Date: Thu, 5 Feb 2015 16:06:47 +0000 Subject: [PATCH] Add information on exclusive namespaces --- drafts/application_services.rst | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/drafts/application_services.rst b/drafts/application_services.rst index c654c010..dfec19f7 100644 --- a/drafts/application_services.rst +++ b/drafts/application_services.rst @@ -86,7 +86,13 @@ In the registration process, the AS provides: "subscribing to" * Namespaces are defined as a list of regexps against which to match room aliases, room IDs, and user IDs. Regexps give the flexibility to say, sub-domain MSISDN - ranges per AS, whereas a blunt prefix string does not. + ranges per AS, whereas a blunt prefix string does not. These namespaces are further + configured by setting whether they are ``exclusive`` or not. An exclusive namespace + prevents entities other than the aforementioned AS from creating/editing/deleting + entries within that namespace. This does not affect the visibility/readability of + entries within that namespace (e.g. it doesn't prevent users joining exclusive + aliases, or ASes from listening to exclusive aliases, but does prevent both users + and ASes from creating/editing/deleting aliases within that namespace). * There is overlap between selecting events via the csv2 Filter API and subscribing to events here - perhaps subscription involves passing a filter token into the registration API.