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 3594 - fn-idref-dtd-8 seems wrong
Summary: fn-idref-dtd-8 seems wrong
Status: RESOLVED FIXED
Alias: None
Product: XML Query Test Suite
Classification: Unclassified
Component: XML Query Test Suite (show other bugs)
Version: 0.9.4
Hardware: Macintosh All
: P2 normal
Target Milestone: ---
Assignee: Carmelo Montanez
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-08-10 17:08 UTC by Martin Probst
Modified: 2006-08-30 19:16 UTC (History)
0 users

See Also:


Attachments

Description Martin Probst 2006-08-10 17:08:23 UTC
fn-idref-dtd-8's description says: "Evaluation of fn:idref with multiple ID matching multiple elements.  This test uses a DTD and should generate a runtime-error."

I don't understand the test and how it's supposed to be an error.

Also it expects this error, which seems unrelated to me:
err:XQDY0025
It is a dynamic error if any attribute of a constructed element does not have a name that is distinct from the names of all other attributes of the constructed element.
Comment 1 David Carlisle 2006-08-10 17:25:13 UTC
[non WG response]
I think the test description is a bit vague but the test itself is correct that 
XQDY0025 is the expected error.

fn:idref(("id1", "id2")  returns the attribute IDREF nodes that have these strings as value, there are two such attributes but they both have name anIdRef
so 
<results>{fn:idref(("id1", "id2"),
copies in two attributes of the same name and hits XQDY0025 

David
Comment 2 Carmelo Montanez 2006-08-10 20:33:32 UTC
MArtin:

Thanks for the observation.
David, You are correct, the problem is in the description.  Regrettably I am home and unable to change antything at the time.  This should not stop 1.0 from getting out though.  It si an editorial issue.

Carmelo
Comment 3 Carmelo Montanez 2006-08-14 15:37:09 UTC
I can change the documentation, but it may be too late to make any changes to
the files and I do not want to risk the release.

Thanks,
Carmelo
Comment 4 Carmelo Montanez 2006-08-30 19:16:48 UTC
All:

Changed documentation to better reflect test scenario.

Thanks,
Carmelo