Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Sign up
Appearance settings

Commit c7bac11

Browse files
dlaxhandrews
authored andcommitted
Reformat jsonschema-validation.xml to 100 columns
1 parent 131e0cb commit c7bac11

File tree

1 file changed

+66
-35
lines changed

1 file changed

+66
-35
lines changed

‎jsonschema-validation.xml‎

Lines changed: 66 additions & 35 deletions
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,9 @@
2121
<?rfc inline="yes" ?>
2222
<rfc category="info" docName="draft-wright-json-schema-validation-01" ipr="trust200902">
2323
<front>
24-
<title abbrev="JSON Schema Validation">JSON Schema Validation: A Vocabulary for Structural Validation of JSON</title>
24+
<title abbrev="JSON Schema Validation">
25+
JSON Schema Validation: A Vocabulary for Structural Validation of JSON
26+
</title>
2527

2628
<author fullname="Austin Wright" initials="A" surname="Wright" role="editor">
2729
<address>
@@ -50,22 +52,25 @@
5052

5153
<abstract>
5254
<t>
53-
JSON Schema (application/schema+json) has several purposes, one of which is JSON instance validation.
54-
This document specifies a vocabulary for JSON Schema to describe the meaning of JSON documents,
55-
provide hints for user interfaces working with JSON data,
56-
and to make assertions about what a valid document must look like.
55+
JSON Schema (application/schema+json) has several purposes, one of which is JSON
56+
instance validation.
57+
This document specifies a vocabulary for JSON Schema to describe the meaning of JSON
58+
documents, provide hints for user interfaces working with JSON data, and to make
59+
assertions about what a valid document must look like.
5760
</t>
5861
</abstract>
5962

6063
<note title="Note to Readers">
6164
<t>
62-
The issues list for this draft can be found at <eref target="https://github.com/json-schema-org/json-schema-spec/issues"/>.
65+
The issues list for this draft can be found at
66+
<eref target="https://github.com/json-schema-org/json-schema-spec/issues"/>.
6367
</t>
6468
<t>
6569
For additional information, see <eref target="http://json-schema.org/"/>.
6670
</t>
6771
<t>
68-
To provide feedback, use this issue tracker, the communication methods listed on the homepage, or email the document editors.
72+
To provide feedback, use this issue tracker, the communication methods listed on the
73+
homepage, or email the document editors.
6974
</t>
7075
</note>
7176
</front>
@@ -116,7 +121,8 @@
116121

117122
<section title="Validation of numeric instances">
118123
<t>
119-
The JSON specification allows numbers with arbitrary precision, and JSON Schema does not add any such bounds.
124+
The JSON specification allows numbers with arbitrary precision, and JSON Schema
125+
does not add any such bounds.
120126
This means that numeric instances processed by JSON Schema can be arbitrarily large and/or
121127
have an arbitrarily long decimal part, regardless of the ability of the
122128
underlying programming language to deal with such data.
@@ -167,8 +173,10 @@
167173
validation succeeds.
168174
</t>
169175
<t>
170-
For example, the "maxLength" keyword will only restrict certain strings (that are too long) from being valid.
171-
If the instance is a number, boolean, null, array, or object, the keyword passes validation.
176+
For example, the "maxLength" keyword will only restrict certain strings (that
177+
are too long) from being valid.
178+
If the instance is a number, boolean, null, array, or object, the keyword passes
179+
validation.
172180
</t>
173181
</section>
174182

@@ -204,8 +212,8 @@
204212
</t>
205213
<t>
206214
Validation keywords that are missing never restrict validation.
207-
In some cases, this no-op behavior is identical to a keyword that exists with certain values,
208-
and these values are noted where known.
215+
In some cases, this no-op behavior is identical to a keyword that exists with
216+
certain values, and these values are noted where known.
209217
</t>
210218
</section>
211219

@@ -217,8 +225,13 @@
217225
<t>
218226
For schema author convenience, there are some exceptions:
219227
<list>
220-
<t>"additionalProperties", whose behavior is defined in terms of "properties" and "patternProperties"; and</t>
221-
<t>"additionalItems", whose behavior is defined in terms of "items".</t>
228+
<t>
229+
"additionalProperties", whose behavior is defined in terms of
230+
"properties" and "patternProperties"; and
231+
</t>
232+
<t>
233+
"additionalItems", whose behavior is defined in terms of "items".
234+
</t>
222235
</list>
223236
</t>
224237
</section>
@@ -227,57 +240,68 @@
227240

228241
<section title="Meta-schema">
229242
<t>
230-
The current URI for the JSON Schema Validation is &lt;http://json-schema.org/draft-06/schema#&gt;.
243+
The current URI for the JSON Schema Validation is
244+
&lt;http://json-schema.org/draft-06/schema#&gt;.
231245
</t>
232246
</section>
233247

234248
<section title="Validation keywords">
235249
<t>
236-
Validation keywords in a schema impose requirements for successful validation of an instance.
250+
Validation keywords in a schema impose requirements for successful validation of an
251+
instance.
237252
</t>
238253

239254
<section title="multipleOf">
240255
<t>
241256
The value of "multipleOf" MUST be a number, strictly greater than 0.
242257
</t>
243258
<t>
244-
A numeric instance is valid only if division by this keyword's value results in an integer.
259+
A numeric instance is valid only if division by this keyword's value results in
260+
an integer.
245261
</t>
246262
</section>
247263

