Issue - 161 - Explicit conformance statements

This issue has been added to the wsbpel issue list with a status of "received".
The status will be changed to "open" if the TC accepts it as identifying a bug in the spec or 
decides it should be accepted specially. Otherwise it will be closed without further consideration (but
will be marked as "Revisitable")

The issues list is posted as a Technical Committee document to the 
OASIS WSBPEL TC pages
on a regular basis. The current edition, as a TC document, is the most recent version of 
the document entitled  in the 
"Issues" folder of the WSBPEL TC document list
- the next posting as a TC document will include this issue.
The list editor's working copy, which will normally include an issue when it is announced, is available at 
this constant URL.

Issue - 161 - Explicit conformance statements
Status: received

Date added: 8 Sep 2004

Categories: Specification editing

Date submitted: 27 August 2004

Submitter: Tony Fletcher

Document: Specification working draft 1.39, Chapter 13.3.3, "Invoking a Compensation Handler".

Description: Add an explicit set of conformance statements, preferably in a conformance section, 
to the specification for 'BPEL'.  The rationale and a draft proposal is given in the
document attached to
Tony Fletcher, 27 Aug 2004

Resolving this issue will not lead to the addition of any new features..  However, it will enhance and clarify the text in a significant manner and therefore is worth tackling at this time.

The process of adding such a conformance section will cause us to think about and address the following questions:

For what sort of 'things' can conform to the BPEL specification?

For each type of 'thing' for which conformance can be claimed, what precisely does that thing have to be / do / not do to be conformant.
 

Links: Tony Fletcher, 24 Aug 2004     
Yaron Y. Goland, 26 Aug 2004     
Tony Fletcher, 26 Aug 2004     
Tony Fletcher, 27 Aug 2004     
Yaron Y. Goland, 27 Aug 2004

Changes: 8 Sep 2004 - new issue

To comment on this issue (including whether it should be accepted), please follow-up to this announcement on the 
 list (replying to this message should automatically send your message to that list), or ensure
the subject line as you send it starts "Issue - 161 - [anything]" or is a reply
to such a message. If you want to formally propose a resolution to an open issue, please start the subject line 
"Issue - 161 - Proposed resolution", without any Re: or similar.

To add a new issue, 
see the issues procedures document (but the address for new issue submission is the sender of this announcement).