[VOTE] Graduate Tuscany as a top level project

[ant elder]

The Tuscany podling respectfully requests the Incubator to consider its
graduation to a Top Level Project.

While incubating Tuscany has made 14(!) releases, voted in 19 new
committers, survived conflicts, formed its PPMC, learned how to govern
itself, resolved licensing issues and an active community continues to grow
around Tuscany.

The community vote for graduation can be found on the Tuscany dev list at:
       http://www.mail-archive.com/tuscany-dev@.../msg24675.html

We have prepared the resolution below to be presented for consideration at
the upcoming Board meeting.

We invite everyone to vote to approve this proposal.

Many thanks,

   ...ant

Establish the Apache Tuscany project:

       WHEREAS, the Board of Directors deems it to be in the best
        interests of the Foundation and consistent with the Foundation's
        purpose to establish a Project Management Committee charged with
        the creation and maintenance of open-source software that
        simplifies the development and deployment of service oriented
        applications and provides a managed service-oriented runtime
        based on the standards defined by the OASIS OpenCSA group,
        for distribution at no charge to the public.

       NOW, THEREFORE, BE IT RESOLVED, that a Project Management
        Committee (PMC), to be known as the "Apache Tuscany Project",
        be and hereby is established pursuant to Bylaws of the
        Foundation; and be it further

       RESOLVED, that the Apache Tuscany Project be and hereby is
        responsible for the creation and maintenance of software
        related to Apache Tuscany;
        and be it further

       RESOLVED, that the office of "Vice President, Apache Tuscany" be
        and hereby is created, the person holding such office to
        serve at the direction of the Board of Directors as the chair
        of the Apache Tuscany Project, and to have primary responsibility
        for management of the projects within the scope of
        responsibility of the Apache Tuscany Project; and be it further

       RESOLVED, that the persons listed immediately below be and
        hereby are appointed to serve as the initial members of the
        Apache Tuscany Project:

            Adriano Crestani            <adrianocrestani at apache dot org>
            Andrew Borley               <ajborley at apache dot org>
            Andy Grove                   <agrove at apache dot org>
            ant elder                       <antelder at apache dot org>
            Brady Johnson              <bjohnson at apache dot org>
            Frank Budinsky             <frankb at apache dot org>
            Ignacio Silva-Lepe          <isilval at apache dot org>
            Jean-Sebastien Delfino   <jsdelfino at apache dot org>
            kelvin goodson               <kelvingoodson at apache dot org>
            Luciano Resende           <lresende at apache dot org>
            Mike Edwards               <edwardsmj at apache dot org>
            Pete Robbins                <robbinspg at apache dot org>
            Raymond Feng              <rfeng at apache dot org>
            Simon Laws                  <slaws at apache dot org>
            Simon Nash                  <nash at apache dot org>
            Venkata Krishnan          <svkrish at apache dot org>

       NOW, THEREFORE, BE IT FURTHER RESOLVED, that Ant Elder
        be appointed to the office of Vice President, Apache Tuscany, to
        serve in accordance with and subject to the direction of the
        Board of Directors and the Bylaws of the Foundation until
        death, resignation, retirement, removal or disqualification,
        or until a successor is appointed; and be it further

       RESOLVED, that the Apache Tuscany Project be and hereby
        is tasked with the migration and rationalization of the Apache
        Incubator Tuscany podling; and be it further

       RESOLVED, that all responsibilities pertaining to the Apache
        Incubator Tuscany podling encumbered upon the Apache Incubator
        Project are hereafter discharged.

[pzfreo]

+1 from me (IPMC and Mentor)

Paul

On 10/12/07, ant elder <ant.elder@...> wrote:

