RE: Optional indicator in direct element and attribute constructors.

> So do this for every element- or attribute-constructing line 
> of a query
> that constructs a new multi-hundred-line XML fragment (e.g., a message
> transformation) and you'll undertand the paragraph. 

If you need to do the same thing repeatedly, put it in a function. Or in
this case, add a second step to the processing pipeline that strips out all
empty elements and attributes.

We can't invent custom syntax for everything that anyone ever wants to do.

Michael Kay



> 
> -----Original Message-----
> From: public-qt-comments-request@w3.org
> [mailto:public-qt-comments-request@w3.org] On Behalf Of David Carlisle
> Sent: Friday, May 13, 2005 6:44 AM
> To: Daniel Engovatov
> Cc: public-qt-comments@w3.org
> Subject: Re: Optional indicator in direct element and attribute
> constructors.
> 
> 
> 
>   Producing this result using computed constructors, conditional
>   statements and custom functions turns out to be quite inelegant,
>   cumbersome and hard to maintain.
> 
> don't you just need to replace
> <b>...</b>
> by
> 
> let $x := <b>...</b>
> return
> if ($x/node()) then $x else ()
> 
> David (non WG reply)
> 
> 
> ______________________________________________________________
> __________
> This e-mail has been scanned for all viruses by Star. The
> service is powered by MessageLabs. For more information on a proactive
> anti-virus service working around the clock, around the globe, visit:
> http://www.star.net.uk
> ______________________________________________________________
> __________
> 
> 
> 
>

Received on Friday, 13 May 2005 15:34:15 UTC