W3C home > Mailing lists > Public > www-ws-desc@w3.org > March 2005

Re: Why do we have a component model?

From: Bijan Parsia <bparsia@isr.umd.edu>
Date: Mon, 7 Mar 2005 08:49:48 -0500
Message-Id: <C535D889-8F0F-11D9-9822-0003936A0B26@isr.umd.edu>
Cc: www-ws-desc@w3.org, Anish Karmarkar <Anish.Karmarkar@oracle.com>
To: Jean-Jacques Moreau <jean-jacques.moreau@crf.canon.fr>

On Mar 7, 2005, at 4:01 AM, Jean-Jacques Moreau wrote:

> The main justification for the component model I can remember is that 
> it cleanly deals with import/include, i.e. it extends the Infoset 
> across files. I'm sure they are others.

Yes, this was explained at the F2F. I kinda sorta knew this but forgot. 
One possible course of action is to document these justifications so 
that people coming to the spec cold understand *why* the component 
model is there.

> I too am quite worried by the complexity of the current spec, not just 
> as the editor.

It is unclear at the moment (to me) if it is possible to reduce the 
complexity of the spec without reducing the complexity of WSDL 2.0 
itself.

Well, that's overstrong. I'm sure there are tweaks and such. But it's 
quite open whether moving away from the component model would *really* 
simplify the presentation all that much.

Cheers,
Bijan Parsia.
Received on Monday, 7 March 2005 13:49:46 GMT

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