[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [no subject]
From: Chiusano Joseph [mailto:chiusano_joseph@bah.com]
Sent: Sun 10/30/2005 3:17 PM
To: Goran Zugic; ebSOA OASIS TC
Subject: RE: [ebsoa] SOA Collaboration Semantics
Goran,
=20
Please keep in mind that you are working in an open process where people =
(like myself) provide feedback on submitted content, even if they have =
not read the entire document. Anyone in this process has the right to =
comment on any part of materials submitted before reading them in their =
entirety. I simply looked at a figure that was labeled to be a =
"high-level information model" for SOA, and noted the absence of what I =
believe (especially based on the work that is being done in the SOA-RM =
TC) is a fundamental piece. I am not required by OASIS policy to =
continue reading the entire document at that point before I provide =
feedback on my observation to a TC.
=20
I suggest that if you cannot donate something to OASIS and then abide by =
OASIS rules in evolving your donation, that you rescind it - and =
immediately.
=20
Joe
=20
________________________________
From: Goran Zugic [mailto:goran.zugic@semantion.com]
Sent: Sat 10/29/2005 8:09 PM
To: Chiusano Joseph; ebSOA OASIS TC
Subject: Re: [ebsoa] SOA Collaboration Semantics
Joe,
=20
This is how I view professionalism in this kind of communication:
=20
1. Do not criticize the content until you have not fully read it.
=20
2. When you criticize something always state your standpoint. Do not =
come up with a negative critique before you explain your position and =
have fully understood the other side's position. In order to achieve =
this, step one is a prerequisite. As you know, our solution is explained =
in three publicly available documents. You said you will clarify your =
viewpoints, I am looking forward to seeing them whenever they are =
ready.
=20
3. Whenever you ask for an answer, or try to find an answer with the =
help of others, be patient with the discussions until all positions are =
clear. Do not rush with critiques such as: "... I am still highly =
skeptical of their usefulness and value..." or "... I frankly don't see =
its value to this TC or standards work in general..." or "...it appears =
to me that the SOA IM was originally written as a process IM, and some =
text regarding "service" was added in as an afterthought ...". Arbitrary =
critiques are not hard to produce, in comparison to years of hard work =
and years of professional experience; both of which were needed to =
produce the specification framework that the ebSOA TC is working on =
right now.=20
=20
When I joined the ebSOA TC back in March of this year, the only ebSOA TC =
architectural specification document (dated August 2004) that was =
present, was a high level abstract draft that you also contributed to. =
You left this in its beginning stage, and I have not seen any further =
contributions since. Coneveniently you reappeared as soon as the =
FERA-based SOA submission was completed, and your intentions were =
questionable at best. What I want to know, is wether you would like to =
help the process, or hindered it like you have been doing thus far. =20
=20
The way I see this, is that I will not waste my time with the chicken =
and egg scenario with endless discussions about SOA, services, service =
orchestration, choreography, and many others. However, we can further =
our discussions, as long as constructive exchanges based on our clearly =
stated positions, and most importantly, the respect for each others work =
are present. Counter-productive arguements without merit, which you have =
displayed, serve as a barrier to our communication. =20
=20
Assuming that we will have more positive and more constructive =
communication in the near future, I look forward to hearing from you =
about your position, views and outlooks, on SOA and all aspects =
surrounding it. =20
=20
Goran
=20
=20
----- Original Message -----=20
From: Chiusano Joseph <mailto:chiusano_joseph@bah.com> =20
To: goran.zugic@semantion.com ; ebSOA OASIS TC =
<mailto:ebsoa@lists.oasis-open.org> =20
Sent: Wednesday, October 26, 2005 5:02 PM
Subject: RE: [ebsoa] SOA Collaboration Semantics
Goran,
=20
I don't believe it is very professional for you to assume what I am =
interested in regarding SOA. In fact, your assumption was quite =
innaccurate.
=20
I will clarify that I am interested in the terminology, the purpose, =
the business process improvements it can provide, and many other =
aspects.
=20
I thank you in advance for updating your high-level information model =
to accurately reflect your stated intent for these specifications. I am =
still highly skeptical of their usefulness and value, but time and =
market will tell.
=20
Joe
=20
Kind Regards,
Joseph Chiusano
Associate
Booz Allen Hamilton
=20
700 13th St. NW
Washington, DC 20005
O: 202-508-6514 =20
C: 202-251-0731
Visit us online@ http://www.boozallen.com <http://www.boozallen.com/>=20
=20
________________________________
From: goran.zugic@semantion.com [mailto:goran.zugic@semantion.com]=20
Sent: Wednesday, October 26, 2005 4:58 PM
To: Chiusano Joseph; Goran Zugic; ebSOA OASIS TC
Subject: Re: [ebsoa] SOA Collaboration Semantics
=09
=09
Joe,
=20
Thank you for being so frank in sharing your opinion. Looks like you =
are interested in terminology of the SOA, not in the purpose of it, or =
in the business process improvements that it can provide. The proposed =
framework deals with ontology, information models, run time architecture =
and semantics for SOA and its implementations, the missing glue areas in =
current standard specifications. When you read the proposed documents in =
more details, you will get answers to all your questions.=20
=20
Fore example, Service entity is explicitly defined in SOA IM. =
Unfortunately your conclusions have been made mostly based on the only =
figure in the SOA IM document, "Figure 1 - SOA Information Model (High =
Level)", yes it says "High Level", which does not graphically include =
Service entity. If you really read the document you would easily find =
out that the Service entity is defined in SOA IM and that it is one of =
the the core SOA IM entities used to support key business process =
entities: activities, decisions and events. However, in our next =
release, we will graphically add, for example, the Service entity to the =
SOA IM high-level figure to help you and similar readers whose focus is =
on the pictures not the content to better understand our specs and =
solution.=20
=20
Few more words about reference and run-time architecture. As I =
mentioned in my previous note FERA reference architecture has been =
created based on many collaborative (business) process use cases and =
installations. The run-time SOA is based on it and SOA Collaboration =
Semantics defines all its architectural components' protocols, =
interfaces and methods. That is how you provide vendors with specs that =
can be used to develop plugable architectural components in a fully =
interoperable way. How you are going to implement it, what technology =
will be used and everything else that comes with it is completely =
independent of this specs.
=20
Analogy with sports. The formalism applied to the abstract definition =
of the ball (service) out of the game (context) does not make too much =
sense. We can debate if the ball should be defined as "soccer ball" or =
"football" forever, and no-one would win that debate. It does not matter =
if we follow the ontology of the game. Players will say "pass me the =
ball", or "share that orange, you hog", and everyone else will =
understand that request given the game being played at the moment.=20
Smart people defined the purpose of services and SOA long time ago but =
nobody has provided the way how the entire SOA should work. We are the =
first group that has created the framework for this kind of the SOA =
specs. More and more people and organizations and even some new OASIS =
TCs starting to realize the importance of the SOA IM and SOA semantics =
which are first introduced by us as the key elements for the complete =
support for business process modeling, deployment and execution in SOA.=20
=09
Goran
=20
-----Original Message-----
From: Chiusano Joseph [mailto:chiusano_joseph@bah.com]
Sent: Wednesday, October 26, 2005 11:04 AM
To: 'Goran Zugic', 'ebSOA OASIS TC'
Subject: RE: [ebsoa] SOA Collaboration Semantics
=09
=09
Please see comments below, marked with [JMC].
=20
Kind Regards,
Joseph Chiusano
Associate
Booz Allen Hamilton
=20
700 13th St. NW
Washington, DC 20005
O: 202-508-6514 =20
C: 202-251-0731
Visit us online@ http://www.boozallen.com <http://www.boozallen.com/> =
=20
=09
=09
________________________________
From: Goran Zugic [mailto:goran.zugic@semantion.com]=20
Sent: Tuesday, October 25, 2005 10:58 PM
To: Chiusano Joseph; ebSOA OASIS TC
Subject: Re: [ebsoa] SOA Collaboration Semantics
=09
=09
Joe,
=20
Thanks for your feedback. These are my answers:
=20
- The run-time architecture is based on analysis of over 130 =
collaborative installations. It is based on FERA which classifies and =
categorizes capabilities required to support all of the use cases =
analyzed. The components are actually reference functional modules that =
have specified functions and interfaces. Our run time SOA is based on =
that model and each component has a well defined role and interface to =
communicate with other components to support the collaborative process.
=20
=09
[JMC] Thank you. The information you provided above is valuable to =
understand the background and history of the run-time architecture. I =
should also emphasize that my original question was: "Since the run-time =
architecture is greatly concrete, is it intended that products be based =
on it? Is it intended for exemplary purposes? Other? ". =20
=20
- SOA IM is based on the process definition in FERA that requires =
certain level of specificity of the process detail. True, FERA does not =
require QoS details, but it provides a robust security policy model. =20
=20
=09
[JMC] It seems to me that if the security policy model is robust as =
you say, it would be reflected in the SOA IM hierarchy shown in Figure 1 =
of the SOA IM document. Why would it not be (sorry, I don't understand).
=20
The IM is derived from FERA process characteristics and there are =
additional data elements required for the run time semantics that are =
used for quality, escalation, monitoring and other administrative =
aspects of run time execution. The SOA IM contains sufficient level of =
detail to extract the semantics and to execute it over the run time SOA. =
True it is a process based model, and that is intentional, because that =
maintains the fidelity of business requirements throughout the entire =
deployment. In this framework, it is less important to define what is a =
service then to satisfy all basic principles of SOA. =20
=20
=09
[JMC] How can one "satisfy all basic principles of SOA" if the most =
fundamental concept of SOA - "service" - is not defined?
=20
That is why it is an SOA IM. =20
=20
=09
[JMC] Given that "Service" does not appear in the IM hierarchy, I =
would asser that it is *not* a SOA IM, and that portraying it as such is =
- a best - a huge stretch.
=20
However, the Service entity is defined in Section 2.1.35 in SOA IM =
document. =20
=20
=09
[JMC] Great - why not put it in the IM hierarchy?
=20
Hence, you see activities, decisions, events, roles, rules and =
metrics as key entities. A service can therefore be any activity, or a =
decision that has defined inputs and outputs, conditions for its =
invocation, metrics for its performance, rules for its execution, matrix =
with the input processing logic and few other entities in the model. =20
=20
=09
[JMC] Great - then that should be reflected in the IM hierarchy, =
with "Service" being related to all of these, IMHO.
=20
Hence the entire model in fact defines services, their =
orchestration, =20
=20
=09
[JMC] Not all SOA instances involve orchestration - that is a =
feature (aspect) that is determined according to business need. So =
building in orchestration "natively", IMHO, makes this an orchestration =
IM (or a process IM), not a SOA IM.
=20
their business rules and other aspects required for SOA definition, =
deployment, maintenance and continuous operational support. The entire =
IM and the architecture is an SOA based on the principles of service =
orientation. =20
=20
=09
[JMC] I believe that it cannot be this, since "Service" is not even =
included in the IM hierarchy, much less as a central focus.
=20
Just like in the sport of soccer nothing is really called soccer, =
but everything else defines the game, players, referees, goals, =
spectators, ball, pitch, etc.
=20
=09
[JMC] Yes, but there are fundamental components you mentioned, such =
as a soccer ball. How can this be SOA (soccer) without depicting a =
soccer ball (Service)?
=20
=09
I am not implying anything more than I am saying here, but it =
appears to me that the SOA IM was originally written as a process IM, =
and some text regarding "service" was added in as an afterthought (just =
my opinion).
=20
Given its current state, I frankly don't see its value to this TC or =
standards work in general.
=20
Thanks,
Joe
=20
Regards,
Goran
----- Original Message -----=20
From: Chiusano Joseph <mailto:chiusano_joseph@bah.com> =20
To: Goran Zugic <mailto:goran.zugic@semantion.com> ; ebSOA OASIS =
TC <mailto:ebsoa@lists.oasis-open.org> =20
Sent: Tuesday, October 25, 2005 4:10 PM
Subject: RE: [ebsoa] SOA Collaboration Semantics
=09
=09
Goran,
=20
Thanks for sending these documents - it's clear that a great deal =
of work has gone into them.
=20
I have a few questions, please:
=20
Run-Time SOA: I get the notion of a reference architecture as shown =
in Figure 1 on p.3. Having said that, I would expect that any run-time =
(concrete) architecture that is depicted as being based on the reference =
architecture is merely for exemplary purposes, yet the run-time =
architecture is simply presented without any indication of its purpose. =
Since the run-time architecture is greatly concrete, is it intended that =
products be based on it? Is it intended for exemplary purposes? Other?
=20
SOA Information Model: Though this is called a "SOA" information =
model, this document looks more to me like a "Process Information Model" =
that is actually independent of SOA (that is, I did not see anything =
that restricted it to SOA). In fact, in order to call something a "SOA" =
information model, I would assert that there are several other areas =
that would need to be incorporated beyond processes - e.g. security, =
policy, QoS, etc. Even considering the process perspective, there is =
nothing that I see in this information model that speaks distinctly to a =
service-oriented paradigm - in fact, figure 1 (p.24) does not even have =
a "Service" concept. What is the intended use of this document for =
ebSOA?
=20
Thanks,
Joe
=20
Joseph Chiusano
Associate
Booz Allen Hamilton
=20
700 13th St. NW
Washington, DC 20005
O: 202-508-6514 =20
C: 202-251-0731
Visit us online@ http://www.boozallen.com =
<http://www.boozallen.com/>=20
=20
________________________________
From: Goran Zugic [mailto:goran.zugic@semantion.com]=20
Sent: Friday, October 21, 2005 2:21 AM
To: 'ebSOA OASIS TC'
Subject: [ebsoa] SOA Collaboration Semantics
=09
=09
Hello ebSOA TC,
=20
Semantion is pleased to announce the completion of its FERA-based =
SOA contribution to ebSOA TC.=20
=20
The SOA Collaboration Semantics document=20
=20
http://www.semantion.com/specs/soa/SOA_CS_V0.1.doc
=20
contains FERA-based SOA semantics specification that together with =
two previously submitted documents, Run-time SOA and SOA Information =
Model, represent Semantion's SOA specification framework.
=20
The new releases of the Run-time SOA document and the SOA =
Information Model document are available at
=20
http://www.semantion.com/specs/soa/SOA_IM_V0.2.doc
=20
http://www.semantion.com/specs/soa/Run-time_SOA_V0.2.doc
=20
These documents should be reviewed in the following order:
=20
- Run-time SOA
- SOA Information Model
- SOA Collaboration Semantics
=20
Please let me know if you have any questions or need more =
information regarding the submitted documents.
=20
Regards,
Goran Zugic
Chief Architect
Semantion Inc.
http://www.semantion.com <http://mail.semantion.com/loading.htm#>=20
416-995-7532
------_=_NextPart_001_01C5DD90.5C7997A5
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">=0A=
=0A=
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">=0A=
<HTML ><HEAD>=0A=
=0A=
<META content=3D"MSHTML 6.00.2900.2769" name=3DGENERATOR>=0A=
<STYLE></STYLE>=0A=
</HEAD>=0A=
<BODY bgColor=3D#ffffff>=0A=
<DIV id=3DidOWAReplyText57534 dir=3Dltr>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 size=3D2>=0A=
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT size=3D2><FONT =0A=
face=3D"Times New Roman"><Quote></FONT></FONT></P>=0A=
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT size=3D2><FONT =0A=
face=3D"Times New Roman">3. Whenever you ask for an answer, or try =
to =0A=
find an answer with the help of others, be =
patient with =0A=
the discussions until all positions are clear. Do not rush with =0A=
critiques such as: "... I am still highly skeptical of their =0A=
usefulness and value..." or "... I frankly don't see its value to this =
TC or =0A=
standards work in general..." or "...it appears to me that the SOA IM =
was =0A=
originally written as a process IM, and some text regarding "service" =
was added =0A=
in as an afterthought ...".</FONT><FONT face=3DArial> </FONT><FONT =0A=
face=3D"Times New Roman">Arbitrary critiques are not hard to produce, in =0A=
comparison to years of hard work and years =
of professional =0A=
experience; both of which were needed to produce the =
specification =0A=
framework that the ebSOA TC is working on right now. </FONT></FONT></P>=0A=
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT face=3D"Times =
New Roman" =0A=
size=3D2></Quote></FONT></P>=0A=
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT =0A=
face=3D"Times New Roman"></FONT> </P>=0A=
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT face=3D"Times =
New Roman">I =0A=
have been very patient with the discussions. I asked a question about =
how you =0A=
viewed the work being used in the future, and you did not respond to =
that =0A=
question. So my assessment at that point was that I was skeptical of the =0A=
usefulness and value of the work, because you were unable to articulate =
how it =0A=
would be used in the future. My response was based on your =
response.</FONT></P>=0A=
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT =0A=
face=3D"Times New Roman"></FONT> </P>=0A=
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT =0A=
face=3D"Times New Roman"><Quote></FONT></P>=0A=
<DIV class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT face=3D"Times =
New Roman" =0A=
size=3D2>When I joined the ebSOA TC back in March of this =
year, the only =0A=
ebSOA TC architectural specification document (dated August =
2004) that =0A=
was present, was a high level abstract draft that you also =
contributed to. =0A=
You left this in its beginning stage, and I have not seen any =
further =0A=
contributions since. Coneveniently you reappeared as soon as the =
FERA-based =0A=
SOA submission was completed, and your intentions were =
questionable at =0A=
best. What I want to know, is wether you would like to help the =
process, or =0A=
hindered it like you have been doing thus =0A=
far. </FONT> </DIV></FONT></DIV></DIV>=0A=
<DIV dir=3Dltr></Quote></DIV>=0A=
<DIV dir=3Dltr><BR>I never contributed to such a draft, and I wish you =
would =0A=
please make sure your facts are straight before making such assertions. =0A=
Furthermore, I (and any OASIS member) have the right to contribute to =
and leave =0A=
any OASIS TC (and then re-join) according to OASIS processes, without =
any other =0A=
OASIS member really having anything justified to say about it.</DIV>=0A=
<DIV dir=3Dltr> </DIV>=0A=
<DIV dir=3Dltr>From this point on I will not respond to any of your =
comments, and =0A=
urge you to see someone within OASIS if you have issues with OASIS =
members =0A=
contributing to the open OASIS process.</DIV>=0A=
<DIV dir=3Dltr> </DIV>=0A=
<DIV dir=3Dltr>Joe</DIV>=0A=
<DIV dir=3Dltr>=0A=
<HR tabIndex=3D-1>=0A=
</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DTahoma size=3D2><B>From:</B> Chiusano Joseph =0A=
[mailto:chiusano_joseph@bah.com]<BR><B>Sent:</B> Sun 10/30/2005 3:17 =0A=
PM<BR><B>To:</B> Goran Zugic; ebSOA OASIS TC<BR><B>Subject:</B> RE: =
[ebsoa] SOA =0A=
Collaboration Semantics<BR></FONT><BR></DIV>=0A=
<DIV>=0A=
<DIV id=3DidOWAReplyText2040 dir=3Dltr>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 =
size=3D2>Goran,</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT> </DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Please keep in mind that you =
are working in =0A=
an open process where people (like myself) provide feedback on submitted =0A=
content, even if they have not read the entire document. Anyone in this =
process =0A=
has the right to comment on any part of materials submitted before =
reading them =0A=
in their entirety. I simply looked at a figure that was labeled to be a =0A=
"high-level information model" for SOA, and noted the absence of what I =
believe =0A=
(especially based on the work that is being done in the SOA-RM TC) is a =0A=
fundamental piece. I am not required by OASIS policy to continue reading =
the =0A=
entire document at that point before I provide feedback on my =
observation to a =0A=
TC.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT> </DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>I suggest that if you cannot =
donate =0A=
something to OASIS and then abide by OASIS rules in evolving your =
donation, that =0A=
you rescind it - and immediately.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT> </DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Joe</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT><BR> </DIV>=0A=
<DIV dir=3Dltr>=0A=
<HR tabIndex=3D-1>=0A=
</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DTahoma size=3D2><B>From:</B> Goran Zugic =0A=
[mailto:goran.zugic@semantion.com]<BR><B>Sent:</B> Sat 10/29/2005 8:09 =0A=
PM<BR><B>To:</B> Chiusano Joseph; ebSOA OASIS TC<BR><B>Subject:</B> Re: =
[ebsoa] =0A=
SOA Collaboration Semantics<BR></FONT><BR></DIV></DIV>=0A=
<DIV>=0A=
<DIV>=0A=
<DIV><FONT face=3DArial>=0A=
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT face=3D"Times =
New Roman" =0A=
size=3D2>Joe,</FONT></P>=0A=
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT face=3D"Times =
New Roman" =0A=
size=3D2></FONT> </P>=0A=
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT face=3D"Times =
New Roman" =0A=
size=3D2>This is how I view<SPAN> </SPAN>professionalism in =
this kind of =0A=
communication:</FONT></P>=0A=
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT face=3D"Times =
New Roman" =0A=
size=3D2></FONT> </P>=0A=
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT face=3D"Times =
New Roman" =0A=
size=3D2>1. Do not criticize the content until you have not =
fully read =0A=
it.</FONT></P>=0A=
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT face=3D"Times =
New Roman" =0A=
size=3D2></FONT> </P>=0A=
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT size=3D2><FONT =0A=
face=3D"Times New Roman">2. When you criticize something =
always state your =0A=
standpoint. Do not come up with a negative critique </FONT><FONT =0A=
face=3D"Times New Roman">before you explain your position and =
have fully =0A=
</FONT><FONT face=3D"Times New Roman">understood the other side's =
position. =0A=
In order to achieve this, step one is a prerequisite</FONT><FONT =0A=
face=3D"Times New Roman">. As you know, </FONT><FONT =0A=
face=3D"Times New Roman">our solution is explained in three =
publicly =0A=
</FONT><FONT face=3D"Times New Roman">available documents. You said you =
will =0A=
clarify your viewpoints,</FONT><FONT face=3D"Times New Roman"> I =
am looking =0A=
forward to seeing them whenever </FONT><FONT =0A=
face=3D"Times New Roman">they are ready.</FONT></FONT></P>=0A=
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT face=3D"Times =
New Roman" =0A=
size=3D2></FONT> </P>=0A=
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT size=3D2><FONT =0A=
face=3D"Times New Roman">3. Whenever you ask for an answer, or try =
to =0A=
find an answer with the help of others, be =
patient with =0A=
the discussions until all positions are clear. Do not rush with =0A=
critiques such as: "... I am still highly skeptical of their =0A=
usefulness and value..." or "... I frankly don't see its value to this =
TC or =0A=
standards work in general..." or "...it appears to me that the SOA IM =
was =0A=
originally written as a process IM, and some text regarding "service" =
was added =0A=
in as an afterthought ...".</FONT><FONT face=3DArial> </FONT><FONT =0A=
face=3D"Times New Roman">Arbitrary critiques are not hard to produce, in =0A=
comparison to years of hard work and years =
of professional =0A=
experience; both of which were needed to produce the =
specification =0A=
framework that the ebSOA TC is working on right now. </FONT></FONT></P>=0A=
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT face=3D"Times =
New Roman" =0A=
size=3D2></FONT> </P></DIV>=0A=
<DIV class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT face=3D"Times =
New Roman" =0A=
size=3D2>When I joined the ebSOA TC back in March of this =
year, the only =0A=
ebSOA TC architectural specification document (dated August =
2004) that =0A=
was present, was a high level abstract draft that you also =
contributed to. =0A=
You left this in its beginning stage, and I have not seen any =
further =0A=
contributions since. Coneveniently you reappeared as soon as the =
FERA-based =0A=
SOA submission was completed, and your intentions were =
questionable at =0A=
best. What I want to know, is wether you would like to help the =
process, or =0A=
hindered it like you have been doing thus =0A=
far. </FONT> </DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><SPAN><FONT =0A=
face=3D"Times New Roman" size=3D2></FONT></SPAN> </P>=0A=
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT size=3D2><FONT =0A=
face=3D"Times New Roman">The way I see this, is that I will not waste my =
time with =0A=
the chicken and egg </FONT><FONT face=3D"Times New Roman">scenario with =
endless =0A=
discussions about SOA, services, service </FONT><FONT =0A=
face=3D"Times New Roman">orchestration, choreography, and many others. =
However, we =0A=
can further our discussions, as long as</FONT><FONT face=3D"Times =
New Roman"> =0A=
constructive exchanges based on our </FONT><FONT =0A=
face=3D"Times New Roman">clearly stated positions, and most importantly, =
the =0A=
respect for each others work are present.</FONT><FONT face=3D"Times New =
Roman"> =0A=
</FONT><FONT face=3D"Times New Roman">Counter-productive arguements =
without =0A=
merit, which you have displayed, serve as a barrier to our =
communication. =0A=
</FONT></FONT></P>=0A=
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT face=3D"Times =
New Roman" =0A=
size=3D2></FONT> </P>=0A=
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT size=3D2><FONT =0A=
face=3D"Times New Roman">Assuming that we will have more positive and =
more =0A=
constructive </FONT><FONT face=3D"Times New Roman">communication in =
the near =0A=
future, I look forward to hearing from you about </FONT><FONT =0A=
face=3D"Times New Roman">your position, views and outlooks, on SOA =
and all =0A=
aspects surrounding it.<SPAN> </SPAN></FONT></FONT></P>=0A=
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT face=3D"Times =
New Roman" =0A=
size=3D2><SPAN></SPAN></FONT> </P>=0A=
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT face=3D"Times =
New Roman" =0A=
size=3D2><SPAN>Goran</SPAN></FONT></P>=0A=
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT face=3D"Times =
New Roman" =0A=
size=3D2></FONT> </P>=0A=
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT face=3D"Times =
New Roman" =0A=
size=3D2></FONT> </P></FONT></DIV></DIV>=0A=
<BLOCKQUOTE dir=3Dltr =0A=
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">=0A=
<DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>=0A=
<DIV style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial"><B>From:</B> <A =0A=
title=3Dchiusano_joseph@bah.com =
href=3D"mailto:chiusano_joseph@bah.com";>Chiusano =0A=
Joseph</A> </DIV>=0A=
<DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
title=3Dgoran.zugic@semantion.com =0A=
=
href=3D"mailto:goran.zugic@semantion.com";>goran.zugic@semantion.com</A> =
; <A =0A=
title=3Debsoa@lists.oasis-open.org =0A=
href=3D"mailto:ebsoa@lists.oasis-open.org";>ebSOA OASIS TC</A> </DIV>=0A=
<DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Wednesday, October 26, =
2005 5:02 =0A=
PM</DIV>=0A=
<DIV style=3D"FONT: 10pt arial"><B>Subject:</B> RE: [ebsoa] SOA =
Collaboration =0A=
Semantics</DIV>=0A=
<DIV><BR></DIV>=0A=
<DIV dir=3Dltr align=3Dleft><SPAN class=3D573210021-26102005><FONT =
face=3DArial =0A=
size=3D2>Goran,</FONT></SPAN></DIV>=0A=
<DIV dir=3Dltr align=3Dleft><SPAN class=3D573210021-26102005><FONT =
face=3DArial =0A=
size=3D2></FONT></SPAN> </DIV>=0A=
<DIV dir=3Dltr align=3Dleft><SPAN class=3D573210021-26102005><FONT =
face=3DArial =0A=
size=3D2>I don't believe it is very professional for you to assume =
what I am =0A=
interested in regarding SOA. In fact, your assumption was quite =0A=
innaccurate.</FONT></SPAN></DIV>=0A=
<DIV dir=3Dltr align=3Dleft><SPAN class=3D573210021-26102005><FONT =
face=3DArial =0A=
size=3D2></FONT></SPAN> </DIV>=0A=
<DIV dir=3Dltr align=3Dleft><SPAN class=3D573210021-26102005><FONT =
face=3DArial =0A=
size=3D2>I will clarify that I am interested in the terminology, the =
purpose, =0A=
the business process improvements it can provide, and many other =0A=
aspects.</FONT></SPAN></DIV>=0A=
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>=0A=
<DIV><SPAN class=3D573210021-26102005><FONT face=3DArial size=3D2>I =
thank you in =0A=
advance for updating your high-level information model to accurately =
reflect =0A=
your stated intent for these specifications. I am still highly =
skeptical of =0A=
their usefulness and value, but time and market will =
tell.</FONT></SPAN></DIV>=0A=
<DIV><SPAN class=3D573210021-26102005><FONT face=3DArial =0A=
size=3D2></FONT></SPAN> </DIV>=0A=
<DIV><SPAN class=3D573210021-26102005><FONT face=3DArial =0A=
size=3D2>Joe</FONT></SPAN></DIV>=0A=
<DIV align=3Dleft><FONT face=3DArial size=3D2></FONT> </DIV>=0A=
<DIV align=3Dleft><FONT face=3DArial size=3D2>Kind =
Regards,</FONT></DIV>=0A=
<DIV align=3Dleft><FONT face=3DArial size=3D2>Joseph =
Chiusano</FONT></DIV>=0A=
<DIV align=3Dleft><FONT face=3DArial size=3D2>Associate</FONT></DIV>=0A=
<DIV align=3Dleft><FONT face=3DArial size=3D2>Booz Allen =
Hamilton</FONT></DIV>=0A=
<DIV align=3Dleft><FONT size=3D1><FONT face=3D"Times New Roman"><FONT =
face=3DArial =0A=
size=3D2></FONT> </DIV></FONT></FONT>=0A=
<DIV align=3Dleft>=0A=
<DIV align=3Dleft><FONT face=3DArial size=3D2>700 13th St. =
NW</FONT></DIV>=0A=
<DIV align=3Dleft><FONT face=3DArial size=3D2>Washington, DC =
20005</FONT></DIV>=0A=
<DIV align=3Dleft><FONT face=3DArial size=3D2>O: 202-508-6514<FONT =0A=
color=3D#ff0000> </FONT></FONT></DIV>=0A=
<DIV align=3Dleft><FONT face=3DArial size=3D2>C: =
202-251-0731</FONT></DIV></DIV>=0A=
<DIV align=3Dleft>=0A=
<DIV align=3Dleft><FONT face=3DArial size=3D2>Visit us online@ =
</FONT><A =0A=
title=3Dhttp://www.boozallen.com/ =
href=3D"http://www.boozallen.com/";><FONT =0A=
title=3Dhttp://www.boozallen.com/ face=3DArial =0A=
size=3D2>http://www.boozallen.com</FONT></A></DIV></DIV>=0A=
<DIV> </DIV><BR>=0A=
<BLOCKQUOTE dir=3Dltr =0A=
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px =
solid; MARGIN-RIGHT: 0px">=0A=
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>=0A=
<HR tabIndex=3D-1>=0A=
<FONT face=3DTahoma size=3D2><B>From:</B> goran.zugic@semantion.com =0A=
[mailto:goran.zugic@semantion.com] <BR><B>Sent:</B> Wednesday, =
October 26, =0A=
2005 4:58 PM<BR><B>To:</B> Chiusano Joseph; Goran Zugic; ebSOA OASIS =0A=
TC<BR><B>Subject:</B> Re: [ebsoa] SOA Collaboration =0A=
Semantics<BR></FONT><BR></DIV>=0A=
<DIV></DIV>=0A=
<DIV><FONT face=3DVerdana color=3D#0000ff size=3D2>Joe,</FONT></DIV>=0A=
<DIV><FONT face=3DVerdana color=3D#0000ff =
size=3D2></FONT> </DIV>=0A=
<DIV><FONT face=3DVerdana color=3D#0000ff size=3D2>Thank you for =
being so frank in =0A=
sharing your opinion. Looks like you are interested in terminology =
of the =0A=
SOA, not in the purpose of it, or in the business process =
improvements that =0A=
it can provide. The proposed framework deals with ontology, =
information =0A=
models, run time architecture and semantics for SOA and its =
implementations, =0A=
the missing glue areas in current standard specifications. When you =
read the =0A=
proposed documents in more details, you will get answers to all your =0A=
questions. <BR> <BR>Fore example, Service entity is explicitly =
defined =0A=
in SOA IM. Unfortunately your conclusions have been made mostly =
based on the =0A=
only figure in the SOA IM document, "Figure 1 - SOA Information =
Model (High =0A=
Level)", yes it says "High Level", which does not graphically =
include =0A=
Service entity. If you really read the document you would easily =
find out =0A=
that the Service entity is defined in SOA IM and that it is one of =
the the =0A=
core SOA IM entities used to support key business process entities: =0A=
activities, decisions and events. However, in our next release, we =
will =0A=
graphically add, for example, the Service entity to the SOA IM =
high-level =0A=
figure to help you and similar readers whose focus is on the =
pictures not =0A=
the content to better understand our specs and solution. =
<BR> <BR>Few =0A=
more words about reference and run-time architecture. As I mentioned =
in my =0A=
previous note FERA reference architecture has been created based on =
many =0A=
collaborative (business) process use cases and installations. The =
run-time =0A=
SOA is based on it and SOA Collaboration Semantics defines all its =0A=
architectural components' protocols, interfaces and methods. That is =
how you =0A=
provide vendors with specs that can be used to develop plugable =0A=
architectural components in a fully interoperable way. How you are =
going to =0A=
implement it, what technology will be used and everything else that =
comes =0A=
with it is completely independent of this specs.<BR> =
<BR>Analogy with =0A=
sports. The formalism applied to the abstract definition of =
the ball =0A=
(service) out of the game (context) does not make too much =0A=
sense. We can debate if the ball should be defined as "soccer =
ball" or =0A=
"football" forever, and no-one would win that debate. It does not =
matter if =0A=
we follow the ontology of the game. Players will say "pass me the =
ball", or =0A=
"share that orange, you hog", and everyone else will understand that =
request =0A=
given the game being played at the moment. <BR>Smart people defined =
the =0A=
purpose of services and SOA long time ago but nobody has provided =
the way =0A=
how the entire SOA should work. We are the first group that has =
created the =0A=
framework for this kind of the SOA specs. More and more people and =0A=
organizations and even some new OASIS TCs starting to realize the =
importance =0A=
of the SOA IM and SOA semantics which are first introduced by us as =
the key =0A=
elements for the complete support for business process =
modeling, =0A=
deployment and execution in SOA. <BR></FONT></DIV>=0A=
<DIV><FONT face=3DVerdana color=3D#0000ff size=3D2>Goran</FONT></DIV>=0A=
<DIV><FONT face=3DVerdana color=3D#0000ff =
size=3D2> </DIV></FONT>=0A=
<BLOCKQUOTE =0A=
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff =
2px solid; MARGIN-RIGHT: 0px"><FONT =0A=
face=3DTahoma size=3D2>-----Original Message-----<BR><B>From:</B> =
Chiusano =0A=
Joseph [mailto:chiusano_joseph@bah.com]<BR><B>Sent:</B> Wednesday, =
October =0A=
26, 2005 11:04 AM<BR><B>To:</B> 'Goran Zugic', 'ebSOA OASIS =0A=
TC'<BR><B>Subject:</B> RE: [ebsoa] SOA Collaboration =0A=
Semantics<BR><BR></FONT>=0A=
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN =0A=
class=3D772324614-26102005>Please see comments below, marked with =0A=
[JMC].</SPAN></FONT></DIV>=0A=
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>=0A=
<DIV align=3Dleft><FONT face=3DArial size=3D2>Kind =
Regards,</FONT></DIV>=0A=
<DIV align=3Dleft><FONT face=3DArial size=3D2>Joseph =
Chiusano</FONT></DIV>=0A=
<DIV align=3Dleft><FONT face=3DArial =
size=3D2>Associate</FONT></DIV>=0A=
<DIV align=3Dleft><FONT face=3DArial size=3D2>Booz Allen =
Hamilton</FONT></DIV>=0A=
<DIV align=3Dleft><FONT size=3D1><FONT face=3D"Times New =
Roman"><FONT face=3DArial =0A=
size=3D2></FONT> </DIV></FONT></FONT>=0A=
<DIV align=3Dleft>=0A=
<DIV align=3Dleft><FONT face=3DArial size=3D2>700 13th St. =
NW</FONT></DIV>=0A=
<DIV align=3Dleft><FONT face=3DArial size=3D2>Washington, DC =
20005</FONT></DIV>=0A=
<DIV align=3Dleft><FONT face=3DArial size=3D2>O: 202-508-6514<FONT =0A=
color=3D#ff0000> </FONT></FONT></DIV>=0A=
<DIV align=3Dleft><FONT face=3DArial size=3D2>C: =
202-251-0731</FONT></DIV></DIV>=0A=
<DIV align=3Dleft>=0A=
<DIV align=3Dleft><FONT face=3DArial size=3D2>Visit us online@ =
</FONT><A =0A=
title=3Dhttp://www.boozallen.com/ =
href=3D"http://www.boozallen.com/"; =0A=
target=3D_blank><FONT title=3Dhttp://www.boozallen.com/ =
face=3DArial =0A=
size=3D2>http://www.boozallen.com</FONT></A></DIV></DIV>=0A=
<DIV><FONT face=3DArial size=3D2></FONT> </DIV><FONT =
face=3DArial =0A=
size=3D2></FONT><BR>=0A=
<BLOCKQUOTE dir=3Dltr =0A=
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 =
2px solid; MARGIN-RIGHT: 0px">=0A=
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>=0A=
<HR tabIndex=3D-1>=0A=
<FONT face=3DTahoma size=3D2><B>From:</B> Goran Zugic =0A=
[mailto:goran.zugic@semantion.com] <BR><B>Sent:</B> Tuesday, =
October 25, =0A=
2005 10:58 PM<BR><B>To:</B> Chiusano Joseph; ebSOA OASIS =0A=
TC<BR><B>Subject:</B> Re: [ebsoa] SOA Collaboration =0A=
Semantics<BR></FONT><BR></DIV>=0A=
<DIV></DIV>=0A=
<DIV>=0A=
<DIV dir=3Dltr align=3Dleft><SPAN =
class=3D687012721-25102005><FONT face=3DArial =0A=
color=3D#0000ff size=3D2>Joe,</FONT></SPAN></DIV>=0A=
<DIV dir=3Dltr align=3Dleft><SPAN =
class=3D687012721-25102005><FONT face=3DArial =0A=
color=3D#0000ff size=3D2></FONT></SPAN> </DIV>=0A=
<DIV dir=3Dltr align=3Dleft><SPAN =
class=3D687012721-25102005><FONT face=3DArial =0A=
color=3D#0000ff size=3D2>Thanks for your feedback. These are my =0A=
answers:</FONT></SPAN></DIV>=0A=
<DIV dir=3Dltr align=3Dleft><SPAN =
class=3D687012721-25102005><FONT face=3DArial =0A=
color=3D#0000ff size=3D2></FONT></SPAN> </DIV>=0A=
<DIV dir=3Dltr align=3Dleft><SPAN =
class=3D687012721-25102005><FONT face=3DArial =0A=
color=3D#0000ff size=3D2>- The run-time architecture is based on =
analysis of =0A=
over 130 collaborative installations. It is based on FERA which =0A=
classifies and categorizes capabilities required to support all =
of the =0A=
use cases analyzed. The components are actually reference =
functional =0A=
modules that have specified functions and interfaces. Our =
run time =0A=
SOA is based on that model and each component has a well defined =
role =0A=
and interface to communicate with other components to support =
the =0A=
collaborative process.</FONT></SPAN></DIV>=0A=
<DIV><SPAN class=3D687012721-25102005><FONT face=3DArial =
color=3D#0000ff =0A=
size=3D2></FONT></SPAN> </DIV>=0A=
<DIV><SPAN class=3D687012721-25102005>=0A=
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial><FONT =
size=3D2><SPAN =0A=
class=3D772324614-26102005>[JMC] Thank you. The information =
you =0A=
provided above is valuable to understand =
the background and =0A=
history of the run-time architecture. I should also =
emphasize that =0A=
my original question was: "</SPAN>Since the run-time =
architecture =0A=
is greatly concrete, is it intended that products be based on =
it? Is it =0A=
intended for exemplary purposes? Other?<SPAN =0A=
=
class=3D772324614-26102005> ". </SPAN></FONT></FONT></DIV=
>=0A=
<DIV dir=3Dltr align=3Dleft><FONT size=3D2><SPAN =0A=
=
class=3D772324614-26102005></SPAN></FONT> </DIV></SPAN></DIV>=0A=
<DIV><SPAN class=3D687012721-25102005><FONT face=3DArial =
color=3D#0000ff =0A=
size=3D2>- SOA IM is based on the process definition in FERA =
that requires =0A=
certain level of specificity of the process detail. True, FERA =
does not =0A=
require QoS details, but it provides a robust security policy =0A=
model. <SPAN class=3D772324614-26102005><FONT =0A=
color=3D#000000> </FONT></SPAN></FONT></SPAN></DIV>=0A=
<DIV><SPAN class=3D687012721-25102005><FONT face=3DArial =
color=3D#0000ff =0A=
size=3D2><SPAN =
class=3D772324614-26102005></SPAN></FONT></SPAN> </DIV>=0A=
<DIV><SPAN class=3D687012721-25102005><FONT face=3DArial =
color=3D#0000ff =0A=
size=3D2><SPAN class=3D772324614-26102005>=0A=
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial><FONT =
size=3D2><FONT =0A=
color=3D#000000><SPAN class=3D772324614-26102005>[JMC] It seems =
to me that =0A=
if the security policy model is robust as you say, it would be =
reflected =0A=
in the SOA IM hierarchy shown in Figure 1 of the SOA IM =
document. Why =0A=
would it not be (sorry, I don't =0A=
understand).</SPAN></FONT></FONT></FONT></DIV>=0A=
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial><FONT =
size=3D2><FONT =0A=
color=3D#000000><SPAN =0A=
=
class=3D772324614-26102005></SPAN></FONT></FONT></FONT> </DIV></SPAN=
></FONT></SPAN></DIV>=0A=
<DIV><SPAN class=3D687012721-25102005><FONT =
color=3D#0000ff><FONT =0A=
face=3DArial><FONT size=3D2><SPAN =
class=3D772324614-26102005> </SPAN>The =0A=
IM is derived from FERA process characteristics and there =
are =0A=
additional data elements required for the run time semantics =
that are =0A=
used for quality, escalation, monitoring and other =
administrative =0A=
aspects of run time execution. The SOA IM contains sufficient =
level of =0A=
detail to extract the semantics and to execute it over the run =
time SOA. =0A=
True it is a process based model, and that is intentional, =0A=
because that maintains the fidelity of business =
requirements =0A=
throughout the entire deployment. In this framework, it is less =0A=
important to define what is a service then to satisfy all =0A=
basic principles of SOA. <SPAN =
class=3D772324614-26102005><FONT =0A=
=
color=3D#000000> </FONT></SPAN></FONT></FONT></FONT></SPAN></DIV>=0A=
<DIV><SPAN class=3D687012721-25102005><FONT =
color=3D#0000ff><FONT =0A=
face=3DArial><FONT size=3D2><SPAN =0A=
=
class=3D772324614-26102005></SPAN></FONT></FONT></FONT></SPAN> </DIV=
>=0A=
<DIV><SPAN class=3D687012721-25102005><FONT =
color=3D#0000ff><FONT =0A=
face=3DArial><FONT size=3D2><SPAN class=3D772324614-26102005>=0A=
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial><FONT =
size=3D2><FONT =0A=
color=3D#000000><SPAN class=3D772324614-26102005>[JMC] How can =
one "satisfy =0A=
all basic principles of SOA" if the most fundamental concept of =
SOA - =0A=
"service" - is not =0A=
=
defined?</SPAN></FONT></FONT></FONT></DIV></SPAN></FONT></FONT></FONT></S=
PAN></DIV>=0A=
<DIV><SPAN class=3D687012721-25102005><FONT =
color=3D#0000ff><FONT =0A=
face=3DArial><FONT size=3D2><SPAN =0A=
=
class=3D772324614-26102005></SPAN></FONT></FONT></FONT></SPAN> </DIV=
>=0A=
<DIV><SPAN class=3D687012721-25102005><FONT =
color=3D#0000ff><FONT =0A=
size=3D+0><FONT face=3DArial size=3D2>That is why it is an SOA =
IM. <SPAN =0A=
class=3D772324614-26102005><FONT =0A=
=
color=3D#000000> </FONT></SPAN></FONT></FONT></FONT></SPAN></DIV>=0A=
<DIV><SPAN class=3D687012721-25102005><FONT =
color=3D#0000ff><FONT =0A=
size=3D+0><FONT face=3DArial size=3D2><SPAN =0A=
=
class=3D772324614-26102005></SPAN></FONT></FONT></FONT></SPAN> </DIV=
>=0A=
<DIV><SPAN class=3D687012721-25102005><FONT =
color=3D#0000ff><FONT =0A=
size=3D+0><FONT face=3DArial size=3D2><SPAN =
class=3D772324614-26102005>=0A=
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial><FONT =
size=3D2><FONT =0A=
color=3D#000000><SPAN class=3D772324614-26102005>[JMC] Given =
that "Service" =0A=
does not appear in the IM hierarchy, I would asser that it is =
*not* a =0A=
SOA IM, and that portraying it as such is - a best - a huge =0A=
stretch.</SPAN></FONT></FONT></FONT></DIV>=0A=
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial><FONT =
size=3D2><FONT =0A=
color=3D#000000><SPAN =0A=
=
class=3D772324614-26102005></SPAN></FONT></FONT></FONT> </DIV></SPAN=
></FONT></FONT></FONT></SPAN></DIV>=0A=
<DIV><SPAN class=3D687012721-25102005><FONT =
color=3D#0000ff><FONT =0A=
size=3D+0><FONT face=3DArial size=3D2>However, the Service =
entity =0A=
is defined in Section 2.1.35 in SOA IM document. <SPAN =0A=
class=3D772324614-26102005><FONT =0A=
=
color=3D#000000> </FONT></SPAN></FONT></FONT></FONT></SPAN></DIV>=0A=
<DIV><SPAN class=3D687012721-25102005><FONT =
color=3D#0000ff><FONT =0A=
size=3D+0><FONT face=3DArial size=3D2><SPAN =0A=
=
class=3D772324614-26102005></SPAN></FONT></FONT></FONT></SPAN> </DIV=
>=0A=
<DIV><SPAN class=3D687012721-25102005><FONT =
color=3D#0000ff><FONT =0A=
size=3D+0><FONT face=3DArial size=3D2><SPAN =
class=3D772324614-26102005>=0A=
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial><FONT =
size=3D2><FONT =0A=
color=3D#000000><SPAN class=3D772324614-26102005>[JMC] Great - =
why not put =0A=
it in the IM hierarchy?</SPAN></FONT></FONT></FONT></DIV>=0A=
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial><FONT =
size=3D2><FONT =0A=
color=3D#000000><SPAN =0A=
class=3D772324614-26102005></SPAN></FONT></FONT></FONT><FONT =0A=
face=3DArial><FONT size=3D2><FONT color=3D#000000><SPAN =0A=
=
class=3D772324614-26102005></SPAN></FONT></FONT></FONT> </DIV></SPAN=
></FONT></FONT></FONT></SPAN></DIV>=0A=
<DIV><SPAN class=3D687012721-25102005><FONT =
color=3D#0000ff><FONT =0A=
size=3D+0><FONT face=3DArial size=3D2>Hence, you see activities, =
decisions, =0A=
events, roles, rules and metrics as key entities. A service can =0A=
therefore be any activity, or a decision that has defined inputs =
and =0A=
outputs, conditions for its invocation, metrics for its =
performance, =0A=
rules for its execution, matrix with the input processing =
logic and =0A=
few other entities in the model. <SPAN =0A=
class=3D772324614-26102005><FONT =0A=
=
color=3D#000000> </FONT></SPAN></FONT></FONT></FONT></SPAN></DIV>=0A=
<DIV><SPAN class=3D687012721-25102005><FONT =
color=3D#0000ff><FONT =0A=
size=3D+0><FONT face=3DArial size=3D2><SPAN =0A=
=
class=3D772324614-26102005></SPAN></FONT></FONT></FONT></SPAN> </DIV=
>=0A=
<DIV><SPAN class=3D687012721-25102005><FONT =
color=3D#0000ff><FONT =0A=
size=3D+0><FONT face=3DArial size=3D2><SPAN =
class=3D772324614-26102005>=0A=
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial><FONT =
size=3D2><FONT =0A=
color=3D#000000><SPAN class=3D772324614-26102005>[JMC] Great - =
then that =0A=
should be reflected in the IM hierarchy, with "Service" being =
related to =0A=
all of these, IMHO.</SPAN></FONT></FONT></FONT></DIV>=0A=
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial><FONT =
size=3D2><FONT =0A=
color=3D#000000><SPAN =0A=
=
class=3D772324614-26102005></SPAN></FONT></FONT></FONT> </DIV></SPAN=
></FONT></FONT></FONT></SPAN></DIV>=0A=
<DIV><SPAN class=3D687012721-25102005><FONT =
color=3D#0000ff><FONT =0A=
size=3D+0><FONT face=3DArial size=3D2>Hence the entire model in =
fact defines =0A=
services, their orchestration, <SPAN =
class=3D772324614-26102005><FONT =0A=
=
color=3D#000000> </FONT></SPAN></FONT></FONT></FONT></SPAN></DIV>=0A=
<DIV><SPAN class=3D687012721-25102005><FONT =
color=3D#0000ff><FONT =0A=
size=3D+0><FONT face=3DArial size=3D2><SPAN =0A=
=
class=3D772324614-26102005></SPAN></FONT></FONT></FONT></SPAN> </DIV=
>=0A=
<DIV><SPAN class=3D687012721-25102005><FONT =
color=3D#0000ff><FONT =0A=
size=3D+0><FONT face=3DArial size=3D2><SPAN =
class=3D772324614-26102005>=0A=
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial><FONT =
size=3D2><FONT =0A=
color=3D#000000><SPAN class=3D772324614-26102005>[JMC] Not all =
SOA instances =0A=
involve orchestration - that is a feature (aspect) that is =
determined =0A=
according to business need. So building in orchestration =
"natively", =0A=
IMHO, makes this an orchestration IM (or a process IM), not a =
SOA =0A=
IM.</SPAN></FONT></FONT></FONT></DIV>=0A=
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial><FONT =
size=3D2><FONT =0A=
color=3D#000000><SPAN =0A=
class=3D772324614-26102005></SPAN></FONT></FONT></FONT><FONT =0A=
face=3DArial><FONT size=3D2><FONT color=3D#000000><SPAN =0A=
=
class=3D772324614-26102005></SPAN></FONT></FONT></FONT> </DIV></SPAN=
></FONT></FONT></FONT></SPAN></DIV>=0A=
<DIV><SPAN class=3D687012721-25102005><FONT =
color=3D#0000ff><FONT =0A=
size=3D+0><FONT size=3D+0><FONT face=3DArial><FONT =
size=3D2>their business rules =0A=
and other aspects required for SOA definition, deployment, =
maintenance =0A=
and continuous operational support. The entire IM and the =
architecture =0A=
is an SOA based on the principles of service =
orientation. <SPAN =0A=
class=3D772324614-26102005><FONT =0A=
=
color=3D#000000> </FONT></SPAN></FONT></FONT></FONT></FONT></FONT></=
SPAN></DIV>=0A=
<DIV><SPAN class=3D687012721-25102005><FONT =
color=3D#0000ff><FONT =0A=
size=3D+0><FONT size=3D+0><FONT face=3DArial><FONT =
size=3D2><SPAN =0A=
=
class=3D772324614-26102005></SPAN></FONT></FONT></FONT></FONT></FONT></SP=
AN> </DIV>=0A=
<DIV><SPAN class=3D687012721-25102005><FONT =
color=3D#0000ff><FONT =0A=
size=3D+0><FONT size=3D+0><FONT face=3DArial><FONT =
size=3D2><SPAN =0A=
class=3D772324614-26102005>=0A=
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial><FONT =
size=3D2><FONT =0A=
color=3D#000000><SPAN class=3D772324614-26102005>[JMC] I believe =
that it =0A=
cannot be this, since "Service" is not even included in the IM =0A=
hierarchy, much less as a central =0A=
focus.</SPAN></FONT></FONT></FONT></DIV>=0A=
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial><FONT =
size=3D2><FONT =0A=
color=3D#000000><SPAN =0A=
class=3D772324614-26102005></SPAN></FONT></FONT></FONT><FONT =0A=
face=3DArial><FONT size=3D2><FONT color=3D#000000><SPAN =0A=
=
class=3D772324614-26102005></SPAN></FONT></FONT></FONT> </DIV></SPAN=
></FONT></FONT></FONT></FONT></FONT></SPAN></DIV>=0A=
<DIV><SPAN class=3D687012721-25102005><FONT =
color=3D#0000ff><FONT =0A=
size=3D+0><FONT size=3D+0><FONT face=3DArial><FONT size=3D2>Just =
like in the =0A=
sport of soccer nothing is really called soccer, but everything =
else =0A=
defines the game, players, referees, goals, spectators, ball, =
pitch, =0A=
etc.</FONT></FONT></FONT></FONT></FONT></SPAN></DIV>=0A=
<DIV><SPAN class=3D687012721-25102005><FONT face=3DArial =
color=3D#0000ff =0A=
size=3D2></FONT></SPAN> </DIV>=0A=
<DIV><SPAN class=3D687012721-25102005>=0A=
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial><FONT =
size=3D2><FONT =0A=
color=3D#000000><SPAN class=3D772324614-26102005>[JMC] Yes, but =
there are =0A=
fundamental components you mentioned, such as a soccer ball. How =
can =0A=
this be SOA (soccer) without depicting a soccer ball =0A=
(Service)?</SPAN></FONT></FONT></FONT></DIV></SPAN></DIV>=0A=
<DIV><SPAN class=3D687012721-25102005><FONT face=3DArial =
color=3D#0000ff =0A=
size=3D2></FONT></SPAN> </DIV>=0A=
<DIV><SPAN class=3D687012721-25102005><SPAN =
class=3D772324614-26102005><FONT =0A=
face=3DArial color=3D#0000ff size=3D2>=0A=
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial><FONT =
size=3D2><FONT =0A=
color=3D#000000><SPAN class=3D772324614-26102005>I am not =
implying anything =0A=
more than I am saying here, but it appears to me that the SOA IM =
was =0A=
originally written as a process IM, and some text regarding =
"service" =0A=
was added in as an afterthought (just my =0A=
opinion).</SPAN></FONT></FONT></FONT></DIV>=0A=
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial><FONT =
size=3D2><FONT =0A=
color=3D#000000><SPAN =0A=
=
class=3D772324614-26102005></SPAN></FONT></FONT></FONT> </DIV>=0A=
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial><FONT =
size=3D2><FONT =0A=
color=3D#000000><SPAN class=3D772324614-26102005>Given its =
current state, I =0A=
frankly don't see its value to this TC or standards work in =0A=
general.</SPAN></FONT></FONT></FONT></DIV>=0A=
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial><FONT =
size=3D2><FONT =0A=
color=3D#000000><SPAN =0A=
=
class=3D772324614-26102005></SPAN></FONT></FONT></FONT> </DIV>=0A=
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial><FONT =
size=3D2><FONT =0A=
color=3D#000000><SPAN =0A=
=
class=3D772324614-26102005>Thanks,</SPAN></FONT></FONT></FONT></DIV>=0A=
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial><FONT =
size=3D2><FONT =0A=
color=3D#000000><SPAN =0A=
class=3D772324614-26102005>Joe</SPAN></FONT></FONT></FONT></DIV>=0A=
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial><FONT =
size=3D2><FONT =0A=
color=3D#000000><SPAN =0A=
=
class=3D772324614-26102005></SPAN></FONT></FONT></FONT> </DIV></FONT=
></SPAN></SPAN></DIV>=0A=
<DIV><SPAN class=3D687012721-25102005><FONT face=3DArial =
color=3D#0000ff =0A=
size=3D2>Regards,</FONT></SPAN></DIV>=0A=
<DIV><SPAN class=3D687012721-25102005><FONT face=3DArial =
color=3D#0000ff =0A=
size=3D2>Goran</FONT></SPAN></DIV></DIV>=0A=
<BLOCKQUOTE dir=3Dltr =0A=
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: =
5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">=0A=
<DIV style=3D"FONT: 10pt arial">----- Original Message ----- =
</DIV>=0A=
<DIV style=3D"BACKGROUND: #e4e4e4; FONT: 10pt =
arial"><B>From:</B> <A =0A=
title=3Dchiusano_joseph@bah.com =
href=3D"mailto:chiusano_joseph@bah.com"; =0A=
target=3D_blank>Chiusano Joseph</A> </DIV>=0A=
<DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =0A=
title=3Dgoran.zugic@semantion.com =0A=
href=3D"mailto:goran.zugic@semantion.com"; =
target=3D_blank>Goran Zugic</A> =0A=
; <A title=3Debsoa@lists.oasis-open.org =0A=
href=3D"mailto:ebsoa@lists.oasis-open.org"; =
target=3D_blank>ebSOA OASIS =0A=
TC</A> </DIV>=0A=
<DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Tuesday, October =
25, 2005 =0A=
4:10 PM</DIV>=0A=
<DIV style=3D"FONT: 10pt arial"><B>Subject:</B> RE: [ebsoa] =
SOA =0A=
Collaboration Semantics</DIV>=0A=
<DIV><FONT face=3DArial size=3D2></FONT><BR></DIV>=0A=
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN =0A=
class=3D625420120-25102005>Goran,</SPAN></FONT></DIV>=0A=
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN =0A=
class=3D625420120-25102005></SPAN></FONT> </DIV>=0A=
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN =0A=
class=3D625420120-25102005>Thanks for sending these documents =
- it's =0A=
clear that a great deal of work has gone into =0A=
them.</SPAN></FONT></DIV>=0A=
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN =0A=
class=3D625420120-25102005></SPAN></FONT> </DIV>=0A=
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN =0A=
class=3D625420120-25102005>I have a few questions, =0A=
please:</SPAN></FONT></DIV>=0A=
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN =0A=
class=3D625420120-25102005></SPAN></FONT> </DIV>=0A=
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN =0A=
class=3D625420120-25102005>Run-Time SOA: I get the notion of a =
reference =0A=
architecture as shown in Figure 1 on p.3. Having said that, I =
would =0A=
expect that any run-time (concrete) architecture that is =
depicted as =0A=
being based on the reference architecture is merely for =
exemplary =0A=
purposes, yet the run-time architecture is simply presented =
without =0A=
any indication of its purpose. Since the run-time architecture =
is =0A=
greatly concrete, is it intended that products be based on it? =
Is it =0A=
intended for exemplary purposes? Other?</SPAN></FONT></DIV>=0A=
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN =0A=
class=3D625420120-25102005></SPAN></FONT> </DIV>=0A=
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial><FONT =
size=3D2><FONT =0A=
size=3D+0><SPAN class=3D625420120-25102005>SOA Information =
Model: Though =0A=
this is called a "SOA" information model, this document =0A=
</SPAN></FONT><FONT size=3D+0>looks more to me like a "Process =0A=
Information Model" that is actually independent of SOA (that =
is, I did =0A=
not see anything that restricted it to SOA).<SPAN =0A=
class=3D625420120-25102005> In fact, in order to call =
something a "SOA" =0A=
information model, I would assert that there are several other =
areas =0A=
that would need to be incorporated beyond processes - e.g. =
security, =0A=
policy, QoS, etc. Even considering the process perspective, =
there is =0A=
nothing that I see in this information model that speaks =
distinctly to =0A=
a service-oriented paradigm - in fact, figure 1 (p.24) does =
not even =0A=
have a "Service" concept. What is the intended use of this =
document =0A=
for ebSOA?</SPAN></FONT></FONT></FONT></DIV>=0A=
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial><FONT =
size=3D2><FONT =0A=
size=3D+0><SPAN =0A=
=
class=3D625420120-25102005></SPAN></FONT></FONT></FONT> </DIV>=0A=
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial><FONT =
size=3D2><FONT =0A=
size=3D+0><SPAN =0A=
=
class=3D625420120-25102005>Thanks,</SPAN></FONT></FONT></FONT></DIV>=0A=
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial><FONT =
size=3D2><FONT =0A=
size=3D+0><SPAN =0A=
=
class=3D625420120-25102005>Joe</SPAN></FONT></FONT></FONT></DIV>=0A=
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>=0A=
<DIV align=3Dleft><FONT face=3DArial size=3D2>Joseph =
Chiusano</FONT></DIV>=0A=
<DIV align=3Dleft><FONT face=3DArial =
size=3D2>Associate</FONT></DIV>=0A=
<DIV align=3Dleft><FONT face=3DArial size=3D2>Booz Allen =0A=
Hamilton</FONT></DIV>=0A=
<DIV align=3Dleft><FONT size=3D1><FONT face=3D"Times New =
Roman"><FONT =0A=
face=3DArial size=3D2></FONT> </DIV></FONT></FONT>=0A=
<DIV align=3Dleft>=0A=
<DIV align=3Dleft><FONT face=3DArial size=3D2>700 13th St. =
NW</FONT></DIV>=0A=
<DIV align=3Dleft><FONT face=3DArial size=3D2>Washington, DC =0A=
20005</FONT></DIV>=0A=
<DIV align=3Dleft><FONT face=3DArial size=3D2>O: =
202-508-6514<FONT =0A=
color=3D#ff0000> </FONT></FONT></DIV>=0A=
<DIV align=3Dleft><FONT face=3DArial size=3D2>C: =0A=
202-251-0731</FONT></DIV></DIV>=0A=
<DIV align=3Dleft>=0A=
<DIV align=3Dleft><FONT face=3DArial size=3D2>Visit us online@ =
</FONT><A =0A=
title=3Dhttp://www.boozallen.com/ =
href=3D"http://www.boozallen.com/"; =0A=
target=3D_blank><FONT title=3Dhttp://www.boozallen.com/ =
face=3DArial =0A=
size=3D2>http://www.boozallen.com</FONT></A></DIV></DIV>=0A=
<DIV> </DIV><BR>=0A=
<BLOCKQUOTE dir=3Dltr =0A=
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: =
#000000 2px solid; MARGIN-RIGHT: 0px">=0A=
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>=0A=
<HR tabIndex=3D-1>=0A=
<FONT face=3DTahoma size=3D2><B>From:</B> Goran Zugic =0A=
[mailto:goran.zugic@semantion.com] <BR><B>Sent:</B> Friday, =
October =0A=
21, 2005 2:21 AM<BR><B>To:</B> 'ebSOA OASIS =
TC'<BR><B>Subject:</B> =0A=
[ebsoa] SOA Collaboration Semantics<BR></FONT><BR></DIV>=0A=
<DIV></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT =
face=3DArial =0A=
size=3D2>Hello ebSOA TC,</FONT></P>=0A=
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT =
face=3DArial =0A=
size=3D2></FONT> </P>=0A=
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT =0A=
face=3DArial><FONT size=3D2>Semantion is pleased to announce =
the =0A=
completion of its FERA-based SOA contribution to ebSOA TC. =0A=
</FONT></FONT></P>=0A=
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT =
face=3DArial =0A=
size=3D2></FONT> </P>=0A=
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT =0A=
face=3DArial><FONT size=3D2>The <EM>SOA Collaboration =
Semantics</EM> =0A=
document </FONT></FONT></P>=0A=
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT =
face=3DArial =0A=
size=3D2></FONT> </P>=0A=
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT =
face=3DArial =0A=
size=3D2><A =
href=3D"http://www.semantion.com/specs/soa/SOA_CS_V0.1.doc"; =0A=
=
target=3D_blank>http://www.semantion.com/specs/soa/SOA_CS_V0.1.doc</A></F=
ONT></P>=0A=
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT =
face=3DArial =0A=
size=3D2></FONT> </P>=0A=
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT =
face=3DArial =0A=
size=3D2>contains FERA-based SOA semantics specification =
that together =0A=
with two previously submitted documents, <EM>Run-time =
SOA</EM> and =0A=
<EM>SOA Information Model,</EM> represent Semantion's =
SOA =0A=
specification framework.</FONT></P>=0A=
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT =
face=3DArial =0A=
size=3D2></FONT> </P>=0A=
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT =
face=3DArial =0A=
size=3D2>The new releases of <EM>the Run-time SOA</EM> =
document and =0A=
<EM>the SOA Information Model</EM> document are =
available =0A=
at</FONT></P>=0A=
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT =
face=3DArial =0A=
size=3D2></FONT> </P>=0A=
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT =
face=3DArial =0A=
size=3D2><A =
href=3D"http://www.semantion.com/specs/soa/SOA_IM_V0.2.doc"; =0A=
=
target=3D_blank>http://www.semantion.com/specs/soa/SOA_IM_V0.2.doc</A></F=
ONT></P>=0A=
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT =
face=3DArial =0A=
size=3D2></FONT> </P>=0A=
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT =
face=3DArial =0A=
size=3D2><A =0A=
=
href=3D"http://www.semantion.com/specs/soa/Run-time_SOA_V0.2.doc"; =0A=
=
target=3D_blank>http://www.semantion.com/specs/soa/Run-time_SOA_V0.2.doc<=
/A></FONT></P>=0A=
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT =
face=3DArial =0A=
size=3D2></FONT> </P>=0A=
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT =
face=3DArial =0A=
size=3D2>These documents should be reviewed in the following =0A=
order:</FONT></P>=0A=
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT =
face=3DArial =0A=
size=3D2></FONT> </P>=0A=
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT =
face=3DArial =0A=
size=3D2><EM>- Run-time SOA</EM></FONT></P>=0A=
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT =
face=3DArial =0A=
size=3D2><EM>- SOA Information Model</EM></FONT></P>=0A=
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT =
face=3DArial =0A=
size=3D2><EM>- SOA Collaboration Semantics</EM></FONT></P>=0A=
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT =
face=3DArial =0A=
size=3D2></FONT> </P>=0A=
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT =
face=3DArial =0A=
size=3D2>Please let me know if you have any questions or =
need more =0A=
information regarding the submitted documents.</FONT></P>=0A=
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT =
face=3DArial =0A=
size=3D2></FONT> </P>=0A=
<DIV>=0A=
<DIV><SPAN =0A=
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Regards,</SPAN></DIV>=0A=
<DIV><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Goran =0A=
Zugic</SPAN></DIV>=0A=
<DIV><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Chief =0A=
Architect</SPAN></DIV>=0A=
<DIV><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Semantion =0A=
Inc.</SPAN></DIV>=0A=
<DIV><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"><A =0A=
=
href=3D"http://mail.semantion.com/loading.htm#";>http://www.semantion.com<=
/A></SPAN></DIV>=0A=
<DIV><SPAN =0A=
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">416-995-7532</SPAN></DIV></DIV></DIV></BLOCKQUOTE></BLOCKQUOTE></B=
LOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></DIV></DIV></BODY></HTM=
L>=0A=
------_=_NextPart_001_01C5DD90.5C7997A5--
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]