JSON Schema Generator & RFC 9535 JSONPath Query Specification Guide
Generate valid JSON Schema Draft 2020-12 models and evaluate IETF RFC 9535 JSONPath expressions in client-side memory.
01. 1. RFC 9535 vs Legacy Goessner JSONPath: The IETF Standard
For nearly two decades following Stefan Goessner's original 2007 blog post, developers relied on fragmented, incompatible implementations of JSONPath. Different programming libraries handled wildcards, slices, and script filters with conflicting behaviors.
In 2024, the Internet Engineering Task Force (IETF) formally published RFC 9535 ('JSONPath: Query Expressions for JSON'). This standard establishes a formal grammar, eliminates arbitrary code execution risks by restricting filter expressions, and standardizes operators such as root '$', current node '@', recursive descent '..', and filter selectors '[?@.price < 10]'.
DevOmniTools implements native RFC 9535 parsing entirely within your browser memory. Queries execute deterministically without relying on insecure eval() calls or cloud APIs.
- Deterministic Grammar: Restricts arbitrary script evaluation while providing expressive comparison operators (==, !=, <, <=, >, >=).
- Safe Recursive Descent: Traverses deep nested trees with $..prop syntax in O(N) complexity.
- Normalized Path Output: Produces canonical bracketed path strings for downstream automated processing.
02. 2. JSON Schema Draft 2020-12 Architecture & Keyword Inference
JSON Schema provides a declarative contract for validating the format, types, and constraints of JSON data. Our client-side schema generator analyzes sample payloads to infer structural properties:
Primitive types (string, number, integer, boolean, null) are categorized with high fidelity. Strings undergo regex heuristics to identify standard formats including 'date-time' (ISO 8601), 'email', 'uuid', 'ipv4', and 'uri'.
For arrays and collections, the engine inspects member items to determine whether elements are homogeneous (producing a clean 'items' object schema) or heterogeneous (producing a combined 'anyOf' schema model).
03. 3. Zero-Leak In-Browser Processing for Enterprise Security
JSON payloads from production microservices often contain sensitive customer records, authentication tokens, and proprietary internal schema fields. Uploading such files to third-party SaaS formatting sites risks GDPR violations and credential leaks.
DevOmniTools executes 100% locally within your browser tab memory using pure TypeScript. Disconnecting your network connection verifies that every transformation, schema generation, and query execution continues to function seamlessly offline.
Frequently Asked Questions (FAQ)
What is the primary difference between RFC 9535 and classic JSONPath?
RFC 9535 is the official IETF standard published in 2024. Unlike Stefan Goessner's 2007 proposal which allowed arbitrary JavaScript expressions inside filters, RFC 9535 specifies a strict, safe comparison syntax that eliminates code injection vulnerabilities.
Which JSON Schema draft should I use for modern APIs?
Draft 2020-12 is the modern industry standard, providing full alignment with modern OpenAPI 3.1 specifications. If your backend relies on legacy validators (like certain Draft 7 Python or Go libraries), choose 'Draft 7' from the dropdown.
How do I filter JSON items based on price or properties?
Use the RFC 9535 filter selector syntax: '$.store.book[[email protected] < 10]' matches books with a price below 10. You can also check for property existence with '$.store.book[[email protected]]'.
Are my JSON payloads uploaded or logged to a remote server?
No. All parsing, schema generation, and JSONPath evaluations occur strictly inside your device's browser memory. Zero network requests are dispatched.