| From | Sent On | Attachments |
|---|---|---|
| ws-bpel issues list editor | Sep 8, 2003 1:17 pm |
| Subject: | Issue - 61 - process priority | |
|---|---|---|
| From: | ws-bpel issues list editor (pete...@choreology.com) | |
| Date: | Sep 8, 2003 1:17:21 pm | |
| List: | org.oasis-open.lists.wsbpel | |
This issue has been added to the wsbpel issue list. 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 document with the title in the "Issues" folder of the WSBPEL TC document list - the next posting 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 - 61 - process priority
Status: open Date added: 8 Sep 2003 Submitter: Sid Askary Date submitted: 04 September 2003 Since we are dealing with an execution language, the question of runtime priority comes to mind. One could imagine an additional process property. While there may be other methods, this could explicitly be expressed as an additional binary attribute to the process element followed, conditionally, by a new element.
a)
<process name="ncname" targetNamespace="uri" queryLanguage="anyURI"? . . prioritize="yes|no"?/>
b)
<priority name="ncname" priorityNumber="anynumber" PriorityNumberBase="anynumber"/>
NOTE: PriorityNumberBase reflects the devisor for PriorityNumber. Alternatively, one could replace the two by a single floating-point fraction. Changes: 8 Sep 2003 - new issue
------------------------------------------------------------------------------
To comment on this issue, please follow-up to this announcement on the wsb...@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 - 61 - [anything]" or is a reply to such a message.
To add a new issue, see the issues procedures document.





