W3C home > Mailing lists > Public > www-ws-desc@w3.org > March 2004

Re: Broken resolution of NCNAME or QNAME

From: Sanjiva Weerawarana <sanjiva@watson.ibm.com>
Date: Mon, 15 Mar 2004 22:54:17 +0600
Message-ID: <065e01c40aae$2a5cab40$02c8a8c0@watson.ibm.com>
To: <ygoland@bea.com>, <www-ws-desc@w3.org>

Per EDTODO from the 20040311 telecon, I have updated the draft
to clarify issue 121:

EDTODO    2004-03-05: Editors to add clarification text with regards to
                      issue 121.

Please verify.

Sanjiva.

----- Original Message -----
From: "Yaron Goland" <ygoland@bea.com>
To: <www-ws-desc@w3.org>
Sent: Friday, January 23, 2004 5:01 AM
Subject: 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.
>
> Thanks,
>
> Yaron
Received on Monday, 15 March 2004 11:55:06 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:58:30 GMT