As per me previous mail I propose that we start to think about implementing
an OASIS compliant version of Tuscany SCA Java. We can't declare OASIS
compliance until the specifications are actually done but I think we need to
start soon so that we are ready. Specifically this means creating two
development streams;
One (in a branch with a 1.x-SNAPSHOT label) to support our existing OSOA
code base
One (in trunk with a 2.x-SNAPSHOT label) to build support for the OASIS
versions of the SCA specifications
What actually goes in trunk to kick off the OASIS development is the subject
of further discussion.
Here's my +1
Simon
