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

Go into a bit more detail about feature profiles

Browse source
This commit is contained in:
Kegan Dougal 2015-10-02 16:34:06 +01:00
parent 2fbf851a75
commit 28fd1aa205
1 changed files with 8 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

11
CHANGELOG.rst
View file

@ -9,9 +9,14 @@
Specification changes in v0.2.0 (2015-10-02) Specification changes in v0.2.0 (2015-10-02)
============================================ ============================================
This update restructures the specification and begins to aggressively standardise This update fundamentally restructures the specification. The specification has
on using Swagger and JSON Schema to document HTTP endpoints and Events been split into more digestible "modules" which each describe a particular
respectively. It also introduces a number of new concepts to Matrix. function (e.g. typing). This was done in order make the specification easier to
maintain and help define which modules are mandatory for certain types
of clients. Types of clients along with the mandatory modules can be found in a
new "Feature Profiles" section. This update also begins to aggressively
standardise on using Swagger and JSON Schema to document HTTP endpoints and
Events respectively. It also introduces a number of new concepts to Matrix.
Additions: Additions:
- New section: Feature Profiles. - New section: Feature Profiles.