• To: <xml-dev@l...>
• Subject: Re: Non-deterministic content models
• From: "Bob Foster" <bob@o...>
• Date: Tue, 15 Jul 2003 19:27:29 -0500
• Cc: "Jeni Tennison" <jeni@j...>
• References: <3.0.6.32.20030715055242.01069350@p...> <20030715040539.GD17627@m...> <1058247974.26014.54.camel@delleric> <48691020885.20030715111931@j...>

From: "Jeni Tennison" <jeni@j...>
> Nice chapter! On the "what to do about ambiguity" front, you mention
> adding an except pattern and using explicit disambiguation rules. A
> third option would be to use type systems that support you saying
> "this value is *both* X and Y".
>...
> You can think of this as multiple inheritance (a new, anonymous, type
> is inherited from both xs:boolean and xs:integer, and the <foo>
> element ends up either being a xs:boolean or an xs:integer, or this
> new anonymous type). A language that used such a type system would
> have to use the usual methods for disambiguation (such as those you
> list in your chapter) in situations where polymorphic operators or
> functions were used with such a type.

What a splendid idea! Too bad it hasn't infected XQuery/XPath 2.0.

Are you aware of any work underway on a query/transform model with a more
inclusive type system?

Bob Foster

• Follow-Ups:
  • Re: Non-deterministic content models
    • From: Jeni Tennison <jeni@j...>

• References:
  • Non-deterministic content models
    • From: Gustaf Liljegren <gustaf.liljegren@b...>
  • Re: Non-deterministic content models
    • From: John Cowan <cowan@m...>
  • Re: Non-deterministic content models
    • From: Eric van der Vlist <vdv@d...>
  • Re: Non-deterministic content models
    • From: Jeni Tennison <jeni@j...>

• Prev by Date: Re: Why 3D Redux?
• Next by Date: Re: Why 3D Redux?
• Previous by thread: Re: Non-deterministic content models
• Next by thread: Re: Non-deterministic content models
• Index(es):
  • Date
  • Thread