Closed glyn closed 1 year ago
Do we intend to replace this with anything? What is its purpose in being here?
The N-1 line also illustrates the point so I think it's probably OK to leave it?
Sorry, I didn't pay attention. The purpose of this example was to show that escaped characters are normalized into their actual equivalents (unless there is a reason not to do so).
The messiness is a workaround for xml2rfc bugs. I'm confident we can get these bugs fixed before this is published; otherwise we might indeed want to skip this example.
Why doesn't the $["\u0061"]
example already show that an escaped character is normalised into its actual equivalent ("a")?
It does. Many implementers will however think that this only applies to 95-ASCII characters (there is no reason for thinking that, but it is a highly likely misunderstanding).
Fixes https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-base/issues/274