[prev in list] [next in list] [prev in thread] [next in thread] 

List:       xml-dev
Subject:    Re: [xml-dev] JSON - The Fat Free Alternative - Redux
From:       Ihe Onwuka <ihe.onwuka () gmail ! com>
Date:       2014-10-07 7:48:57
Message-ID: CALfs7+xd=t5KMsTgeDahZDNOcqF7GN8JGkqcf5_toP20QUCmKg () mail ! gmail ! com
[Download RAW message or body]

On Thu, Oct 2, 2014 at 9:45 PM, Dimitre Novatchev <dnovatchev@gmail.com>
wrote:

> 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/#json
>
>
Sorry for the tardy reply Dmitre. Good question.

The answer is probably  I could but I don't think I want to.

The problem I am solving (and the source of the json ) is described here

http://en.wikibooks.org/wiki/XQuery/Freebase

but I had to reimplent the JSON to XML conversion in JSONiq because of the
performance of the xqjson utility. I haven't yet looked at XSLT 3.0 but I
have seen references to xsl:iterate floating around and I imagine that
would be the mechanism for iterating over all the cursors.

Since in this case  a lossless conversion of the JSON can be done the
question I would ask  is what value is  added by writing a program that
entails data formats from more than one technology domain. The answer is
none, so why then risk the disadvantages of an application that is
dependent on bleeding edge technology.

The fact that a cure {JSONiq, XSLT3) exists for a disease (JSON) isn't good
reason to inflict the disease upon yourself. Yes I called it a disease
because it pops up in places where it has no business being. If you are
integrating corporate data feeds or XHTML (natural format for data scraped
from the web) you need someone giving you JSON like you need a hole in the
head. The harder you look the more it looks like the result of a
misdiagnosis

[Attachment #3 (text/html)]

<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Oct 2, \
2014 at 9:45 PM, Dimitre Novatchev <span dir="ltr">&lt;<a \
href="mailto:dnovatchev@gmail.com" \
target="_blank">dnovatchev@gmail.com</a>&gt;</span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"><span>On Thu, Oct 2, 2014 at 12:07 PM, Ihe Onwuka \
&lt;<a href="mailto:ihe.onwuka@gmail.com" \
target="_blank">ihe.onwuka@gmail.com</a>&gt; wrote:<br> &gt; Which brings me on to \
the last point. JSONiq is not an option if XSLT is<br> &gt; part of the solution<br>
<br>
<br>
</span>So, what about using XSLT 3.0 native capabilities for processing JSON:<br>
<br>
        <a href="http://www.w3.org/TR/2014/WD-xslt-30-20141002/#json" \
target="_blank">http://www.w3.org/TR/2014/WD-xslt-30-20141002/#json</a><br> \
<br></blockquote></div><br></div><div class="gmail_extra">Sorry for the tardy reply \
Dmitre. Good question. <br><br></div><div class="gmail_extra">The answer is probably  \
I could but I don&#39;t think I want to.<br><br></div><div class="gmail_extra">The \
problem I am solving (and the source of the json ) is described here <br><br><a \
href="http://en.wikibooks.org/wiki/XQuery/Freebase" \
target="_blank">http://en.wikibooks.org/wiki/XQuery/Freebase</a><br><br></div><div \
class="gmail_extra">but I had to reimplent the JSON to XML conversion in JSONiq \
because of the performance of the xqjson utility. I haven&#39;t yet looked at XSLT \
3.0 but I have seen references to xsl:iterate floating around and I imagine that \
would be the mechanism for iterating over all the cursors.</div><div \
class="gmail_extra"><br></div><div class="gmail_extra">Since in this case   a \
lossless conversion of the JSON can be done the question I would ask   is what value \
is   added by writing a program that entails data formats from more than one \
technology domain. The answer is none, so why then risk the disadvantages of an \
application that is dependent on bleeding edge technology.</div><div \
class="gmail_extra"><br></div><div class="gmail_extra">The fact that a cure {JSONiq, \
XSLT3) exists for a disease (JSON) isn&#39;t good reason to inflict the disease upon \
yourself. Yes I called it a disease because it pops up in places where it has no \
business being. If you are integrating corporate data feeds or XHTML (natural format \
for data scraped from the web) you need someone giving you JSON like you need a hole \
in the head. The harder you look the more it looks like the result of a \
misdiagnosis</div><div class="gmail_extra"><br></div></div>



[prev in list] [next in list] [prev in thread] [next in thread]