Merge 92084268f1 into 0e05e45d84

Update proposals.md: add reference to the guide about how to handle not-yet-known MSC number (#2153 )
Suggest how to number the draft before user have the PR/MSC ID, referring to the other guide.
2026-04-23 03:04:09 +02:00 · 2025-06-25 15:39:21 +01:00 · 2025-06-24 17:46:02 +01:00 · 2025-04-09 10:39:45 +02:00 · 2025-04-09 10:39:37 +02:00
4 changed files with 7 additions and 0 deletions
--- a/changelogs/application_service/newsfragments/2132.clarification
+++ b/changelogs/application_service/newsfragments/2132.clarification
@ -0,0 +1 @@
+Declare the Application Service Registration schema to follow JSON Schema spec 2020-12.
--- a/content/proposals.md
+++ b/content/proposals.md
@ -185,6 +185,10 @@ is as follows:
    -   Take care in creating your proposal. Specify your intended
        changes, and give reasoning to back them up. Changes without
        justification will likely be poorly received by the community.
+    -   At the time of creating your draft you will not yet know the PR number, so you
+        should use a placeholder number to name your file and edit that
+        after PR submission. The suggested steps are described in
+        detail [in the proposals guide](https://github.com/matrix-org/matrix-spec-proposals#1-writing-the-proposal).
 -   Fork and make a PR to the
    [matrix-spec-proposals](https://github.com/matrix-org/matrix-spec-proposals) repository.
    The ID of your PR will become the MSC ID for the lifetime of your
--- a/data/api/application-service/definitions/namespace_list.yaml
+++ b/data/api/application-service/definitions/namespace_list.yaml
@ -11,6 +11,7 @@
 # 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.
+$schema: https://json-schema.org/draft/2020-12/schema

 type: array
 items:
--- a/data/api/application-service/definitions/registration.yaml
+++ b/data/api/application-service/definitions/registration.yaml
@ -11,6 +11,7 @@
 # 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.
+$schema: https://json-schema.org/draft/2020-12/schema

 type: object
 title: Registration
Author	SHA1	Message	Date
V02460	935b94da9f	Merge `92084268f1` into `0e05e45d84`	2025-06-25 15:39:21 +01:00
Peter Gervai	0e05e45d84	Update proposals.md: add reference to the guide about how to handle not-yet-known MSC number (#2153 ) Some checks failed Spec / 🔎 Validate OpenAPI specifications (push) Has been cancelled Details Spec / 🔎 Check Event schema examples (push) Has been cancelled Details Spec / 🔎 Check OpenAPI definitions examples (push) Has been cancelled Details Spec / 🔎 Check JSON Schemas inline examples (push) Has been cancelled Details Spec / ⚙️ Calculate baseURL for later jobs (push) Has been cancelled Details Spec / 📢 Run towncrier for changelog (push) Has been cancelled Details Spell Check / Spell Check with Typos (push) Has been cancelled Details Spec / 🐍 Build OpenAPI definitions (push) Has been cancelled Details Spec / 📖 Build the spec (push) Has been cancelled Details Spec / 🔎 Validate generated HTML (push) Has been cancelled Details Spec / 📖 Build the historical backup spec (push) Has been cancelled Details Suggest how to number the draft before user have the PR/MSC ID, referring to the other guide.	2025-06-24 17:46:02 +01:00
Kai A. Hiller	92084268f1	Add newsfragment Signed-off-by: Kai A. Hiller <git@kaialexhiller.de>	2025-04-09 10:39:45 +02:00
Kai A. Hiller	6ae25e7df4	Add meta schema to AS registration schema Signed-off-by: Kai A. Hiller <git@kaialexhiller.de>	2025-04-09 10:39:37 +02:00
				`@ -0,0 +1 @@`
				`Declare the Application Service Registration schema to follow JSON Schema spec 2020-12.`