W3C home > Mailing lists > Public > www-ws-desc@w3.org > November 2006

Re: Duplicate assertions

From: Arthur Ryman <ryman@ca.ibm.com>
Date: Fri, 24 Nov 2006 16:51:12 -0500
To: Lawrence Mandel <lmandel@ca.ibm.com>
Cc: www-ws-desc@w3.org, www-ws-desc-request@w3.org
Message-ID: <OFD300C4AA.3ED246B5-ON85257230.007777B6-85257230.00780B2E@ca.ibm.com>

Thx. I'll eliminate the dups.

Arthur Ryman,
IBM Software Group, Rational Division

blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca

Lawrence Mandel/Toronto/IBM@IBMCA 
Sent by: www-ws-desc-request@w3.org
11/13/2006 09:53 PM


Duplicate assertions

While creating some tests for assertions I've come across some assertions 
that I think specify the same requirement. I'll point these out here and 
suggest that a single assertion be defined for each restriction as 
multiple assertions may lead to problems interpreting the spec and will 
lead to ambiguity wrt the assertion that should be flagged as an error for 
a WSDL document that does not comply with the spec. 

1. Import-0001 
However, any WSDL 2.0 document that contains component definitions that 
refer by QName to WSDL 2.0 components that belong to a different namespace 
MUST contain a wsdl:import element information item for that namespace 
(see 4.2 Importing Descriptions ). 

As with XML schema, any WSDL 2.0 document that references a foreign 
component MUST have a wsdl:import element information item for the 
associated foreign namespace (but which does not necessarily provide a 
location attribute information item that identifies the WSDL 2.0 document 
in which the referenced component is defined). 

2. QName-0002 
Furthermore, all QName references, whether to the same or to different 
namespaces MUST resolve to components (see 2.17 QName resolution ). 

A Description component MUST NOT have such broken references. 

Every QName reference MUST resolve (see 2.17 QName resolution). 

3. Import-0003 
Imported components have different target namespace values from the WSDL 
2.0 document that is importing them. 

This value MUST NOT match the actual value of targetNamespace attribute 
information item in the enclosing WSDL 2.0 document. 

4. Schema-0016 
A WSDL 2.0 document MUST NOT refer to XML Schema components in a given 
namespace unless an xs:import or xs:schema element information item for 
that namespace is present or the namespace is the XML Schema namespace, 
http://www.w3.org/2001/XMLSchema, which contains built-in types as defined 
in XML Schema Part 2: Datatypes Second Edition [XML Schema: Datatypes]. 

When resolving QNames references for schema definitions, the namespace 
MUST be imported by the referring WSDL 2.0 document. 


Lawrence Mandel

Software Developer
IBM Rational Software
Phone: 905 - 413 - 3814   Fax: 905 - 413 - 4920
Received on Friday, 24 November 2006 21:51:32 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:55:02 UTC