RE: [business-transaction] Towards a single standards platformforbusiness transaction management and application coordination

[Mark Potts <mark.potts@talkingblocks.com>]

Krishna

I thought this was what we were doing?

and of course don't forget the interoperability profiles that need to be determined in the time between the consolidated specs!


Cheers

> -----Original Message-----
> From: Krishna Sankar [mailto:ksankar@cisco.com]
> Sent: Friday, August 09, 2002 12:42 PM
> To: 'Alastair Green'; business-transaction@lists.oasis-open.org
> Subject: RE: [business-transaction] Towards a single 
> standards platform
> forbusiness transaction management and application coordination
> 
> 
> Alastair,
> 
> 	I have a proposition. (Sorry for the duplicate msg to BT-Spec!)
> 
> 	Would it be much easier if we take six months and publish spec
> in every Web Services area (orchestration, transaction, security,...)
> per organization or combinations of organizations ? E.g.. IBM/MS/BEA,
> IBM/HP, HP/IONA/BEA, .... After everybody has tried all 
> combinations of
> politics and exhaustively published all combinations of web services
> specs ( a rough calculation - about 8 companies, at least 3 companies
> organize to develop one spec - i.e. a minimum three companies 
> can stand
> each other long enough to produce a version of a spec), 4 
> areas, yields
> 8C3 X 4 = ((8 * 7 * 6) * 4)/(1*2*3)) = 56 * 4 = 224 documents), we can
> then submit all of them to any organization which can then create 5
> cohesive and coherent specs out of them. 
> 
> 	BTW, we also will need a registry to dole out specification
> names, already we are into names like BPEL4WS, which is a good number
> for an auto plate but not a good name for a specification !
> 
> 	Any takers ?
> 
> Cheers and have a nice weekend
> 
> 
> |  -----Original Message-----
> |  From: Alastair Green [mailto:alastair.green@choreology.com] 
> |  Sent: Friday, August 09, 2002 12:27 PM
> |  To: business-transaction@lists.oasis-open.org
> |  Subject: [business-transaction] Towards a single standards 
> |  platform for business transaction management and application 
> |  coordination
> |  
> |  
> |  Choreology Ltd supports the formation of usable and valid 
> |  specifications 
> |  which will enable interoperable application coordination.
> |  
> |  OASIS BTP is one such specification; it appears that 
> |  WS-Transaction and 
> |  WS-Coordination, due to be released soon by Microsoft, IBM 
> |  and BEA, are 
> |  similar in their intent and coverage.
> |  
> |  We are committed to providing this kind of facility to our 
> |  end-user and 
> |  software vendor customers. Our Cohesions 1.0 (TM) product 
> |  will enable 
> |  application coordination using Web Services, and in other service 
> |  deployment and infrastructure environments typical in the 
> |  modern enterprise.
> |  
> |  We intend to work with other vendors to evolve a standards 
> |  platform for 
> |  business transaction management for application coordination, 
> |  incorporating the best of all past, current and future initiatives.
> |  
> |  We want to see a single standards platform in this field 
> |  that has the 
> |  backing of the whole software industry and its customers. 
> |  Our product 
> |  will reflect that goal.
> |  
> |  -- 
> |  
> |  Alastair Green
> |  CEO, Choreology Ltd
> |  
> |  Cohesions 1.0 (TM)
> |  Business transaction management software for application 
> coordination
> |  
> |  +44 207.670.1679
> |  +44 207.670.1785 (fax)
> |  
> |  
> |  
> |  ----------------------------------------------------------------
> |  To subscribe or unsubscribe from this elist use the subscription
> |  manager: <http://lists.oasis-open.org/ob/adm.pl>
> |  
> 
> 
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>
>