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

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

I think, especially in the context of error messages about data
formats, that even an audience originally assumed to be all techies
will bleed out to the non-technical.
At some point the nice little lady in accounting wants to know what
"error 1606, temporal distortion field in effect" means.  Of course
when that happens one can say it was because people didn't understand
that their proper audience was non-technical, but that sounds like the
kind of hindsight best practiced when the EndTime of a meeting occurs
before the StartTime (because then it is predictive, yes?)

Cheers,
Bryan Rasmussen

On 2/12/07, Michael Kay <mike@saxonica.com> wrote:
>
> 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
>
>