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 1701 - [FS] what is [For/FLWR]?
Summary: [FS] what is [For/FLWR]?
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Formal Semantics 1.0 (show other bugs)
Version: Last Call drafts
Hardware: PC Windows 2000
: P2 trivial
Target Milestone: ---
Assignee: Jerome Simeon
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-17 23:13 UTC by Fred Zemke
Modified: 2005-09-29 10:48 UTC (History)
0 users

See Also:


Attachments

Description Fred Zemke 2005-07-17 23:13:23 UTC
4.8 [For/FLWR] expressions
What is a "[For/FLWR] expression"?  Don't you mean FLWORExpr?
Comment 1 Jerome Simeon 2005-07-19 18:02:06 UTC
The reason for the notation is that FLWOR expressions appear in XQuery, and For
expressions appear in XPath. The formal semantics serves as one formal semantics
specification for both languages, hence the [For/FLWR] notation.
Comment 2 Fred Zemke 2005-07-19 23:12:48 UTC
Perhaps we could reword the first sentence of 4.8 as follows:
"[XPath] provides ForExpr, and [XQuery] provides FLWORExpr, 
which will be collectively referred to as [For/FLWOR].  
[For/FLWR] expressions are used for iteration, ...".

Note that I propose to respell it [For/FLWOR] to align with [XQuery].
Comment 3 Jerome Simeon 2005-07-20 20:43:44 UTC
I agree we should make sure to respell [For/FLWR] to [For/FLWOR].

We should also explains what that mean. We can do it as you suggest, possibly we
could also indicate this right at the beginning in the preliminaries.

Any preference about how we do this?
- Jerome
Comment 4 Fred Zemke 2005-07-26 22:49:26 UTC
(In reply to comment #3)
> I agree we should make sure to respell [For/FLWR] to [For/FLWOR].
> 
> We should also explains what that mean. We can do it as you suggest, possibly we
> could also indicate this right at the beginning in the preliminaries.
> 
> Any preference about how we do this?

If you put it as a general statement in the preliminaries, then it would 
something like "[x/y] refers to something that is called 'x' in [XPath] 
and called 'y' in [XQuery]."  However, [expression/query] is not 
actually called "expression" in either specification; it is called Expr
in both, though I see XPath has XPath ::= Expr and XQuery has 
QueryBody ::= Expr.  Similarly [For/FLWOR] is not actually called For or
FLWOR.  So there is no syntactic transform from [x/y] to its referents.
This good be arranged, but it is probably simpler to just supply a 
definition whenever one of these symbols is introduced.

Fred
Comment 5 Jerome Simeon 2005-09-29 10:37:26 UTC
The [For/FLOWR] case has been fixed, but this particular comment does not touch
any formal notation. This is automatically generated text for shared
specifications (which FS is). [expression/query] for instance is intended in the
english sense, an 'expression' or a 'query'.

I don't think there is necessity to add formal description of that unformal
written form.

- Jerome