Skip to content

Commit d90219d

Browse files
committed
update template to align with actual proposal
1 parent ffdd2c3 commit d90219d

File tree

1 file changed

+16
-15
lines changed

1 file changed

+16
-15
lines changed

proposals/proposal-template.md

+16-15
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ This document proposes a change to the ??? specification by adding ???.
1919

2020
<!--
2121
Status is free text: just something to explain where the proposal is in
22-
its journey. This status does not align with the SLDC feature life cycle.
22+
its journey. This status does not align with the SDLC feature life cycle.
2323
-->
2424

2525
## Note to Readers
@@ -60,26 +60,27 @@ also apply to this document.
6060

6161
## Change Details
6262

63-
### Target
64-
6563
<!--
66-
Where does this change go?
64+
This is where the specification changes are defined. This must be precise as
65+
these changes will be made verbatim.
6766
6867
For example
6968
70-
This proposal will add the {{propertyDependencies}} section contained herein as
71-
a subsection of JSON Schema Core, section 10.2.2 "Keywords for Applying
72-
Subschemas Conditionally."
73-
69+
1. The following section will be added to the JSON Schema Core specification as
70+
a subsection of "Keywords for Applying Subschemas Conditionally".
71+
> ### {New section name}
72+
>
73+
> {Feature description}
74+
2. The following subschema will be added to the Applicator Vocabulary schema,
75+
`https://json-schema.org/<version>/<release>/meta/applicator`, at
76+
`/properties/{keyword}`:
77+
```jsonc
78+
{
79+
// keyword schema
80+
}
81+
```
7482
-->
7583

76-
This proposal will add the {{???}} section contained herein as
77-
a subsection of ???.
78-
79-
### ???
80-
81-
<!-- What is the text that will appear in the specification? -->
82-
8384
## [Appendix] Change Log
8485

8586
* [MMMM YYYY] Created

0 commit comments

Comments
 (0)