Here is the final text for the website main page (including Sebastien's comments). Can someone please post it on the website while we are waiting for David to complete the prototype?
Welcome to the Apache Tuscany free open source project that is licensed under version 2 of the Apache License<http://www.apache.org/licenses/LICENSE-2.0_>. This project is currently in incubation within the Apache incubator. 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 together provide one complete infrastructure which caters to this goal. This includes the 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. 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. · 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 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 based on real use case scenarios which will help Apache Tuscany become a first class solution for simplifying the development of SOA-based systems. On 8/28/06, Jim Marino <[EMAIL PROTECTED]> wrote:
Sorry for taking so long to answer...I got tied up in some things and then spaced out on this. I like it and agree with Sebastien's comments. Thanks, this sounds really good. Jim On Aug 28, 2006, at 4:53 PM, Jean-Sebastien Delfino wrote: > haleh mahbod wrote: >> Hello Tuscany community, >> >> Please review the following text as a proposed text for our main >> web page. >> >> Jim, >> Thanks for your feedback. I tried to capture your comments in the new >> writeup. >> Please feel free to re-write this if you think it needs >> improvement :) >> >> Haleh >> ------------------------------------------------------- Start of text >> --------------------------------------------------------------------- >> ---------- >> >> Welcome to the Apache Tuscany free open source project that is >> licensed >> under version 2 of the Apache >> License<http://www.apache.org/licenses/LICENSE-2.0_>. This project is >> currently in incubation within the Apache incubator. >> >> 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 together >> provide >> one complete infrastructure which caters to this goal. This >> includes the >> following: >> >> · Service Component Architecture (SCA) enables composition of >> service networks through assembly of existing and new services. >> >> Apache Tuscany implements SCA in Java and C++. Tuscany SCA >> runtime 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. >> >> · Service Data Object (SDO) provides a uniform interface for >> handling different forms of data that can exist in a network of >> services and >> provides the mechanism for tracking changes in data. Apache Tuscany >> provides Java and C++ implementations for SDO. >> >> · Service Data Access (DAS) provides a uniform interface for >> interacting with persistent data when using SDO. 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 based on real use case scenarios which will help Apache >> Tuscany >> become a first class solution for simplifying the development of >> SOA-based >> systems. >> < General Tuscany diagram would go here> >> >> On 8/17/06, Jim Marino <[EMAIL PROTECTED]> wrote: >>> >>> Thanks Haleh for taking the time to write this up again...more >>> comments inline. >>> >>> Jim >>> >>> >>> On Aug 16, 2006, at 6:34 PM, haleh mahbod wrote: >>> >>> > Jim, >>> > Thanks for the comments. I took a look at the links and your >>> > comments. How >>> > about this write-up? >>> > >>> > >>> > Welcome to the Apache Tuscany free open source project that is >>> > licensed >>> > under version 2 of the Apache >>> > License<http://www.apache.org/licenses/LICENSE-2.0_>. >>> > This project is currently in incubation within the Apache >>> incubator. >>> > >>> > The aim of the Apache Tuscany is to create, as a community, a >>> robust >>> > framework that simplifies the development of SOA-based systems >>> through >>> > seamless handling of many infrastructure and data handling >>> > complexities >>> > which exist in heterogeneous Service Oriented Architecture (SOA) >>> > environment. >>> IMO the first statement needs to be really direct and as free of >>> buzzwords as possible since it is the first thing people are >>> going to >>> judge us on. I'd try and limit the use of SOA as much as possible >>> since the term is abused these days. I'd also try and not talk about >>> "business problems" since we are targeting primarily systems >>> developers (to join the project) and secondarily end-user >>> applications developers. With that in mind, I would say Tuscany is >>> "infrastructure" (as opposed to a "framework" like Rails, RIFE, >>> parts >>> of Spring, etc.) that simplifies the development of SOA-based >>> systems. It does so by providing technology for composing service >>> networks ("service assemblies") based on SCA and technologies for >>> managing data in that environment based on SDO. >>> >>> At some point I also think we need to make it clear that SCA, SDO >>> and >>> DAS are independent technologies. >>> >>> If I had to characterize the message I would want to send the two >>> constituencies it would be: >>> >>> - system developers: the stuff we're working on involves solving >>> really hard problems and you should be part of building out the next >>> generation infrastructure and doing innovative things. >>> - application developers: our technologies are cool, work with stuff >>> you already know, and will enable you to build really interesting >>> applications. >>> >>> > Tuscany reduces development effort and cost by enabling the >>> > application developer to focus on addressing the business problem. >>> > Tuscanyconsists of the following technologies: >>> > >>> >>> > · Tuscany runtime is based on Service Component >>> > Architecture (SCA) >>> > specification and provides the infrastructure for hosting and >>> > assembling >>> > services. This runtime can easily be extended to support new >>> > communication >>> > transports, qualities of service and programming models. >>> I'd make sure we mention C++ and Java, keeping thins simple as in: >>> >>> >> - SCA-based Java and C++ runtimes for hosting and assembling >>> services >>> >> which can be extended to support new communications transports, >>> >> qualities of service, and programming models >>> >>> >>> > Tuscany runtime >>> The Tuscany SCA runtime >>> > can be used independently or in conjunction with other >>> technologies >>> > such as >>> > Spring, Axis, and Celtix to create and assemble composite >>> > applications. >>> > >>> > · Tuscany offers an implementation for Service Data Object >>> > (SDO) >>> > specification which enables the application developer with a >>> uniform >>> > interface for handling and tracking disparate data as it flows >>> across >>> > service assemblies. >>> I'd maybe reword slightly as: >>> An SDO implementation which provides a uniform interface for >>> handling >>> and tracking disparate data as it flows across service assemblies >>> > >>> > · Tuscany also provides a data access service (DAS) as an >>> > intermediary between SDO and different types of persistent data. >>> > >>> > The specifications that Tuscany is based on are located at >>> > www.osoa.org . Please >>> > join us to build this first class infrastructure that simplifies >>> > development >>> > of SOA-based systems. >>> I'd maybe not highlight the specifications as much. I think it is >>> important that we convey the message Tuscany is not limited to SCA >>> and SDO and we're not just following what a group of vendors write >>> up. It may also be good to say that Tuscany is a way to feed back >>> into those specifications. >>> > >>> > A high level view of the Tuscany offerings is shown below. You can >>> > click on >>> > the diagram to learn more about specific technologies. Tuscany is >>> > supported >>> > in Java and C++. >>> > <Diagram goes here> >>> > >>> > >>> > On 8/16/06, Jim Marino <[EMAIL PROTECTED]> wrote: >>> >> >>> >> >>> >> On Aug 16, 2006, at 8:42 AM, Kevin Williams wrote: >>> >> >>> >> > This is a nice succinct intro to the project. I like it. >>> >> > >>> >> > >>> >> > haleh mahbod wrote: >>> >> > >>> >> >> Hi, >>> >> >> I am following the chapter in this book (http:// >>> producingoss.com/) >>> >> >> that >>> >> >> explains how to create an effective website, pages 22-25. It >>> >> >> suggests that a >>> >> >> good website provides the following information upfront >>> >> >> >>> >> >> 1) A clear mission statement >>> >> >> 2) States whether this open source is free or not and what >>> license >>> >> >> it is >>> >> >> under >>> >> >> 3) It's content is progressive. It allows the reader to >>> learn more >>> >> >> as he >>> >> >> reads more. >>> >> >> >>> >> >> Based on this guideline I re-wrote the text on Tuscany >>> website's >>> >> >> main page >>> >> >> as follows. It can still be improved. Would you review and >>> >> >> comment please? >>> >> >> Thanks >>> >> >> >>> >> >> >>> >> >>> -------------------------------------------------------------------- >>> - >>> >> >> ----------Start >>> >> >> of website >>> >> >> >>> >> >>> text---------------------------------------------------------------- >>> - >>> >> >> --------------------------------------------------- >>> >> >> >>> >> >> Welcome to the Apache Tuscany free open source project that is >>> >> >> licensed >>> >> >> under version 2 of the Apache >>> >> >> License<http://www.apache.org/licenses/LICENSE-2.0_>. >>> >> >> This project is currently in incubation within the Apache >>> >> incubator. >>> >> >> >>> >> >> The aim of the Apache Tuscany is to create, as a community, >>> the >>> >> >> infrastructure that simplifies the development of business >>> >> >> solutions based >>> >> >> on Service Oriented Architecture (SOA). Users of Apache >>> Tuscany >>> >> >> can create >>> >> >> SOA based solutions by combining new or existing services with >>> >> >> little or no >>> >> >> programming. They can also alter the solutions easily when >>> >> business >>> >> >> requirements change. >>> >> I think this is an improvement over what we have but have a >>> couple of >>> >> additional suggestions. Specifically, I don't think the statement >>> >> "with little or no programming" is something we want to claim. >>> It is >>> >> not really accurate and the primary audience coming to the >>> website I >>> >> imagine to be developers who by nature don't believe those >>> kind of >>> >> statements. I would prefer the page to be oriented to developers, >>> >> with the particular purpose of recruiting those interested in >>> writing >>> >> systems-level software, i.e. working on Tuscany. I find these >>> types >>> >> to be generally skeptical by nature and focused on "cool >>> >> technologies." >>> >> >>> >> Some good examples to use for comparison would be Microsoft >>> (who I >>> >> think has generally excellent developer marketing), Spring >>> (Rod is >>> >> also a really good marketer too) and ServiceMix: >>> >> >>> >> http://msdn.microsoft.com/winfx/technologies/communication/ >>> >> default.aspx >>> >> >>> >> http://www.springframework.org/ >>> >> >>> >> http://www.servicemix.org/site/home.html >>> >> >>> >> >>> >> Based on these, I would rephrase and highlight the message that >>> >> developers can leverage Tuscany technologies to build out SOA- >>> based >>> >> systems (as opposed to "business solutions"): >>> >> >>> >> The aim of the Apache Tuscany is to create infrastructure that >>> >> simplifies the development of SOA-based systems. Tuscany >>> technologies >>> >> may be used independently or in conjunction with other >>> technologies >>> >> such as Spring, Axis, and Celtix to create and assemble composite >>> >> applications, or "service assemblies". Specifically, Tuscany >>> >> provides: >>> >> >>> >> - SCA-based Java and C++ runtimes for hosting and assembling >>> services >>> >> which can be extended to support new communications transports, >>> >> qualities of service, and programming models >>> >> - An SDO implementation for representing and tracking data as it >>> >> flows across service assemblies >>> >> - A Data Access Service for declaratively accessing persistent >>> data >>> >> in a service-oriented manner >>> >> >>> >> >>> >> >>> >> >>> >> >>> >> >> >>> >> >> The Tuscany project does this by providing implementations >>> for the >>> >> >> Service >>> >> >> Component Architecture (SCA) and Service Data Objects (SDO) >>> >> >> specifications >>> >> >> and by providing a Data Access Service that supports SDO. >>> >> >> Specifications >>> >> >> for SDO and SCA can be found on www.osoa.org. Tuscany >>> integrates >>> >> >> with well >>> >> >> established Web Services and server technologies such as >>> Apache >>> >> >> Axis2, >>> >> >> Apache Tomcat and Geronimo. >>> >> >> >>> >> >> A high level view of the Tuscany runtime is shown below. >>> You can >>> >> >> click on >>> >> >> the diagram to learn more about specific technologies. >>> Tuscany is >>> >> >> supported >>> >> >> in Java and C++. >>> >> >> >>> >> >> >>> >> >> >>> >> >> <Diagram goes here> >>> >> >> >>> >> > >>> >> > >>> >> > >>> >> > >>> >> >>> -------------------------------------------------------------------- >>> - >>> >> > 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] >>> >> >>> >> >>> >>> >>> -------------------------------------------------------------------- >>> - >>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>> For additional commands, e-mail: [EMAIL PROTECTED] >>> >>> >> > > Nice. I just have a few suggestions: > - We could add that Tuscany/SCA helps you develop service > components in different languages (Java, Javascript, C++ etc). > - We could also say that SCA applications can talk to your average > Web service (to make service network more concrete maybe) > - SDO could say that it helps you work with data in XML documents > - DAS could say that it helps you get/put data in a database (again > more concrete than "persistent data") > > -- > Jean-Sebastien > > > --------------------------------------------------------------------- > 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]
