From: Kirill Lisovsky <lisovsky@acm.org>
Cc: guile-user@gnu.org
Subject: Re: Guile & Sablotron
Date: Tue, 20 Apr 2004 13:59:06 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.58.0404201337130.29660@ant> (raw)
In-Reply-To: <20040317180243.A2923@kiwi.pyrotechnics.com>
Hello,
Please drop a look at SXML:
http://okmij.org/ftp/Scheme/SXML.html
It represents
> > <division id="North">
> > <revenue>10</revenue>
> > <growth>9</growth>
> > <bonus>7</bonus>
> > </division>
...
> (division (id "North")
> (revenue 10)
> (growth 9)
> (bonus 7))
as
(division (@ (id "North"))
(revenue 10)
(growth 9)
(bonus 7))
which makes it clear that "id" is attribute, and not a nested element.
It also provides support for Namespaces, SXPath and XPath,
xml->sxml parsing, sxml->xml/html transformation, and much more...
More information may be found at:
http://ssax.sourceforge.net
http://okmij.org/ftp/Scheme/xml.html
http://pair.com/lisovsky/xml/
http://celtic.benderweb.net/webit/
Maillist:
http://lists.sourceforge.net/lists/listinfo/ssax-sxml
A Guile-oriented tutorial may be found at:
http://www-106.ibm.com/developerworks/library/x-matters31.html
Best regards,
Kirill.
On Wed, 17 Mar 2004, Christopher Cramer wrote:
> On Tue, Mar 09, 2004 at 09:32:05AM -0800, Brian S McQueen wrote:
> > Guile & Sablotron! Who is interested? I need to discuss this with
> > someone! TTN! You do a lot of web work. Using a template engine is the
> > way to go for handling the presentation of data. The programs can produce
> > generic data of this sort:
> >
> > <sales>
> >
> > <division id="North">
> > <revenue>10</revenue>
> > <growth>9</growth>
> > <bonus>7</bonus>
> > </division>
> >
> > <division id="South">
> > <revenue>4</revenue>
> > <growth>3</growth>
> > <bonus>4</bonus>
> > </division>
> >
> > <division id="West">
> > <revenue>6</revenue>
> > <growth>-1.5</growth>
> > <bonus>2</bonus>
> > </division>
> >
> > </sales>
>
> I'm pretty much sold on the idea of integrating templates into Recluse.
> But that sort of output seems a little less elegant than I would like.
> You'd end up with display or format calls outputting XML, which is an
> improvement over outputting HTML, but I wonder if instead of outputting
> XML we could just return a list.
>
> Something like:
>
> '(sales
> (division (id "North")
> (revenue 10)
> (growth 9)
> (bonus 7))
>
> (division (id "South")
> (revenue 4)
> (growth 3)
> (bonus 4)))
>
> I think being able to write the whole thing using just sql->list, map,
> append, etc. (or even backquotes) would make it a lot easier.
>
> I suppose there might be interoperability benefits to using XML though.
> Maybe we should have some ->xml and xml-> procedures.
>
> --
> Christopher Cramer <crayc@pyro.net> <http://www.pyro.net/~crayc/>
> In politics you have to understand not where the voters are when a poll
> is taken, but where they are likely to end up on Election Day.
> -- Rep. Tom Davis, former NRCC Chairman
>
>
> _______________________________________________
> Guile-user mailing list
> Guile-user@gnu.org
> http://mail.gnu.org/mailman/listinfo/guile-user
>
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
prev parent reply other threads:[~2004-04-20 17:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-09 17:32 Guile & Sablotron Brian S McQueen
2004-03-12 8:52 ` Thien-Thi Nguyen
2004-03-14 9:09 ` XML, HTML and Scheme (was: Guile & Sablotron) Daniel Skarda
2004-03-15 16:36 ` Guile & Sablotron Mike Gran
2004-03-18 0:02 ` Christopher Cramer
2004-04-20 17:59 ` Kirill Lisovsky [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.58.0404201337130.29660@ant \
--to=lisovsky@acm.org \
--cc=guile-user@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).