> The Tuscany podling respectfully requests the Incubator to consider its
> graduation to a Top Level Project.
>
> While incubating Tuscany has made 14(!) releases, voted in 19 new
> committers, survived conflicts, formed its PPMC, learned how to govern
> itself, resolved licensing issues and an active community continues to grow
> around Tuscany.
>
> The community vote for graduation can be found on the Tuscany dev list at:
>        http://www.mail-archive.com/tuscany-dev@.../msg24675.html
>
> We have prepared the resolution below to be presented for consideration at
> the upcoming Board meeting.
>
> We invite everyone to vote to approve this proposal.
>
> Many thanks,
>
>    ...ant
>
> Establish the Apache Tuscany project:
>
>        WHEREAS, the Board of Directors deems it to be in the best
>         interests of the Foundation and consistent with the Foundation's
>         purpose to establish a Project Management Committee charged with
>         the creation and maintenance of open-source software that
>         simplifies the development and deployment of service oriented
>         applications and provides a managed service-oriented runtime
>         based on the standards defined by the OASIS OpenCSA group,
>         for distribution at no charge to the public.
>
>        NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>         Committee (PMC), to be known as the "Apache Tuscany Project",
>         be and hereby is established pursuant to Bylaws of the
>         Foundation; and be it further
>
>        RESOLVED, that the Apache Tuscany Project be and hereby is
>         responsible for the creation and maintenance of software
>         related to Apache Tuscany;
>         and be it further
>
>        RESOLVED, that the office of "Vice President, Apache Tuscany" be
>         and hereby is created, the person holding such office to
>         serve at the direction of the Board of Directors as the chair
>         of the Apache Tuscany Project, and to have primary responsibility
>         for management of the projects within the scope of
>         responsibility of the Apache Tuscany Project; and be it further
>
>        RESOLVED, that the persons listed immediately below be and
>         hereby are appointed to serve as the initial members of the
>         Apache Tuscany Project:
>
>             Adriano Crestani            <adrianocrestani at apache dot org>
>             Andrew Borley               <ajborley at apache dot org>
>             Andy Grove                   <agrove at apache dot org>
>             ant elder                       <antelder at apache dot org>
>             Brady Johnson              <bjohnson at apache dot org>
>             Frank Budinsky             <frankb at apache dot org>
>             Ignacio Silva-Lepe          <isilval at apache dot org>
>             Jean-Sebastien Delfino   <jsdelfino at apache dot org>
>             kelvin goodson               <kelvingoodson at apache dot org>
>             Luciano Resende           <lresende at apache dot org>
>             Mike Edwards               <edwardsmj at apache dot org>
>             Pete Robbins                <robbinspg at apache dot org>
>             Raymond Feng              <rfeng at apache dot org>
>             Simon Laws                  <slaws at apache dot org>
>             Simon Nash                  <nash at apache dot org>
>             Venkata Krishnan          <svkrish at apache dot org>
>
>        NOW, THEREFORE, BE IT FURTHER RESOLVED, that Ant Elder
>         be appointed to the office of Vice President, Apache Tuscany, to
>         serve in accordance with and subject to the direction of the
>         Board of Directors and the Bylaws of the Foundation until
>         death, resignation, retirement, removal or disqualification,
>         or until a successor is appointed; and be it further
>
>        RESOLVED, that the Apache Tuscany Project be and hereby
>         is tasked with the migration and rationalization of the Apache
>         Incubator Tuscany podling; and be it further
>
>        RESOLVED, that all responsibilities pertaining to the Apache
>         Incubator Tuscany podling encumbered upon the Apache Incubator
>         Project are hereafter discharged.
>

--
Paul Fremantle
Co-Founder and VP of Technical Sales, WSO2
OASIS WS-RX TC Co-chair

blog: http://pzf.fremantle.org
paul@...

"Oxygenating the Web Service Platform", www.wso2.com

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

[dims]

+1 (IPMC and ex-Mentor :)

-- dims

On 10/12/07, Paul Fremantle <pzfreo@...> wrote:

