Re: re: generation of qnames/prefixes in content and v

See http://www.w3.org/TR/xslt20req #1.5 about QName-aware string functions

Also, isn't the prefix completely irrelevant as long as
the prefix that the XSLT processor generates resolves to
the same namespace URI that you are talking about?

That is, it should not matter if the XSLT processor spits out "ns00123:integer" instead of "xsd:integer"
as long as the prefix "ns00123" is mapped in scope
to the same namespace URI that the convential "xsd"
prefix is mapped to, right?

<svg xmlns="http://www.w3.org/2000/svg" width="100%" height="100%">
  <defs>
  <!--  java implementation used preferentially by Batik   -->
  <script implements="http://www.example.com/cad-like-behavior"
      type="application/java-archive"
src="jar:http://www.example.com/cad-like-behavior/cad.jar!/com/example/cad.class"/>
  <!--  COM implementation used preferentially by Adobe SVG
             (type didn't seem appropriate)  -->
  <script implements="http://www.example.com/cad-like-behavior"
      src="clsid:3545465756-5656-5757-5876769696"/>
  <!--   ecmascript behavior used if others aren't supported  -->
  <script implements="http://www.example.com/cad-like-behavior"
      type="text/ecmascript">
       alert("Advanced functionality is not supported on this platform");
       ...
   </script>
   </defs>
</svg>