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 4156 - Static typing of fn-node-name-2
Summary: Static typing of fn-node-name-2
Status: CLOSED FIXED
Alias: None
Product: XML Query Test Suite
Classification: Unclassified
Component: XML Query Test Suite (show other bugs)
Version: 1.0.2
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Andrew Eisenberg
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-01-08 16:33 UTC by Tim Mills
Modified: 2010-03-16 15:55 UTC (History)
0 users

See Also:

Attachments

Description Tim Mills 2007-01-08 16:33:50 UTC 
Under the rules given in the formal semantics specification, the filter expression [positino() = last()] does not normalize in the same way as if it had been written as [last()] (see 4.3.2 Filter Expressions).  The result of this is that this argument to fn:node-name in this query is a zero-or-more sequence, rather than a zero-or-one sequence.


(: Name: fn-node-name-2 :)
(: Description: Evaluation of node-name function with argument set to comment no
de. :)
(: Use fn:count to avoid empty file :)

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

fn:count(fn:node-name($input-context1/works[1]/employee[2]/child::text()[position()=last()]))
Comment 1 Tim Mills 2007-01-08 16:41:59 UTC 
fn-nilled-2 has a similar problem.
Comment 2 Carmelo Montanez 2007-03-09 21:18:47 UTC 
Tim:

Thanks for the message.  Changed test by removing static typing dependencies.

Thanks,
Carmelo