> +1 from me (IPMC and Mentor)
>
> Paul
>
> On 10/12/07, ant elder <ant.elder@...> wrote:
> > The Tuscany podling respectfully requests the Incubator to consider its
> > graduation to a Top Level Project.
> >
> > While incubating Tuscany has made 14(!) releases, voted in 19 new
> > committers, survived conflicts, formed its PPMC, learned how to govern
> > itself, resolved licensing issues and an active community continues to grow
> > around Tuscany.
> >
> > The community vote for graduation can be found on the Tuscany dev list at:
> >        http://www.mail-archive.com/tuscany-dev@.../msg24675.html
> >
> > We have prepared the resolution below to be presented for consideration at
> > the upcoming Board meeting.
> >
> > We invite everyone to vote to approve this proposal.
> >
> > Many thanks,
> >
> >    ...ant
> >
> > Establish the Apache Tuscany project:
> >
> >        WHEREAS, the Board of Directors deems it to be in the best
> >         interests of the Foundation and consistent with the Foundation's
> >         purpose to establish a Project Management Committee charged with
> >         the creation and maintenance of open-source software that
> >         simplifies the development and deployment of service oriented
> >         applications and provides a managed service-oriented runtime
> >         based on the standards defined by the OASIS OpenCSA group,
> >         for distribution at no charge to the public.
> >
> >        NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> >         Committee (PMC), to be known as the "Apache Tuscany Project",
> >         be and hereby is established pursuant to Bylaws of the
> >         Foundation; and be it further
> >
> >        RESOLVED, that the Apache Tuscany Project be and hereby is
> >         responsible for the creation and maintenance of software
> >         related to Apache Tuscany;
> >         and be it further
> >
> >        RESOLVED, that the office of "Vice President, Apache Tuscany" be
> >         and hereby is created, the person holding such office to
> >         serve at the direction of the Board of Directors as the chair
> >         of the Apache Tuscany Project, and to have primary responsibility
> >         for management of the projects within the scope of
> >         responsibility of the Apache Tuscany Project; and be it further
> >
> >        RESOLVED, that the persons listed immediately below be and
> >         hereby are appointed to serve as the initial members of the
> >         Apache Tuscany Project:
> >
> >             Adriano Crestani            <adrianocrestani at apache dot org>
> >             Andrew Borley               <ajborley at apache dot org>
> >             Andy Grove                   <agrove at apache dot org>
> >             ant elder                       <antelder at apache dot org>
> >             Brady Johnson              <bjohnson at apache dot org>
> >             Frank Budinsky             <frankb at apache dot org>
> >             Ignacio Silva-Lepe          <isilval at apache dot org>
> >             Jean-Sebastien Delfino   <jsdelfino at apache dot org>
> >             kelvin goodson               <kelvingoodson at apache dot org>
> >             Luciano Resende           <lresende at apache dot org>
> >             Mike Edwards               <edwardsmj at apache dot org>
> >             Pete Robbins                <robbinspg at apache dot org>
> >             Raymond Feng              <rfeng at apache dot org>
> >             Simon Laws                  <slaws at apache dot org>
> >             Simon Nash                  <nash at apache dot org>
> >             Venkata Krishnan          <svkrish at apache dot org>
> >
> >        NOW, THEREFORE, BE IT FURTHER RESOLVED, that Ant Elder
> >         be appointed to the office of Vice President, Apache Tuscany, to
> >         serve in accordance with and subject to the direction of the
> >         Board of Directors and the Bylaws of the Foundation until
> >         death, resignation, retirement, removal or disqualification,
> >         or until a successor is appointed; and be it further
> >
> >        RESOLVED, that the Apache Tuscany Project be and hereby
> >         is tasked with the migration and rationalization of the Apache
> >         Incubator Tuscany podling; and be it further
> >
> >        RESOLVED, that all responsibilities pertaining to the Apache
> >         Incubator Tuscany podling encumbered upon the Apache Incubator
> >         Project are hereafter discharged.
> >
>
>
> --
> Paul Fremantle
> Co-Founder and VP of Technical Sales, WSO2
> OASIS WS-RX TC Co-chair
>
> blog: http://pzf.fremantle.org
> paul@...
>
> "Oxygenating the Web Service Platform", www.wso2.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@...
> For additional commands, e-mail: general-help@...
>
>

--
Davanum Srinivas :: http://davanum.wordpress.com

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

[robert burrell donkin-2]

On 10/12/07, ant elder <ant.elder@...> wrote:

<snip>

some grammar queries

