the
purpose of my suggestion is that that "such as" does not have an implied
orchestration of service fulfillment
and
discovery of service elements
demonstration
Joe,
to what extent will your specification of a BPEL element to the demo address the
orchestration and discovery aspects of SOA?
Will
the web service description language (WSDL) use demonstrate an interface to a
small ontology?
Might
the demo suggest how an ontology interface might be created..... and might
the demo suggest how service discovery might occur in the context of everyday
business interactions?
And
then lastly, orchestration can be applied to many different aspects of service
interactions... even to the original definition of new services or
uniquely specified service request and responses - in real
time.
I find
the work done by Cory and Joe wonderful..... and a good basis for
extending the demo?
the the Approach
section of
i suggest
replacing
Model
Driven Architecture techniques will be used to model the community and produce
technology interfaces such as WSDL-SOA interfaces, Ws-Security and BPEL
business processes –
with
Model
Driven Architecture techniques will be used to model the community and produce
technology interfaces that use
WSDL-SOA
interfaces,
Ws-Security
and
BPEL
business processes
the
such as is vague and the "that use" is specific (reducing the
vagueness)
|