Issue - 240 - Glossary term to encompass variable type, element, messageType

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 - 240 - Glossary term to encompass variable type, element, messageType
Status: received

Date added: 7 Dec 2005

Categories: Specification editing

Date submitted: 07 December 2005

Submitter: Danny van der Rijn

Description: We need a term that we can use in the spec to encompass the possible 
things that a variable can be declared as:  type, element, messageType.  
This term should be defined in the text (and in a Glossary if we ever 
have one), and used liberally throughout the spec where we use verbiage 
that is ambiguous.

Changes: 7 Dec 2005 - 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 - 240 - [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 - 240 - 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).