- From: <bugzilla@jessica.w3.org>
- Date: Fri, 14 Jul 2017 11:42:15 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=30145
Bug ID: 30145
Summary: [xslt30ts] streamable-015 expected result assumes
validation of xsl:source-document input
Product: XPath / XQuery / XSLT
Version: Proposed Recommendation
Hardware: PC
OS: Windows NT
Status: NEW
Severity: normal
Priority: P2
Component: XSLT 3.0 Test Suite
Assignee: abel.online@xs4all.nl
Reporter: botond23@gmail.com
QA Contact: public-qt-comments@w3.org
Target Milestone: ---
The test case streamable-015 in the streamable test-set assumes validation/type
info on the document processed by xsl:source-document.
>From https://www.w3.org/TR/xslt-30/#validation §3 I'd assume that the lack of
the validation attribute on the xsl:source-document has the same effect as
validation="strip".
So when constructing the attributes UnpaidPrincipalBalanceAmount the value
won't be converted to string via FmAmount/xs:decimal (as it would be with
available psvi) and thus retaining the trailing .0 in the values. However the
3rd assert expects the integer form:
<assert>deep-equal(//@UnpaidPrincipalBalanceAmount/string(),
('350000', '350000', '500000', '750000',
'175000'))</assert>
Imho one could choose from the following resolutions:
a) add a validation attribute to the xsl:source-document with a value other
than strip
b) update the test asserts
c) the default validation mode on xsl:source-document is other than strip - in
which case I kindly ask for a reference to the relevant part of the xslt spec.
best regards,
Botond Biró
p.s. in the streamable test-set there are several other test cases -specifying
a source with @validation="strict" - that could be also affected
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Friday, 14 July 2017 11:42:22 UTC