On Dec 18, 2006, at 3:27 PM, Simon Nash wrote:
See comments inline.
Simon
Jim Marino wrote:
Hi Venkat,
Sorry for the delay. Can we include some slight wording changes
and clarifications along the following lines?
Jim
"Welcome to the Apache Tuscany open source project licensed under
version 2 of the Apache License. This project is currently in
incubation at Apache.
The aim of the Apache Tuscany project is to create, as a
community, a robust infrastructure that simplifies the
development of SOA-based systems.
Apache Tuscany is based on independent technologies that provide
following:
Service Component Architecture (SCA) enables composition of
service networks through assembly of existing and new services.
As an example, a service can be a webservice.
[JFM: shouldn't the previous be something like: For example, a
Java class, JAX-WS service, Spring Bean, or EJB]
I think Venkat is focusing on the service binding, and you are
focusing
on the service implementation. These are both valid categorizations,
depending on whether the audience is consumers or implementers. I
agree
that we should add some text explaining the different
implementation types.
The word "be" to me implied "implemented as". It would be more
correct and maybe clearer to say:
1. A service can be *exposed* as a web service
2. A service can implemented as a JAX-WS service, Spring Bean or EJB
It's not a big deal but we should probably be as clear as possible.
Tuscany SCA allows services to be implemented in variety of
languages such as Java, JavaScript and C++. Tuscany SCA runtime
is implemented in Java and C++ and can easily be extended to
support any communication transport, qualities of service or
programming model and can be used in conjunction with other
technologies such as Spring, Axis and Celtix.
[JFM the above sentence combines two separate things. I would re-
word as:
There are Java and C++ SCA runtimes that support services
implemented in variety of languages such as Java, JavaScript and C
++. Both runtimes and can easily be extended to support
additional communication transports, qualities of service or
programming models. In addition, they can be used in conjunction
with other technologies such as Spring, Axis and Celtix.]
Today we have two separate runtimes for Java and C++. I'd like to
see us
move towards what Venkat is describing, i.e., an integrated runtime
that
supports components written in Java, C++ and other languages.
It depends on what you mean by "integrated". For me "federated" may
be a way to describe it as the runtime architectures are fairly
distinct as well as the capabilities of the two implementations.
Service Data Object (SDO) provides a uniform interface for
handling different forms of data, including XML documents, that
can exist in a network of services and provides the mechanism for
tracking changes[I would delete: in data]. Apache Tuscany
provides Java and C++ implementations for SDO.
Data Access Service (DAS) provides a simple SDO interface to
relational databases. Apache Tuscany provides a Java
implementation for DAS.
SCA and SDO technologies can be used independent of one another.
The specifications for these technologies are located at
www.osoa.org . Apache Tuscany project provides input to the
specifications.
Please join us to develop this innovative infrastructure and/or
provide feedback [do we need this, i.e. are there "fake"
scenarios ;-) based on real use case scenarios]
>
I don't understand this comment about "fake" scenarios. I think we
need
help with developing the infrastructure, and also with feedback.
Can you
clarify this comment and what change you would like to see in this
wording?
I think we should just say "and/or provide feedback". We don't need
the word "scenarios". If we use the word scenarios, I don't think we
need to qualify it was additional adjectives. Again, it's just a
suggestion as my preference is to be as direct as possible given
people's attention spans.
Jim
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
