| Re: R: [soa-iwg] IWG media launch on April 22 |
I see we're to quoting the process document again.I would assert that any working group that wants to call itself 'open' should actually be 'open'. If that means fixing the process document, then I suggest it be done.
Scott Oliver Wolf wrote:
Scott,I think the main issue here is that AFAIK Composent, Inc. is not an Eclipse member company. The Eclipse Industry Working Group Process [1] document states in section 2 that"[...] Participation in IWGs is only open to certain Members of the Eclipse Foundation. [...]"As I understand this statement, membership in Eclipse is a prerequisite for participation in IWGs. You, Scott, as a committer on the ECF project are definitely a member of the Foundation and you're therefore free to participate in any IWG as an individual. Your company, Composent, Inc., is not a member.It might look like nitpicking, but the rationale behind this arguably strict rule is that the Foundation wants to encourage organizations that intend to participate in IWGs and benefit from the joint marketing effort to become full members and -- ultimately -- help fund the Foundations's work with their membership fees.Oliver [1] http://www.eclipse.org/org/industry-workgroups/industry_wg_process.phpAm 16.04.2010 um 16:10 schrieb Scott Lewis:Hi Zsolt, Yeah I think it is nitpicking Zsolt. Is not the working group open to organizations as well as individuals? Can organizations participate in an open organization? Then why cannot Composent be considered a participant? Scott Zsolt Beothy-Elo wrote:Scott,perhaps it seems to be a bit nitpicking, but Composent, Inc. is not a member of the IWG, but you as an individial commiter. Therefore I would disapprove off adding dismiss to add Composent, Inc..Zsolt Am 14.04.2010 um 23:05 schrieb Scott Lewis:Ian, In existing draft, it says this as a bullet item: * REST and SOAP support for remote services, based on the OSGi 4.2 remote services specification. I suggest that this be broken into two bullet items: 1) Support for the OSGi 4.2 remote services specification 2) REST and SOAP support for OSGi remote services Before the ECF contribution, the SOA package did not have support for the OSGi 4.2 remote services specification, and that is major technology/interoperability addition by itself. The REST and SOAP support for remote services extends things significantly...in the direction of REST-based and SOAP-based remote services. I think it would be better not to conflate these two things (i.e. standards-based support remote services in general, and specific implementation styles/approaches for remote services). Also...you can add Composent, Inc. to the list of participating companies. If you want a quote from me then I can provide one. Scott Ian Skerrett wrote:All, Thanks for the feedback. Attached is a draft version of a proposedrelease. Please let me know your comments.I would like to get quotes from each participating company. I did asample quote for Engineering based on some of their input and would behappy to work with the other participants. Marc, I did not include your suggestions since you weren't sure if itwas okay to talk about them. If people think it makes sense I can addsomething.The goal is to announce this next week at the SOA Day in Germany. This really doesn't give much time. Will it be possible to getquotes and feedback before the end of this week? Ian On 4/14/2010 2:55 AM, majori wrote:Hi Ian,I just wanted to just wanted to add to the mail of Marc that EngineeringGroup participates also with two new project (accepted)-eBAM (extended Business Activity Monitoring) project that aims to realize a monitoring platform supporting the performance and management analysis of external systems. The goal of eBAM is to provide both build-time and runtimetools for a BAM platform. eBAM start from SpagoBI know how, The only entirely Open Source Business Intelligence suite.-eBPM, (extended Business Process Management) based on contribution of theOW2 project Spagic (free/open source platform for the governance ofmiddleware services and the development of SOA applications). eBPM aims at the realization of a complete BPM solution for OSGi. The project will alsoprovide UI and runtime support, to be able to deploy and manage OSGi services, in a declarative way, leveraging the capabilities of OSGi declarative services.With SpagoBI and Spagic, Enginnering group has develop many project indifferent areas: government, finance, industry, healthcare. Regards, Antonio -----Messaggio originale-----Da: soa-iwg-bounces@xxxxxxxxxxx <mailto:soa-iwg-bounces@xxxxxxxxxxx> [mailto:soa-iwg-bounces@xxxxxxxxxxx] Perconto di Marc Dutoo Inviato: martedì 13 aprile 2010 18.03 A: SOA Industry Working Group Oggetto: Re: [soa-iwg] IWG media launch on April 22 Hi Ian As fare as I know (though I'm not a member of the IWG) : About JWT :* Open Wide has a JWT reference (integrated in the OW2 Scarbo SCA BPM platform) in production since February, but maybe our client will find it abit too early to talk about it* among mailing list participants, Mastek Ltd has built a product on topof JWT, I can ask them about it (I planned to anyway)Engineering has an STP IM reference, as said in the Mangrove article (Kudosto Adrian BTW). What about Obeo and the SCA Editor ?Going further, it would be a good idea to gather all these references in adedicated part of the website(s). What do you think ? Regards, Marc Ian Skerrett a écrit :Zsolt, Thanks for posting these. I think these are a good start, seecomments below, but I think we need to have some technology oriented features. What is new/exciting/different that will result from theIWG? Why is the IWG different from other SOA solutions? On 4/13/2010 9:50 AM, Zsolt Beothy-Elo wrote:Here are SOPERAS findings of the of the top 5 new/exciting things that will be accomplished by the IWG: * The foundation of the new IWG shows the strong interest of the industry in the further server-side development of Eclipse technologies * The foundation of the IWG is also a strong signal that SOA technologies and projects within Eclipse have reached a good level of maturity. Because of this, the industry now is interested in using Eclipse technologies in own productsDo we have examples of companies using the IWG technology for their products. I am assuming Sopera has a product available, can we reference it. Are there other companies/products?* * Through the foundation of the Eclipse SOA IWG, the goal of the creation of a fully functional, common SOA platform on the basis of Eclipse will be reached much faster * The interoperability between the platforms of the IWG members will be further strengthenedCan you explain this more or give examples of interoperability? ---------------------------------------------------------------------- -- _______________________________________________ soa-iwg mailing list soa-iwg@xxxxxxxxxxx <mailto:soa-iwg@xxxxxxxxxxx> https://dev.eclipse.org/mailman/listinfo/soa-iwg_______________________________________________ soa-iwg mailing list soa-iwg@xxxxxxxxxxx <mailto:soa-iwg@xxxxxxxxxxx> https://dev.eclipse.org/mailman/listinfo/soa-iwg _______________________________________________ soa-iwg mailing list soa-iwg@xxxxxxxxxxx <mailto:soa-iwg@xxxxxxxxxxx> https://dev.eclipse.org/mailman/listinfo/soa-iwg-- Ian Skerrett Director of Marketing Eclipse Foundation Tel: 613-224-9461 ext 227Blog: ianskerrett.wordpress.com <http://ianskerrett.wordpress.com> <http://ianskerrett.wordpress.com/>Twitter: IanSkerrett <http://twitter.com/IanSkerrett> Plan to attend EclipseCon 2010 <http://www.eclipsecon.org/2010/>, March 22-25 ------------------------------------------------------------------------ _______________________________________________ soa-iwg mailing list soa-iwg@xxxxxxxxxxx <mailto:soa-iwg@xxxxxxxxxxx> https://dev.eclipse.org/mailman/listinfo/soa-iwg_______________________________________________ soa-iwg mailing list soa-iwg@xxxxxxxxxxx <mailto:soa-iwg@xxxxxxxxxxx> https://dev.eclipse.org/mailman/listinfo/soa-iwg_______________________________________________ soa-iwg mailing list soa-iwg@xxxxxxxxxxx <mailto:soa-iwg@xxxxxxxxxxx> https://dev.eclipse.org/mailman/listinfo/soa-iwg_______________________________________________ soa-iwg mailing list soa-iwg@xxxxxxxxxxx <mailto:soa-iwg@xxxxxxxxxxx> https://dev.eclipse.org/mailman/listinfo/soa-iwgOliver Wolf Tel.: +49 228-182 19059 Fax: +49 228-182 19193 Mobil: +49 160-98931313 oliver.wolf@xxxxxxxxx <mailto:oliver.wolf@xxxxxxxxx> SOPERA GmbH - Open Source SOASubscription Services, Support & Maintenance, Training, Technical SOA Consulting & Customized Development www.sopera.de <http://www.sopera.de/> SOPERA GmbH · Geschäftsführer: Dr. Ricco Deutscher, Harald WeimerSträßchensweg 10 · 53113 Bonn · Handelsregister: Bonn HRB 15336 Hohenlindnerstraße 11b · 85622 MünchenVertraulichkeitshinweis: Diese Nachricht und jeder übermittelte Anhang beinhaltet vertrauliche Informationen und ist nur für die Personen oder das Unternehmen bestimmt, an welche sie tatsächlich gerichtet ist. Sollten Sie nicht der Bestimmungsempfänger sein, weisen wir Sie darauf hin, dass die Verbreitung, das (auch teilweise) Kopieren sowie der Gebrauch der empfangenen E-Mail und der darin enthaltenen Informationen gesetzlich verboten ist und gegebenenfalls Schadensersatzpflichten auslösen kann. Sollten Sie diese Nachricht aufgrund eines Übermittlungsfehlers erhalten haben, bitten wir Sie, den Sender unverzüglich hiervon in Kenntnis zu setzen.------------------------------------------------------------------------ _______________________________________________ soa-iwg mailing list soa-iwg@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/soa-iwg