[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Python and JSON vs XML???

• To: Bob Foster <bob@o...>
• Subject: Re: Python and JSON vs XML???
• From: Alan Gutierrez <alan-xml-dev@e...>
• Date: Thu, 25 Aug 2005 20:44:23 -0400
• Cc: Pete Cordell <petexmldev@t...>, XML Developers List <xml-dev@l...>
• In-reply-to: <430DF57C.9010307@o...>
• Mail-followup-to: Bob Foster <bob@o...>,Pete Cordell <petexmldev@t...>,XML Developers List <xml-dev@l...>
• References: <e3a5cb2c05082500045293f51e@m...> <001b01c5a97e$713131b0$a300a8c0@RW> <430DF57C.9010307@o...>
• User-agent: Mutt/1.4.1i

* Bob Foster <bob@o...> [2005-08-25 12:44]:
> Pete Cordell wrote:
> > FWIW - I've also developed a text based data representation language,
> > including on the wire format and, more significantly from what I have
> > seen of other proposals, a message specification language.
> >
> > I lowered the priority on it because the force behind XML and XML Schema
> > seemed to huge too compete against (Betamax / VHS type arguments etc.)
> > Whether the observations made below represent a genuine move away from
> > XML, or represent a small pocket of newly discovered dissenters I don't
> > know. Personally,  in the data representation space I find that
> > commercially I'm interested in XML Schema being successful, but
> > aesthetically it would be nice for something like my proposal to be
> > successful.
> >
> > I targetted this at the IETF, but at the time they seemed to be going
> > the W3C schema route.  Maybe I should knock on their door again!

> Who _hasn't_ designed a text based data representation language? ;-}

    Guilty.

> It would be interesting to collect these designs and examine them for 
> common characteristics. Some features of my last effort that I suspect 
> would appear in a number of others:

> - No attributes and no "normalization".
> - No DTDs or entities.
> - Use of brackets { [ ] } etc. instead of end tags.
> - Sequences (a la XQuery) at the document level.
> - Parse much faster than XML (of course).

    I created a language that were children were denoted by
    indentation, so it was Pythonesque. This was supposed to make
    life easier on my wrists, and make most language look like
    Python.

    xsl:stylesheet -version 2.0 
                   -xmlns:xsl "http://www.w3.org/1999/XSL/Transform"

        xsl:import -href foo.xslt

        xsl:template -match "/"

            xsl:if test "@foo = 'true'"
                xsl:message foo

            xsl:apply-templates -mode foo-mode

    No matching end tags. Children are simply indented. 

    They *only* reason I'd want this would be because it's easier to
    type. It would be more difficult to parse, and even worse to
    serialize, I'm sure.

--
Alan Gutierrez - alan@e...
    - http://engrm.com/blogometer/index.html
    - http://engrm.com/blogometer/rss.2.0.xml

    

• References:
  • Python and JSON vs XML???
    • From: Michael Champion <michaelc.champion@g...>
  • Re: Python and JSON vs XML???
    • From: "Pete Cordell" <petexmldev@t...>
  • Re: Python and JSON vs XML???
    • From: Bob Foster <bob@o...>

• Prev by Date: Python and JSON customer implementation
• Next by Date: Re: Python and JSON vs XML???
• Previous by thread: Re: Python and JSON vs XML???
• Next by thread: Re: Python and JSON vs XML???
• Index(es):
  • Date
  • Thread