Skip to content

Commit cd373ea

Browse files
jdesrosiersRelequestual
authored andcommitted
ADR decouping from IETF draft 4
Include feedback about referencing JSON Schema in other standards without the backing of a recognized standards body.
1 parent b538730 commit cd373ea

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

adr/2022-08-decouple-from-ietf.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -122,9 +122,10 @@ we don't have the same unpleasant history with W3C than we do with IETF.
122122

123123
* Not being associated with a recognized standards organization such as IETF,
124124
W3C, or IEEE reduces the credibility of JSON Schema in the eyes of some.
125-
However, people seem comfortable adopting OpenAPI without it being associated
126-
with a standards organization, so we don't expect this to be a significant
127-
issue for JSON Schema either.
125+
However, we have received feedback from people involved in standards
126+
development that say they are comfortable adopting OpenAPI without it being
127+
associated with a standards organization, so we don't expect this to be a
128+
significant issue for JSON Schema either.
128129
* If we don't go the standardization route with IETF or W3C, we lose access to
129130
their expert review process.
130131
* One of the benefits of an RFC is other standards can normatively reference it,

0 commit comments

Comments
 (0)