- From: <bugzilla@wiggum.w3.org>
- Date: Fri, 16 Feb 2007 03:00:36 +0000
- To: public-ws-policy-qa@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=4331
Summary: WSDL WG comment 1
Product: WS-Policy
Version: FPWD
Platform: PC
URL: http://lists.w3.org/Archives/Public/public-ws-policy-
comments/2007Feb/0000.html
OS/Version: Windows XP
Status: NEW
Severity: normal
Priority: P2
Component: WSDL1.1-Element-Identifiers
AssignedTo: pcotton@microsoft.com
ReportedBy: Paul.Cotton@microsoft.com
QAContact: public-ws-policy-qa@w3.org
WSDL WG comment 1:
As in WSDL 2.0 component designators, this spec recommends the creation of an
identifier from the targetNamespace of the WSDL 1.1 document, and that this
identifier can be resolved without considering imports and includes. Unlike
WSDL 2.0, in WSDL 1.1 the targetNamespace is not required, and although there
is no wsdl11:include, we have some evidence that some customers have used
multiple wsdl11:imports of the same namespace (which can be the same as the
targetNamespace) and different locations to modularlize their documents – and
that a number of popular tools actually support this “abuse” of import.
These situations demonstrate the limits of the assumption of a 1-1
correspondence between a WSDL 1.1 document and a WSDL 1.1 targetNamespace. The
spec’s recommendation to construct an identifier using the targetNamespace
doesn’t work in these situations. The spec should at least note situations
(edge cases) which conflict with the advice about creation of an element
identifier from the targetNamespace.
Received on Friday, 16 February 2007 03:00:45 UTC