[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qexo-general] Re: most critical Qexo bugs/missing features?
From: |
François Leygues |
Subject: |
Re: [Qexo-general] Re: most critical Qexo bugs/missing features? |
Date: |
Wed, 21 Aug 2002 22:35:25 +0200 |
User-agent: |
Mozilla/5.0 (compatible; MSIE 5.5; Windows 98; DigExt) |
Per Bothner wrote:
2) My wish list includes of course a full coverage of the (still to
be finalized) spec. However, I would like first :
- read the names of element or attribute nodes
The document model "name" function returns the (expanded) QName
(i.e. a pair of a URL and a local string). Is that what you're
looking for? Or are you looking for the "unexpanded" name,
with a namespace prefix, like "html:ul"?
Well both, the second being preferred for "normal" processing. But I
ignore something: is this possible today with qexo ? If yes, it can be
very useful , in fact what I need is to be able to do:
define function x(){<a b="c" d="e"/>/@*}
for $a in x() return <foo name="{attribute-name($a)}"
value="{string($a)}" />
which would return :
<foo name="b" value="c"/><foo name="d" value="e"/>
- compute element and attribute names.
Like te ComputedElementConstructor or the ComputedAttributeConstructor
in the latest (Auguest 14) specification?
yes! http://www.w3.org/TR/xquery/#computedConstructors
But you have something similar anyway (finally , I have found it...):
let $x:= "a" , $y = "b" return make-element($x, make-attribute($y,"3"))
returns what I want : <a b="3"/>
Bye!