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

Re: what's missing in XML? What's coming?

• From: Andrew Welch <andrew.j.welch@gmail.com>
• To: David Lee <dlee@calldei.com>
• Date: Tue, 3 Jan 2012 11:27:12 +0000

On 3 January 2012 11:15, David Lee <dlee@calldei.com> wrote:
>
>
> The *purpose* of XDM is to be the input to XQuery and XSLT. They are
> only defined to operate over XDM instances. I think I must not be
>
>
>
> Try sending a sequence, non document node or atomic type as the primary
> input to xquery or xslt.
>
> Not supported, very annoying for languages that as you say whose purpose is
> process is processing XDM

It's worked around easily enough by using a standalone transform and
supplying it as a parameter, or by pulling it in using a combination
of unparsed-text(), some wrapper markup and a parse() extension.

I think primary input xml might die off as the language evolves.


-- 
Andrew Welch
http://andrewjwelch.com

• Follow-Ups:
  • RE: what's missing in XML? What's coming?
    • From: "David Lee" <dlee@calldei.com>

• References:
  • Re: what's missing in XML? What's coming?
    • From: Rick Jelliffe <rjelliffe@allette.com.au>
  • RE: what's missing in XML? What's coming?
    • From: "David Lee" <dlee@calldei.com>
  • RE: what's missing in XML? What's coming?
    • From: Liam R E Quin <liam@w3.org>
  • RE: what's missing in XML? What's coming?
    • From: "David Lee" <dlee@calldei.com>
  • RE: what's missing in XML? What's coming?
    • From: Liam R E Quin <liam@w3.org>
  • Re: what's missing in XML? What's coming?
    • From: David Lee <dlee@calldei.com>