Comments on: XSLT and XPath for JSON

By: XSLT equivalent for JSON – Knowleage Exchange

XSLT equivalent for JSON – Knowleage Exchange — Mon, 23 Apr 2018 16:59:58 +0000

[…] a company which may have implemented something suitable […]

By: Python:How can I use python finding particular json value by key? – IT Sprite

Fri, 30 Oct 2015 09:48:27 +0000

[…] Maybe this is what you need? p6r.com/articles/2008/05/06/xslt-and-xpath-for-json […]

By: Mark Joseph

Mark Joseph — Mon, 03 Oct 2011 21:52:29 +0000

>>I hate to break it to you, but you are wrong about the structure of JSON in general. >>You assume that parse-able JSON is necessarily a document. This is false. JSON represents different types >>of data. >>You further assume that all JSON “documents,” for instance, have a root-level curly-brace-pair. This is >>not necessarily the case. You could, for instance, be representing a naked array with JSON. >>It would use a square-bracket-pair instead. >> Actually we use a document paradigm to simplify things but our parsing and XPATH handles all the cases you mention above. We do not assume that a JSON string starts with a curly brace pair. Our tools also support JsonML completely which is all array based with no problem. (We are referenced on the www.jsonml.com web site.) As a blog document there is limited space to show all the JSON forms we support. >> >>I also find it horrible that all JSON XPath expressions would in general have to lead >>with “/JSON-document/” as that is a ridiculously long string – why not just use “/” as your root string >>and assume the rest? >> I don't much like this either it is a bit too long. XPath requires a root node which JSON does not have to have. This convention makes it easy to tell the XPath processor to handle that case. >> >>And why not support arrays through adding integer offsets as keys? >>For instance: >>[ "a", "b", { "key": 9 }] >>Xpath( “/0″ ) –> “a” >Xpath( “/2/key” ) –> 9 >> I don't believe what you propose is standard XPath. If it is please point me to where in the XPath standard document that you can specify an array index as a path element. >> >> One thing you are missing. Our tools support XSLT and XPATH 2.0 which are significantly more powerful than the 1.0 versions. There still are not many 2.0 implementations out there. Our software allows JSON processing with the power of XPATH 2.0 expressions which include regular expressions. With the full JsonML support it is a powerful tool.

By: Tyler

Tyler — Mon, 03 Oct 2011 21:29:15 +0000

Project 6 Research,

I hate to break it to you, but you are wrong about the structure of JSON in general.

You assume that parse-able JSON is necessarily a document. This is false. JSON represents different types of data.

You further assume that all JSON “documents,” for instance, have a root-level curly-brace-pair. This is not necessarily the case. You could, for instance, be representing a naked array with JSON. It would use a square-bracket-pair instead.

I also find it horrible that all JSON XPath expressions would in general have to lead with “/JSON-document/” as that is a ridiculously long string – why not just use “/” as your root string and assume the rest?

And why not support arrays through adding integer offsets as keys?

For instance:
[ "a", "b", { "key": 9 }]

Xpath( “/0″ ) –> “a”
Xpath( “/2/key” ) –> 9
etc.

I really don’t see anything mind-blowing there, nor anything really that incompatible with the rest of your ideas.

By: Phil Gibbs

Phil Gibbs — Sat, 24 May 2008 15:30:40 +0000

Very useful – will evaluate.

By: A SAX-like Parser for JSON | Project 6 Research - Articles

A SAX-like Parser for JSON | Project 6 Research - Articles — Fri, 23 May 2008 00:09:59 +0000

[...] 2.0 and XSLT 2.0 products. How the second goal was achieved is described in another P6R article: XSLT and XPath for JSON. We should note that our SAX-like JSON parser is fully implemented and is part of our P6Platform [...]

By: An XPath Enabled Rule Engine | Project 6 Research - Articles

An XPath Enabled Rule Engine | Project 6 Research - Articles — Thu, 22 May 2008 17:05:35 +0000

[...] Our XPath 2.0 supports stated facts defined in either XML or JSON , thus our Rule Engine is also JSON [...]