|
82 | 82 | <section title="Syntax">
|
83 | 83 | <t>
|
84 | 84 | A Relative JSON Pointer is a Unicode string (see RFC 4627,
|
85 |
| - <xref target="RFC4627">Section 3</xref>), comprising a positive integer, |
| 85 | + <xref target="RFC4627">Section 3</xref>), comprising a non-negative integer, |
86 | 86 | followed by either a '#' (%x23) character or a JSON Pointer
|
87 | 87 | (<xref target="RFC6901">RFC 6901</xref>).
|
88 | 88 | </t>
|
|
98 | 98 | </preamble>
|
99 | 99 | <artwork>
|
100 | 100 | <![CDATA[
|
101 |
| - relative-json-pointer = positive-integer <json-pointer> |
102 |
| - relative-json-pointer =/ positive-integer "#" |
103 |
| - positive-integer = %x30 / %x31-39 *( %x30-39 ) |
104 |
| - ; "0", or digits without a leading "0" |
| 101 | + relative-json-pointer = non-negative-integer <json-pointer> |
| 102 | + relative-json-pointer =/ non-negative-integer "#" |
| 103 | + non-negative-integer = %x30 / %x31-39 *( %x30-39 ) |
| 104 | + ; "0", or digits without a leading "0" |
105 | 105 | ]]>
|
106 | 106 | </artwork>
|
107 | 107 | <postamble>
|
|
121 | 121 | integer value representing an array index.
|
122 | 122 | </t>
|
123 | 123 | <t>
|
124 |
| - Evaluation begins by processing the positive-integer prefix. This |
125 |
| - can be found by taking the longest continuous sequence of decimal |
| 124 | + Evaluation begins by processing the non-negative-integer prefix. |
| 125 | + This can be found by taking the longest continuous sequence of decimal |
126 | 126 | digits available, starting from the beginning of the string, taking
|
127 | 127 | the decimal numerical value. If this value is more than zero, then
|
128 | 128 | the following steps are repeated that number of times:
|
|
0 commit comments