1451 2005-05-16 15:25:17 +0000 [XQuery]: Optional indicator in direct element and attribute constructors 2005-09-29 18:12:19 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XQuery 1.0 Last Call drafts PC Linux CLOSED WONTFIX http://lists.w3.org/Archives/Public/public-qt-comments/2005May/0216.html futureConsideration P2 normal --- 1 cmsmcq chamberl dengovatov public-qt-comments oldest_to_newest 3261 0 cmsmcq 2005-05-16 15:25:17 +0000 [Transcribed from comments list by CMSMcQ. See also the thread beginning http://lists.w3.org/Archives/Public/public-qt-comments/2005May/0216.html] This is an enhancement proposal based upon a very frequently encountered problem among users of our implementation: an external consumer of XML generated by XQuery does want to have certain empty elements and attributes to be omitted. For example: for a query <a><b>{()}</b><c foo="{()}"/></a>, instead of returning <a><b/><c foo=""/></a> to return <a><c/></a> Producing this result using computed constructors, conditional statements and custom functions turns out to be quite inelegant, cumbersome and hard to maintain. Proposed extension is to add "optional" indicators, using '?' character ("?"?) to the direct element and attribute constructors: Change production DirElemConstructor to [94] DirElemConstructor ::= "<" QName "?"? DirAttributeList ("/>" | (">" DirElemContent* "</" QName S? ">")) /* ws: explicit */ And for [95] DirAttributeList ::= (S (QName "?"? S? "=" S? DirAttributeValue)?)* When '?' is present, elements with no children should be omitted, and attributes with value "" should be omitted. Query in the example would be written <a><b?>{()}</b><c foo?="{()}"/></a> To produce <a><c/></a> Daniel; 2731 1 chamberl 2005-06-10 17:29:37 +0000 On May 16, the Query Working Group decided that this request was beyond the scope of XQuery Version 1. Your request for new functionality will be considered in a future version of XQuery. Please let us know whether you are satisfied with this resolution of your comment. 6613 2 dengovatov 2005-09-29 18:05:10 +0000 Should not the bug be kept open against a future version of XQuery? We would not want the issue to be dropped. 6614 3 pcotton 2005-09-29 18:12:19 +0000 The WG is tracking issues for V.Next and this item will not be dropped. /paulc