Document reasons for not using existing JSON query languages

[aaronpk]

Repeating my live comment from the IETF 121 meeting... It would be worth documenting the reasons for creating a new JSON query syntax instead of using JSONPath or alternatives.

[babisRoutis]

Haven't followed the reasoning to introduce Claim Path yet to my understanding:

• JSON Poinrter
  • Too narrow to express requirements as verifier (What to present), given that it misses a wild-card for arrays.
  • Could be used by wallet to calculate disclosures to include in a presentation
• JSON Path
  • Too broad for both the verifier and the wallet
  • Ultimately leads to interoperability issues.

Claim Path
That's the sweet spot. I think it as a DSL pointer.

• Easy to implement
• Allows verifier to use wildcards for arrays
• Allows wallet to calculate disclosures (Practically omitting wildcard is one-to-one mapping with JSONPointer, except the root)