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 13049 - [CVS] stf-replace-node-02
Summary: [CVS] stf-replace-node-02
Status: NEW
Alias: None
Product: XQuery Update Facility Test Suite
Classification: Unclassified
Component: XQuery Update Facility Test Suite (show other bugs)
Version: unspecified
Hardware: PC Windows 3.1
: P2 normal
Target Milestone: ---
Assignee: Benjamin Nguyen
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-24 16:02 UTC by Tim Mills
Modified: 2012-12-04 00:52 UTC (History)
0 users

See Also:


Attachments

Description Tim Mills 2011-06-24 16:02:33 UTC
Because static typing implementations can extend the type checking rules in FS, this test can be failed by a static-typing implementation.

In this case, it is possible to infer that $target has static type element(employee)? in

let $target as node()? := $input-context/works[1]/employee[1]

I would suggest altering the test to:

(: Name: stf-replace-node-02 :)
(: Description: replace-node: ST of TargetExpr is too vague. :)

(: insert-start :)
declare variable $input-context external;
(: insert-end :)

let $target as node()? := 
  if (exists($input-context/works[1]/employee[1])
  then $input-context/works[1]/employee[1]
  else $input-context
return
    replace node $target with <employee name='John Q Public'/>
Comment 1 Tim Mills 2011-06-27 13:59:51 UTC
There are similar problems in the following tests.

stf-delete-01
stf-insert-01
stf-insert-after-02
stf-replace-node-02
stf-replace-node-06
stf-replace-value-of-node-02
stf-transform-02
Comment 2 Tim Mills 2011-06-28 08:58:11 UTC
There is also a similar problem in stf-replace-node-04.