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.
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.
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?
which will help Apache Tuscany become a first
class solution for simplifying the development of SOA-based systems."
On Dec 18, 2006, at 10:02 AM, Venkata Krishnan wrote:
Hi,
On the weekly IRC today we have decided to go ahead with the changes
proposed for our website. The proposed one can be found at
http://people.apache.org/~rfeng/tuscany/site-publish/.
To this it is planned that we do the following:
i) Sync up with the contents of the current website as there has been
some
recent updates in the wake of some releases made. This will bring the
proposed website content in sync with the currently active one.
ii) Work on sizing of background images making them relative and
scale with
fonts so that they appear consistently on all browsers.
iii) More specifically add the following contents :
- Add navigation links titled 'Releases' and 'FAQ' for each of
SCA, SDO
and DAS
- Update the SCA Downloads page with the M2 Release artifacts
posted by
Jeremy in another mail
- Merge the content that Simon Nash has posted recently for 'Getting
Started'
In the context of this update being planned I request the following
from the
community: -
- Please do no make any updates from now on, to the website until the
proposed one goes public
- We need help to make the content that should go into the 'Releases'
pages
for SCA, SDO and DAS. I imagine that the Releases page will contain the
details on the contents of each release ending with a link to the
downloads
page. Also if we can have some FAQs aggregated over the wiki, we can
post
them over as soon as the site is done.
- After I have done the changes, I will post the changes to a private
place
from where I request that people help with some testing
- If there is anything that I have missed out in all of this, then
please
point the same.
I am starting with this update work to our website rightaway.
Thanks.
- Venkat
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
