Re: Exclude prefixes on p:inline

All,

I just looked at this, as I was thinking this could be useful for  
inline XForms instances as well.

I have a few comments/questions:

* The XProc namespace is excluded automatically. Is it correct to say  
that if I want to pass an inline pipeline definition to a processor,  
which uses the same prefix as the enclosing pipeline, then I can  
redefine the namespace on the root element of the inline document? Or,  
do I even have to do that?

* Related: the text doesn't seem to say what happens if you exclude a  
prefix, and that prefix turns out to be used as element or attribute  
prefix. Should it be an error? Or is the prefix not excluded? It seems  
that XSLT says there is namespace fixup taking place. Maybe the same  
needs to be said here.

A little example to try to understand this:

<p:inline>
   <p:foo bar="p:gaga1">
     <gigi bar="p:gaga2"/>
   </p:foo>
</p:inline>

What happens with this?

* Is it expected to work at all?
* Can the attribute value p:gaga1 be resolved by the recipient of the  
document?
* Can the attribute value p:gaga2 be resolved by the recipient of the  
document? I.e. if ns fixup occurs, does it only apply to p:foo?

-Erik

On May 1, 2008, at 4:22 AM, Norman Walsh wrote:

> / ht@inf.ed.ac.uk (Henry S. Thompson) was heard to say:
> | The DTD as I just checked it in allows it on
>
> I just did a cvs update and didn't get any new schemas...
>
>                                        Be seeing you,
>                                          norm
>
> -- 
> Norman Walsh <ndw@nwalsh.com> | One's never alone with a rubber duck.
> http://nwalsh.com/            |

--
Orbeon Forms - Web Forms for the Enterprise Done the Right Way
http://www.orbeon.com/

Received on Friday, 16 May 2008 23:24:52 UTC