XML.orgXML.org
FOCUS AREAS |XML-DEV |XML.org DAILY NEWSLINK |REGISTRY |RESOURCES |ABOUT
OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [xml-dev] Rick Jelliffe's article on XSLT 1.0 performance

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@antenna.co.jp


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS