RECOMMENDATION: Stand up new SC

Mike and Martin,

Given the growing discussion thread surrounding issue ASSEMBLY 80 on creating an event processing model for SCA, and the more recent issues regarding adding SCA support for pub/sub in general, may I recommend that you stand up a new Subcommittee (SC) under the auspices of the SCA-Assembly TC. This is very easy to do under the OASIS framework. It has the advantage of being able to appoint an SC chair (or co-chairs), create a separate Kavi space for capturing SC artifacts, meeting announcements, etc., and, perhaps most importantly, any recommended technical products emerging from the SC must still pass a full vote of the parent TC; in this case, the SCA-Assembly TC. Anish, Martin, and others have done an outstanding job in crafting candidate solutions to address issue ASSEMBLY 80; however, there is clearly a lot of work still to do and dissension still remains on a solution set. In other words, a final solution that we can all live with does not appear imminent; hence, the need to stand up a separate SC. Just a suggestion.

Now, even if we were to standup a new SC, my personal feeling is that every effort should be made to get the current (non-eventing) SCA-Assembly spec ratified as an OASIS standard at the very earliest possible date. It is only when these specs become formal industry standards that we will be able to enforce its conformance criteria with the ultimate goal of full interoperability of the solutions that implement these specs.

Note that I will be on travel next week and unable to attend both the TC meeting on Tue and supporting eventing discussion on Wed so if this issue comes up, I won’t be available to address any questions regarding standing up an SC. Nevertheless, it’s very easy to do and our friends from the OASIS staff can assist us. We’ve done it readily on other TCs I serve.

Regards…

- Jeff E.

sca-assembly message