-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Official documentation #523
Comments
Generally, the IETF is not in the business of providing or maintaining such resources. This may sound negative, but the upside is that these resources are not mired in IETF process, which is heavier for its main goal of standards settings than it needs to be for these resources. |
FWIW, I've added some tutorial materials to my learning site https://learn.json-everything.net/json-path. |
What is your idea behind misspelling my name, Greg?
https://blog.json-everything.net/posts/json-path-spec/
…--
Stefan
Am 03.07.2024 um 00:23 schrieb Greg Dennis:
FWIW, I've added some tutorial materials to my learning site
https://learn.json-everything.net/json-path.
—
Reply to this email directly, view it on GitHub
<#523 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABFM6WWOZLMZLUQWLI7MMA3ZKMR7VAVCNFSM6AAAAABI5RNZWSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBUGU3DAMBQGE>.
You are receiving this because you are subscribed to this
thread.Message ID:
***@***.***>
|
I'm an idiot american! 😆 I'll fix it. Sorry. |
Again, what is your idëa behind misspëlling my namë, Grëg? https://blog.json-everything.net/posts/json-path-spec/
-- Stefan
Am 17.07.2024 um 15:01 schrieb Stefan Gössner:
… It's hard for me to believe, that you can't see the difference between
* correct ... 'Gössner'
* alternate ... 'Goessner', since 'ö' equiv 'oe'
* misspelled ... 'Goëssner'
as you do in ...
https://blog.json-everything.net/posts/json-path-spec/
--
Stefan
Am 16.07.2024 um 08:46 schrieb Stefan Gössner:
> What is your idea behind misspelling my name, Greg?
>
> https://blog.json-everything.net/posts/json-path-spec/
>
> --
> Stefan
>
>
> Am 03.07.2024 um 00:23 schrieb Greg Dennis:
>>
>> FWIW, I've added some tutorial materials to my learning site
>> https://learn.json-everything.net/json-path.
>>
>> —
>> Reply to this email directly, view it on GitHub
>> <#523 (comment)>,
>> or unsubscribe
>> <https://github.com/notifications/unsubscribe-auth/ABFM6WWOZLMZLUQWLI7MMA3ZKMR7VAVCNFSM6AAAAABI5RNZWSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBUGU3DAMBQGE>.
>> You are receiving this because you are subscribed to this
>> thread.Message ID:
>> ***@***.***>
>>
>
|
Then why is your username @goessner? I'll do it with a PR this time. |
I think everybody took the spelling from https://goessner.net/index.html. Are PR's to all JSONPath github sites in order? |
In order to foster adoption of the new RFC (9535), we should have a documentation site that describes how JSON Path works in less "specification-y" terms.
@cabo/@timbray what is the typical IETF approach to this sort of thing?
The text was updated successfully, but these errors were encountered: