- From: <bugzilla@wiggum.w3.org>
- Date: Wed, 18 Jan 2006 20:46:27 +0000
- To: public-qt-comments@w3.org
- Cc:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=2726 Summary: [XSLT] Restrictions on [xsl:]type for elements Product: XPath / XQuery / XSLT Version: Candidate Recommendation Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: XSLT 2.0 AssignedTo: mike@saxonica.com ReportedBy: joannet@ca.ibm.com QAContact: public-qt-comments@w3.org 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.
Received on Wednesday, 18 January 2006 20:46:32 UTC