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

Re: XPath 1.5? (was RE: typing and markup)

• To: David Carlisle <davidc@n...>
• Subject: Re: XPath 1.5? (was RE: typing and markup)
• From: jborden@a...
• Date: Wed, 08 May 2002 13:53:36 +0000
• Cc: ricko@a..., xml-dev@l...

> 
> > A Schematron assertion (that the node list is non-null) would then always
> > fail, even at "compile" time.
> > 
> > I think this behavior would be _better_ for Schematron.
> 
> How can that be better for schematron? It completely breaks the whole
> purpose of the schematron schema, which is to find the "bad" markup and
> to report the occurrences to the user. Having your schematron schema
> fail to compile because it is looking for illegal cases means that
> almost all schematron schema would not compile.

A followup, and to be crystal clear, I did not mean to imply
that the Schematron schema would fail to "compile" whatever
that means (I suppose it would be some sort of static type
analysis?)

What I said is that the "assertion would fail" that is it
would be known that an assertion, which depends on a 
particular node set being not null, i.e. not empty, would 
_never be true_ as long as the XML document was e.g. XSD valid.

The Schematron schema would be entirely "correct" -- assertions
are intended to "fail" i.e. trigger some event when that
which is asserted is "not true" i.e. "null"

Jonathan

• Prev by Date: Re: XQuery types was Re: Yet another plea for XUpdate...
• Next by Date: Re: XPath 1.5? (was RE: typing and markup)
• Previous by thread: RE: XPath 1.5? (was RE: typing and markup)
• Next by thread: Re: XPath 1.5? (was RE: typing and markup)
• Index(es):
  • Date
  • Thread