Advanced Pattern 3.1.1 NoTargetNamespace disallowed by WS-I BP1.1 R2105
- Raised by:
- Vladislav Bezrukov
- Opened on:
Description: The Advanced Patterns Spec  considers a Schema Pattern (3.1.1) having the targetNamespace omitted. The WS-I Basic Profile 1.1  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.  http://www.w3.org/2002/ws/databinding/edcopy/advanced/advanced.html  http://www.ws-i.org/Profiles/BasicProfile-1.1.html
- Related emails:
- ISSUE-76: Advanced Pattern 3.1.1 NoTargetNamespace disallowed by WS-I BP1.1 R2105 (from firstname.lastname@example.org on 2006-10-24)
No additional notes.