Fix JSONPath in test-cases to follow RFC 9535

[jduchateau]

Fix JSONPath in test-cases to follow RFC 9535:
RMLTC10a
RMLTC10b
RMLTC10c
RMLTC23f
RMLTC10a
RMLTC28a
RMLTC28b
RMLTC28c

fix #122

[dachafra]

@jduchateau could you add the sections of the spec in json path to support these changes?

[jduchateau]

Hello,
To be fair, I detected this only because I used a library that claim being RFC9535 compliant.

When checking the standard,

• $.['somethinh'] is invalid as we have 2 child-segments, one with an invalid member-name-shorthand as name-first is missing, the second with bracketed-selection section 2.5.1.1.
• test 23f, is simply missing the root-identifier $, and {Name} does not comply with member-name-shorthand (section 2.5.1.1).
• and 28a, 28b are just missing root-identifier $ (section 2.2.1)

[pmaria]

Hello, To be fair, I detected this only because I used a library that claim being RFC9535 compliant.

When checking the standard,

• $.['somethinh'] is invalid as we have 2 child-segments, one with an invalid member-name-shorthand as name-first is missing, the second with bracketed-selection section 2.5.1.1.
• test 23f, is simply missing the root-identifier $, and {Name} does not comply with member-name-shorthand (section 2.5.1.1).
• and 28a, 28b are just missing root-identifier $ (section 2.2.1)

Yes, thanks for this PR. There are many variations of what libraries support. We should follow the RFC in our test cases

[dachafra]

Perfect, @jduchateau could you also regenerate the documentation? (Open dev.html with an http server —> export as index.html and save in docs folder, index.html and a folder with the date of the day). Thanks!

[jduchateau]

@dachafra the test-cases documentation was regenerated. There is something strange about the date, as the document shows the 10 November 2025 (the date of the commit?), even if we are the 18th.