W3C home > Mailing lists > Public > public-ws-desc-comments@w3.org > August 2006

[selectors-api] Normative/Informative dependencies

From: <karl@w3.org>
Date: Wed, 09 Aug 2006 03:33:50 -0000
To: public-ws-desc-comments@w3.org
Message-Id: <20060809033403.A9B2D4F574@homer.w3.org>

Hi,
This is a QA Review comment for "Web Services Description Language (WSDL) Version 2.0: RDF Mapping"
http://www.w3.org/TR/2006/WD-wsdl20-rdf-20060518/
2006-03-27
Last Call WD

About http://www.w3.org/TR/2006/WD-wsdl20-rdf-20060518/#description

	In 2.1.1 Description class, the prose says
	
	"The core WSDL specification does not consider the case of combining multiple independent WSDL documents and it doesn't mandate that independent documents describe consistently components with the same name. This is, however, an assumption when combining multiple WSDL documents in the RDF representation. See more on this point in section 4.2."

	is it really an assumption or a normative requirement. Section 4 of the document being informative. Will it breach interoperability if the assumption is not met. If it's a requirement necessary for interoperability the group is better to define it normatively. And/or if the "assumption" is not met to define a mechanism achieving the same results.
	


-- 
Karl Dubost - http://www.w3.org/People/karl/
W3C Conformance Manager, QA Activity Lead
   QA Weblog - http://www.w3.org/QA/
      *** Be Strict To Be Cool ***
Received on Wednesday, 9 August 2006 03:34:11 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:20:32 GMT