Draft: draft-ietf-jsonpath-base

Commentary: This can be done in many different ways . This PR values noise reduction over consistency . Comments welcome . 
 That is indeed a problem in several sections , there are enough subtopics common to both that you would need to go back and forth . Note how I dissolved the " logical operators " subsection from the semantics by adding the one sentence to the syntax subsection . I also believe we have to live with this . 
 Specifically , { { comparisons } } in { { filter - selector } } { { syntax - index } } { { index - semantics } } { { extest } } 
 Do you propose to delete these headings and the references , add numbers to these headings , or what ? 
 Use unnumbered sections only where this is simple internal structure . As soon as sections are referenced , this is no longer the case . 
 May I leave this change to you ? Assigning it to you for clarity . 
 This all seems reasonable to me . Note : now that the Filter Selector / Syntax section is visible in the TOC , it 's a little disturbing that it contains quite a lot of semantics . I tried separating these out once , but it became unreadable because the semantics section repeated a lot of syntax so the two could be associated properly . I think we have to live with this .
Paragraph (version A):
The following examples show the name selector in use by child
segments.
Paragraph (version A):
The following examples show the "wildcard" selector in use by a child
segment.
Paragraph (version A):
The following examples show the index selector in use by a child
segment.
Paragraph (version B):
The examples in tbl-index show the index selector in use by a child
segment.
Paragraph (version A):
The following examples show the array slice selector in use by a
child segment.
Paragraph (version A):
Logical expressions offer the usual Boolean operators ("||" for OR,
"&&" for AND, and "!" for NOT).  Parentheses MAY be used within
"logical-expr" for grouping.
Paragraph (version B):
Logical expressions offer the usual Boolean operators ("||" for OR,
"&&" for AND, and "!" for NOT).  They have the normal semantics of
Boolean algebra and obey its laws (see, for example, BOOLEAN-LAWS).
Parentheses MAY be used within "logical-expr" for grouping.
Paragraph (version A):
The following table lists filter expression operators in order of
precedence from highest (binds most tightly) to lowest (binds least
tightly).
Paragraph (version B):
tbl-prec lists filter expression operators in order of precedence
from highest (binds most tightly) to lowest (binds least tightly).
Paragraph (version A):
The order in which the children of an object appear in the resultant
nodelist is not stipulated, since JSON objects are unordered.  In the
resultant nodelist, children of an array are ordered by their
position in the array.
Paragraph (version B):
In the resultant nodelist, children of an array are ordered by their
position in the array.  The order in which the children of an object
(as opposed to an array) appear in the resultant nodelist is not
stipulated, since JSON objects are unordered.
Paragraph (version A):
The logical AND, OR, and NOT operators have the normal semantics of
Boolean algebra and obey its laws (see, for example, BOOLEAN-LAWS).
Paragraph (version A):
Filter selectors may use function extensions, which are covered in
fnex.
Paragraph (version A):
The following examples show the filter selector in use by a child
segment.