Broken resolution of NCNAME or QNAME

I realize I'm putting myself in the running for pedant of the year by
bringing this up but I couldn't find a statement anywhere in Part 1 that
requires a WSDL engine to fault if it can't successfully resolve a NCNAME or
QNAME reference within a WSDL instance. E.g. if a message attribute points
to a QNAME for a Schema definition that isn't actually defined then this is
a fault.



Received on Thursday, 22 January 2004 18:01:35 UTC