Public Comment

[comment-form@oasis-open.org]

Comment from: james.boggs@verizon.net

Name:  James D. Boggs
Title: Associate
Organization: Booz Allen Hamilton
Regarding Specification: Reference Model for SOA, 10 Feb 2006

Line 456, The statement that service orchestration is not "strictly part of SOA" as a reason for not addressing orchectration is not a strong reason; having the extent of the process model not fully defined as stated earlier in the paragraph is OK.  Do not weaken that argument. Furthermore, ISO 19119, Clause 7.3.5 provides good input for the process model by addressing three general types of service architecture patterns for orchestration or chaining.  I recommend that this reference be considered during completion of the OASIS SOA RM process model. First, a user-defined chain in which the human manages the workflow is called transparent. Second, worklfow-managed chaining in which the human requests a WF manager package (or service) to control the chain, but also provide awareness of progress is called translucent. Third, chaining in which the user invokes a service with no awareness of progress is called opaque and offers the same limited knowledge of the service chain that the OASIS RM line 273 defines for a service. Tying ISO 19119 and other standards to the process model will promote chaining and has the possibility of greater savings for industry and government contemplating SOA.