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] Schematron Question: proper way to express the text version of assertions?

just to note the test should probably use the number function
number(EndTime) > number(StartTime) but of course this does not
allow us to do checks on three day meetings :)

as for your question I guess it depends.

I have a lot of crappy schematron error messages that were just
written by me having no time and having to translate cryptic
bureaucratic danish into english.

these are often in the form of
EndTime must be greater than StartTime

which people then call up and say huh?

One thing, from learning better, is that we have seperated out error
messages from the schematron file, the error messages are kept in an
external file, the schematron has an id on the assertion, the
schematron is run through a preprocessor and has the error message put
in. This allows someone other than me to hopefully write some clear
lengthy human comprehensible error messages like,

you have a meeting in which the EndTime comes before the StartTime,
the standard requires that the EndTime must always come after the
StartTime. Error ID number 25.

Bryan Rasmussen

On 2/12/07, Costello, Roger L. <costello@mitre.org> wrote:
> Hi Folks,
> Consider this simple XML document:
> <Meeting>
>       <StartTime>0900</StartTime>
>       <EndTime>1000</EndTime>
> </Meeting>
> With Schematron I can express this data constraint:
>        "The Meeting's EndTime must be after its StartTime"
> This is expressed using a Schematron rule:
> <sch:rule context="Meeting">
>      <sch:assert test="EndTime &gt; StartTime">
>              -- text version of assertion --
>      </sch:assert>
> </sch:rule>
> Read as: "In the context of the Meeting element, I assert that the
> value of EndTime must be greater than the value of StartTime"
> Question:
> 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"?
> 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?
> /Roger
> _______________________________________________________________________
> XML-DEV is a publicly archived, unmoderated list hosted by OASIS
> to support XML implementation and development. To minimize
> spam in the archives, you must subscribe before posting.
> [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
> Or unsubscribe: xml-dev-unsubscribe@lists.xml.org
> subscribe: xml-dev-subscribe@lists.xml.org
> List archive: http://lists.xml.org/archives/xml-dev/
> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php

[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