> Establish the Apache Tuscany project:
>
>        WHEREAS, the Board of Directors deems it to be in the best
>         interests of the Foundation and consistent with the Foundation's
>         purpose to establish a Project Management Committee charged with
>         the creation and maintenance of open-source software that
                                                                 ^^^^^^^
http://www.apache.org/foundation/records/certificate.html uses open source

>         simplifies the development and deployment of service oriented

              ^^^^^^^^^^
>         applications and provides a managed service-oriented runtime

 ^^^^^^^^^

which is right?

- robert

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

[robert burrell donkin-2]

<snip>

On 10/12/07, ant elder <ant.elder@...> wrote:

> Establish the Apache Tuscany project:
>
>        WHEREAS, the Board of Directors deems it to be in the best
>         interests of the Foundation and consistent with the Foundation's
>         purpose to establish a Project Management Committee charged with
>         the creation and maintenance of open-source software that
>         simplifies the development and deployment of service oriented
>         applications and provides a managed service-oriented runtime
>         based on the standards defined by the OASIS OpenCSA group,
            ^^^^
>         for distribution at no charge to the public.

1. is 'based' the right term?

2. grrr SOA! i'm unclear what this really means in this case. though
i've been following the lists for quite a while now, i still find it
really hard to understand the target use cases are for tuscany. is it
possible to accurately describe what what tuscany is used for without
using buzzwords?

3. is the definition a little ambiguous?

((simplifies the development and deployment of service oriented
applications) and (provides a managed service-oriented runtime))
based on the standards defined by the OASIS OpenCSA group

vs

(simplifies the development and deployment of service oriented
applications) and ((provides a managed service-oriented runtime)
based on the standards defined by the OASIS OpenCSA group)

4. does tuscany really want to limit itself to a single standard? if
another organisation created standards in this same area, would
tuscany really wish to exclude itself from creating an implementation?

- robert

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

[Mike Edwards-5]

Folks,

Comments inline...

Robert Burrell Donkin wrote:

> <snip>
>
> On 10/12/07, ant elder <ant.elder@...> wrote:
>
>> Establish the Apache Tuscany project:
>>
>>        WHEREAS, the Board of Directors deems it to be in the best
>>         interests of the Foundation and consistent with the Foundation's
>>         purpose to establish a Project Management Committee charged with
>>         the creation and maintenance of open-source software that
>>         simplifies the development and deployment of service oriented
>>         applications and provides a managed service-oriented runtime
>>         based on the standards defined by the OASIS OpenCSA group,
>             ^^^^
>>         for distribution at no charge to the public.
>
> 1. is 'based' the right term?
>

We discussed this within the Tuscany project.  The intent is to say that
Tuscany will implement the SCA & SDO standards, without being limited to
them.  Tuscany today goes beyond what is in the standards - for example,
  there are implementations of things like XQuery, JSON, Ruby, none of
which are (yet) in the standards.  "Based on" is intended to give the
flavour of implementing the standards and also going further.


> 2. grrr SOA! i'm unclear what this really means in this case. though
> i've been following the lists for quite a while now, i still find it
> really hard to understand the target use cases are for tuscany. is it
> possible to accurately describe what what tuscany is used for without
> using buzzwords?
>

I must admit that I hadn't perceived "SOA" as a buzzword.  I agree that
it is a deliberately imprecise term, but that it does describe a general
architectural approach to building applications.  Do you think we need
to build some paragraphs here that describe what service-oriented
architecture means?

As for the target use cases for Tuscany - it is when you want to build a
distributed application from independently acting, loosely coupled
service components, which may be written using any of a range of
programming technologies (Java, C++, Ruby, PHP....) and which may be
connected using any of a range of communication technologies (Web
services, REST, JMS, RMI-IIOP....).

> 3. is the definition a little ambiguous?
>
> ((simplifies the development and deployment of service oriented
> applications) and (provides a managed service-oriented runtime))
> based on the standards defined by the OASIS OpenCSA group
>
> vs
>
> (simplifies the development and deployment of service oriented
> applications) and ((provides a managed service-oriented runtime)
> based on the standards defined by the OASIS OpenCSA group)
>

It's the former and I think we can improve the text by adding a comma
before "based".

