From: Ricardo Wurmus <rekado@elephly.net>
To: John Cowan <cowan@ccil.org>
Cc: 20339@debbugs.gnu.org
Subject: bug#20339: sxml simple: sxml->xml mishandles namespaces?
Date: Tue, 05 Feb 2019 10:12:06 +0100 [thread overview]
Message-ID: <874l9iiopl.fsf@elephly.net> (raw)
In-Reply-To: <CAD2gp_ScjmURZ7yTFronxyR9r4P4P2L91mXNHguXpZG86chdVA@mail.gmail.com>
Hi John,
> The trouble with that is that XML rnamespaces are lexically scoped, like
> Scheme
> local variables. It is perfectly valid to map a prefix to more than one
> URL,
> as long as the namespace declarations are in either disjoint or nested
> elements. So you don't know what the absolute name of the element
> or attribute is from just the prefix and the local part.
>
> Furthermore, it is also legal to define more than one prefix for
> the same URL, in which case names using either prefix are normally
> treated as equivalent (however, you can't have elements like
> <a:foo>...</b:foo>
> even if a and b map to the same namespace).
>
> * Is the value for “namespaces” that’s passed in to the
>> FINISH-ELEMENT procedure always the same?
>>
>> * Will the second return value of the final call to FINISH-ELEMENT
>> really always be the complete list of *all* namespaces that have been
>> encountered?
>>
>
> Definitely not, only the namespaces that are currently in scope.
Thanks for the clarifications!
In that case we coud have FINISH-ELEMENT add all namespace declarations
that are in scope to the current node that is about to be returned. It
would be a little verbose, but more correct.
What do you think?
--
Ricardo
next prev parent reply other threads:[~2019-02-05 9:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-15 19:47 bug#20339: sxml simple: sxml->xml mishandles namespaces? tomas
2015-04-20 7:45 ` bug#20339: [PATCH] sxml->xml and namespaces: updated patch tomas
2015-04-21 9:24 ` bug#20339: sxml simple: sxml->xml mishandles namespaces? Ricardo Wurmus
2015-04-21 9:44 ` tomas
2015-04-22 14:29 ` Ricardo Wurmus
2015-04-23 6:57 ` tomas
2015-04-23 7:04 ` Ricardo Wurmus
2015-04-23 7:40 ` tomas
2015-04-25 20:25 ` tomas
2015-04-26 10:28 ` tomas
2016-06-23 19:32 ` Andy Wingo
2016-07-13 13:24 ` tomas
2016-07-13 18:08 ` tomas
2016-07-14 10:10 ` Andy Wingo
2016-07-14 10:26 ` tomas
2019-02-04 20:44 ` Ricardo Wurmus
2019-02-04 22:55 ` John Cowan
2019-02-05 9:12 ` Ricardo Wurmus [this message]
2019-02-05 12:57 ` Ricardo Wurmus
2019-04-08 12:14 ` tomas
2019-02-12 9:56 ` tomas
2019-02-12 20:30 ` Ricardo Wurmus
2019-05-03 10:46 ` bug#20339: Taking a step back (was: sxml simple: sxml->xml mishandles namespaces?) 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=874l9iiopl.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=20339@debbugs.gnu.org \
--cc=cowan@ccil.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).