Skip to content

Commit 4e0a10e

Browse files
handrewshandrews
authored
Merge pull request #491 from handrews/minor
Rebase previously approved PR
2 parents 5f305b8 + 23fa364 commit 4e0a10e

File tree

3 files changed

+90
-90
lines changed

3 files changed

+90
-90
lines changed

‎jsonschema-core.xml

Lines changed: 25 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -169,7 +169,7 @@
169169
A JSON document to which a schema is applied is known as an "instance".
170170
</t>
171171

172-
<section title="Instance data model">
172+
<section title="Instance Data Model">
173173
<t>
174174
JSON Schema interprets documents according to a data model. A JSON value
175175
interpreted according to this data model is called an "instance".
@@ -211,7 +211,7 @@
211211
</t>
212212
</section>
213213

214-
<section title="Instance media types">
214+
<section title="Instance Media Types">
215215
<t>
216216
JSON Schema is designed to fully work with "application/json" documents,
217217
as well as media types using the "+json" structured syntax suffix.
@@ -230,7 +230,7 @@
230230
</t>
231231
</section>
232232

233-
<section title="Instance equality">
233+
<section title="Instance Equality">
234234
<t>
235235
Two JSON instances are said to be equal if and only if they are of the same type
236236
and have the same value according to the data model. Specifically, this means:
@@ -258,7 +258,7 @@
258258
</section>
259259
</section>
260260

261-
<section title="JSON Schema documents">
261+
<section title="JSON Schema Documents">
262262
<t>
263263
A JSON Schema document, or simply a schema, is a JSON document used to describe
264264
an instance.
@@ -269,7 +269,7 @@
269269
fragment identifier syntax and semantics provided by
270270
"application/schema-instance+json".
271271
</t>
272-
<section title="JSON Schema values and keywords">
272+
<section title="JSON Schema Values and Keywords">
273273
<t>
274274
A JSON Schema MUST be an object or a boolean.
275275
</t>
@@ -314,7 +314,7 @@
314314
properties.
315315
</t>
316316
</section>
317-
<section title="JSON Schema vocabularies" anchor="vocabulary">
317+
<section title="JSON Schema Vocabularies" anchor="vocabulary">
318318
<t>
319319
A JSON Schema vocabulary is a set of keywords defined for a particular
320320
purpose. The vocabulary specifies the meaning of its keywords as
@@ -354,7 +354,7 @@
354354
</cref>
355355
</t>
356356
</section>
357-
<section title="Root schema and subschemas">
357+
<section title="Root Schema and Subschemas">
358358
<t>
359359
The root schema is the schema that comprises the entire JSON document
360360
in question.
@@ -386,7 +386,7 @@
386386

387387
</section>
388388

389-
<section title="Fragment identifiers" anchor="fragments">
389+
<section title="Fragment Identifiers" anchor="fragments">
390390
<t>
391391
In accordance with section 3.1 of <xref target="RFC6839"></xref>,
392392
the syntax and semantics of fragment identifiers specified for
@@ -424,17 +424,17 @@
424424
</t>
425425
</section>
426426

427-
<section title="General considerations">
427+
<section title="General Considerations">
428428

429-
<section title="Range of JSON values">
429+
<section title="Range of JSON Values">
430430
<t>
431431
An instance may be any valid JSON value as defined by <xref target="RFC7159">JSON</xref>.
432432
JSON Schema imposes no restrictions on type: JSON Schema can describe any JSON
433433
value, including, for example, null.
434434
</t>
435435
</section>
436436

437-
<section title="Programming language independence" anchor="language">
437+
<section title="Programming Language Independence" anchor="language">
438438
<t>
439439
JSON Schema is programming language agnostic, and supports the full range of
440440
values described in the data model.
@@ -443,7 +443,7 @@
443443
</t>
444444
</section>
445445

446-
<section title="Mathematical integers" anchor="integers">
446+
<section title="Mathematical Integers" anchor="integers">
447447
<t>
448448
Some programming languages and parsers use different internal representations
449449
for floating point numbers than they do for integers.
@@ -476,7 +476,7 @@
476476

477477
</section>
478478

