Re: [xml-dev] Schematron Question: proper way to express the text versio

["bryan rasmussen" <rasmussen.bryan@gmail.com>]

hmm sorry, I thought you were talking about the diagnostics that would
be output

Cheers,
Bryan Rasmussen

On 2/12/07, Costello, Roger L. <costello@mitre.org> wrote:
> Michael Kay wrote:
>
> > You can't design error messages ...
>
> No, it's not an error message that is being specified within the
> <sch:assert> element.  Error messages are specified in a diagnostic:
>
> <sch:assert test="EndTime &gt; StartTime" diagnostics="lessThan">
>              -- text version of assertion --
> </sch:assert>
>
> <sch:diagnostics>
>       <sch:diagnostic id="lessThan">
>                         -- Put error message here --
> </sch:diagnostic>
>
> The message that is specified within the <sch:assert> element is a
> natural language version of the XPath expression (in the assertion's
> test attribute).
>
> My question is with regards to the proper way to express that natural
> language statement.  Namely, is it expressed using "is", or "should
> be", or "must be".
>
> /Roger
>
> -----Original Message-----
> From: Michael Kay [mailto:mike@saxonica.com]
> Sent: Monday, February 12, 2007 8:58 AM
> To: Costello, Roger L.; xml-dev@lists.xml.org
> Subject: RE: [xml-dev] Schematron Question: proper way to express the
> text version of assertions?
>
>
> You can't design error messages without knowing the audience they are
> designed for. The right answer to your question depends on who you
> expect to
> see the messages and act on them.
>
> Michael Kay
> http://www.saxonica.com/
>
>
> > -----Original Message-----
> > From: Costello, Roger L. [mailto:costello@mitre.org]
> > Sent: 12 February 2007 12:44
> > To: xml-dev@lists.xml.org
> > Subject: [xml-dev] Schematron Question: proper way to express
> > the text version of assertions?
> >
> > 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
> >
>
>
> _______________________________________________________________________
>
> 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
>
>