Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Sign up
Appearance settings

Commit e651255

Browse files
Change appendix heading pattern
1 parent 3a799f4 commit e651255

File tree

8 files changed

+16
-16
lines changed

8 files changed

+16
-16
lines changed

‎README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -54,7 +54,7 @@ features they make available to you.
5454
- [remark-headings](/json-schema-org/json-schema-spec/blob/main/remark-headings.js)
5555
-- A collection of enhancements for headings.
5656
- Adds hierarchical section numbers to headings.
57-
- Use the `[Appendix]` prefix on headings that should be numbered as an
57+
- Use the `%appendix%` prefix on headings that should be numbered as an
5858
appendix.
5959
- Adds id anchors to headers that don't have one
6060
- Example: `#section-2-13`

‎remark/remark-headings.js

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ import { toString as nodeToString } from "mdast-util-to-string";
77
const defaultOptions = {
88
startDepth: 1,
99
skip: [],
10-
appendixToken: "[Appendix]",
10+
appendixToken: "%appendix%",
1111
appendixPrefix: "Appendix"
1212
};
1313

‎specs/jsonschema-core.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -2156,7 +2156,7 @@ Bray, T., Ed., Hollander, D., Ed., Layman, A., Ed., and R. Tobin, Ed.,
21562156
"Namespaces in XML 1.1 (Second Edition)", August 2006,
21572157
<<http://www.w3.org/TR/2006/REC-xml-names11-20060816>>.
21582158

2159-
## [Appendix] Schema identification examples {#idexamples}
2159+
## %appendix% Schema identification examples {#idexamples}
21602160

21612161
Consider the following schema, which shows `$id` being used to identify both the
21622162
root schema and various subschemas, and `$anchor` being used to define plain
@@ -2258,7 +2258,7 @@ Document location `/$defs/C`:
22582258
- base IRI of enclosing (root.json) resource plus fragment:
22592259
`https://example.com/root.json#/$defs/C`
22602260

2261-
## [Appendix] Manipulating schema documents and references
2261+
## %appendix% Manipulating schema documents and references
22622262

22632263
Various tools have been created to rearrange schema documents based on how and
22642264
where references (`$ref`) appear. This appendix discusses which use cases and
@@ -2300,7 +2300,7 @@ scope of this specification to determine or provide a set of safe `$ref` removal
23002300
transformations, as they depend not only on the schema structure but also on the
23012301
intended usage.
23022302

2303-
## [Appendix] Example of recursive schema extension {#recursive-example}
2303+
## %appendix% Example of recursive schema extension {#recursive-example}
23042304

23052305
Consider the following two schemas describing a simple recursive tree structure,
23062306
where each node in the tree can have a "data" field of any type. The first
@@ -2394,7 +2394,7 @@ of the node schema objects were moved under `$defs`. It is the matching
23942394
`$dynamicAnchor` values which tell us how to resolve the dynamic reference, not
23952395
any sort of correlation in JSON structure.
23962396

2397-
## [Appendix] References and generative use cases
2397+
## %appendix% References and generative use cases
23982398

23992399
While the presence of references is expected to be transparent to validation
24002400
results, generative use cases such as code generators and UI renderers often
@@ -2444,7 +2444,7 @@ instance of a distinct class.
24442444
This style of usage requires the annotation to be in the same object as the
24452445
reference, which must be recognizable as a reference.
24462446

2447-
## [Appendix] Acknowledgments
2447+
## %appendix% Acknowledgments
24482448

24492449
Thanks to Gary Court, Francis Galiegue, Kris Zyp, Geraint Luff, and Henry
24502450
Andrews for their work on the initial drafts of JSON Schema.
@@ -2454,7 +2454,7 @@ Bowman, Gowry Sankar, Donald Pipowitch, Dave Finlay, Denis Laxalde, Phil
24542454
Sturgeon, Shawn Silverman, and Karen Etheridge for their submissions and patches
24552455
to the document.
24562456

2457-
## [Appendix] Change Log[^19]
2457+
## %appendix% Change Log[^19]
24582458

24592459
### draft-bhutton-json-schema-next
24602460
- Use IRIs instead of URIs, including allowing unicode in plain-name fragments

‎specs/jsonschema-validation.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -886,7 +886,7 @@ draft-bhutton-json-schema-01, June 2022,
886886
Hoehrmann, B., "Scripting Media Types", RFC 4329, DOI 10.17487/RFC4329, April
887887
2006, <<https://www.rfc-editor.org/info/rfc4329>>.
888888

889-
## [Appendix] Acknowledgments
889+
## %appendix% Acknowledgments
890890

891891
Thanks to Gary Court, Francis Galiegue, Kris Zyp, Geraint Luff, and Henry
892892
Andrews for their work on the initial drafts of JSON Schema.
@@ -896,7 +896,7 @@ Bowman, Gowry Sankar, Donald Pipowitch, Dave Finlay, Denis Laxalde, Phil
896896
Sturgeon, Shawn Silverman, and Karen Etheridge for their submissions and patches
897897
to the document.
898898

899-
## [Appendix] Change Log[^6]
899+
## %appendix% Change Log[^6]
900900

901901
- *draft-next*
902902
- Use IRIs instead of URIs

‎specs/proposals/propertyDependencies-adr.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -235,7 +235,7 @@ cases carried a lower priority.
235235
- Properties with non-string values cannot be supported using this keyword and
236236
the `allOf`-`if`-`then` pattern must still be used.
237237

238-
## [Appendix] Problems With Existing Patterns {#problems}
238+
## %appendix% Problems With Existing Patterns {#problems}
239239

240240
### `oneOf`/`anyOf`
241241

‎specs/proposals/propertyDependencies.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -129,7 +129,7 @@ vocabulary](../jsonschema-core.md#applicators).
129129
}
130130
```
131131

132-
## [Appendix] Change Log
132+
## %appendix% Change Log
133133

134134
- \[March 2021\] - Initially proposed
135135
- \[October 2021\] Added to specification document

‎specs/proposals/proposal-template.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -81,11 +81,11 @@ For example
8181
```
8282
-->
8383

84-
## [Appendix] Change Log
84+
## %appendix% Change Log
8585

8686
- \[MMMM YYYY\] Created
8787

88-
## [Appendix] Champions
88+
## %appendix% Champions
8989

9090
| Champion | Company | Email | URI |
9191
| -------------------------- | ------- | ----------------------- | -------------------------------- |

‎specs/proposals/vocabularies.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -258,11 +258,11 @@ worth the time and effort to fill in this section just yet. As such, please
258258
read the above sections for loose requirements. For tighter requirements,
259259
please assume conformance with the 2020-12 Core and Validation specifications.*
260260

261-
## [Appendix] Change Log
261+
## %appendix% Change Log
262262

263263
- 2024年06月10日 - Created
264264

265-
## [Appendix] Champions
265+
## %appendix% Champions
266266

267267
| Champion | Company | Email | URI |
268268
| ----------- | ------- | ------------------------------ | ------------------------------- |

0 commit comments

Comments
(0)

AltStyle によって変換されたページ (->オリジナル) /