[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: Joe English <jenglish@f...>
• Subject: Re: XPath 1.5? (was RE: typing and markup)
• From: Jeni Tennison <jeni@j...>
• Date: Thu, 9 May 2002 09:50:49 +0100
• Cc: xml-dev@l...
• In-reply-to: <200205090046.g490kCf00493@d...>
• Organization: Jeni Tennison Consulting Ltd
• References: <1071433640305.20020509000505@j...><5.1.0.14.0.20020508063440.0498cd58@n...><001901c1f5a1$88103d70$6501a8c0@pcukmka><p04330103b8fd71b18eac@[192.168.254.4]><5.1.0.14.0.20020507090946.04de98a8@n...><5.1.0.14.0.20020508063440.0498cd58@n...><5.1.0.14.0.20020508075809.048c7e98@n...><200205090046.g490kCf00493@d...>
• Reply-to: Jeni Tennison <jeni@j...>

Hi Joe,

>> There are several aspects of HTML that can't be validated by
>> grammar-based schema languages, such as the fact that form elements
>> shouldn't occur within other form elements at any level [...]
>
> The HTML DTD specifies this constraint with an exclusion exception
> (a feature that was left out of XML):
>
>     <!ELEMENT FORM - - %body.content -(FORM) +(INPUT|SELECT|TEXTAREA)>
>
> TREX can also express it concisely with a combination of CONCUR and
> NOTALLOWED. CONCUR was left out of RELAX-NG, but it can also express
> this constraint, as can RELAX and any other schema language based on
> tree-regular grammars.

Sorry, I should have said XHTML and specified XML Schema or RELAX NG.
What's pertinent here is that the XQuery Semantics doesn't (from what
I can tell) have a concur constraint, and even if it did you wouldn't
be able to express it in XML Schema in order to enable an XQuery or
XPath processor to check it.

But I should have picked a more indicative constraint. What about "The
name attribute of the META element should have a value from the
profile described at the URL specified by the profile attribute on the
HEAD element." or "If a table contains COLGROUP or COL elements, then
the number of columns indicated by the COLGROUP and COL elements must
match the number of columns in the longest row within the table." or
"In client-side image maps, the various areas defined by AREA elements
should completely cover the image's geometry."

Cheers,

Jeni

---
Jeni Tennison
http://www.jenitennison.com/

• References:
  • Re: XPath 1.5? (was RE: typing and markup)
    • From: Jeni Tennison <jeni@j...>
  • Re: XPath 1.5? (was RE: typing and markup)
    • From: Jonathan Robie <jonathan.robie@d...>
  • RE: XPath 1.5? (was RE: typing and markup)
    • From: "Michael Kay" <michael.h.kay@n...>
  • RE: XPath 1.5? (was RE: typing and markup)
    • From: Elliotte Rusty Harold <elharo@m...>
  • Re: XPath 1.5? (was RE: typing and markup)
    • From: Jonathan Robie <jonathan.robie@d...>
  • Re: XPath 1.5? (was RE: typing and markup)
    • From: Jonathan Robie <jonathan.robie@d...>
  • Re: XPath 1.5? (was RE: typing and markup)
    • From: Joe English <jenglish@f...>

• Prev by Date: Re: XPath 1.5? (was RE: typing and markup)
• 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