BTP issues by status and category

This is an alternative ordering (by status, and then by category) of the OASIS BTP issue list.
NumberNameCategoryStatus
Issue 7SOAP RPCtechnicalchange agreed
Issue 8Deaf clientstechnicalchange agreed
Issue 24The apparent complexity of model is too great.technicalresolved
Issue 25Clarity needed between atomic and cohesiontechnicalresolved
Issue 26Multiple conformance points should be defined.technicalresolved
Issue 29Redirectiontechnicalchange agreed
Issue 30Assume that coordinators are potential sub-coordinators.technicalchange agreed
Issue 47Handle and Identifiertechnicalresolved
Issue 49type of Handletechnicalresolved
Issue 50Default parameter valuestechnicalchange agreed
Issue 72Scope of Contexttechnicalresolved
Issue 75Ensure that all the participants of a BT are enrolled.technicalresolved
Issue 79Normalising the message settechnicalchange agreed
Issue 87Conformance Leveltechnicalchange agreed
Issue 88Cohesion vs Atomictechnicalresolved
Issue 89J2EE Inter operability - JMS short circuittechnicalresolved
Issue 1Format of binding addressesminor technicalchange agreed
Issue 5Reference to SOAP should be SOAP/HTTPminor technicalchange agreed
Issue 10Reflect message compounding in the XML Schemaminor technicalchange agreed
Issue 11Clean up qualifiers in XML Schemaminor technicalchange agreed
Issue 15Negative reply to BEGINminor technicalchange agreed
Issue 16Negative reply to REDIRECTminor technicalchange agreed
Issue 18Response to CONTRADICTION ?minor technicalresolved
Issue 19FAULTs from RESIGNED ?minor technicalchange agreed
Issue 20Resending PREPAREminor technicalchange agreed
Issue 21Multiple Superior:Inferior relationships within a Cohesionminor technicalresolved
Issue 39Resigning Inferiorminor technicalresolved
Issue 46Ordering of A+Bminor technicalchange agreed
Issue 48completion of enrollmentminor technicalresolved
Issue 52Forms of PREPAREminor technicalresolved
Issue 53will or may contradict ?minor technicalresolved
Issue 54hazard formsminor technicalchange agreed
Issue 55CONFIRM_ONE_PHASE and PREPAREminor technicalchange agreed
Issue 60address-as-role or role addressminor technicalchange agreed
Issue 62Names of the relationshipsminor technicalchange agreed
Issue 64can inferior know type of superior ?minor technicalresolved
Issue 65participant as immediate inferior of composer ?minor technicalresolved
Issue 67"Hazard" from autonomous decision ?minor technicalchange agreed
Issue 68(sub)coordinators, (sub)composers with no inferiorsminor technicalresolved
Issue 69prepared subcomposer with unprepared inferiors ?minor technicalresolved
Issue 70Confirm-set evolutionminor technicalresolved
Issue 77Inferior identificationminor technicalchange agreed
Issue 78Addresses used for identificationminor technicalchange agreed
Issue 80CONTEXT_REPLY unnecessary for CONTEXT/cohesionminor technicalchange agreed
Issue 81Resending ENROLminor technicalchange agreed
Issue 82ENROL related to application messageminor technicalchange agreed
Issue 83BTP message related to *part of* application messageminor technicalchange agreed
Issue 84What determines one-shot is usedminor technicalchange agreed
Issue 85Relationship by separate container, not containmentminor technicalchange agreed
Issue 86Reply address on CONTEXT, target address on CONTEXT_REPLYminor technicalchange agreed
Issue 94Target addressing information may be absentminor technicalchange agreed
Issue 95fault data for WrongState FAULTminor technicalchange agreed
Issue 96Reply address on SUPERIOR, INFERIOR_STATUSminor technicalchange agreed
Issue 99PREPARE_INFERIORS and FAULT(InvalidInferior)minor technicalchange agreed
Issue 100Separation of delivery information from payload minor technicalchange agreed
Issue 104RESIGN, disruption and CONFIRM_ONE_PHASEminor technicalchange agreed
Issue 106Free text for all FAULTsminor technicalchange agreed
Issue 108Participant and service identificationminor technicalchange agreed
Issue 109SOAPAction HTTP header must be presentminor technicalchange agreed
Issue 2Partial sentence in BEGUNeditorialchange agreed
Issue 4Glossary is out-of-dateeditorialchange agreed
Issue 6Informative appendices - spec or primereditorialresolved
Issue 9Better explanation of Atom/Cohesioneditorialresolved
Issue 13Definition of Terminatoreditorialresolved
Issue 17Use of word "peer"editorialchange agreed
Issue 27Draft 0.9 is opaque, difficult to read and to understand.editorialresolved
Issue 28Need for state diagrams and explanatory texteditorialresolved
Issue 33Rewordingeditorialchange agreed
Issue 34Superior and Inferioreditorialresolved
Issue 35Superior and Inferior (2)editorialresolved
Issue 36Two-phase cancel - NOTeditorialresolved
Issue 37Acceptable to application or participanteditorialresolved
Issue 38First use of "cohesion"editorialresolved
Issue 40Sending ENROLLEDeditorialresolved
Issue 41ENROL/no-rsp-reqeditorialchange agreed
Issue 42Cohesive Superioreditorialresolved
Issue 43REQUEST_STATUS and STATUS couplingeditorialresolved
Issue 44Decider and other termseditorialresolved
Issue 45Compound addresseseditorialresolved
Issue 51RESIGN and PREPAREDeditorialchange agreed
Issue 56State table texteditorialresolved
Issue 57XML Schema applicable to more than SOAPeditorialchange agreed
Issue 59Interposition description needededitorialresolved
Issue 61Tables of send/receives for each roleeditorialchange agreed
Issue 63Clarify the terminology around actors, roles and relationshipseditorialresolved
Issue 66Event diagram for termination protocoleditorialchange agreed
Issue 71Messages for Terminatoreditorialresolved
Issue 73ACID relaxation in overvieweditorialresolved
Issue 74WrongState from CONFIRM_ONE_PHASEeditorialchange agreed
Issue 76Need for explanatory materialeditorialresolved
Issue 97Version identification on xml namespaceseditorialchange agreed
Issue 98MIME-Version should not be HTTP headereditorialchange agreed
Issue 107Reply to CONFIRM_TRANSACTION if all is okeditorialchange agreed
Issue 3Reference to "Full Superior"minor editorialchange agreed
Issue 12Minor editorialsminor editorialchange agreed
Issue 14Minor editorialsminor editorialchange agreed
Issue 32Italics for first use of "Business Transaction"minor editorialresolved
Issue 58Minor editorialsminor editorialchange agreed
Issue 101Identifiers and addresses in received messagesminor technicaldeferred
Issue 102Is entity identity modification to be allowed within BTP.minor technicaldeferred
Issue 103CONTEXT used only with application msgs, not with BEGIN, BEGUNminor technicaldeferred
Issue 105Qualifier to allow automatic completion of all-cancelled cohesionsminor technicaldeferred
Issue 110SOAP/HTTP binding should include HTTP/SSLminor technicaldeferred
Issue 90Process Flows and TRX switch formatstechnicalwithdrawn
Issue 91Global state visibility - Cohesionstechnicalwithdrawn
Issue 92Benchmarking Metricstechnicalwithdrawn
Issue 22Lack of accountability reflected from D0.6 to D0.9editorialwithdrawn
Issue 23Lack of minutes to support decisionseditorialwithdrawn
Issue 31Absense of rationale confuses normative text.editorialwithdrawn
Issue 93The Spec leveleditorialwithdrawn

This file last updated 15:33 19 May 2002 (UTC)