OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

bpel4people message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: NEW ISSUE: Task Priority is underspecified


Title: NEW ISSUE: Task Priority is underspecified

TARGET: WS-HT, General
Description:
The task priority is a user-centric property and therefore should be displayable in a human-readable form. Task information is rendered by various applications (task-list-UIs, task-description-Uis, task-UIs), which are decoupled and may even have different vendors. These applications need a common convention how to interpret the priority and how to render it to the end user. Currently the WS-HT specification defines it too loosely just as an integer, which limits the interoperability. Imagine that your applicatiosn receives the value 51435 - what would you display in the UI?

"priority: This element is used to specify the priority of the task. It is an optional element which value is an integer expression. If not present, the priority of the task is unspecified. 0 is the highest priority, larger numbers identify lower priorities. The result of the expression evaluation is of type xsd:integer. The expressionLanguage attribute specifies the language used in the expression. The attribute is optional. If not specified, the default language as inherited from the closest enclosing element that specifies the attribute is used

There is also ambiguity in the current specification about the optional nature of the priority - what is the query behaviour for tasks without priority and what integer correspond to the 'unspecified' value (this should be returned by the getTaskPriority operation).

Proposal:
1. Define an enumeration of 4 fixed integer values and define them as Very High, High, Normal, Low. These MUST be understood by compatible clients. As it would be good to re-use an existing standard, I propose to take the codes from the UN/EDIFACT task priority definition (
http://www.unece.org/trade/untdid/d07b/tred/tred4037.htm) and probably extend them. Additional extension would be introducing code 7 with value Low.

2. Define the priority as a mandatory property with default value Normal.
Detailed technical proposal will follow if the issue is opened.

smime.p7s



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]