> Your way is OK too. I guess we should have an issue on whether <name> and
> <param> allow elements from other namespaces.
<name> can have elements without any problem because it is whitespace-normalized.
But in case of <param>, we can't normalize whitespaces because it may
be significant. This interferes with child elements.
In other words, if we see
<param> a <child /> b </param>
What shall we pass to a datatype library? " a b "?
> I don't like this. I think it's a slippery slope. If we add a type to
> attribute, then we'll need to add a type attribute to element; then we'll
> need to add key/keyRef attributes as well; then we'll need to allow param
> children.
That's right.
--
Kohsuke KAWAGUCHI +1 650 786 0721
Sun Microsystems
