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 2705 - [XSLT] misleading sentence in section 11.1.2
Summary: [XSLT] misleading sentence in section 11.1.2
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XSLT 2.0 (show other bugs)
Version: Candidate Recommendation
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Michael Kay
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-11 18:56 UTC by Joanne Tong
Modified: 2006-02-02 19:54 UTC (History)
0 users

See Also:


Attachments

Description Joanne Tong 2006-01-11 18:56:02 UTC
Second note in section 11.1.2 (Attribute Nodes for Literal Result Elements) 
reads:

"The same is true of the schema-defined attributes xsi:type, xsi:nil, 
xsi:noNamespaceSchemaLocation, and xsi:schemaLocation. If the stylesheet is 
processed by a schema processor, these attributes will be recognized and 
interpreted by the schema processor, but they have no special meaning to the 
XSLT processor. The attributes are copied to the result tree in the same way 
as any other attribute. If the result tree is validated, the copied attributes 
will again be recognized and interpreted by the schema processor."

The sentence "... but they have no special meaning to the XSLT processor" 
should be rephrased because those attributes do have a meaning when validation 
is requested by an XSLT processor.  The second note in section 19.2.1.1 
(Validation using the [xsl:]validation Attribute) reads: 

"If an element that is being validated has an xsi:type attribute, then the 
value of the xsi:type attribute will be taken into account when performing the 
validation...."
Comment 1 Michael Kay 2006-01-27 20:51:27 UTC
The sentence has been changed to read:

If the stylesheet is processed by a schema processor,
these attributes will be recognized and interpreted by the schema processor, but 
in addition the XSLT processor treats them like any other attribute
on a literal result element: that is, their effective value
(after expanding attribute value templates) is copied to the result
tree in the same way as any other attribute.