This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 4733 - [FT] editorial: E XML Syntax (XQueryX) for XQuery 1.0 and XPath 2.0 Full-Text 1.0
Summary: [FT] editorial: E XML Syntax (XQueryX) for XQuery 1.0 and XPath 2.0 Full-Text...
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Full Text 1.0 (show other bugs)
Version: Last Call drafts
Hardware: All All
: P2 minor
Target Milestone: ---
Assignee: Jim Melton
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-06-23 10:16 UTC by Michael Dyck
Modified: 2007-08-12 10:03 UTC (History)
0 users

See Also:


Attachments

Description Michael Dyck 2007-06-23 10:16:57 UTC
E XML Syntax (XQueryX) for XQuery 1.0 and XPath 2.0 Full-Text 1.0

[1]
"Because XQuery 1.0 and XPath 2.0 Full-Text 1.0 integrates seamlessly with
XQuery 1.0"
    I would say there's a visible seam where the two join.
    Delete "seamlessly".

[2]
'([XQuery 1.0 and XPath 2.0 Full-Text Requirements], section 4.3,
Composability, states that "XQuery/XPath Full-Text MUST be composable with
XQuery, and SHOULD be composable with itself.")'
    This is kind of clunky for a parenthetical remark. Delete it, I think.

[3]
"it follows that the XML Syntax for XQuery 1.0 and XPath 2.0 Full-Text 1.0
must integrate seamlessly with the XML Syntax for XQuery 1.0."
    This sentence is saying something like "because this spec satisfies
    requirement X, it therefore satisfies requirement Y". Is it the spec's
    job to point out how it comes to satisfy its requirements?
Comment 1 Jim Melton 2007-08-12 02:08:59 UTC
The editor responsible for Appendix E has applied the two suggestions found in your items 1 and 2.  That editor believes that no changes are needed in response to your item 3.  We have marked this bug FIXED (even though item 3 resulted in no changes to the document).  If you are satisfied with this action, please mark the bug CLOSED.