Skip to content

Commit 48b346b

Browse files
committed
apparently the footnote needs to be at the end for this file
1 parent 54f15de commit 48b346b

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

adr/2024-11-2-assertion-format.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -66,10 +66,6 @@ The primary downside is that the current system of (1) configuring the tool or
6666
(2) incluing the `format-assertion` vocab[^1] is confusing for many and doesn't
6767
align with user expectations.
6868

69-
[^1]: The `format-assertion` vocabulary will no longer be an option since we have
70-
demoted vocabularies to a proposal for the stable release. This leaves tool
71-
configuration as the only option to enable `format` validation.
72-
7369
### `format` becomes an assertion keyword by default
7470

7571
We change the spec to require `format` validation. Furthermore:
@@ -99,3 +95,7 @@ The TSC has decided via vote (see voting issue above) that we should change
9995
validation outcome.
10096
- The burden on implementations will be greater since format validation was
10197
previously optional.
98+
99+
[^1]: The `format-assertion` vocabulary will no longer be an option since we
100+
have demoted vocabularies to a proposal for the stable release. This leaves tool
101+
configuration as the only option to enable `format` validation.

0 commit comments

Comments
 (0)