File tree Expand file tree Collapse file tree 1 file changed +7
-4
lines changed Expand file tree Collapse file tree 1 file changed +7
-4
lines changed Original file line number Diff line number Diff line change 1
1
# Decoupling from IETF
2
2
3
3
* Status: accepted
4
- * Deciders: @jdesrosiers @relequestual @awwright
4
+ * Deciders: @jdesrosiers @relequestual @awwright @ handrews
5
5
* Date: 2022-08-17
6
6
7
7
Related Issues:
@@ -123,9 +123,12 @@ we don't have the same unpleasant history with W3C than we do with IETF.
123
123
* Not being associated with a recognized standards organization such as IETF,
124
124
W3C, or IEEE reduces the credibility of JSON Schema in the eyes of some.
125
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.
126
+ development that told us that they were comfortable referencing OpenAPI's self
127
+ published specification in their standards and that OpenAPI's membership with
128
+ the Linux Foundation was an important aspect of what makes them comfortable
129
+ doing so. JSON Schema is a member of the OpenJS Foundation, which is a
130
+ sub-group of the Linux Foundation, so we expect standards developers to be
131
+ just as comfortable referencing JSON Schema as they are referencing OpenAPI.
129
132
* If we don't go the standardization route with IETF or W3C, we lose access to
130
133
their expert review process.
131
134
* One of the benefits of an RFC is other standards can normatively reference it,
You can’t perform that action at this time.
0 commit comments