OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

business-transaction message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: RE: Action items and sub-committee list


Title: RE: Action items and sub-committee list
Hi,
 
    I could lead #3:Security Requirements. But I am not sure if I am "officially" on the group as a member.
 
cheers
-----Original Message-----
From: Tina Tuan [mailto:ttuan@crosslogix.com]
Sent: Friday, March 16, 2001 10:15 AM
To: 'Pal Takacsi-Nagy'; business-transaction@lists.oasis-open.org
Subject: RE: Action items and sub-committee list

I am interested in participating in #2: security.

Thanks,
Tina Tuan
www.CrossLogix.com
direct: (650) 596-5918
main: (650) 596-5757
2200 Bridge Parkway, Suite 203
Redwood Shores, CA 94065


-----Original Message-----
From: Pal Takacsi-Nagy [mailto:pal.takacsi@bea.com]
Sent: Wednesday, March 14, 2001 2:37 PM
To: business-transaction@lists.oasis-open.org
Subject: Action items and sub-committee list


Here is a summary of what we agreed to yesterday:

Scope of the BTP work:
----------------------

0, What's the set of trans. model supported by BTP
1, Legacy TP integration
2, Extensible transaction properties (as proposed by Choreology)
3, Security (only define requirements for)
4, Reliable messaging (only define assumptions for the underlying messaging
system)
5, Collaboration (make sure that BTP is/can be aligned with collaboration
layer standards)
6, What's the reason for BTP/ where it applies
7, Complexity of BTP: it shoudl be simple
8, Use cases to better understand scope
9, What's the end result of the committee's work:
        - protocol, system messages
        - architecture examples of various target implementations
        - actors
10, Services of coordinator/trans. service
11, Technical terminology
12, Interoperability (vote taken that portability is out of scope)

Timeline:
---------

- weekly conf. calls 8-9 THR PST (no conf. call this week)
- 5 face-to-face counting 3/13, 1 per month, 4 left
2 East (Sequioa 4/23, Bowstreet 6/18), 1 West (hosted by BEA 7/18-19), 1
Europe (5/17-18)


4/1 Requirements done
5/31 1st draft of BTP spec
7/31 v 1.0 available for vote in OASIS

Sub-committees:
---------------

1, Messaging/binding, system messages
2, Security (liason)
3, Requirements, Use Cases, Terminology
   Transaction models -> protocol model
4, Requirements - Use Cases
5, Interoperability/Conformance testing
7, Specification doc
8, Workflow (liason)

Please express your interest in participating in one or more sub-committees
via e-mail
by 3/16 EOB. At the 3/22 conference call we will finalize the composition of
the sub-committees. Also, don't feel precluded from starting to work on
areas of your interest and posting ideas on the mailing-list, before the
sub-committees get finalized.

Thanks: Pal






------------------------------------------------------------------
To unsubscribe from this elist send a message with the single word
"unsubscribe" in the body to: business-transaction-request@lists.oasis-open.org



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Powered by eList eXpress LLC