Point of clarification - is this an issue in the WSDL generationfor ws binding? NCNAME and NMTOKEN use

[Eric Johnson <eric@tibco.com>]

In section 4.5 (20070926 draft), the specification discusses WSDL
generation.

<definitions name="componentName/serviceName"
             targetNamespace="HTTP Base URI/componentName/serviceName"....

The trouble is that in WSDL, /definitions/@name is an NMTOKEN, so "/" is
not allowed to appear.
(http://www.w3.org/TR/wsdl#A4.1,
http://www.w3.org/TR/2000/WD-xml-2e-20000814#NT-Nmtoken) Am I simply
misunderstanding the generation here?

Likewise, with:
  <binding
name="/service/binding.ws[n]/@name+[/soapVersionPrefix]+'Binding'"
           type="SCA service interface portType name">

the binding/@name attribute is likewise an NCNAME, so slashes are again
not allowed.
(http://www.w3.org/TR/1999/REC-xml-names-19990114/#NT-NCName)

If I'm reading this correctly, the spec says to generate invalid WSDL.

Could someone confirm?

-Eric.