From 49831fb74fbde025c6d1c95a57ae5d15d0919fd5 Mon Sep 17 00:00:00 2001 From: Travis Ralston Date: Mon, 10 Jun 2019 13:48:55 -0600 Subject: [PATCH] Clarifications about namespaces --- specification/index.rst | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/specification/index.rst b/specification/index.rst index 375e19c0..547375e3 100644 --- a/specification/index.rst +++ b/specification/index.rst @@ -446,12 +446,13 @@ Namespacing Namespacing helps prevent conflicts between multiple applications and the specification itself. Where namespacing is used, ``m.`` prefixes are used by the specification to indicate that the field is controlled by the specification. Custom or non-specified -namespaces used in the wild SHOULD use the Java package naming convention to prevent +namespaces used in the wild MUST use the Java package naming convention to prevent conflicts. -As an example, event types are namespaced under ``m.`` in the specification however -any client can send a custom event type, such as ``com.example.game.score`` without -needing to put the event into the ``m.`` namespace. +As an example, event types defined in the specification are namespaced under the +special ``m.`` prefix, however any client can send a custom event type, such as +``com.example.game.score`` (assuming the client has rights to the ``com.example`` +namespace) without needing to put the event into the ``m.`` namespace. Timestamps ~~~~~~~~~~