Skip to content

Commit 0dd82e8

Browse files
fgefge
committed
Fixes to core spec
* Fix typo in URI resolution section. * Change the wording about non JSON Pointer fragments in JSON References. * Fix some spelling mistakes. Thanks-to: Alain Fagot <alain.fagot@gmail.com> Thanks-to: Tim Olson <kashapa@gmail.com>
1 parent e196905 commit 0dd82e8

File tree

3 files changed

+36
-36
lines changed

3 files changed

+36
-36
lines changed

‎proposals/json-schema-core.html‎

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -143,9 +143,9 @@
143143
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc">&nbsp;TOC&nbsp;</a></td></tr></table>
144144
<table summary="layout" width="66%" border="0" cellpadding="0" cellspacing="0"><tr><td><table summary="layout" width="100%" border="0" cellpadding="2" cellspacing="1">
145145
<tr><td class="header">Internet Engineering Task Force</td><td class="header">fge. Galiegue</td></tr>
146-
<tr><td class="header">Internet-Draft</td><td class="header">January 21, 2013</td></tr>
146+
<tr><td class="header">Internet-Draft</td><td class="header">January 25, 2013</td></tr>
147147
<tr><td class="header">Intended status: Informational</td><td class="header">&nbsp;</td></tr>
148-
<tr><td class="header">Expires: July 25, 2013</td><td class="header">&nbsp;</td></tr>
148+
<tr><td class="header">Expires: July 29, 2013</td><td class="header">&nbsp;</td></tr>
149149
</table></td></tr></table>
150150
<h1><br />JSON Schema: core definitions and terminology<br />json-schema-core</h1>
151151

@@ -174,7 +174,7 @@ <h3>Status of This Memo</h3>
174174
It is inappropriate to use Internet-Drafts as reference material or to cite
175175
them other than as &ldquo;work in progress.&rdquo;</p>
176176
<p>
177-
This Internet-Draft will expire on July 25, 2013.</p>
177+
This Internet-Draft will expire on July 29, 2013.</p>
178178

179179
<h3>Copyright Notice</h3>
180180
<p>
@@ -341,7 +341,7 @@ <h3>Table of Contents</h3>
341341
<p>
342342
A JSON Schema is a JSON document, and that document MUST be an object. Object
343343
members (or properties) defined by JSON Schema (this specification, or related
344-
specifcations) are called keywords, or schema keywords.
344+
specifications) are called keywords, or schema keywords.
345345

346346
</p>
347347
<p>
@@ -507,7 +507,7 @@ <h3>Table of Contents</h3>
507507
JSON Schema allows applications to validate instances, either non interactively
508508
or interactively. For instance, an application may collect JSON data and check
509509
that this data matches a given set of constraints; another application may use a
510-
JSON Schema to build an interactve interface in order to collect user input
510+
JSON Schema to build an interactive interface in order to collect user input
511511
according to constraints described by JSON Schema.
512512

513513
</p>
@@ -656,7 +656,7 @@ <h3>Table of Contents</h3>
656656
against the current version of the specification);
657657
</p>
658658
<p>"http://json-schema.org/draft-04/schema#" (JSON Schema written
659-
against against JSON Schema, draft v4 -- this version);
659+
against JSON Schema, draft v4 -- this version);
660660
</p>
661661
<p>"http://json-schema.org/draft-04/hyper-schema#" (JSON Schema hyperschema
662662
written against JSON Schema, draft v4 -- this version);
@@ -789,7 +789,7 @@ <h3>Table of Contents</h3>
789789
<dd>http://x.y.z/otherschema.json#
790790
</dd>
791791
<dt>#/schema2/nested</dt>
792-
<dd>http://x.y.z/rootschema.json#bar
792+
<dd>http://x.y.z/otherschema.json#bar
793793
</dd>
794794
<dt>#/schema2/alsonested</dt>
795795
<dd>http://x.y.z/t/inner.json#a
@@ -910,8 +910,8 @@ <h3>Table of Contents</h3>
910910
<p>
911911
Extended JSON References using fragments which are not JSON Pointers are not
912912
dereferenceable by implementations choosing not to support inline dereferencing.
913-
This addressing mechanism is defined for backwards compatibility, and SHOULD NOT
914-
be used in new schemas.
913+
This kind of reference is defined for backwards compatibility, and SHOULD NOT be
914+
used in new schemas.
915915

916916
</p>
917917
<a name="anchor33"></a><br /><hr />

‎proposals/json-schema-core.txt‎

