«

Max wrote:
> Lasse Reichstein Nielsen ha scritto:
>> Not really. It shows that a particularly naïve implementation of a
>> conversion from XML to JSON doesn't work well.
>
> Really, then most of implementations of conversion from XML to JSON are
> naïve!

It would seem you are not exactly in a position to make a correct assessment.

>> What if the conversion of <e> some <a>textual</a> content </e>
>>
>> was:
>>
>> {"tag": "e", "content" : [ "some", {"tag": "a", "content": ["textual"]}
>> "content" ]}
>>
>> What is the big difference then?
>
> For JSON, "textual" is a value of "a"

Nonsense.

> and then { a: "textual" }.

And if there was

{ a: "textual", b: "foo" }

you could not know which one came first.

> This convertion is your expansive implementation created to bypass the
> JSON limitations...

There are no limitations in JSON but those you make up here.

> In fact, to obtain the string "some" instead of (example) e["#text"], you
> must use a blinded mode tag.content[1],

Not necessarily. As the DOM provides getElementsByTagName(), a similar
method can be implemented to traverse the object created from parsing JSON.

> while it is more correct to log on with the real name of the object/tag,
> that is "e"!

You are mistaken. Text child nodes of the same level do not belong together
unless they are adjacent. Your approach would allow for one text child node
per element only.


PointedEars
--
Prototype.js was written by people who don't know javascript for people
who don't know javascript. People who don't know javascript are not
the best source of advice on designing systems that use javascript.
-- Richard Cornford, cljs, <f806at$ail$1$>

Max wrote:
> According to Stefan Goessner, to obtain a correct conversion from XML to
> JSON it must apply some patterns to maintain order and structure of the
> elements. This not only serves to ensure a reversible conversion, but
> especially for documents such as SVG and SMIL that they require a
> precisely correct order of the elements.

That may be true if the text you are dealing with is primarily document. If it
is primarily data, then preservation of document structure will add a lot of
inefficiency to the JSON data structure. A problem in much XML practice is that
it is sometime difficult to understand the difference.

There are a number of transformations possible between JSON and XML. See for
example org.json.XML and org.json.JSONML at www.json.org/java

Thomas 'PointedEars' Lahn ha scritto:
> Max wrote:
>> Lasse Reichstein Nielsen ha scritto:
>>> Not really. It shows that a particularly naïve implementation of a
>>> conversion from XML to JSON doesn't work well.
>> Really, then most of implementations of conversion from XML to JSON are
>> naïve!
>
> It would seem you are not exactly in a position to make a correct assessment.

Why? I'm talking about proper implementation of a XML2JSON converter.
I say that then most of converters are naïve because I find many
converters that make a simple conversion from JSON.
At the same json.org website there are examples of simple conversion
(http://www.json.org/example.html)!
I have raised doubts and asked a question:
"Can you suggests to me a good XML-JSON converter?"
I have not received any answer, but only chats.

Max

Douglas Crockford ha scritto:
> That may be true if the text you are dealing with is primarily document.
> If it is primarily data, then preservation of document structure will
> add a lot of inefficiency to the JSON data structure. A problem in much
> XML practice is that it is sometime difficult to understand the difference.
>
> There are a number of transformations possible between JSON and XML. See
> for example org.json.XML and org.json.JSONML at www.json.org/java

Thank you Douglas. I hope to find a solution to implement a Javascript
converter from XML to JSON.
(Pay attention to page examples on json.org because there are errors)

Max

Max wrote:
> Thomas 'PointedEars' Lahn ha scritto:
>> Max wrote:
>>> Lasse Reichstein Nielsen ha scritto:
>>>> Not really. It shows that a particularly naïve implementation of a
>>>> conversion from XML to JSON doesn't work well.
>>> Really, then most of implementations of conversion from XML to JSON
>>> are naïve!
>> It would seem you are not exactly in a position to make a correct
>> assessment.
>
> Why? I'm talking about proper implementation of a XML2JSON converter. I
> say that then most of converters are naïve because I find many converters
> that make a simple conversion from JSON. At the same json.org website
> there are examples of simple conversion
> (http://www.json.org/example.html)! I have raised doubts and asked a
> question: "Can you suggests to me a good XML-JSON converter?" I have not
> received any answer, but only chats.

You have received several answers addressing your question while we have
been engaging in a technical discussion about what would make up a good
converter. Whether you like that or not is a different matter, and how to
use search engines is beyond the scope of this newsgroup.

<http://jibbering.com/faq/>


PointedEars
--
var bugRiddenCrashPronePieceOfJunk = (
navigator.userAgent.indexOf('MSIE 5') != -1
&& navigator.userAgent.indexOf('Mac') != -1
) // Plone, register_function.js:16

Thomas 'PointedEars' Lahn ha scritto:

> You have received several answers addressing your question while we have
> been engaging in a technical discussion about what would make up a good
> converter. Whether you like that or not is a different matter, and how to
> use search engines is beyond the scope of this newsgroup.

Ok, i have received technical answers but also accusation of lack about
XML2JSON converters... The only practical help was posted by Douglas. I
was wondering just that. Everything else is chats.

Max

Max wrote:
> Thomas 'PointedEars' Lahn ha scritto:
>> You have received several answers addressing your question while we have
>> been engaging in a technical discussion about what would make up a good
>> converter. Whether you like that or not is a different matter, and how to
>> use search engines is beyond the scope of this newsgroup.
>
> Ok, i have received technical answers but also accusation of lack about
> XML2JSON converters... The only practical help was posted by Douglas. I
> was wondering just that. Everything else is chats.

Ask for a refund.


Score adjusted

PointedEars
--
Anyone who slaps a 'this page is best viewed with Browser X' label on
a Web page appears to be yearning for the bad old days, before the Web,
when you had very little chance of reading a document written on another
computer, another word processor, or another network. -- Tim Berners-Lee

Max wrote:
> (Pay attention to page examples on json.org because there are errors)

That remark is not helpful. If there are errors, it would be helpful if you
specifically identified them. You can thank the community for the free
information you have obtained by providing correct information of your own.

On Aug 9, 8:19*am, Max <a...@tiscali.it> wrote:
> According to Stefan Goessner, to obtain a correct conversion from XML to
> JSON it must apply some patterns to maintain order and structure of the
> elements. This not only serves to ensure a reversible conversion, but
> especially for documents such as SVG and SMIL that they require a
> precisely correct order of the elements.
> For example, in the case of:
>
[snip]
>
> Max

jQuery has a RSS to JSON converter. No doubt order is maintained
here.
You might like to take a look:
http://ejohn.org/projects/rss2json/

On Aug 11, 10:57*am, lorlarz <lorl...@gmail.com> wrote:
> On Aug 9, 8:19*am, Max <a...@tiscali.it> wrote:

> [snip]
>
> > Max
>
> jQuery has a RSS to JSON converter. *No doubt order is maintained
> here.
> You might like to take a look:http://ejohn.org/projects/rss2json/

Sorry. That link is to a page for a Perl script to do the conversion
(by John Resig, jQuery creator).

There IS a jQuery "plugin" to do the conversion though (also):
http://plugins.jquery.com/project/xml2json