matrix-spec-proposals/specification/modules.rst

.. Copyright 2016 OpenMarket Ltd
.. Copyright 2019 The Matrix.org Foundation C.I.C.
..
.. Licensed under the Apache License, Version 2.0 (the "License");
.. you may not use this file except in compliance with the License.
.. You may obtain a copy of the License at
..
..     http://www.apache.org/licenses/LICENSE-2.0
..
.. Unless required by applicable law or agreed to in writing, software
.. distributed under the License is distributed on an "AS IS" BASIS,
.. WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
.. See the License for the specific language governing permissions and
.. limitations under the License.

Modules
=======

Modules are parts of the Client-Server API which are not universal to all
endpoints. Modules are strictly defined within this specification and
should not be mistaken for experimental extensions or optional features.
A compliant server implementation MUST support all modules and supporting
specification (unless the implementation only targets clients of certain
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.
Add a license to the spec We're licensing hte spec under ASLv2. Add the LICENSE file, and add the short-form to as much of the source as is practical right now (adding it to json source is a massive pita). 8 years ago			`.. Copyright 2016 OpenMarket Ltd`
Clarify what a "module" is and update feature profiles for clients Fixes https://github.com/matrix-org/matrix-doc/issues/2009 5 years ago			`.. Copyright 2019 The Matrix.org Foundation C.I.C.`
Add a license to the spec We're licensing hte spec under ASLv2. Add the LICENSE file, and add the short-form to as much of the source as is practical right now (adding it to json source is a massive pita). 8 years ago			`..`
			`.. Licensed under the Apache License, Version 2.0 (the "License");`
			`.. you may not use this file except in compliance with the License.`
			`.. You may obtain a copy of the License at`
			`..`
			`.. http://www.apache.org/licenses/LICENSE-2.0`
			`..`
			`.. Unless required by applicable law or agreed to in writing, software`
			`.. distributed under the License is distributed on an "AS IS" BASIS,`
			`.. WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.`
			`.. See the License for the specific language governing permissions and`
			`.. limitations under the License.`

Implement relative title styles Templates don't know at what level they will be inserted. Previously, we hard-coded the title style which is not compatible with the build target system. Define a set of styles which will be replaced by the gendoc script when it encounters them: '<' : Make this title a sub-heading '/' : Make this title a heading at the same level '>' : Make this title a super-heading The build target system is now basically complete and functioning. 9 years ago			`Modules`
			`=======`

Clarify what a "module" is and update feature profiles for clients Fixes https://github.com/matrix-org/matrix-doc/issues/2009 5 years ago			`Modules are parts of the Client-Server API which are not universal to all`
Remove incomplete and weird sentence 5 years ago			`endpoints. Modules are strictly defined within this specification and`
Clarify what compliant implementations are 5 years ago			`should not be mistaken for experimental extensions or optional features.`
			`A compliant server implementation MUST support all modules and supporting`
			`specification (unless the implementation only targets clients of certain`
			`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.`