Skip to content

Main content

JSON Pointer Final Token Is Empty Tool

Distinguish root from a terminal empty token using the existing RFC 6901 pointer validator.

Loading tool…

Description

Invoke the linked pointer parser and return root from the empty input, finalTokenEmpty from its terminal-empty flag, and tokenCount.

JSON Pointer separates path tokens with slashes and escapes literal slash and tilde inside member names. The empty pointer denotes the document root; an empty token can name an actual empty-string member.

Invoke the linked pointer parser and return root from the empty input, finalTokenEmpty from its terminal-empty flag, and tokenCount.

When to use this tool

Use JSON Pointer Final Token Is Empty when you need a pointer token, depth, or representation check.

How to use the tool and how it works

  1. Enter pointer. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read root, finalTokenEmpty, tokenCount. Inspect root, finalTokenEmpty before interpreting the associated values.

Invoke the linked pointer parser and return root from the empty input, finalTokenEmpty from its terminal-empty flag, and tokenCount.1

The linked terminal-empty-segment parser validates pointer syntax and supplies the token count and trailing-empty-token flag.2

Input fieldMeaning and unitsAccepted input
pointerPointer text in the exact syntax accepted by this tool.Required. Text; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
rootWhether the pointer identifies the whole document root.Required. Boolean.
finalTokenEmptyFinal Token EmptyRequired. Boolean.
tokenCountNumber of parsed pointer reference tokens; root has none.Required. Safe integer.
json
{
  "input": {
    "pointer": "/a/"
  },
  "output": {
    "root": false,
    "finalTokenEmpty": true,
    "tokenCount": 2
  }
}

Limitations and assumptions

  • This reports parsed pointer structure without resolving a value or checking document membership.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.

Alternative or Complementary methods

Use a complete pointer parser and resolve against the actual document when existence or array access matters.

References

  1. Calculation and input contract: json/json-pointer-final-token-is-empty — tool.io

  2. Calculation or validation: json/json-pointer-terminal-empty-segment — tool.io

Similar or alternative tools