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 2726 - [XSLT] Restrictions on [xsl:]type for elements
Summary: [XSLT] Restrictions on [xsl:]type for elements
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-18 20:46 UTC by Joanne Tong
Modified: 2006-02-02 20:07 UTC (History)
0 users

See Also:


Attachments

Description Joanne Tong 2006-01-18 20:46:27 UTC
The first bullet of section 19.2.1.2 indicates that the type specified in [xsl:]
type is used as the "processor-stipulated type definition" in applying the 
rules in section 3.3.4 "Element Declaration Validation Rules", validation 
rule "Schema-Validity Assessment (Element)", clauses 1.2 and 2.  Subclause 
1.2.1.1 refers to section 5.2 of the Schema Structures spec.  The first item in 
the numbered list in 5.2 indicates that the type identified by the user or 
application should be a complex type definition.

XSLT 2.0 defines ERR XTSE1530 if the [xsl:]type for an attribute refers to a 
complex type.  However, there is no corresponding error if the [xsl:]type for 
an element refers to a simple type.

The XSL WG should track bug 2723 (http://www.w3.org/Bugs/Public/show_bug.cgi?
id=2723) to get Schema's view on this.  If Schema relaxes the requirement, no 
change is required to XSLT; otherwise, XSLT needs a static error.
Comment 1 Michael Kay 2006-02-02 20:06:54 UTC
Resolved to address this with a note at the end of the first bullet:

It is not an error if the identified type definition is a simple type, although
<bibref ref="xmlschema-1"/> does not define explicitly that this case is permitted.