W3C home > Mailing lists > Public > public-xsd-databinding@w3.org > October 2006

ISSUE-76: Advanced Pattern 3.1.1 NoTargetNamespace disallowed by WS-I BP1.1 R2105

From: Databinding Issue Tracker <dean+cgi@w3.org>
Date: Tue, 24 Oct 2006 13:50:21 +0000 (GMT)
To: public-xsd-databinding@w3.org
Message-Id: <20061024135021.88143BDA8@w3c4.w3.org>


ISSUE-76: Advanced Pattern 3.1.1 NoTargetNamespace disallowed by WS-I BP1.1 R2105

http://www.w3.org/2005/06/tracker/databinding/issues/76

Raised by: Vladislav Bezrukov
On product: Advanced

Description:

The Advanced Patterns Spec [1] considers a Schema Pattern (3.1.1) having the
targetNamespace omitted.

The WS-I Basic Profile 1.1 [2] in the section 4.3.2 disallows this pattern in
R2105 with an exception as follows:

4.3.2 Schema targetNamespace Structure

Requiring a targetNamespace on all xsd:schema elements that are children of
wsdl:types is a good practice, places a minimal burden on authors of WSDL
documents, and avoids the cases that are not as clearly defined as they might be.

R2105 All xsd:schema elements contained in a wsdl:types element of a DESCRIPTION
MUST have a targetNamespace attribute with a valid and non-null value, UNLESS
the xsd:schema element has xsd:import and/or xsd:annotation as its only child
element(s).


Proposal:
To align with the R2105.


[1] http://www.w3.org/2002/ws/databinding/edcopy/advanced/advanced.html
[2] http://www.ws-i.org/Profiles/BasicProfile-1.1.html
Received on Tuesday, 24 October 2006 13:50:35 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 18:20:37 GMT