Skip to content

Update Readme.md with the rationale to use JMES Path vs JSON Path #104

Open
Open
Update Readme.md with the rationale to use JMES Path vs JSON Path#104

Description

@dubnemo
dubnemo
opened on Jul 21, 2025

Help me understand the shortcomings of IETF's JSON PATH that motivated you to create JMES Path. Clearly you leveraged many of the existing capabilities of JSON PATH.
Are you planning to submit this to IETF as a future version of JSON PATH to gain further adoption?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions