One more duplicate assertion

There is another assertion that I think has been duplicated or rather 
further clarified in other assertions in the WSDL 2.0 spec. According to 
the assertions, if, for example, Interface-0030 fails Description-0024 
will also fail. Although I like the broad coverage of Description-0024 I 
don't like the redundancy in the other assertions I've highlighted.

Description-0024
Each WSDL 2.0 or type system component of the same kind MUST be uniquely 
identified by its qualified name. 

Interface-0030
For each Interface component in the {interfaces} property of a Description 
component, the {name} property MUST be unique. 

Binding-0057
For each Binding component in the {bindings} property of a Description 
component, the {name} property MUST be unique. 

Endpoint-0065
For each Endpoint component in the {endpoints} property of a Service 
component, the {name} property MUST be unique. 

InterfaceOperation-0035
For each Interface Operation component in the {interface operations} 
property of an Interface component, the {name} property MUST be unique. 

Server-0063
For each Service component in the {services} property of a Description 
component, the {name} property MUST be unique. 

Schema-0018
A WSDL 2.0 document MUST NOT define the same element or type in more than 
one inlined schema. 


Thanks,

Lawrence Mandel

Software Developer
IBM Rational Software
Phone: 905 - 413 - 3814   Fax: 905 - 413 - 4920
lmandel@ca.ibm.com
----- Forwarded by Lawrence Mandel/Toronto/IBM on 11/13/2006 10:08 PM 
-----

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

To
www-ws-desc@w3.org
cc

Subject
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 ). 

Import-0070 
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 ). 

QName-resolution-1219000 
A Description component MUST NOT have such broken references. 

Types-1300000 
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. 

Import-0071 
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]. 

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


Thanks, 

Lawrence Mandel

Software Developer
IBM Rational Software
Phone: 905 - 413 - 3814   Fax: 905 - 413 - 4920
lmandel@ca.ibm.com