wholetrans/docs-matrix-spec
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Clarifications about namespaces

Browse source
This commit is contained in:
Travis Ralston 2019-06-10 13:48:55 -06:00
parent b9c9396c11
commit 49831fb74f
1 changed files with 5 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

9
specification/index.rst
View file

@ -446,12 +446,13 @@ Namespacing
Namespacing helps prevent conflicts between multiple applications and the specification Namespacing helps prevent conflicts between multiple applications and the specification
itself. Where namespacing is used, ``m.`` prefixes are used by the specification to 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 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. conflicts.
As an example, event types are namespaced under ``m.`` in the specification however As an example, event types defined in the specification are namespaced under the
any client can send a custom event type, such as ``com.example.game.score`` without special ``m.`` prefix, however any client can send a custom event type, such as
needing to put the event into the ``m.`` namespace. ``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 Timestamps
~~~~~~~~~~ ~~~~~~~~~~