Change appendix heading pattern

README.md

@@ -54,7 +54,7 @@ features they make available to you.
 - [remark-headings](/json-schema-org/json-schema-spec/blob/main/remark-headings.js)
   -- A collection of enhancements for headings.
   - Adds hierarchical section numbers to headings.
-    - Use the `[Appendix]` prefix on headings that should be numbered as an
+    - Use the `%appendix%` prefix on headings that should be numbered as an
       appendix.
   - Adds id anchors to headers that don't have one
     - Example: `#section-2-13`

remark/remark-headings.js

@@ -7,7 +7,7 @@ import { toString as nodeToString } from "mdast-util-to-string";
 const defaultOptions = {
   startDepth: 1,
   skip: [],
-  appendixToken: "[Appendix]",
+  appendixToken: "%appendix%",
   appendixPrefix: "Appendix"
 };
 

specs/jsonschema-core.md

@@ -2156,7 +2156,7 @@ Bray, T., Ed., Hollander, D., Ed., Layman, A., Ed., and R. Tobin, Ed.,
 "Namespaces in XML 1.1 (Second Edition)", August 2006,
 <<http://www.w3.org/TR/2006/REC-xml-names11-20060816>>.
 
-## [Appendix] Schema identification examples {#idexamples}
+## %appendix% Schema identification examples {#idexamples}
 
 Consider the following schema, which shows `$id` being used to identify both the
 root schema and various subschemas, and `$anchor` being used to define plain
@@ -2258,7 +2258,7 @@ Document location `/$defs/C`:
 - base IRI of enclosing (root.json) resource plus fragment:
   `https://example.com/root.json#/$defs/C`
 
-## [Appendix] Manipulating schema documents and references
+## %appendix% Manipulating schema documents and references
 
 Various tools have been created to rearrange schema documents based on how and
 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
 transformations, as they depend not only on the schema structure but also on the
 intended usage.
 
-## [Appendix] Example of recursive schema extension {#recursive-example}
+## %appendix% Example of recursive schema extension {#recursive-example}
 
 Consider the following two schemas describing a simple recursive tree structure,
 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
 `$dynamicAnchor` values which tell us how to resolve the dynamic reference, not
 any sort of correlation in JSON structure.
 
-## [Appendix] References and generative use cases
+## %appendix% References and generative use cases
 
 While the presence of references is expected to be transparent to validation
 results, generative use cases such as code generators and UI renderers often
@@ -2444,7 +2444,7 @@ instance of a distinct class.
 This style of usage requires the annotation to be in the same object as the
 reference, which must be recognizable as a reference.
 
-## [Appendix] Acknowledgments
+## %appendix% Acknowledgments
 
 Thanks to Gary Court, Francis Galiegue, Kris Zyp, Geraint Luff, and Henry
 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
 Sturgeon, Shawn Silverman, and Karen Etheridge for their submissions and patches
 to the document.
 
-## [Appendix] Change Log[^19]
+## %appendix% Change Log[^19]
 
 ### draft-bhutton-json-schema-next
 - Use IRIs instead of URIs, including allowing unicode in plain-name fragments

specs/jsonschema-validation.md

@@ -886,7 +886,7 @@ draft-bhutton-json-schema-01, June 2022,
 Hoehrmann, B., "Scripting Media Types", RFC 4329, DOI 10.17487/RFC4329, April
 2006, <<https://www.rfc-editor.org/info/rfc4329>>.
 
-## [Appendix] Acknowledgments
+## %appendix% Acknowledgments
 
 Thanks to Gary Court, Francis Galiegue, Kris Zyp, Geraint Luff, and Henry
 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
 Sturgeon, Shawn Silverman, and Karen Etheridge for their submissions and patches
 to the document.
 
-## [Appendix] Change Log[^6]
+## %appendix% Change Log[^6]
 
 - *draft-next*
   - Use IRIs instead of URIs

specs/proposals/propertyDependencies-adr.md

@@ -235,7 +235,7 @@ cases carried a lower priority.
 - Properties with non-string values cannot be supported using this keyword and
   the `allOf`-`if`-`then` pattern must still be used.
 
-## [Appendix] Problems With Existing Patterns {#problems}
+## %appendix% Problems With Existing Patterns {#problems}
 
 ### `oneOf`/`anyOf`
 

specs/proposals/propertyDependencies.md

@@ -129,7 +129,7 @@ vocabulary](../jsonschema-core.md#applicators).
     }
     ```
 
-## [Appendix] Change Log
+## %appendix% Change Log
 
 - \[March 2021\] - Initially proposed
 - \[October 2021\] Added to specification document

specs/proposals/proposal-template.md

@@ -81,11 +81,11 @@ For example
     ```
 -->
 
-## [Appendix] Change Log
+## %appendix% Change Log
 
 - \[MMMM YYYY\] Created
 
-## [Appendix] Champions
+## %appendix% Champions
 
 | Champion                   | Company | Email                   | URI                              |
 | -------------------------- | ------- | ----------------------- | -------------------------------- |

specs/proposals/vocabularies.md

@@ -258,11 +258,11 @@ worth the time and effort to fill in this section just yet.  As such, please
 read the above sections for loose requirements.  For tighter requirements,
 please assume conformance with the 2020-12 Core and Validation specifications.*
 
-## [Appendix] Change Log
+## %appendix% Change Log
 
 - 2024-06-10 - Created
 
-## [Appendix] Champions
+## %appendix% Champions
 
 | Champion    | Company | Email                          | URI                             |
 | ----------- | ------- | ------------------------------ | ------------------------------- |