- From: <bugzilla@wiggum.w3.org>
- Date: Fri, 10 Nov 2006 16:03:25 +0000
- To: public-qt-comments@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=3790
tim@cbcl.co.uk changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |
------- Comment #2 from tim@cbcl.co.uk 2006-11-10 16:03 -------
Could you please explain why this space is spurious. For example, in
copynamespaces-4 (below) the in-scope-prefixes($new//child::*) should return a
sequence of three strings ("xml", "foo", "").
Either:
1. I'm wrong and the result of in-scope-prefixes should only be ("xml",
"foo").
2. I'm right but the space should be dropped for some reason (why?) - if so,
the test doesn't discriminate between the results ("xml", "foo") and ("xml",
"foo", "").
declare namespace foo = "http://example.org";
declare copy-namespaces preserve,inherit;
(: insert-start :)
declare variable $input-context1 external;
(: insert-end :)
let $existingElement := <existingElement
xmlns="www.existingnamespace.com">{"Exi
sting Content"}</existingElement>
let $new := <foo:newElement xmlns =
"www.mynamespace.com">{$existingElement}</fo
o:newElement>
for $var in (in-scope-prefixes($new//child::*))
order by $var ascending
return $var
Received on Friday, 10 November 2006 16:03:33 UTC