Skip to content

Commit a74c0a9

Browse files
committed
Link to specific sections in JSON spec from our definitions (#173)
1 parent 04c0399 commit a74c0a9

File tree

1 file changed

+12
-15
lines changed

1 file changed

+12
-15
lines changed

1.0-draft/index.html

Lines changed: 12 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -269,32 +269,30 @@ <h3 data-link-for="conventions">Terms Used</h3>
269269
<ul>
270270
<li>
271271
<dfn data-lt="json object">Object</dfn>
272-
- This is an unordered set of <code>{"name":"value"}</code> pairs. An object begins with <code>{</code> (left brace) and ends with <code>}</code> (right brace). Each name is followed by <code>:</code> (colon) and the <code>{"name":"value"}</code> pairs are separated by <code>,</code> (comma).
272+
- A <a data-cite="RFC8259#section-4">JSON object</a>.
273273
</li>
274274
<li>
275-
<dfn
276-
data-lt="key|keyword|fields">
277-
field
278-
</dfn> - is the alternative term used throughout to refer to the key or name part in a <code>{"name":"value"}</code> pair in a JSON object as defined by [[RFC8259]].
279-
Or more loosely, a "key" in JSON data. The typical convention when dealing with APIs or programmatic querying of
280-
records is to use the term "fields" rather than "keys", so we have chosen to use that term in this specification
281-
when speaking of objects to query/request or respond with.
275+
<dfn data-lt="key|keyword|fields">Field</dfn>
276+
- The alternative term used throughout to refer to the name part of a <code>{"name":"value"}</code> pair in a <a data-cite="RFC8259#section-4">JSON object</a>.
277+
Or more loosely, a "key" in JSON data. The typical convention when dealing with APIs or programmatic querying of
278+
records is to use the term "fields" rather than "keys", so we have chosen to use that term in this specification
279+
when speaking of objects to query/request or respond with.
282280
</li>
283281
<li>
284282
<dfn data-lt="text">String</dfn>
285-
- This is a sequence of zero or more Unicode characters. Strings are written within double quotes and can contain various escape characters.
283+
- A <a data-cite="RFC8259#section-7">JSON string</a>.
286284
</li>
287285
<li>
288-
<dfn data-lt="number">Integer</dfn>
289-
- This is a signed decimal number (ex. 20) that may contain a fractional part and may use exponential E notation. JSON does not support octal or hexadecimal numbers.
286+
<dfn data-lt="integer">Number</dfn>
287+
- A <a data-cite="RFC8259#section-6">JSON number</a>.
290288
</li>
291289
<li>
292290
<dfn data-lt="list">Array</dfn>
293-
- This is an ordered collection of values. An array begins with <code>[</code> (left bracket) and ends with <code>]</code> (right bracket). Values are separated by <code>,</code> (comma).
291+
- A <a data-cite="RFC8259#section-5">JSON array</a>.
294292
</li>
295293
<li>
296294
<dfn>Boolean</dfn>
297-
- This is either <code>true</code> or <code>false</code>.
295+
- A <a data-cite="RFC8259#section-3">JSON value</a> that is either <code>true</code> or <code>false</code>.
298296
</li>
299297

300298
<li>
@@ -386,8 +384,7 @@ <h3 data-link-for="property values">Property Values</h3>
386384
<ul>
387385
<li>A {{string}};</li>
388386
<li>A {{boolean}};</li>
389-
<li>An {{integer}};</li>
390-
<li>A floating-point value;</li>
387+
<li>A {{number}};</li>
391388
<li>An {{entity}}.</li>
392389
</ul>
393390
</p>

0 commit comments

Comments
 (0)