[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Schematron Question: proper way to express the textversion

  • From: Rick Jelliffe <rjelliffe@a...>
  • To: xml-dev@l...
  • Date: Tue, 13 Feb 2007 13:27:04 +1100

Re:  Schematron Question: proper way to express the textversion
Costello, Roger L. wrote:
> Hi Folks,
> Within the <sch:assert> element you can provide a textual description
> of the assertion (which I indicate above using "-- text version of
> assertion --").  What is the best way of stating the text version of an
> assertion: 
>          "is", "should be", or "must be"?
In English? Who knows!
> For the above example, which of these is best:
> (a) EndTime is greater than StartTime
> (b) EndTime should be greater than StartTime 
> (c) EndTime must be greater than StartTime
> Or perhaps something else?
> What is recommended?
 For contingent constraints, such as business rules, I tend towards the form

   An X should be Y, because Z.

For necessary constraints, such as your date range example, I tend 
towards the form

  An X must be Y.

For example
 <assert test=" startTime &lt; endTime " role="rangeConstraint">
  Meeting times are specified by two times. The start time must be 
earlier than the end time.

You might consider specifying the assertion text in terms of the problem 
domain rather than the markup. This way the assertion can be written or 
maintained by domain experts who don't know the particular serialization 
used, and the assertion can be understood by users who have the XML data 
mediated through some GUI (and so cannot see the element names or 

One approach is to think "Are these assertions compehensible if typeset 
as bullet points?"  (I think Michael is correct to bring up the expected 
users of the text, though they may not be used as validation messages or 
diagnostics as  Roger mentioned.) In fact, you might even think "What 
forms of assertion allow maximum repurposing?"

Even for texts that are not diagnostic, the tone may be important. An 
old usability text I read said that users react strongly to messages 
that they think are strident and which seem to blame the user. So 
shifting "must" to the more polite "should", which will be a locale- and 
language-dependent consideration of course, might be friendly. On the 
other hand, when assertions are used contractually, then precision and 
definiteness may override politeness, I suppose.

Rick Jelliffe

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


Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
First Name
Last Name
Subscribe in XML format
RSS 2.0
Atom 0.3

Stylus Studio has published XML-DEV in RSS and ATOM formats, enabling users to easily subcribe to the list from their preferred news reader application.

Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website. they were not included by the author in the initial post. To view the content without the Sponsor Links please click here.

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.