You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
mapping <a>strings</a> to values in the <ahref="#JSON-value-space">value space</a> where the key-value pairs are ordered by key (using <adata-cite="I18N-GLOSSARY#dfn-code-point" class="lint-ignore">Unicode code point</a> order),
1846
+
finite unordered maps
1847
+
mapping <a>strings</a> to values in the <ahref="#JSON-value-space">value space</a>,
1848
1848
<adata-cite="INFRA#list">lists</a>
1849
1849
of values in the <ahref="#JSON-value-space">value space</a>, and
1850
1850
literal values (<adata-cite="INFRA#boolean">`true`, `false`</a>, and <adata-cite="INFRA#nulls">`null`</a>)
1851
1851
from [[[INFRA]]] [[INFRA]] and [[[XMLSCHEMA11-2]]] [[XMLSCHEMA11-2]].
1852
1852
1853
-
<pclass="note">The value space of <adata-cite="INFRA#ordered-map">maps</a>
1853
+
<pclass="note">The value space of finite unordered maps
1854
1854
and <adata-cite="INFRA#list">lists</a> does not include values having themselves as members,
The constraint to order map entries in the value space is only meant to make the order of object-member the lexical space irrelevant. In other word, it ensures that both lexical values <code>{"a": "b", "c": "d"}</code> and <code>{"c": "d", "a": "b"}</code> are mapped to the same element of the value space. Implementations may omit to sort the entries, as long as they treat the maps in the value space as unordered.
1905
+
The finite unordered maps can be implemented with <adata-cite="INFRA#ordered-map">ordered maps</a> [[INFRA]]
1906
+
by systematically sorting key-value pairs by key (using <adata-cite="I18N-GLOSSARY#dfn-code-point" class="lint-ignore">Unicode code point</a> order).
1907
+
This ensures that lexical forms that differ only in the order of object members are mapped to the same element of the value space
1908
+
(e.g. <code>{"a": "b", "c": "d"}</code> and <code>{"c": "d", "a": "b"}</code>).
1908
1909
</p>
1909
-
<pclass="issue" data-number="116">The issue refers to the use
1910
-
of <adata-cite="INFRA#ordered-map">ordered map</a>
1911
-
from [[INFRA]] for describing the value space of <adata-cite="RFC8259#section-4">JSON Objects</a>
1912
-
and suggests defining a new datatype for unordered maps.</p>
0 commit comments