• From: Tony Graham <tgraham@a...>
• To: xml-dev@l...
• Date: Wed, 15 Feb 2017 10:20:52 +0000

On 15/02/2017 09:57, Rick Jelliffe wrote:
...

For Schematron I am still not sure whether it would be better to have

<sch:rule context="person">
   <sch:let name="payrate"  value="//rate[$for = current()/@class]"
as="xs:number"/>

or


<sch:rule context="person">
   <sch:let name="payrate"  value="//rate[$for = current()/@class]"  />

  <sch:assert tes"number(payrate)" >The payrate should be a
number</sch:assert>

Presumably the second form is 'better' Schematron because it has a
human-readable message. The separate test also means that you can do
things like have separate messages if a value that should be an integer
is a number but not an integer or is not a number at all.

Regards,


Tony Graham.
--
Senior Architect
XML Division
Antenna House, Inc.
----
Skerries, Ireland
tgraham@a...

• Follow-Ups:
  • Re: Rick Jelliffe's article on XSLT 1.0 performance
    • From: Tony Graham <tgraham@a...>

• References:
  • Rick Jelliffe's article on XSLT 1.0 performance
    • From: Michael Kay <mike@s...>
  • Re: Rick Jelliffe's article on XSLT 1.0 performance
    • From: Rick Jelliffe <rjelliffe@a...>
  • Re: Rick Jelliffe's article on XSLT 1.0 performance
    • From: "Liam R. E. Quin" <liam@w...>
  • Re: Rick Jelliffe's article on XSLT 1.0 performance
    • From: Rick Jelliffe <rjelliffe@a...>
  • Re: Rick Jelliffe's article on XSLT 1.0 performance
    • From: Michael Kay <mike@s...>
  • Re: Rick Jelliffe's article on XSLT 1.0 performance
    • From: Rick Jelliffe <rjelliffe@a...>