| CARVIEW |
Select Language
HTTP/2 200
date: Thu, 09 Oct 2025 04:06:01 GMT
content-type: text/html
content-encoding: gzip
last-modified: Thu, 20 Jul 2023 23:26:49 GMT
cache-control: max-age=2592000, public
expires: Fri, 07 Nov 2025 22:15:57 GMT
vary: Accept-Encoding
access-control-allow-origin: *
x-request-id: 98b8fff92a3e5142
strict-transport-security: max-age=15552015; preload
x-frame-options: deny
x-xss-protection: 1; mode=block
cf-cache-status: HIT
set-cookie: __cf_bm=qd_R6iAfGPOztwcSfmA06FMF9zKCpLttdNIaaDfvrSo-1759982761-1.0.1.1-z6mS4btqLtExWa3lB3tk8kIrJjrcXaTkT1bbb7N2kBOMWU8VybUFywFD2ElS7jZ4C37rg6_QbHUbCh4UKSltPM0nc9CH_dSC7PDjyfRs8GY; path=/; expires=Thu, 09-Oct-25 04:36:01 GMT; domain=.w3.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98bb00becdb11ec2-BLR
alt-svc: h3=":443"; ma=86400
Broken resolution of NCNAME or QNAME from Yaron Goland on 2004-01-22 (www-ws-desc@w3.org from January 2004)
Broken resolution of NCNAME or QNAME
- From: Yaron Goland <ygoland@bea.com>
- Date: Thu, 22 Jan 2004 15:01:33 -0800
- To: <www-ws-desc@w3.org>
- Message-ID: <02b601c3e13b$ae8f1ac0$65e5e40c@bea.com>
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 Thursday, 22 January 2004 18:01:35 UTC