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

RE: xPath 2.0, XSLT 2.0 ... size increase over v1.0

• To: "'Murali Mani'" <mani@C...>,"'Dare Obasanjo'" <dareo@m...>
• Subject: RE: xPath 2.0, XSLT 2.0 ... size increase over v1.0
• From: "Michael Kay" <michael.h.kay@n...>
• Date: Thu, 12 Jun 2003 23:47:13 +0100
• Cc: "'Bob Foster'" <bob@o...>,<xml-dev@l...>
• Importance: Normal
• In-reply-to: <Pine.SOL.4.33.0306121311320.3617-100000@p...>
• Reply-to: <michael.h.kay@n...>

> Thanks for the clarification, these are the things I was 
> hoping someone could tell me, using for iterator etc, have we 
> introduced more non-closed operators?? Has someone looked at 
> them closely..?? I suspect there will be some more operators 
> of this nature in XPath 2.0..

The input and output of XPath operations are constrained to be values
described by the XPath data model. In that sense the language is closed.
Whether the data model has the particular mathematical properties you
are looking for is something I can't easily judge.

There are a few glitches in terms of closure, for example I'm not very
comfortable with the fact that the semantics of FLWR expressions in
XQuery are defined using a notion of "tuples" which are objects that
can't be represented directly in the data model, but overall I think
it's pretty clean.

Michael Kay

• Follow-Ups:
  • RE: xPath 2.0, XSLT 2.0 ... size increase over v1.0
    • From: Murali Mani <mani@C...>

• References:
  • RE: xPath 2.0, XSLT 2.0 ... size increase over v1.0
    • From: Murali Mani <mani@C...>

• Prev by Date: RE: xPath 2.0, XSLT 2.0 ... size increase over v1.0
• Next by Date: Re: XML Indirection Facility
• Previous by thread: RE: xPath 2.0, XSLT 2.0 ... size increase over v1.0
• Next by thread: RE: xPath 2.0, XSLT 2.0 ... size increase over v1.0
• Index(es):
  • Date
  • Thread