From: Andy Wingo <wingo@pobox.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guile-devel@gnu.org
Subject: Re: sxml simple, sxml->xml and namespaces
Date: Mon, 20 Jun 2016 14:11:42 +0200 [thread overview]
Message-ID: <87porchxfl.fsf@pobox.com> (raw)
In-Reply-To: <87d1ncdtds.fsf@elephly.net> (Ricardo Wurmus's message of "Mon, 20 Jun 2016 12:52:47 +0200")
On Mon 20 Jun 2016 12:52, Ricardo Wurmus <rekado@elephly.net> writes:
> Andy Wingo <wingo@pobox.com> writes:
>
>> Apologies for the long delay here. I'm with you regarding namespaces
>> and sxml->xml. In the past I made sure to always get the namespaces
>> attached to the root element via the @ xmlns attributes, and then have
>> namespaced uses just be local names, not qnames, and that way sxml->xml
>> works fine. But, perhaps that doesn't cover all cases in a nice way.
>> Do you still have thoughts on this patch? Is the right thing for you?
>> In any case we need better documentation in the manual about how to deal
>> with namespaces and SXML, in practice, with examples.
>
> Here is another proposal, mirroring what is done in “xml->sxml”:
Neat! Can you elaborate on how it is supposed to work? In a final form
it would need documentation, tests, and an update to the docstring, but
I'd be interested in some xml->sxml->xml round trips as an example.
Andy
next prev parent reply other threads:[~2016-06-20 12:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-08 20:55 sxml simple, sxml->xml and namespaces tomas
2016-06-20 8:56 ` Andy Wingo
2016-06-20 10:52 ` Ricardo Wurmus
2016-06-20 11:20 ` tomas
2016-06-20 12:11 ` Andy Wingo [this message]
2016-06-21 20:36 ` Ricardo Wurmus
2016-06-21 20:58 ` Andy Wingo
2016-06-20 11:18 ` tomas
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=87porchxfl.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=rekado@elephly.net \
/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).