This list covers real and perceived errors and omissions in the Business Transaction Protocol Committee Specification 1.0, as distinct from suggested addtitions and enhancements (which go in the extensions and enhancements list).
Members of the committee should comment on these issues by sending to the bt specification list, preferably as a follow-up to the original announcement of the issue (to keep the thread connection). Members of the committee can submit new issues by sending to Peter Furniss, Choreology who will assign a number, add an entry and announce the issue on the bt specification list.
Procedures for the addition and discussion of issues on this list may be changed shortly
Issue numbers are m.1, m.2 etc to distinguish them from the original, pre-1.0 issues, and the extensions issues (x.1, x.2 etc).
To update your oasis mailing list subscriptions, go to http://lists.oasis-open.org/ob/adm.pl.
| Number | Name | Category | status |
|---|---|---|---|
| Issue m.1 | HAZARD after receiving CANCEL | minor technical | new |
| Issue m.2 | CONFIRMED element should be confirm-received | minor technical | new |
| Issue m.3 | CONFIRM_ONE_PHASE against autonomous confirm | minor technical | new |
Status category is shown in headers :
green=closed, one way or another,
teal=deferred (closed for 1.0 - transferred to extensions and additions list),
maroon=solution proposed,
fuchsia=voting,
orange=depends on another issue,
red=new, open
The error occurs in both the schema and specification (section 10.2.13, line 3700)
Original reports: Mark Potts, 9 Jul 2002 Alex Ceponkus, 10 Jul 2002
Discussion threads in email archive:
Announcement, 17 Oct 2002
This imposes restrictions on an implementation, as it may be difficult to avoid the messages crossing inside
the superior communications mechanisms.
Suggested solution:
Allow a transition to S1 in the decide to confirm one-phase / H1 cell.
Discussion threads in email archive:
Announcement, 17 Oct 2002
This file last updated 14:52 17 Oct 2002 (UTC)