248264
<section title="maximum">
249265
<t>
250-
The value of "maximum" MUST be a number, representing an inclusive upper limit for a numeric instance.
266+
The value of "maximum" MUST be a number, representing an inclusive upper limit
267+
for a numeric instance.
251268
</t>
252269
<t>
253-
If the instance is a number, then this keyword validates only if the instance is less than or exactly equal to "maximum".
270+
If the instance is a number, then this keyword validates only if the instance is
271+
less than or exactly equal to "maximum".
254272
</t>
255273
</section>
256274

257275
<section title="exclusiveMaximum">
258276
<t>
259-
The value of "exclusiveMaximum" MUST be number, representing an exclusive upper limit for a numeric instance.
277+
The value of "exclusiveMaximum" MUST be number, representing an exclusive upper
278+
limit for a numeric instance.
260279
</t>
261280
<t>
262-
If the instance is a number, then the instance is valid only if it has a value strictly less than (not equal to) "exclusiveMaximum".
281+
If the instance is a number, then the instance is valid only if it has a value
282+
strictly less than (not equal to) "exclusiveMaximum".
263283
</t>
264284
</section>
265285

266286
<section title="minimum">
267287
<t>
268-
The value of "minimum" MUST be a number, representing an inclusive upper limit for a numeric instance.
288+
The value of "minimum" MUST be a number, representing an inclusive upper limit
289+
for a numeric instance.
269290
</t>
270291
<t>
271-
If the instance is a number, then this keyword validates only if the instance is greater than or exactly equal to "minimum".
292+
If the instance is a number, then this keyword validates only if the instance is
293+
greater than or exactly equal to "minimum".
272294
</t>
273295
</section>
274296

275297
<section title="exclusiveMinimum">
276298
<t>
277-
The value of "exclusiveMinimum" MUST be number, representing an exclusive upper limit for a numeric instance.
299+
The value of "exclusiveMinimum" MUST be number, representing an exclusive upper
300+
limit for a numeric instance.
278301
</t>
279302
<t>
280-
If the instance is a number, then the instance is valid only if it has a value strictly greater than (not equal to) "exclusiveMinimum".
303+
If the instance is a number, then the instance is valid only if it has a value
304+
strictly greater than (not equal to) "exclusiveMinimum".
281305
</t>
282306
</section>
283307

@@ -327,7 +351,8 @@
327351

328352
<section title="items">
329353
<t>
330-
The value of "items" MUST be either a valid JSON Schema or an array of valid JSON Schemas.
354+
The value of "items" MUST be either a valid JSON Schema or an array of valid
355+
JSON Schemas.
331356
</t>
332357
<t>
333358
This keyword determines how child instances validate for arrays,
@@ -551,8 +576,8 @@
551576
The value of "propertyNames" MUST be a valid JSON Schema.
552577
</t>
553578
<t>
554-
If the instance is an object, this keyword validates if every property name in the instance
555-
validates against the provided schema.
579+
If the instance is an object, this keyword validates if every property name in
580+
the instance validates against the provided schema.
556581
Note the property name that the schema is testing will always be a string.
557582
</t>
558583
<t>
@@ -595,7 +620,8 @@
595620
or "integer" which matches any number with a zero fractional part.
596621
</t>
597622
<t>
598-
An instance validates if and only if the instance is in any of the sets listed for this keyword.
623+
An instance validates if and only if the instance is in any of the sets listed
624+
for this keyword.
599625
</t>
600626
</section>
601627

@@ -831,7 +857,8 @@
831857
This attribute applies to string instances.
832858
</t>
833859
<t>
834-
A string instance is valid against this attribute if it is a valid URI Reference (either a URI or a relative-reference),
860+
A string instance is valid against this attribute if it is a valid URI
861+
Reference (either a URI or a relative-reference),
835862
according to <xref target="RFC3986"/>.
836863
</t>
837864
</section>
@@ -860,13 +887,17 @@
860887

861888
<section title="Security considerations">
862889
<t>
863-
JSON Schema validation defines a vocabulary for JSON Schema core and concerns all the security considerations listed there.
890+
JSON Schema validation defines a vocabulary for JSON Schema core and concerns all
891+
the security considerations listed there.
864892
</t>
865893
<t>
866-
JSON Schema validation allows the use of Regular Expressions, which have numerous different (often incompatible) implementations.
867-
Some implementations allow the embedding of arbitrary code, which is outside the scope of JSON Schema and MUST NOT be permitted.
868-
Regular expressions can often also be crafted to be extremely expensive to compute (with so-called "catastrophic backtracking"),
869-
resulting in a denial-of-service attack.
894+
JSON Schema validation allows the use of Regular Expressions, which have numerous
895+
different (often incompatible) implementations.
896+
Some implementations allow the embedding of arbitrary code, which is outside the
897+
scope of JSON Schema and MUST NOT be permitted.
898+
Regular expressions can often also be crafted to be extremely expensive to compute
899+
(with so-called "catastrophic backtracking"), resulting in a denial-of-service
900+
attack.
870901
</t>
871902
</section>
872903

0 commit comments

Comments
(0)

AltStyle によって変換されたページ (->オリジナル) /