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 8480 - XQTS: CVS: comp-attr-bad-name-1 vs. K2-ComputeConAttr-38
Summary: XQTS: CVS: comp-attr-bad-name-1 vs. K2-ComputeConAttr-38
Status: RESOLVED FIXED
Alias: None
Product: XML Query Test Suite
Classification: Unclassified
Component: XML Query Test Suite (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: 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: 2009-12-11 16:09 UTC by Tim Mills
Modified: 2010-04-05 15:48 UTC (History)
2 users (show)

See Also:


Attachments

Description Tim Mills 2009-12-11 16:09:25 UTC
Recently added test 'comp-attr-bad-name-1'

(: 3.7.3.2 Computed Attribute Constructor per XQ.E19
   XQDY0044 if namespace prefix is 'xmlns'
   Mary Holstege
 :)

(: insert-start :)
(: insert-end :)

<result>{attribute {"xmlns:error"} {}}</result>

and older test K2-ComputeConAttr-38

  (:*******************************************************:)
  (: Test: K2-ComputeConAttr-38                            :)
  (: Written by: Frans Englich                             :)
  (: Date: 2007-11-22T11:31:21+01:00                       :)
  (: Purpose: This query yields XPST0081 because the prefix 'xmlns' is unbound(
  #2). :)
  (:*******************************************************:)
  attribute {"xmlns:localName"} {"content"}

essentially test the same thing but expect different errors.
Comment 1 Andrew Eisenberg 2009-12-22 21:24:23 UTC
comp-attr-bad-name-1 was written to test the effect of erratum XQ.E19. Our older test, K2-ComputeConAttr-38, should probably be updated to expect the same error.

Looking at our new rules in 3.7.3.2 Computed Attribute Constructors, I'm concerned that some additional work on the spec is required. I'll report back after the WGs have considered this.
Comment 2 Andrew Eisenberg 2010-04-05 15:45:49 UTC
In Bug #8537, the WGs determined that the changes for XQ.E19 had not been correctly applied to our PER document. The corrected text for section 3.7.3.2, Computed Attribute Constructors, will read, in part:

If the keyword attribute is followed by a name expression, the name
expression is processed as follows:

   1. ...
   2. ...
   3. If the atomized value of the name expression is of type xs:string or
      xs:untypedAtomic, ... If conversion of the atomized name expression
      to an expanded QName is not successful, a dynamic error is raised
      [err:XQDY0074].

A dynamic error is raised [err:XQDY0044] if the node-name of the constructed
attribute node has any of the following properties:

    * Its namespace prefix is xmlns. 
    * ...


In Bug #8500, we said that we would be liberal in accepting possible errors in our test cases.

Considering these two resolutions, I am changing both comp-attr-bad-name-1 and K2-ComputeConAttr-38 to accept both err:XQDY0074 and err:XQDY0044.

Please close this bug if you are satisfied with this resolution.