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

Clarify what compliant implementations are

Browse source
This commit is contained in:
Travis Ralston 2019-06-06 17:32:59 -06:00
parent 87d8d97074
commit 06ee60f004
1 changed files with 7 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

11
specification/modules.rst
View file

@ -18,7 +18,10 @@ Modules
Modules are parts of the Client-Server API which are not universal to all Modules are parts of the Client-Server API which are not universal to all
endpoints. Modules are strictly defined within this specification and endpoints. Modules are strictly defined within this specification and
should not be mistaken for XEP or equivalent extensions from other protocols should not be mistaken for experimental extensions or optional features.
- in order for an implementation to be compliant with the Client-Server A compliant server implementation MUST support all modules and supporting
specification it MUST support all modules and supporting specification. specification (unless the implementation only targets clients of certain
The exception being clients, which are governed by `Feature Profiles <#feature-profiles>`_. profiles, in which case only the required modules for those feature profiles
MUST be implemented). A compliant client implementation MUST support all
the required modules and supporting specification for the `Feature Profile <#feature-profiles>`_
it targets.