Skip to content

Commit 15d2a32

Browse files
committed
Clarify definition of response position
1 parent 9bec2cb commit 15d2a32

File tree

1 file changed

+6
-4
lines changed

1 file changed

+6
-4
lines changed

spec/Section 7 -- Response.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -76,10 +76,12 @@ The value of this entry is described in the "Extensions" section.
7676
<!-- Legacy link, this section was previously titled "Path" -->
7777
</a>
7878

79-
:: A _response position_ is a uniquely identifiable position in the response
80-
data produced during execution. It is either a direct entry in the {resultMap}
81-
of a {ExecuteSelectionSet()}, or it is a position in a (potentially nested) List
82-
value. Each response position is uniquely identifiable via a _response path_.
79+
:: A _response position_ is a uniquely identifiable location in the response
80+
structure evaluated during execution. It may correspond to a {responseName}
81+
evaluated by {ExecuteCollectedFields()}, or to an element within a (potentially
82+
nested) List value evaluated by {CompleteValue()}. A _response position_ does
83+
not appear in the _execution result_ when elided by error propagation. Each
84+
response position is uniquely identifiable by a _response path_.
8385

8486
:: A _response path_ uniquely identifies a _response position_ via a list of
8587
path segments (response names or list indices) starting at the root of the

0 commit comments

Comments
 (0)