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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
