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

Assertions that are not assertions

From: Lawrence Mandel <lmandel@ca.ibm.com>
Date: Mon, 13 Nov 2006 21:53:51 -0500
To: www-ws-desc@w3.org
Message-ID: <OFA261B7B4.088E02A8-ON85257226.000D205B-85257226.000FEA9B@ca.ibm.com>
The following assertions do not appear to really be assertions at all. I 
suggest removing them from the assertions table and removing their 
assertion identifiers.

Description-1201000
WSDL 2.0 definitions are represented in XML by one or more WSDL 2.0 
Information Sets (Infosets), that is one or more description element 
information items. 

LM: I think this is too broad to be an assertion.


Description-1201005
Zero or more element information items amongst its [children], in order as 
follows: 

LM: I don't think this statement contains an assertion and if this is an 
assertion there are many other instances of this statement that should be 
added to the assertions table. 


Types-1300002
Specifically components that the schema imports via xs:import are NOT 
referenceable. 

LM: This assertion does not use the MUST NOT convention and I think is 
covered by the other schema import assertions although I think the text is 
still useful in the WSDL spec.


Types-1300003
Similarly, components defined in an inlined XML schema are NOT 
automatically referenceable within WSDL 2.0 document that imported (using 
wsdl:import ) the WSDL 2.0 document that inlines the schema (see 4.2 
Importing Descriptions for more details). 

LM: This assertion does not use the MUST NOT convention and I think is 
covered by the other schema and WSDL import assertions although I think 
the text is still useful in the WSDL spec.


Thanks,

Lawrence Mandel

Software Developer
IBM Rational Software
Phone: 905 - 413 - 3814   Fax: 905 - 413 - 4920
lmandel@ca.ibm.com
Received on Tuesday, 14 November 2006 02:54:20 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:58:42 GMT