Re: XSLT functions for JSON

On Sun, May 18, 2008 at 11:09 AM, M. David Peterson
<m.david@xxxxxxxxxxxxx> wrote:
> On Sun, 18 May 2008 11:35:05 -0600, Dimitre Novatchev <dnovatchev@xxxxxxxxx>
> wrote:
>
>> XML with some additional restrictions is no longer "XML" and JSON with
>> restrictions is no longer "JSON" -- it is as simple as that. You are
>> changing the initial problem and solving another -- and this is not
>> bad -- but do take care to rename the problem to the new one so not to
>> confuse anyone that you're trying to do the impossible.
>
> Absolutely agree, Dimitre!
>
> Couple of questions that might help guide the overall conversation in a
> productive direction, and therefore towards a renaming of the problem at
> hand,
>
>  * Is it worth the effort to find ways of transforming JSON into another
> serialization format and/or back into JSON (e.g. filtering) using XSLT?

This is the best question.  No, in my opinion.


>  * Is this possible with XSLT 1.0, or is this strictly an XSLT 2.0-type
> solution?

Many things are possible, but are they worth the effort?

>  * Is it even possible with XSLT 2.0?
>  * If it isn't possible, what pieces of RFC 4627 would need to be avoided to
> make it possible?

We should not try to correct something that is broken

>  * If these pieces were avoided in any given JSON file, would JSON still be
> of value?

No, because this would no longer be JSON

>   * In other words, just like I can avoid using DTD declarations in XML
> without losing any inherent value or real world applicability,

Are you sure?

> could the
> same be said about the pieces of JSON that would need to be avoided to
> ensure compatibility with XSLT 2.0?
>  * Does JSON have to be serialized into XML /before/ it can be transformed
> into something else via XSLT 2.0?

This has to be directed to whoever cares about JSON, we are members of
the xsl-list


>
> I'm sure there are other questions that might help make this conversation
> more productive.  Thoughts?


This conversation cannot be productive because it is about a broken
concept (JSON/XML equivalence).


>
> --
> /M:D
>
> M. David Peterson
> Co-Founder & Chief Architect, 3rd&Urban, LLC
> Email: m.david@xxxxxxxxxxxxxxx | m.david@xxxxxx
> Mobile: (206) 999-0588
> http://3rdandUrban.com | http://amp.fm |
> http://www.oreillynet.com/pub/au/2354
>
>



-- 
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
-------------------------------------
You've achieved success in your field when you don't know whether what
you're doing is work or play