From 9dd0854aee812a142f49237b7022ebeef38eec8b Mon Sep 17 00:00:00 2001 From: Alexey Rusakov Date: Tue, 30 Mar 2021 19:34:28 +0200 Subject: [PATCH] Add a link to CS API --- proposals/2312-matrix-uri.md | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/proposals/2312-matrix-uri.md b/proposals/2312-matrix-uri.md index 7b01cff0..81a66c46 100644 --- a/proposals/2312-matrix-uri.md +++ b/proposals/2312-matrix-uri.md @@ -49,12 +49,13 @@ This MSC does not introduce new Matrix entities, nor API endpoints - it merely defines a mapping between URIs with the scheme name `matrix:` and Matrix identifiers, as well as operations on them. The MSC should be sufficient to produce an implementation that would convert Matrix URIs to -a series of CS API calls, entirely on the client side. It is recognised, -however, that most of the URI processing logic can and should (eventually) -be on the server side in order to facilitate adoption of Matrix URIs; -further MSCs are needed to define details for that, as well as to extend -the mapping to more resources (including those without equivalent -Matrix identifiers, such as room state or user profile data). +a series of [CS API](https://matrix.org/docs/spec/client_server/latest) calls, +entirely on the client side. It is recognised, however, that most of +the URI processing logic can and should (eventually) be on the server side +in order to facilitate adoption of Matrix URIs; further MSCs are needed +to define details for that, as well as to extend the mapping to more resources +(including those without equivalent Matrix identifiers, such as room state or +user profile data). The Matrix identifier (or identifiers) can be reconstructed from `{id without sigil}` by prepending a sigil character corresponding to `{type}`.