Mailing-List: contact general-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@incubator.apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Message-ID: <438F2B36.2080208@apache.org>
Date: Thu, 01 Dec 2005 08:56:22 -0800
From: Jeremy Boynes <jboynes@apache.org>
User-Agent: Mozilla Thunderbird 1.0.7-1.1.fc3 (X11/20050929)
MIME-Version: 1.0
To: general@incubator.apache.org
Subject: Re: [PROPOSAL] Incubate Tuscany SOA Project
References: <438DEBF2.1040203@apache.org>
	 <3842911A-0EA4-44CC-B82F-A1825D47AFDB@gbiv.com>
	 <32384427-9E5D-4AB4-AE5D-8B980DFACA7E@apache.org>
 <88f5d710512010525n248db98cvd3e465022ff69789@mail.gmail.com>
In-Reply-To: <88f5d710512010525n248db98cvd3e465022ff69789@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Paul Fremantle wrote:
> 
> Now - can someone give me an idea of how "open" the model is? In other words
> are the specifications behind Tuscany open to being modified? Will they be
> submitted to a standards body and in what timeframe? It would be good to
> know that Apache and in particular the committers can have input into the
> model and not just write code to a fixed specification that has no way for
> committers to improve except if they work for one of the publishing
> companies.
> 

The specifications themselves are not final and are open for suggestions
and improvements. Facilitating this was one reason they have been held
back from submission to a standards body at this time though the
intention is to do so in the future. When? Well, when they're ready.

On the other hand, Tuscany is not a "reference" implementation of the
specifications, constrained by the functionality they define. As an open
and independent community we are free to develop the features and
function we think most important. Portability and interoperability, as
provided by the specifications, are naturally very important and I think
our implementation will reflect that; however, innovation, flexibility
and responsiveness to users' needs are equally important and we have the
opportunity to provide those as well.

There are many things that we've thought of doing that are not covered
by the specifications; some of those are in the proposal, others aren't.
Implementing them, along with other people's new ideas, is one way in
which we hope to build the developer community.

--
Jeremy

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org