Skip to content

Commit 42185bd

Browse files
committed
update availability details for meta-schemas
1 parent c6424fe commit 42185bd

File tree

1 file changed

+12
-7
lines changed

1 file changed

+12
-7
lines changed

PROCESS.md

+12-7
Original file line numberDiff line numberDiff line change
@@ -87,22 +87,27 @@ Once a specification document has been published, neither the document (save for
8787

8888
### Meta-schemas
8989

90-
A release meta-schema will be published under the same path using `schema` as the file name.
90+
A release meta-schema will be published under the same path using `schema.json` as the file name.
9191

9292
```
93-
https://json-schema.org/1/2025/schema
93+
https://json-schema.org/1/2025/schema.json
9494
```
9595

96-
The meta-schema for the latest release in a version will also be published under the version path with `schema` as the file name.
96+
The website will also be configured to:
9797

98-
```
99-
https://json-schema.org/1/schema
100-
```
98+
- serve the meta-schema from its release folder
99+
```
100+
https://json-schema.org/1/2025/
101+
```
102+
- serve the meta-schema for the latest release in a version from its version folder
103+
```
104+
https://json-schema.org/1/
105+
```
101106

102107
The latest-release meta-schemas will be updated with proposals as indicated by the [Proposal section](#proposal) of this document.
103108

104109
```diff
105-
@@ These are merely publication URLs. The specification will define the `$id` values for the meta-schemas. @@
110+
@@ These are only publication and availability URLs. The specification will define the `$id` values for the meta-schemas. @@
106111
```
107112

108113
## Feature Life Cycle

0 commit comments

Comments
 (0)