From: mark.d.witmer@gmail.com
Cc: guile-user@gnu.org
Subject: Re: Guile XCB
Date: Tue, 18 Jun 2013 09:54:43 -0700 [thread overview]
Message-ID: <8761xbz7e4.fsf@mark-desktop.PK5001Z> (raw)
In-Reply-To: <CAGua6m0OHtELesFC1ORXudv2M0Zw_rfdLg=CQGPU9=FETCZy_A@mail.gmail.com> (Stefan Israelsson Tampe's message of "Tue, 18 Jun 2013 17:43:42 +0200")
The following message is a courtesy copy of an article
that has been posted to gmane.lisp.guile.user as well.
Stefan Israelsson Tampe <stefan.itampe@gmail.com> writes:
> Hi Mark!
>
> Nice tool!
>
> A bit off topic but maybe something that is perhaps useful in this
> project, is there any scheme framework
> centered around the scheme xsd specification to validate and translate
> data.
>
> If not, I could help. I'm wanting to learn that technology
> and could in the mean time code something useful for
> all to enjoy
>
> If I would do that I would combine the guile module system and
> xml namespaces an look at code that executes to a sxml-similar
> representation.
>
> Transfoming xml and parsing xml would mean that one uses syntax-parse,
> syntax-rules
> etc..
>
> WDYT
>
> /Stefan
>
That's a cool idea. sxml-match provides a pattern-matching library for
xml with a way of binding variables to values extracted from the
sxml. Unlike xsd, however, it's missing a convenient way to constrain
the number of a particular child-element in some node (beyond specifying
0, 1, or many), and a way to check the type of data stored inside a
node. I had to write a few functions to do that stuff. I could see an
augmented version of sxml-match being useful as Scheme-friendly xsd
alternative.
--
Mark Witmer
prev parent reply other threads:[~2013-06-18 16:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-18 3:25 Guile XCB mark
2013-06-18 12:50 ` Ludovic Courtès
2013-06-18 16:49 ` mark.d.witmer
2013-06-18 15:43 ` Stefan Israelsson Tampe
2013-06-18 16:54 ` mark.d.witmer [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=8761xbz7e4.fsf@mark-desktop.PK5001Z \
--to=mark.d.witmer@gmail.com \
--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).