Updated 8.23.2006 at 11:02 to insert "DRAFT" into the post title, and add the following clarifying note:
The linked document is a "work in progress", and not (yet) an
official RFI. In other words, please review the RFI for content
(additions, changes, deletions), not for submitting a response. Thanks.
[The original post starts here]
The Object Management Group’s SOA SIG is looking for community (practitioner, vendor, researcher, observer) feedback on a draft request for information (RFI) on event-driven architecture (EDA) and its relationship with service-oriented architecture (SOA) & business-process management (BPM).
Here’s the RFI Summary:
The EDA Sub-group of the OMG SOA SIG seeks information from members of the EDA, BPM and SOA community as well as anyone interested in promoting standards in this area. Requested information will be evaluated by the EDA Sub-group, resulting in the development of Requests for Proposal(s) (RFP) for standardization of Event definition, relationship between EDA, BPM and SOA that will ultimately allow development of standards for Complete Life Cycle of Events -Ontology of Events, Sense and Respond Services, Events Metrics and processing of complex events. Please note that it is our intent to develop modeling standards for the EDA/SOA and EDA-Business Process interaction and provide standards for the implementation of that interaction as well.
For those (like me) not completely familiar with the OMG process, here’s the description of the RFI process taken from section 8 of The OMG Hitchhiker’s Guide, V7.3:
The intent of the Request for Information (RFI) is to gather information for the purpose of guiding a subgroup in its efforts to provide solutions to industry problems. The RFI is an optional process used by a subgroup to canvass a targeted industry segment for one or more of the following purposes:
- Soliciting assistance in identifying potential technology sources.
- Soliciting input to and validate a subgroup’s roadmap.
- Acquiring general or specific information about industry requirements.
Generally speaking, the RFI process determines which Request For Proposals (RFPs) get issued (and, based on negative feedback, which don’t) or influences the way a particular RFP is constructed.
There are no restrictions on who may receive or respond to a RFI. Both OMG Members and non-members can respond. RFI Responses may include information about relevant technologies, products, standards, research, requirements, and other guidance for the subgroup.
If you are interested in EDA (simple, stream, complex), take a look at the RFI and provide comments to Dr. Harsh Sharma. The plan calls for a final review of the RFI at the OMG’s September Technical Meeting in Anaheim.
I suppose this is where I say “I’m going to Disneyland!” I am a guest contributor (no $ exchanged either way) to the EDA subgroup of the OMG SOA SIG.