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

The XQuery working Group has just published new versions of the following specifications: XQuery 1.1: An XML Query Language http://www.w3.org/TR/2009/WD-xquery-11-20091215/ XQueryX 1.1 http://www.w3.org/TR/2009/WD-xqueryx-11-20091215/ XQuery 1.1 Requirements http://www.w3.org/TR/2009/WD-xquery-11-requirements-20091215/ These include a number of significant new XQuery features, including: * group by clause in FLWOR Expressions * tumbling window and sliding window in FLWOR Expressions * count clause in FLWOR Expressions * allowing empty in 3.8.2 For Clause (for functionality similar to outer joins in SQL) * try/catch expressions * Dynamic function invocation * Inline functions * Private functions * Nondeterministic functions * Switch expressions * Computed namespace constructors * Output declarations The XQuery and XSL Working Groups have published First Public Working Drafts of the following specifications: XPath 2.1 http://www.w3.org/TR/2009/WD-xpath-21-20091215/ XQuery and XPath Data Model 1.1 http://www.w3.org/TR/2009/WD-xpath-datamodel-11-20091215/ XPath and XQuery Functions and Operators 1.1 http://www.w3.org/TR/2009/WD-xpath-functions-11-20091215/ XSLT and XQuery Serialization 1.1 http://www.w3.org/TR/2009/WD-xslt-xquery-serialization-11-20091215/ Jonathan

Continued here:
New XQuery / XPath Working Drafts

Hello, We are using mxquery 0.6. A few months ago, I noticed a problem where our xquery updates were losing newlines. One of my coworkers did some testing, closed it as “not a bug, cannot reproduce”, but now today I’ve found that the problem is still happening when inserting attributes but not replacing them (which is probably what he tested).

Read more here:
Problems inserting an attribute that contains new
lines

Hi All, I am creating a result tree from my source tree using XQuery . I have source tree sample data as follows: * “Conservancy.”A charitable corporation * My result tree data should be like this : * "Conservancy. " A charitable corporation * My question is, how can i convert *”* (single quote) in my source tree into its Unicode equivalent *" * in my result tree using XQuery.

More:
How to preserve "
in text node output in result tree