479-
<section title='The "$schema" keyword'>
479+
<section title='The "$schema" Keyword'>
480480
<!-- TODO a custom $schema keyword might also be used to enforce minimum required functionality of a validator -->
481481
<t>
482482
The "$schema" keyword is both used as a JSON Schema version identifier and the
@@ -521,7 +521,7 @@
521521
</t>
522522
</section>
523523

524-
<section title='Schema references with "$ref"'>
524+
<section title='Schema References With "$ref"'>
525525
<t>
526526
The "$ref" keyword is used to reference a schema, and provides the ability to
527527
validate recursive structures through self-reference.
@@ -548,8 +548,8 @@
548548
</t>
549549
</section>
550550

551-
<section title="Base URI and dereferencing">
552-
<section title="Initial base URI">
551+
<section title="Base URI and Dereferencing">
552+
<section title="Initial Base URI">
553553
<t>
554554
<xref target="RFC3986">RFC3986 Section 5.1</xref> defines how to determine the
555555
default base URI of a document.
@@ -560,7 +560,7 @@
560560
</t>
561561
</section>
562562

563-
<section title='The "$id" keyword' anchor="id-keyword">
563+
<section title='The "$id" Keyword' anchor="id-keyword">
564564
<t>
565565
The "$id" keyword defines a URI for the schema, and the base URI that
566566
other URI references within the schema are resolved against.
@@ -646,7 +646,7 @@
646646
<t hangText="#/definitions/C">urn:uuid:ee564b8a-7a87-4125-8c96-e9f123d6766f</t>
647647
</list>
648648
</t>
649-
<section title="Internal references">
649+
<section title="Internal References">
650650
<t>
651651
Schemas can be identified by any URI that has been given to them, including
652652
a JSON Pointer or their URI given directly by "$id".
@@ -692,7 +692,7 @@
692692
resolve the fragment against the base URI.
693693
</t>
694694
</section>
695-
<section title="External references">
695+
<section title="External References">
696696
<t>
697697
To differentiate schemas between each other in a vast ecosystem, schemas are
698698
identified by URI. As specified above, this does not necessarily mean
@@ -714,7 +714,7 @@
714714
</section>
715715
</section>
716716

717-
<section title='Comments with "$comment"'>
717+
<section title='Comments With "$comment"'>
718718
<t>
719719
This keyword is reserved for comments from schema authors to readers or
720720
maintainers of the schema.
@@ -746,7 +746,7 @@
746746
</t>
747747
</section>
748748

749-
<section title="Usage for hypermedia">
749+
<section title="Usage for Hypermedia">
750750

751751
<t>
752752
JSON has been adopted widely by HTTP servers for automated APIs and robots. This
@@ -755,7 +755,7 @@
755755
<xref target="RFC8288">Web linking</xref>.
756756
</t>
757757

758-
<section title='Linking to a schema'>
758+
<section title='Linking to a Schema'>
759759
<t>
760760
It is RECOMMENDED that instances described by a schema provide a link to
761761
a downloadable JSON Schema using the link relation "describedby", as defined by
@@ -778,7 +778,7 @@ Link: <http://example.com/my-hyper-schema#>; rel="describedby"
778778
</section>
779779

780780

781-
<section title='Identifying a schema via a media type parameter' anchor="parameter">
781+
<section title='Identifying a Schema via a Media Type Parameter' anchor="parameter">
782782
<t>
783783
Media types MAY allow for a "schema" media type parameter, which gives
784784
HTTP servers the ability to perform Content-Type Negotiation based on schema.
@@ -847,7 +847,7 @@ Link: </alice>;rel="schema", </bob>;rel="schema"
847847

848848
</section>
849849

850-
<section title="Usage over HTTP">
850+
<section title="Usage Over HTTP">
851851
<t>
852852
When used for hypermedia systems over a network,
853853
<xref target="RFC7231">HTTP</xref> is frequently the protocol of choice for
@@ -883,7 +883,7 @@ User-Agent: product-name/5.4.1 so-cool-json-schema/1.0.2 curl/7.43.0
883883

884884
</section>
885885

886-
<section title="Security considerations" anchor="security">
886+
<section title="Security Considerations" anchor="security">
887887
<t>
888888
Both schemas and instances are JSON values. As such, all security considerations
889889
defined in <xref target="RFC7159">RFC 7159</xref> apply.

0 commit comments

Comments
 (0)