Draft: draft-ietf-jsonpath-base

Commentary: ... instead of " JSON document " or " JSON value " . " JSON value " is retained in some contexts where it refers to specific values i JSON rather than a whole document . Fixes 
 JSON text is a sequence of characters , an unparsed piece of JSON for interchange , with newlines and backslashes and all that . JSONPath never looks at JSON texts . JSON value is the RFC 8259 term for what  looks at . 
 What should be done here is replacing all occurrences of " JSON document " with " JSON value " . 
 Fixed with a force push . Sorry for misinterpreting the issue . 
 Terminology that would be nice to have could be " the JSON value that represents an entire  text " . People are often using " JSON document " for that , but that is ambiguous between the serialization ( JSON text ) and the data ( JSON value ) . If the text would really benefit from such a term , maybe we should coin it . 
 This was opened and closed in just over 3 hours . I was asleep that entire time and had no chance to review . Please be sure that PRs stay open for at least a day so they can be reviewed by everyone . 
 Thanks for the reminder Sorry I forgot . 
 We agreed to use the RFC 8259 terms , which would be " JSON text " . 
 ( And some occurrences actually talk about the JSON value . )
Paragraph (version A):
A Normalized Path is a JSONPath with restricted syntax that
identifies a node by providing a query that results in exactly that
node.  For example, the JSONPath expression "$.book[?(@.price<10)]"
could select two values with Normalized Paths "$['book'][3]" and
"$['book'][5]".  For a given JSON document, there is a one to one
correspondence between the document's nodes and the Normalized Paths
that identify these nodes.
Paragraph (version B):
A Normalized Path is a JSONPath with restricted syntax that
identifies a node by providing a query that results in exactly that
node.  For example, the JSONPath expression "$.book[?(@.price<10)]"
could select two values with Normalized Paths "$['book'][3]" and
"$['book'][5]".  For a given JSON value, there is a one to one
correspondence between the value's nodes and the Normalized Paths
that identify these nodes.
Paragraph (version A):
Since bracket notation is more general than dot notation, it is used
to construct Normalized Paths.  Single quotes are used to delimit
string member names.  This reduces the number of characters that need
escaping when Normalized Paths appear as strings (which are delimited
with double quotes) in JSON documents.
Paragraph (version A):
The syntax of Normalized Paths is restricted so that there is one and
only one way of representing any given Normalized Path.  Putting this
another way, for any two distinct Normalized Paths, a JSON document
exists that will yield distinct results when the Normalized Paths are
applied to it.
Paragraph (version B):
Since bracket notation is more general than dot notation, it is used
to construct Normalized Paths.  Single quotes are used to delimit
string member names.  This reduces the number of characters that need
escaping when Normalized Paths appear as strings (which are delimited
with double quotes) in JSON texts.
Paragraph (version B):
The syntax of Normalized Paths is restricted so that there is one and
only one way of representing any given Normalized Path.  Putting this
another way, for any two distinct Normalized Paths, a JSON value
exists that will yield distinct results when the Normalized Paths are
applied to it.