ISSUE-76

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

State:

OPEN

Product:

Advanced

Raised by:

Vladislav Bezrukov

Opened on:

2006-10-24

Description:

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

Related emails:

1. ISSUE-76: Advanced Pattern 3.1.1 NoTargetNamespace disallowed by WS-I BP1.1 R2105 (from dean+cgi@w3.org on 2006-10-24)

Related notes:

No additional notes.