Why do we have a component model? from Anish Karmarkar on 2005-03-04 (www-ws-desc@w3.org from March 2005)

From: Anish Karmarkar <Anish.Karmarkar@oracle.com>
Date: Fri, 04 Mar 2005 08:26:45 -0800
To: www-ws-desc@w3.org
Message-ID: <42288C45.3050205@oracle.com>

* Apologies for raising this issue at this stage *

I would like to understand why we have the component model in the spec? 
How and who does it help?

Currently we have the component model in section 2 (of part 1), Infoset 
mapping, pseudo-schema, Z-notation and the type of the properties are 
specified using XML Schema types. This makes it complex and hard to 
understand. Is there any advantage to this added complexity?

Infoset is abstract and therefore can be mapped to different 
serializations. Do we anticipate that the WSDL component model will be 
mapped to things other than Infoset. IOW, isn't specifying things in 
Infoset good enough?

-Anish
--

Received on Friday, 4 March 2005 16:30:32 UTC