Lines changed: 21 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -2,9 +2,9 @@
22

33

44
Internet Engineering Task Force fge. Galiegue
5-
Internet-Draft January 21, 2013
5+
Internet-Draft January 25, 2013
66
Intended status: Informational
7-
Expires: July 25, 2013
7+
Expires: July 29, 2013
88

99

1010
JSON Schema: core definitions and terminology
@@ -34,7 +34,7 @@ Status of This Memo
3434
time. It is inappropriate to use Internet-Drafts as reference
3535
material or to cite them other than as "work in progress."
3636

37-
This Internet-Draft will expire on July 25, 2013.
37+
This Internet-Draft will expire on July 29, 2013.
3838

3939
Copyright Notice
4040

@@ -52,7 +52,7 @@ Copyright Notice
5252

5353

5454

55-
Galiegue Expires July 25, 2013 [Page 1]
55+
Galiegue Expires July 29, 2013 [Page 1]
5656

5757
Internet-Draft JSON Schema January 2013
5858

@@ -108,7 +108,7 @@ Table of Contents
108108

109109

110110

111-
Galiegue Expires July 25, 2013 [Page 2]
111+
Galiegue Expires July 29, 2013 [Page 2]
112112

113113
Internet-Draft JSON Schema January 2013
114114

@@ -150,7 +150,7 @@ Internet-Draft JSON Schema January 2013
150150

151151
A JSON Schema is a JSON document, and that document MUST be an
152152
object. Object members (or properties) defined by JSON Schema (this
153-
specification, or related specifcations) are called keywords, or
153+
specification, or related specifications) are called keywords, or
154154
schema keywords.
155155

156156
A JSON Schema MAY contain properties which are not schema keywords.
@@ -164,7 +164,7 @@ Internet-Draft JSON Schema January 2013
164164

165165

166166

167-
Galiegue Expires July 25, 2013 [Page 3]
167+
Galiegue Expires July 29, 2013 [Page 3]
168168

169169
Internet-Draft JSON Schema January 2013
170170

@@ -220,7 +220,7 @@ Internet-Draft JSON Schema January 2013
220220

221221

222222

223-
Galiegue Expires July 25, 2013 [Page 4]
223+
Galiegue Expires July 29, 2013 [Page 4]
224224

225225
Internet-Draft JSON Schema January 2013
226226

@@ -276,14 +276,14 @@ Internet-Draft JSON Schema January 2013
276276

277277

278278

279-
Galiegue Expires July 25, 2013 [Page 5]
279+
Galiegue Expires July 29, 2013 [Page 5]
280280

281281
Internet-Draft JSON Schema January 2013
282282

283283

284284
collect JSON data and check that this data matches a given set of
285285
constraints; another application may use a JSON Schema to build an
286-
interactve interface in order to collect user input according to
286+
interactive interface in order to collect user input according to
287287
constraints described by JSON Schema.
288288

289289
4.2. Hypermedia and linking
@@ -332,7 +332,7 @@ Internet-Draft JSON Schema January 2013
332332

333333

334334

335-
Galiegue Expires July 25, 2013 [Page 6]
335+
Galiegue Expires July 29, 2013 [Page 6]
336336

337337
Internet-Draft JSON Schema January 2013
338338

@@ -388,13 +388,13 @@ Internet-Draft JSON Schema January 2013
388388

389389

390390

391-
Galiegue Expires July 25, 2013 [Page 7]
391+
Galiegue Expires July 29, 2013 [Page 7]
392392

393393
Internet-Draft JSON Schema January 2013
394394

395395

396396
"http://json-schema.org/draft-04/schema#" (JSON Schema written
397-
against against JSON Schema, draft v4 -- this version);
397+
against JSON Schema, draft v4 -- this version);
398398