> 4. does tuscany really want to limit itself to a single standard? if
> another organisation created standards in this same area, would
> tuscany really wish to exclude itself from creating an implementation?
>

No, Tuscany does not want to limit itself - indeed it already uses other
standards like some of the WS-* standards.  We had thought that the
wording above didn't imply any limitation, but if we're mistaken in that
view, perhaps we need to add some explicit words like:

"...based on but not limited to..."

> - robert
>


Yours,  Mike.

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

[Matthieu Riou-5]

+1 on graduation, with the two edits proposed by Mike (comma before "based"
and "on but not limited to"). SOA is often used as a buzzword but it's also
unfortunately the only acronym available for that style of architecture.

Good luck guys!

On 10/12/07, Mike Edwards <mike.edwards.inglenook@...> wrote:

>
> Folks,
>
> Comments inline...
>
> Robert Burrell Donkin wrote:
> > <snip>
> >
> > On 10/12/07, ant elder <ant.elder@...> wrote:
> >
> >> Establish the Apache Tuscany project:
> >>
> >>        WHEREAS, the Board of Directors deems it to be in the best
> >>         interests of the Foundation and consistent with the
> Foundation's
> >>         purpose to establish a Project Management Committee charged
> with
> >>         the creation and maintenance of open-source software that
> >>         simplifies the development and deployment of service oriented
> >>         applications and provides a managed service-oriented runtime
> >>         based on the standards defined by the OASIS OpenCSA group,
> >             ^^^^
> >>         for distribution at no charge to the public.
> >
> > 1. is 'based' the right term?
> >
>
> We discussed this within the Tuscany project.  The intent is to say that
> Tuscany will implement the SCA & SDO standards, without being limited to
> them.  Tuscany today goes beyond what is in the standards - for example,
>   there are implementations of things like XQuery, JSON, Ruby, none of
> which are (yet) in the standards.  "Based on" is intended to give the
> flavour of implementing the standards and also going further.
>
>
> > 2. grrr SOA! i'm unclear what this really means in this case. though
> > i've been following the lists for quite a while now, i still find it
> > really hard to understand the target use cases are for tuscany. is it
> > possible to accurately describe what what tuscany is used for without
> > using buzzwords?
> >
>
> I must admit that I hadn't perceived "SOA" as a buzzword.  I agree that
> it is a deliberately imprecise term, but that it does describe a general
> architectural approach to building applications.  Do you think we need
> to build some paragraphs here that describe what service-oriented
> architecture means?
>
> As for the target use cases for Tuscany - it is when you want to build a
> distributed application from independently acting, loosely coupled
> service components, which may be written using any of a range of
> programming technologies (Java, C++, Ruby, PHP....) and which may be
> connected using any of a range of communication technologies (Web
> services, REST, JMS, RMI-IIOP....).
>
> > 3. is the definition a little ambiguous?
> >
> > ((simplifies the development and deployment of service oriented
> > applications) and (provides a managed service-oriented runtime))
> > based on the standards defined by the OASIS OpenCSA group
> >
> > vs
> >
> > (simplifies the development and deployment of service oriented
> > applications) and ((provides a managed service-oriented runtime)
> > based on the standards defined by the OASIS OpenCSA group)
> >
>
> It's the former and I think we can improve the text by adding a comma
> before "based".
>
> > 4. does tuscany really want to limit itself to a single standard? if
> > another organisation created standards in this same area, would
> > tuscany really wish to exclude itself from creating an implementation?
> >
>
> No, Tuscany does not want to limit itself - indeed it already uses other
> standards like some of the WS-* standards.  We had thought that the
> wording above didn't imply any limitation, but if we're mistaken in that
> view, perhaps we need to add some explicit words like:
>
> "...based on but not limited to..."
>
> > - robert
> >
>
>
> Yours,  Mike.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@...
> For additional commands, e-mail: general-help@...
>
>

[Bertrand Delacretaz]

On 10/12/07, Matthieu Riou <matthieu@...> wrote:
> +1 on graduation, with the two edits proposed by Mike...

+1 for graduation, with these two edits.

-Bertrand

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

