[Home] [By Thread] [By Date] [Recent Entries]

  • From: John Cowan <cowan@m...>
  • To: Kurt Cagle <kurt.cagle@g...>
  • Date: Mon, 21 Feb 2011 14:34:26 -0500

Kurt Cagle scripsit:

> What this points to is that either the corresponding JSON libs would
> need to be adapted to properly parse XML blocks (which would be lovely,
> but which I'd say is about as likely as Hixie suddenly becoming an
> ardent XML-phile),

Oh, I see; you want a conventional way of *embedding* XML in pure JSON,
as opposed to an *extension* of JSON.  I didn't realize that.  In that
case, I'd rather use the style in which

        <a href="http://example.com">This is <i>mixed</i> text</a>

becomes

        {"#name" : "a",
         "#attrs" : {"href" : "http://example.com"},
         "#children" : [
            "This is ",
            {"#name" : "i",
             "#attrs" : {},
             "#children" : ["mixed"]},
            " text"]}

Verbose, but it requires only one parser, not two.

-- 
John Cowan  cowan@c...  http://ccil.org/~cowan
If I have seen farther than others, it is because I was standing on
the shoulders of giants.
        --Isaac Newton


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]


Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member