-
-
Notifications
You must be signed in to change notification settings - Fork 256
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
format
as a annotation by default - separate vocabs (option 3)
#1027
Changes from 1 commit
62b9c21
9949508
9d29a9f
8acb128
242cfd0
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -540,20 +540,19 @@ | |
|
||
<t> | ||
The current URI for this vocabulary, known as the Format-Annotation vocabulary, is: | ||
<https://json-schema.org/draft/2020-11/vocab/format-annotation>. This vocabulary | ||
is required by this specification. | ||
<https://json-schema.org/draft/2020-11/vocab/format-annotation>. The current | ||
URI for the corresponding meta-schema is: | ||
<eref target="https://json-schema.org/draft/2020-11/meta/format-annotation"/>. | ||
Implementing support for this vocabulary is REQUIRED. | ||
</t> | ||
<t> | ||
In addition to the Format-Annotation vocabulary, a secondary vocabulary is available | ||
for custom meta-schemas that defines "format" as an assertion. The URI for the | ||
Format-Assertion vocabulary, is: | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. remove comma |
||
<https://json-schema.org/draft/2020-11/vocab/format-assertion>. | ||
</t> | ||
<t> | ||
The current URI for the corresponding meta-schema is: | ||
<eref target="https://json-schema.org/draft/2020-11/meta/format"/>. Because the | ||
syntactic requirements of "format" do not change between the annotation and assertion | ||
vocabularies, the meta-schema is shared between them. | ||
<https://json-schema.org/draft/2020-11/vocab/format-assertion>. The current | ||
URI for the corresponding meta-schema is: | ||
<eref target="https://json-schema.org/draft/2020-11/meta/format-assertion"/>. | ||
Implementing support for the Format-Assertion vocabulary is OPTIONAL. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. suggested change:
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. OPTIONAL is proper language. RFC 2119 section 5. |
||
</t> | ||
<t> | ||
Specifying both the Format-Annotation and the Format-Assertion vocabularies is functionally | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,14 @@ | ||
{ | ||
"$schema": "https://json-schema.org/draft/2019-09/schema", | ||
"$id": "https://json-schema.org/draft/2019-09/meta/format-annotation", | ||
"$vocabulary": { | ||
"https://json-schema.org/draft/2019-09/vocab/format-annotation": true | ||
}, | ||
"$dynamicAnchor": "meta", | ||
|
||
"title": "Format vocabulary meta-schema", | ||
gregsdennis marked this conversation as resolved.
Show resolved
Hide resolved
|
||
"type": ["object", "boolean"], | ||
"properties": { | ||
"format": { "type": "string" } | ||
} | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
suggested change (using the proper IETF language):
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
REQUIRED is proper language. RFC 2119 section 1.