[robert burrell donkin-2]

On 10/12/07, Mike Edwards <mike.edwards.inglenook@...> wrote:
> Robert Burrell Donkin wrote:
> > <snip>
> >
> > On 10/12/07, ant elder <ant.elder@...> wrote:

<snip>

> > 2. grrr SOA! i'm unclear what this really means in this case. though
> > i've been following the lists for quite a while now, i still find it
> > really hard to understand the target use cases are for tuscany. is it
> > possible to accurately describe what what tuscany is used for without
> > using buzzwords?
> >
>
> I must admit that I hadn't perceived "SOA" as a buzzword. I agree that
> it is a deliberately imprecise term, but that it does describe a general
> architectural approach to building applications.  Do you think we need
> to build some paragraphs here that describe what service-oriented
> architecture means?

the problem with meta-architectures is that most have no canonical
definition or description and so the same term means different things
to different people. once a meta-architecture gets hot, it leads to
outbreaks of Humpty Dumpty syndrome - "When I use a word, it means
exactly what I intend it to mean, no more, no less.". IMHO SOA has now
reached this stage.

> As for the target use cases for Tuscany - it is when you want to build a
> distributed application from independently acting, loosely coupled
> service components, which may be written using any of a range of
> programming technologies (Java, C++, Ruby, PHP....) and which may be
> connected using any of a range of communication technologies (Web
> services, REST, JMS, RMI-IIOP....).
                  ^^^^^
some would say that SOA excludes REST. perhaps tuscany may (one day)
want to wire up ROA as well as SOA ;-)

anyway, tuscany simplifies the development, deployment and management
of distributed applications composed of independently acting, loosely
coupled, linguistically hetrogenous components connected using any of
a wide range of communication technologies

maybe it would be better to state this unambiguously rather than
relying on the correct interpretation of an ill-defined buzzword

<snip>

> > 4. does tuscany really want to limit itself to a single standard? if
> > another organisation created standards in this same area, would
> > tuscany really wish to exclude itself from creating an implementation?
> >
>
> No, Tuscany does not want to limit itself - indeed it already uses other
> standards like some of the WS-* standards.  We had thought that the
> wording above didn't imply any limitation, but if we're mistaken in that
> view, perhaps we need to add some explicit words like:
>
> "...based on but not limited to..."

'based on' worries me - the language seems to me to be uncomfortably
close to  'derived from'. it's also a long sentence. perhaps something
like

"Tuscany will implement relevant open standards including ..."

would be better

- robert

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

[ant elder]

On 10/13/07, Robert Burrell Donkin <robertburrelldonkin@...> wrote:

>
> On 10/12/07, Mike Edwards <mike.edwards.inglenook@...> wrote:
> > Robert Burrell Donkin wrote:
> > > <snip>
> > >
> > > On 10/12/07, ant elder <ant.elder@...> wrote:
>
> <snip>
>
> > > 2. grrr SOA! i'm unclear what this really means in this case. though
> > > i've been following the lists for quite a while now, i still find it
> > > really hard to understand the target use cases are for tuscany. is it
> > > possible to accurately describe what what tuscany is used for without
> > > using buzzwords?
> > >
> >
> > I must admit that I hadn't perceived "SOA" as a buzzword. I agree that
> > it is a deliberately imprecise term, but that it does describe a general
> > architectural approach to building applications.  Do you think we need
> > to build some paragraphs here that describe what service-oriented
> > architecture means?
>
> the problem with meta-architectures is that most have no canonical
> definition or description and so the same term means different things
> to different people. once a meta-architecture gets hot, it leads to
> outbreaks of Humpty Dumpty syndrome - "When I use a word, it means
> exactly what I intend it to mean, no more, no less.". IMHO SOA has now
> reached this stage.
>
> > As for the target use cases for Tuscany - it is when you want to build a
> > distributed application from independently acting, loosely coupled
> > service components, which may be written using any of a range of
> > programming technologies (Java, C++, Ruby, PHP....) and which may be
> > connected using any of a range of communication technologies (Web
> > services, REST, JMS, RMI-IIOP....).
>                   ^^^^^
> some would say that SOA excludes REST. perhaps tuscany may (one day)
> want to wire up ROA as well as SOA ;-)
>
> anyway, tuscany simplifies the development, deployment and management
> of distributed applications composed of independently acting, loosely
> coupled, linguistically hetrogenous components connected using any of
> a wide range of communication technologies
>
> maybe it would be better to state this unambiguously rather than
> relying on the correct interpretation of an ill-defined buzzword
>
> <snip>
>
> > > 4. does tuscany really want to limit itself to a single standard? if
> > > another organisation created standards in this same area, would
> > > tuscany really wish to exclude itself from creating an implementation?
> > >
> >
> > No, Tuscany does not want to limit itself - indeed it already uses other
> > standards like some of the WS-* standards.  We had thought that the
> > wording above didn't imply any limitation, but if we're mistaken in that
> > view, perhaps we need to add some explicit words like:
> >
> > "...based on but not limited to..."
>
> 'based on' worries me - the language seems to me to be uncomfortably
> close to  'derived from'. it's also a long sentence. perhaps something
> like
>
> "Tuscany will implement relevant open standards including ..."
>
> would be better
>
> - robert

