Issue - 262 - Use of CamelCase Conceptual descriptive terms

[ws-bpel issues list editor <peter.furniss@erebor.co.uk>]

This issue has been added to the wsbpel issue list with a status of "received". The status will be changed to "open" if a motion to open the issue is proposed and that motion is approved by the TC. A motion could also be proposed to close it without further consideration. Otherwise it will remain as "received".

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 - 262 - Use of CamelCase Conceptual descriptive terms

Status: received
Date added: 14 Apr 2006
Date submitted: 11 April 2006
Submitter: Prasad Yendluri
Description: Chapter 9 of the specification uses the CamelCase form "CorrelationSet" to refer to the "conceptual term" in addition to the Syntactic element form <CorrelationSet> and the free form text with separate terms "correlation set".  There were arguments for and against removal of the camel case form and using the syntactic element form and the free form text kinds only, though out.

There are also other such special terms such as FaultHandler and EventHandler that have the same issue associated with them. Any resolution should be applied uniformly to all applicable special terms.
Submitter's proposal:

(1) Use only the syntactic element and free form text kinds only throughout.

If the above is not done then

(2) Add a clear explanation that explains the use of the CamelCase forms in the "2. Notational Conventions" section.
Changes: 14 Apr 2006 - new issue

---

To comment on this issue (including whether it should be accepted), please follow-up to this announcement on the wsbpel@lists.oasis-open.org list (replying to this message should automatically send your message to that list), or ensure the subject line as you send it starts "Issue - 262 - [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 - 262 - 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).