9 messages in org.w3.xproc-devRe: calabash: p:wrap step
FromSent OnAttachments
James FullerNov 18, 2008 12:50 pm 
Norman WalshNov 18, 2008 12:53 pm 
Henry S. ThompsonNov 19, 2008 3:50 am 
mozerNov 19, 2008 5:10 am 
mozerNov 19, 2008 5:14 am 
Norman WalshNov 19, 2008 5:44 am 
David A. LeeNov 22, 2008 6:38 am 
Jeni TennisonNov 22, 2008 7:45 am 
David A. LeeNov 22, 2008 8:37 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: calabash: p:wrap stepActions...
From:mozer (xmli@gmail.com)
Date:Nov 19, 2008 5:10:56 am
List:org.w3.xproc-dev

I'm ok with this one match pattern should match also document node() to be able to have

<?xml version="1.0"?> <?my PI?> <my-root/> <!-- mycomment -->

and do

<p:wrap match="/" wrapper="some_element"/>

to have as a result <?xml version="1.0"?> <some_element> <?my PI?> <my-root/> <!-- mycomment --> </some_element>

Xmlizer

On Tue, Nov 18, 2008 at 9:54 PM, Norman Walsh <nd@nwalsh.com> wrote:

"James Fuller" <jame@gmail.com> writes:

consider

<p:pipeline name="pipeline" xmlns:p="http://www.w3.org/ns/xproc" xmlns:my="http://www.example.org/test/mine">

<p:wrap match="/" wrapper="some_element"/>

</p:pipeline>

never seems to match any top level elements irregardless of source input ...

is this the correct behavior or a bug ?

That pipeline should raise err:XC0023:

It is a dynamic error (err:XC0023) if the [match] pattern matches anything other than element, text, processing instruction, and comment nodes.

Perhaps that's a bug. Perhaps we should allow the match pattern to match document nodes as well so that you can wrap all the leading PIs, comments, and whitespace.

Be seeing you, norm