Talk:JSONPath

I am one of the editors of IETF RFC 9535 which proposes a standard for JSONPath. Glyn normington (talk) 03:57, 22 March 2024 (UTC)Reply

Talk:JSONPath

Conflict of interest

I am one of the editors of IETF RFC 9535 which proposes a standard for JSONPath. Glyn normington (talk) 03:57, 22 March 2024 (UTC)Reply

Pronunciation

The JSON article goes into some detail of pronunciation. Since JSONPath extends the pronunciation of JSON, is it worth saying something in this article about pronunciation? Glyn normington (talk) 17:57, 23 March 2024 (UTC)Reply

Implementations

Would it be valuable to add a list of implementations, possibly grouped by programming language? Glyn normington (talk) 17:58, 23 March 2024 (UTC)Reply

SQL JSONPath

SQL apparently has support for JSONPath. SQL does not appear to be an open standard. Is there some way of verifying the JSONPath content and, if so, is it worth adding an item to the Standards section of the JSONPath article? Glyn normington (talk) 19:08, 23 March 2024 (UTC)Reply

Content Disclaimer

Informasi ini disarikan dari Wikipedia dan disajikan kembali untuk tujuan edukasi. Konten tersedia di bawah lisensi CC BY-SA 3.0. Kami tidak bertanggung jawab atas ketidakakuratan data yang bersumber dari kontribusi publik tersebut.

  1. The information displayed on this website is sourced in part or in whole from Wikipedia and has been adapted for the purpose of restating it. We strive to provide accurate and relevant information, however:
  2. There is no guarantee of absolute accuracy. Wikipedia is an open, collaborative project that can be edited by anyone, so information is subject to change.
  3. It is not intended to constitute professional advice. The content displayed is for informational and educational purposes only. For important decisions (e.g., medical, legal, or financial), please consult a professional.
  4. Content copyright. Wikipedia is licensed under the Creative Commons Attribution-ShareAlike License (CC BY-SA). This means that content may be reused with appropriate attribution and shared under a similar license.
  5. Responsible use. Any risk arising from the use of information from this website is entirely the responsibility of the user.