Just to clarify, you said that you think: <myns:mytask> <myns:mytype /> </myns:mytask>
should be legal, as should: <myns:mytask xmlns="uri-corresponding-to-myns"> <mytype /> </myns:mytask> but not: <myns:mytask> <mytype /> </myns:mytask> as in beta2? -Matt --- Stefan Bodewig <[EMAIL PROTECTED]> wrote: > On Wed, 5 Nov 2003, Matt Benson > <[EMAIL PROTECTED]> wrote: > > In beta1, the following worked: > > > > <myns:mytask> > > <myns:mytype /> > > </myns:mytask> > > > > In beta2, I get an error to the effect that > "mytask" > > does not support nested "mytype". > > Not yet fully decided - one of the issues that is > holding up the 1.6 > release. > > I'd say it should work exactly that way (and only > work for the default > namespace if you've defined a local default > namespace): > > <myns:mytask xmlns="uri-corresponding-to-myns"> > <mytype /> > </myns:mytask> > > Stefan > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > __________________________________ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
