W3C home > Mailing lists > Public > public-qt-comments@w3.org > March 2009

[Bug 6677] [UPD] bug in static typing checking for transform expression in XQUF

From: <bugzilla@wiggum.w3.org>
Date: Tue, 17 Mar 2009 01:53:25 +0000
To: public-qt-comments@w3.org
Message-Id: <E1LjOUf-00039t-Gp@wiggum.w3.org>

Michael Dyck <jmdyck@ibiblio.org> changed:

           What    |Removed                     |Added
                 CC|                            |jmdyck@ibiblio.org

--- Comment #2 from Michael Dyck <jmdyck@ibiblio.org>  2009-03-17 01:53:24 ---
Andrew said:
> As the copied nodes can be replaced in the modify clause, we should
> infer only node()* for these variables in the return clause.

I disagree. Although you can replace copied nodes, you can't replace the
node that a TransformExpr-variable is bound to, because it doesn't have a
parent. (And even if you *could*, the variable would stay bound to the
node, not the replacement.)

So, to resolve this issue, I propose that in the rule in question,
in the two premises of the form:
    statEnvi = statEnvi-1 + varType(Variablei => Typei)
we change the "Typei" to
    [[ node() ]]_sequencetype

That is, the static type of each variable (thoughout its scope) is node().

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Tuesday, 17 March 2009 01:53:34 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:26 UTC