Re: Problems with xml-parse-string

[Wojciech Meyer]

On Wed, Sep 22, 2010 at 1:09 PM, Lars Magne Ingebrigtsen <address@hidden> wrote:
> Wojciech Meyer <address@hidden> writes:
>
>> We should use S-XML. S-expression based XML for this and other places
>> where we have XML.
>
> Why on earth would we shoot ourselves in our feet by converting XML to a
> parse tree that looks like this?
>
>     (*TOP*
>       (@ (*NAMESPACES*
>            (HTML "http://www.w3.org/TR/REC-html40";)))
>       (RESERVATION
>         (NAME (@ (HTML:CLASS "largeSansSerif"))
>           "Layman, A")
>         (SEAT (@ (HTML:CLASS "largeMonotype")
>                  (CLASS "Y"))
>            "33B")
>         (HTML:A (@ (HREF "/cgi-bin/ResStatus"))
>            "Check Status")
>         (DEPARTURE "1997-05-24T07:55:00+1")))

Why not? What's the problem here?

Having an Sxml framework will open new doors, and that's the appropriate
method of doing that (IMHO).

Personally, I think because it's:
- well known standard in representing XML with s-expressions
- it would be easier to port existing tools (like some Scheme Xpath
query language
 to Elisp)
- because it supports everything that XML supports

Wojciech