JSONPath/Pointer changes for 2.1

decentralized-identity / presentation-exchange

Specification that codifies an inter-related pair of data formats for defining proof presentations (Presentation Definition) and subsequent proof submissions (Presentation Submission)

https://identity.foundation/presentation-exchange

Apache License 2.0

84 stars 36 forks source link

JSONPath/Pointer changes for 2.1 #456

Open kimdhamilton opened 1 year ago

kimdhamilton commented 1 year ago

Concerns

JSONPath: security issues
2.1 breaking change

Structure of PE spec

base: simple stuff
features: advanced, under-defined

Structurally better to have jsonpointer at the base layer, but breaking change

Decision:

Add a new pointer property at same level of path. Strong preference for this in implementation notes
Soft launch with preference for jsonpointer that falls back to jsonpath
In 3.0, path becomes a feature

pmhsfelix commented 1 year ago

What does it mean In 3.0, path becomes a feature?

colbyharrison commented 11 months ago

I believe this means that in the 3.0 release Json Path will become an extension on the spec and not required to be conformant with the spec. See: https://identity.foundation/presentation-exchange/#structure-of-this-document

OR13 commented 8 months ago

You should update your references to this nice shiny new RFC:

https://datatracker.ietf.org/doc/html/rfc9535

kimdhamilton commented 8 months ago

So shiny, thanks!

Sakurann commented 8 months ago

as discussed in https://github.com/openid/OpenID4VCI/issues/266, even JSON Pointer might not meet all the requirements like indexing array entries. alternative mechanism could be something like proposed here: https://github.com/openid/OpenID4VCI/pull/276