399399
"http://json-schema.org/draft-04/hyper-schema#" (JSON Schema
400400
hyperschema written against JSON Schema, draft v4 -- this
@@ -444,7 +444,7 @@ Internet-Draft JSON Schema January 2013
444444

445445

446446

447-
Galiegue Expires July 25, 2013 [Page 8]
447+
Galiegue Expires July 29, 2013 [Page 8]
448448

449449
Internet-Draft JSON Schema January 2013
450450

@@ -493,14 +493,14 @@ Internet-Draft JSON Schema January 2013
493493

494494
#/schema2 http://x.y.z/otherschema.json#
495495

496-
#/schema2/nested http://x.y.z/rootschema.json#bar
496+
#/schema2/nested http://x.y.z/otherschema.json#bar
497497

498498

499499

500500

501501

502502

503-
Galiegue Expires July 25, 2013 [Page 9]
503+
Galiegue Expires July 29, 2013 [Page 9]
504504

505505
Internet-Draft JSON Schema January 2013
506506

@@ -556,7 +556,7 @@ Internet-Draft JSON Schema January 2013
556556

557557

558558

559-
Galiegue Expires July 25, 2013 [Page 10]
559+
Galiegue Expires July 29, 2013 [Page 10]
560560

561561
Internet-Draft JSON Schema January 2013
562562

@@ -593,7 +593,7 @@ Internet-Draft JSON Schema January 2013
593593

594594
Extended JSON References using fragments which are not JSON Pointers
595595
are not dereferenceable by implementations choosing not to support
596-
inline dereferencing. This addressing mechanism is defined for
596+
inline dereferencing. This kind of reference is defined for
597597
backwards compatibility, and SHOULD NOT be used in new schemas.
598598

599599
8. Recommended correlation mechanisms for use with the HTTP protocol
@@ -612,7 +612,7 @@ Internet-Draft JSON Schema January 2013
612612

613613

614614

615-
Galiegue Expires July 25, 2013 [Page 11]
615+
Galiegue Expires July 29, 2013 [Page 11]
616616

617617
Internet-Draft JSON Schema January 2013
618618

@@ -668,7 +668,7 @@ Internet-Draft JSON Schema January 2013
668668

669669

670670

671-
Galiegue Expires July 25, 2013 [Page 12]
671+
Galiegue Expires July 29, 2013 [Page 12]
672672

673673
Internet-Draft JSON Schema January 2013
674674

@@ -724,5 +724,5 @@ Author's Address
724724

725725

726726

727-
Galiegue Expires July 25, 2013 [Page 13]
727+
Galiegue Expires July 29, 2013 [Page 13]
728728

‎proposals/json-schema-core.xml‎

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -91,7 +91,7 @@
9191
<t>
9292
A JSON Schema is a JSON document, and that document MUST be an object. Object
9393
members (or properties) defined by JSON Schema (this specification, or related
94-
specifcations) are called keywords, or schema keywords.
94+
specifications) are called keywords, or schema keywords.
9595
</t>
9696

9797
<t>
@@ -215,7 +215,7 @@
215215
JSON Schema allows applications to validate instances, either non interactively
216216
or interactively. For instance, an application may collect JSON data and check
217217
that this data matches a given set of constraints; another application may use a
218-
JSON Schema to build an interactve interface in order to collect user input
218+
JSON Schema to build an interactive interface in order to collect user input
219219
according to constraints described by JSON Schema.
220220
</t>
221221
</section>
@@ -330,7 +330,7 @@
330330
<t>"http://json-schema.org/hyper-schema#" (JSON Schema written
331331
against the current version of the specification);</t>
332332
<t>"http://json-schema.org/draft-04/schema#" (JSON Schema written
333-
against against JSON Schema, draft v4 -- this version);</t>
333+
against JSON Schema, draft v4 -- this version);</t>
334334
<t>"http://json-schema.org/draft-04/hyper-schema#" (JSON Schema hyperschema
335335
written against JSON Schema, draft v4 -- this version);</t>
336336
<t>"http://json-schema.org/draft-03/schema#" (JSON Schema written
@@ -438,7 +438,7 @@
438438
<t hangText="# (document root)">http://x.y.z/rootschema.json#</t>
439439
<t hangText="#/schema1">http://x.y.z/rootschema.json#foo</t>
440440
<t hangText="#/schema2">http://x.y.z/otherschema.json#</t>
441-
<t hangText="#/schema2/nested">http://x.y.z/rootschema.json#bar</t>
441+
<t hangText="#/schema2/nested">http://x.y.z/otherschema.json#bar</t>
442442
<t hangText="#/schema2/alsonested">http://x.y.z/t/inner.json#a</t>
443443
<t hangText="#/schema3">some://where.else/completely#</t>
444444
</list>
@@ -549,8 +549,8 @@
549549
<t>
550550
Extended JSON References using fragments which are not JSON Pointers are not
551551
dereferenceable by implementations choosing not to support inline dereferencing.
552-
This addressing mechanism is defined for backwards compatibility, and SHOULD NOT
553-
be used in new schemas.
552+
This kind of reference is defined for backwards compatibility, and SHOULD NOT be
553+
used in new schemas.
554554
</t>
555555
</section>
556556
</section>

0 commit comments

Comments
 (0)