presentation-exchange icon indicating copy to clipboard operation
presentation-exchange copied to clipboard

JSONPath/Pointer changes for 2.1

Open kimdhamilton opened this issue 2 years ago • 5 comments

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

kimdhamilton avatar Nov 02 '23 17:11 kimdhamilton

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

pmhsfelix avatar Nov 15 '23 12:11 pmhsfelix

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

colbyharrison avatar Dec 13 '23 20:12 colbyharrison

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

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

OR13 avatar Feb 29 '24 18:02 OR13

So shiny, thanks!

kimdhamilton avatar Feb 29 '24 19:02 kimdhamilton

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

Sakurann avatar Mar 01 '24 09:03 Sakurann