So bringing together all the comments so far gives something like:

...establish a Project Management Committee charged with the
creation and maintenance of open-source software that simplifies
the development, deployment and management of distributed
applications composed of independently acting, loosely coupled,
linguistically hetrogenous components connected using any of a
wide range of communication technologies. This software will implement
relevant open standards including, but not limited to, standards defined
by the OASIS OpenCSA group, for distribution at no charge to the public.

I'll wait a while to see if there's any further comments over this and if
not restart a clean vote thread.

   ...ant

[robert burrell donkin-2]

On 10/13/07, ant elder <ant.elder@...> wrote:
> On 10/13/07, Robert Burrell Donkin <robertburrelldonkin@...> wrote:

<snip>

> So bringing together all the comments so far gives something like:
>
> ...establish a Project Management Committee charged with the
> creation and maintenance of open-source software that simplifies
> the development, deployment and management of distributed
> applications composed of independently acting, loosely coupled,
> linguistically hetrogenous components connected using any of a
> wide range of communication technologies. This software will implement
> relevant open standards including, but not limited to, standards defined
> by the OASIS OpenCSA group, for distribution at no charge to the public.

the concatination makes last sentence is a little ambiguous. might be
better to either start another sentence

> This software will implement
> relevant open standards including, but not limited to, standards defined
> by the OASIS OpenCSA group. This software will be distribution at no charge to the public.

or move the phrase next to open source:

> ...establish a Project Management Committee charged with the
> creation and maintenance of open-source software for distribution at no charge to the public

maybe someone on the board could jump with guideance

- robert

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

[robert burrell donkin-2]

On 10/13/07, Robert Burrell Donkin <robertburrelldonkin@...> wrote:

> On 10/13/07, ant elder <ant.elder@...> wrote:
> > On 10/13/07, Robert Burrell Donkin <robertburrelldonkin@...> wrote:
>
> <snip>
>
> > So bringing together all the comments so far gives something like:
> >
> > ...establish a Project Management Committee charged with the
> > creation and maintenance of open-source software that simplifies
> > the development, deployment and management of distributed
> > applications composed of independently acting, loosely coupled,
> > linguistically hetrogenous components connected using any of a
> > wide range of communication technologies. This software will implement
> > relevant open standards including, but not limited to, standards defined
> > by the OASIS OpenCSA group, for distribution at no charge to the public.
>
> the concatination makes last sentence is a little ambiguous. might be
> better to either start another sentence

it's wonderfully ironic that my grammar critique is not a sentence (or
at least, not in english)

- robert

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

[Noel J. Bergman]

Robert Burrell Donkin wrote:

> "Tuscany will implement relevant open standards including ..."

As previously noted, the core standards for Tuscany are SCA and SDO, with
others as desired by the community.  What distinguishes Tuscany from
ServiceMix from Synapse is:

  Tuscany: SCA / SDO
  ServiceMix: JBI
  Synapse: WSDL / SOAP

        --- Noel



---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...