[business-transaction] BTP status February 21

[William Z Pope <zpope@pobox.com>]

Here is a fairly concise statement of where the work currently stands.


BTP Status

==========================================================
February 21, 2002
==========================================================

Marketing of BTP
=================
- OMG
  Mark Little
  Tony Fletcher, Peter Furniss, Alastair Green
  Bill Cox
- JavaOne
  BTP: Mark Potts, Mark Little
- Internal Marketing
  - What can be done do assist TC member companies with acceptance of
    BTP?   


Specification
==============
- Version 0.9.2.1 is on the web site.
- Needs the model section.


Primer
=======
- Outline published to list.
- Needs a plan for completion
  - refine outline
  - align with model work
- Gather up available info
  - previous drafts
  - email


Issues
=======
- 104 Issues total
-  51 Open
-  13 with solution proposed
-  40 change agreed or resolved

Issues Open
------------
Starred (*) MAY be closable as duplicates or withdrawn. 
Plussed (+) SHOULD be addressed in the model section. 
  4   Glossary is out-of-date
  9+  Better explanation of Atom/Cohesion
 13+  Definition of Terminator
 21   Multiple Superior:Inferior relationships within a Cohesion
 22*  Lack of accountability reflected from D0.6 to D0.9
 24+  The apparent complexity of model is too great.
 25+  Clarity needed between atomic and cohesion (includes conformance).
 26   Multiple conformance points should be defined.
 27   Draft 0.9 is opaque, difficult to read and understand.
 28   Need for state diagrams and explanatory text
 29   Redirection
 31   Absense of rationale confuses normative text.
 32   Italics for first use of "Business Transaction"
 34   Superior and Inferior
 35   Superior and Inferior (2)
 36   Two-phase cancel - NOT
 37   Acceptable to application or participant
 38   First use of "cohesion"
 42+  Cohesive Superior
 43   REQUEST_STATUS and STATUS coupling
 44   Decider and other terms
 45   Compound addresses
 48   completion of enrollment
 53   will or may contradict?
 56   State table text
 59   Interposition description needed
 61   Tables of send/receives for each role
 63   Clarify the terminology around actors, roles, and relationships
 64   can inferior know type of superior?
 65   participant as immediate inferior of composer
 66   Event diagram for termination protocol
 68   (sub)coordinator, (sub)composers with no inferior
 69   prepared subcomposer with unprepared inferiors?
 70   Confirm-set evolution
 72   Scope of Context
 73+  ACID relaxation overview
 75   Ensure that all the participants of  BT are enrolled.
 76+  Need for explanatory material.
 87*  Conformance Level (duplicate of 26)
 88   Cohesion vs Atomic (conformance levels)
 89   J2EE Interoperability - JMS short circuit
 90   Process Flows and TRX switch formats (specific diagrams needed)
 92*  Benchmarking Metrics (solution proposed - postpone to post 1.0)
 93   The Spec level (required elements and conformance)
 96   Reply address on SUPERIOR, INFERIOR_STATUS
 97   Version identification on xml namespaces
 98   MIME-Version should not be HTTP header
 99   PREPARE_INFERIORS and FAULT (InvalidInferior)
100   Separation of delivery information from payload
101   Identifiers and addresses in received messages.
103   CONTEXT used only with application msgs, not with BEGIN, BEGUN

Issues Solution Proposed
-------------------------
  2   Partial sentence in BEGUN
  3   Reference to "Full Superior"
 15   Negative reply to BEGIN
 16   Negative reply to REDIRECT
 19   FAULTs from RESIGNED
 39   Resigning Inferior
 41   ENROL/no-rsp-req
 50   Default parameter values
 60   address-as-role or role address
 67   "Hazard" from autonomous decision? 
 71   Messages for Terminator
 95   fault data for WrongState FAULT
102   Is entity identity modification to be allowed within BTP.

==========================================================

William Z Pope
zpope@pobox.com