Re: XQuery and XPath Full Text 1.0 going to CR

* Jim Melton <jim.melton@acm.org> [2008-04-26 20:29-0600]
>
> Gentle DAWGs,
>
> The Full Text Task Force (a joint task force of the XML Query WG and the 
> XSL WG) has completed processing all of the comments received during, and 
> after, the Last Call comment period (see  
> http://www.w3.org/News/2007#item103) and the Working Groups themselves 
> have voted to progress the resulting XQuery and XPath Full Text 1.0 spec 
> to Candidate Recommendation.
>
> The DAWG is cited as a WG with potential interest in this specification.  
> I am writing this message to you by way of informing you of changes that 
> have been made to the Full Text specification since publication of the 
> Last Call Working Draft.  You can find a detailed log of all such changes 
> at  
> http://www.w3.org/XML/Group/qtspecs/specifications/xpath-full-text-10/html/Overview.html#id-xqft-changelog 
> but a brief summary might be helpful to you.
>
> * We clarified the process of tokenization.
>
> * We significantly re-organized some normative material to associate  
> related text more closely.
>
> * We repositioned a prolog extension to the first part of the XQuery  
> prolog from the second part.
>
> * We made many editorial changes in improvement of the text, both for  
> comprehension and to remove ambiguities.
>
> * We identified Features at Risk and drafted a Conformance clause.
>
> * We parsed all code used for examples and for the functions describing 
> the formal semantics of the language, correcting syntax errors as they 
> were found.  Similarly, we made a few revisions to the Full Text XQueryX 
> schemas and stylesheet, bot for clarity and for correctness.
>
> We do not believe that any of those changes are likely to invalidate the 
> review of any group or individual, but we want to offer you the  
> opportunity to confirm or deny that for your group.

From XPath, SPARQL uses these functions:
  definition of the type <numeric>

  fn:not(xs:boolean)
  op:boolean-less-than(boolean, boolean), greater-than

  op:numeric-unary-plus(numeric), minus
  op:numeric-equal(numeric, numeric)
  op:numeric-less-than(numeric, numeric), greater-than
  op:numeric-multiply(numeric, numeric), divide, add, subtract

  fn:compare(xs:string, xs:string); including the regexp language

  op:dateTime-equal(xs:dateTime, xs:dateTime)
  op:dateTime-less-than(xs:dateTime, xs:dateTime), greater-than

  constructor functions for boolean, float decimal, double, integer,
  dateTime and string.

From XQuery, we use <type error>, Expression Processing, 
and lean a bit on Effective Boolean Value 

None of those appear to have changed either in semantics or in the
text needed to describe their invocation. Based on this, I believe
that DAWG has no dependencies on this update to XQuery and XPath
Full Text.

Good luck.


> We have planned a Transition Call on Monday, 2008-04-28 at 14:00 Zakim 
> time, and would appreciate a response as early on that day as possible.
>
> Hope this helps,
>    Jim
>
> ========================================================================
> Jim Melton --- Editor of ISO/IEC 9075-* (SQL)     Phone: +1.801.942.0144
>   Co-Chair, W3C XML Query WG; XQX (etc.) editor    Fax : +1.801.942.3345
> Oracle Corporation        Oracle Email: jim dot melton at oracle dot com
> 1930 Viscounti Drive      Standards email: jim dot melton at acm dot org
> Sandy, UT 84093-1063 USA          Personal email: jim at melton dot name
> ========================================================================
> =  Facts are facts.   But any opinions expressed are the opinions      =
> =  only of myself and may or may not reflect the opinions of anybody   =
> =  else with whom I may or may not have discussed the issues at hand.  =
> ======================================================================== 
>

-- 
-eric

office: +1.617.258.5741 32-G528, MIT, Cambridge, MA 02144 USA
mobile: +1.617.599.3509

(eric@w3.org)
Feel free to forward this message to any list for any purpose other than
email address distribution.