Hi Roger, What you were expecting might correspond to the following XQuery Scripting Extension program (mind the semi-colons, which apply the PUL): let $source := doc(‘FitnessCenter. xml ‘) for $i in $source//Member return ( delete node $i/Name; replace node $i/@level with attribute {‘id’} {data($i/Name)}; ) With this program, for each member, the second instruction sees the side effect of the first instruction – unlike your original XQuery Update Facility program, it should fail and the attribute id will be empty. In an XQuery Update Facility (XQUF) program, as Markus said, you will not see any side effects during the execution of the program (this is called snapshot semantics).

Read the rest here:
[Newbie] Why can I delete an element and then use
its value?

Hi Roger, XQuery updates do not apply during execution. Instead your query will just return a pending update list (during its creation the element is still there) and will then apply all updates. Best Markus On Sat, Mar 13, 2010 at 6:07 PM, Costello, Roger L.

Excerpt from:
[Newbie] Why can I delete an element and then use
its value?

Hi Martin, Thanks, that was something I missed (a lot of docs to sift through when learning XQuery !) Unfortunately, my implementation (in BEA ALSB 2.6) does not support that declaration. However, the in-scope-prefixes() function does work so I will try to use that to add the namespaces and hope that they do not get re-removed. Sean SAS Platform Team Work – 902.487.4993 Cell – 902.220.0946 —–Original Message—– From: Martin Probst [mailto:http://x-query.com/mailman/listinfo/talk] Sent: March 10, 2010 9:25 AM To: Garagan, Sean Cc: http://x-query.com/mailman/listinfo/talk Subject: Re: Maintaining namespace for attribute type Hi, did you find the copy-namespaces declaration

Visit link:
Maintaining namespace for attribute type

Registration is now open for two publicly-subscribed deliveries of our hands-on XSLT /XQuery training coming up, one in Europe and one in the US. These are the most in-depth configurations of Crane’s XSLT and XQuery training classes, covering the use of every element, every attribute, every keyword and every function of both XSLT/ XPath 1.0 and 2.0 and XQuery 1.0 with more detail and more exercises than other available configurations of our material. Prague, Czech Republic – March 15-19, 2010 http://www.CraneSoftwrights.com/index.html#Crane201003CZ A post-conference tutorial for XML Prague 2010 – http://XMLPrague.cz Practical Transformation Using XSLT , XQuery and XPath (5 days): http://www.CraneSoftwrights.com/training/ptuxq/ptuxqsyl.htm Venue – Residence Retezov

_____ From: Sweta Kedia [mailto:http://x-query.com/mailman/listinfo/talk] Sent: 04 January 2010 04:33 To: Michael Kay Subject: Re: Substring of an attribute. Hi, The Error message I am getting is XPTY0004: A sequence of more than one item is not allowed as the first argument of compare() (“”, “”, …) Thank you.

Read this article:
Substring of an attribute.

Dear James, thank you for the clarification. This answers my question. Best regards, looking forward to an interesting conference in Prague ! Dana On Dec 22, 2009, at 9:27 AM, James Fuller wrote: > as promised, here is a more official followup from the University > about speakers presentations and published papers.

More here:
Follow Up Re: [ANN] XML Prague 2010 Final Call for
Participation (CFP)

Hi Jens, as an alternative to using XSLT or XQuery Update, my standard XQuery solution would be to create a recursive filter function with a typeswitch statement. Tested with saxon : declare namespace dc=”http://purl.org/dc/elements/1.1/”; declare variable $ xml := petal://kjc-fs2.kjc.uni-heidelberg.de:8081/HIEditor_2.0-Service/P67/V33052″ xml:lang=”en”> daṃtahastavināyaka ; declare function local:modify($title as element(dc:title)) { {$title/text()} }; declare function local:filter($node as node()) { typeswitch ($node) case element(dc:title) return ($node, local:modify($node)) case element() return element { node-name($node) } { $node/@*, for $child in $node/node() return local:filter($child) } default return $node }; local:filter($xml) Wolfgang

More here:
adding elements

James, Michael, thanks for your answers. I think my question wasn’t clear. XML Prague has to take a clear decision about the status of the papers: (a) are they part of an informal proceedings (in which case they can be submitted somewhere else without infringing any copyright and affecting prior publication status), or (b) they are part of a copyrighted publication (in which case they cannot)

See the original post here:
[ANN] XML Prague 2010 Final Call for Participation
(CFP)

> > I’m trying to declare a function that can return 2 element > types but with no success. Maybe its not possible. If foo and bar are sufficiently related to be alternative results of the function, then perhaps they should be members of a substitution group, in which case you can say $root as schema -element(s) where s is the name of the substitution group

Follow this link:
XQuery functions returning multiple element types

> specification explicitly doesn’t say that a conforming implementation must > reject any construct that isn’t defined in (or “supported by”) the spec: and > as far as I have been able to determine, that is a deliberate omission. The > cultural background of XQuery is in the database world, where vendors > routinely expect to implement their own enhancements to standards and users > typically don’t complain

Read the original:
How to copy in-scope namespace bindings