On Thu, Oct 2, 2014 at 12:07 PM, Ihe Onwuka <
ihe.onwuka@gmail.com> wrote:
> Which brings me on to the last point. JSONiq is not an option if XSLT is
> part of the solution
So, what about using XSLT 3.0 native capabilities for processing JSON:
http://www.w3.org/TR/2014/WD-xslt-30-20141002/#jsonBTW, Congratulations for the XSLT WG for rolling out a 2nd Last Call
draft
today!
--
Cheers,
Dimitre Novatchev
---------------------------------------
Truly great madness cannot be achieved without significant intelligence.
---------------------------------------
To invent, you need a good imagination and a pile of junk
-------------------------------------
Never fight an inanimate object
-------------------------------------
To avoid situations in which you might make mistakes may be the
biggest mistake of all
------------------------------------
Quality means doing it right when no one is looking.
-------------------------------------
You've achieved success in your field when you don't know whether what
you're doing is
work or play
-------------------------------------
To achieve the impossible dream, try going to sleep.
-------------------------------------
Facts do not cease to exist because they are ignored.
-------------------------------------
Typing monkeys will write all Shakespeare's works in 200yrs.Will they
write all patents, too? :)
-------------------------------------
I finally figured out the only reason to be alive is to enjoy it.
_______________________________________________________________________
XML-DEV is a publicly archived, unmoderated list hosted by OASIS
to support XML implementation and development. To minimize
spam in the archives, you must subscribe before posting.
[Un]Subscribe/change address:
http://www.oasis-open.org/mlmanage/Or unsubscribe:
xml-dev-unsubscribe@lists.xml.orgsubscribe:
xml-dev-subscribe@lists.xml.orgList archive:
http://lists.xml.org/archives/xml-dev/List Guidelines:
http://www.oasis-open.org/maillists/guidelines.php