RE: Duplicate assertions

Thank you for this comments.  The Working Group has resolved these issues as
follows:

 

Unless you let us know otherwise by the end of January, we will assume you
agree with the resolution of these issues.

 

Jonathan Marsh -  <http://www.wso2.com> http://www.wso2.com -
<http://auburnmarshes.spaces.live.com> http://auburnmarshes.spaces.live.com

 

 

  _____  

From: www-ws-desc-request@w3.org [mailto:www-ws-desc-request@w3.org] On
Behalf Of Lawrence Mandel
Sent: Monday, November 13, 2006 6:54 PM
To: www-ws-desc@w3.org
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
<http://dev.w3.org/cvsweb/%7Echeckout%7E/2002/ws/desc/wsdl20/wsdl20.html?con
tent-type=text/html;%20charset=utf-8#imports> 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). 

The Working Group tracked this comment as CR100 [1].  The Working Group
removed the assertion markup for Import-0001, see [2].

 

[1] http://www.w3.org/2002/ws/desc/5/cr-issues/issues.html#CR100 

[2]
http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl20/wsdl20.html?content-
type=text/html;%20charset=utf-8#Description_details 

 


2. QName-0002 
Furthermore, all QName references, whether to the same or to different
namespaces MUST resolve to components (see
<http://dev.w3.org/cvsweb/%7Echeckout%7E/2002/ws/desc/wsdl20/wsdl20.html?con
tent-type=text/html;%20charset=utf-8#qnameres> 2.17 QName resolution ). 

QName-resolution-1219000 
A Description
<http://dev.w3.org/cvsweb/%7Echeckout%7E/2002/ws/desc/wsdl20/wsdl20.html#com
ponent-Description>  component MUST NOT have such broken references. 

Types-1300000 
Every QName reference MUST resolve (see
<http://dev.w3.org/cvsweb/%7Echeckout%7E/2002/ws/desc/wsdl20/wsdl20.html?con
tent-type=text/html;%20charset=utf-8#qnameres> 2.17 QName resolution). 

The Working Group tracked this comment as CR101 [3].  The Working Group
removed the assertion markup from QName-0002 and Types-1300000, see [4, 5].

 

[3] http://www.w3.org/2002/ws/desc/5/cr-issues/issues.html#CR101  

[4]
http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl20/wsdl20.html?content-
type=text/html;%20charset=utf-8#Description_details 

[5]
http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl20/wsdl20.html?content-
type=text/html;%20charset=utf-8#schemaLocation-attribute

 

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

Import-0071 
 
<http://dev.w3.org/cvsweb/%7Echeckout%7E/2002/ws/desc/wsdl20/wsdl20.html?con
tent-type=text/html;%20charset=utf-8#Import-0071> This value MUST NOT match
the actual value of targetNamespace attribute information item in the
enclosing WSDL 2.0 document. 



 

The Working Group tracked this comment as CR102 [6].  The Working Group
removed the assertion markup from Import-0003 and rewrote the assertion to
avoid talking about imported components, see [7].

 

[6] http://www.w3.org/2002/ws/desc/5/cr-issues/issues.html#CR102   

[7]
http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl20/wsdl20.html?content-
type=text/html;%20charset=utf-8#Description_XMLRep


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 [
<http://dev.w3.org/cvsweb/%7Echeckout%7E/2002/ws/desc/wsdl20/wsdl20.html?con
tent-type=text/html;%20charset=utf-8#XMLSchemaP2> XML Schema: Datatypes]. 

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

The Working Group tracked this comment as CR103 [8].  The Working Group
removed the assertion markup from Types-1300001 and reworded it into a note,
added a reference to Schema-0016 (currently broken, but Arthur has been
notified), and additionally moved the last sentence of 3.1.1.2 to 3.1.2, see
[9, 10].

 

[8] http://www.w3.org/2002/ws/desc/5/cr-issues/issues.html#CR103    

[9]
http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl20/wsdl20.html?content-
type=text/html;%20charset=utf-8#schemaLocation-attribute

[10]
http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl20/wsdl20.html?content-
type=text/html;%20charset=utf-8#inlining-xsd

 


Thanks, 

Lawrence Mandel

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