Skip to content

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

@dubnemo

Description

@dubnemo

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?

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