Re: Dynamic creation of parameters without @namespace

/ Toman_Vojtech@emc.com was heard to say:
[...]
| This solution is, in my opinion, much cleaner/clearer (although it needs
| about the same amount of code as the previous one :-)

Yes. For generating c:param elements, the @name (is an NCName) +
@namespace route is definitely the easiest. (We mandate it in
p:parameters.)

(I don't think, though maybe I was confused, that there was ever any motion
to remove that option.)

However, the QName form is easier if you're going to be putting a few
in explicitly:

<p:xslt>
  <p:input port="parameters">
    <p:inline>
      <c:param-set xmlns:x="http://my/xslt/parameter/namespace">
        <c:param name="x:foo" value="1"/>
        <c:param name="x:bar" value="2"/>
        <c:param name="x:baz" value="3"/>
      </c:param-set>
    </p:inline>
  </p:input>
</p:xslt>

*All* I was suggesting was that this:

  <c:param-set xmlns:x="http://my/xslt/parameter/namespace">
     <c:param name="x:foo" value="1" namespace="http:/something/else"/>
  </c:param-set>

should be an error. Saying that its supposed to be equivalent to this:

  <c:param-set xmlns:x="http://my/xslt/parameter/namespace">
     <c:param name="x:foo" value="1" xmlns:x="http:/something/else"/>
  </c:param-set>

doesn't seem very useful because parameter names are QNames so the
implementation never cares about the prefix anyway.

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@nwalsh.com> | The First Amendment is often
http://nwalsh.com/            | inconvenient. But that is besides the
                              | point. Inconvenience does not absolve
                              | the government of its obligation to
                              | tolerate speech.--Justice Anthony
                              | Kennedy, in 91-155