[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: AW: [bpel4people-editors] Forward Progress on BP-16 - Revised Comments
Section 4
==========
Line 1075:
"The name combined with the target namespace of a task element is used to uniquely identify the task definition. "
Change to
"The name combined with the target namespace MUST uniquely identify a task element enclosed in the task definition."
Line 1396:
"For all deadlines if a status is not reached within a certain time then an escalation action, specified using element <escalation>, can be triggered. "
Change to
"For all deadlines if a status is not reached within a certain time then an escalation action, specified using element <escalation>, is triggered. "
Line 1411: keep "MAY"
Line 1432:
"In the case where several reassignment escalations are triggered, the first reassignment (lexical order) will be considered for execution. "
change to
"In the case where several reassignment escalations are triggered, the first reassignment (lexical order) MUST be considered for execution by the WS-HumanTask Processor. "
Line 1436: keep "MAY"
Line 1643:
"People queries that cannot be executed successfully are treated as if they were returning an empty set. "
change to
"People queries that cannot be executed successfully MUST be treated as if they were returning an empty set. "
Line 1646: keep "must" and change to "MUST"
Line 1718: keep "may" and change to "MAY"
Line 1763:
"The name combined with the target namespace of a notification element is used to uniquely identify the notification definition. "
change to
"The name combined with the target namespace MUST uniquely identify a notification in the notification definition. "
Section 7
==========
Line 1981:
"The calling application MAY set values of the following attributes of
the task definition:"
change to
"The WS-HumanTask Parent MAY set values of the following attributes of
the task definition"
Line 1998:
"that the parent application MUST use to send all protocol messages
"
change to
"that the WS-HumanTask Parent MUST use to send all protocol
messages"
Line 2001: "The parent application reacts to that message by sending "
change to
"The WS-HumanTask Parent reacts to that message by sending
"
Line 2023: "Only priority and people assignments MUST be overridden for a
notification"
change to
"Only priority and people assignments MAY be overridden for a
notification"
Line 2029: "between the WS-HumaTask Processor and Application.
"
change to
"between the WS-HumaTask Processor and WS-HumanTask
Parent."
Line 2039: "available to the WS-HumanTask processor" change to "available
to the WS-HumanTask Processor"
Line 2040: "registration service MUST be passed by Applicaton" change to
"registration service MUST be passed by WS-HumanTask
Parent"
Line 2127: "the exit protocol message MUST be passed to the subprocess
by"
change to
"the exit protocol message MUST be passed to the task by "
Line 2193: "This policy assertion may be associated" change to "This
policy assertion can be associated "
Line 2197: "the provider of a human task MAY signal whether or not the
corresponding task may communicate with an invoking component via the
WS-HumanTask coordination protocol. " change to "the provider of a human task
can signal whether or not the corresponding task can communicate with an
invoking component via the WS-HumanTask coordination protocol.
"
Line 2204: "This policy assertion specifies that the sender of an input
message MUST include context information for a human task coordination type
passed with the message." change to "This policy assertion specifies that the
WS-HumanTask Parent, in this case sender, MUST include context information for a
human task coordination type passed with the
message."
Line 2223: "In that case it means that the sender of an input message MAY
pass the human task context information with the
message."
change to
"In that case it means that the WS-HumanTask Parent, in this case the
sender, MAY pass the human task context information with the
message."
Section 8
==========
Line 2230: "Passing this callback information from a caller (i.e. a
requesting application) to a human task may override static deployment
information that may have been set. "
change to
"Passing this callback information from a WS-HumanTask Parent (i.e. a
requesting application) to a human task MAY override static deployment
information that may have been set. "
Line 2279: "This element of the EPR MUST be sent by the caller" change to
"This element of the EPR MUST be sent by the WS-HumanTask Parent, the
caller, "
Line 2287: "message from the WS-HumanTask Processor back to the caller"
change to "message from the WS-HumanTask Processor back to the WS-HumanTask
Parent, the caller"
Line 2294:""If this element is specified the <htcp:responseAction>
element MUST NOT be specified by the caller." change to
"If this element is specified the <htcp:responseAction> element
MUST NOT be specified by the WS-HumanTask Parent."
Line 2385: "Note that the [fault endpoint] property is not used " change to "Note that the [fault endpoint] property MUST NOT be used "
Ivana
Trickovic
Standards Architect
SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf, Germany
T +49 6227
7-63228
F
+49 6227 78-33160
M +49 151 57118422
mailto:ivana.trickovic@sap.com
www.sap.com
Sitz der
Gesellschaft/Registered Office: Walldorf, Germany
Vorstand/SAP Executive Board:
Henning Kagermann (Sprecher/Co-CEO), Léo Apotheker (Sprecher/Co-CEO), Werner
Brandt, Claus Heinrich, Gerhard Oswald, John Schwarz, Peter
Zencke
Vorsitzender des
Aufsichtsrats/Chairperson of the SAP Supervisory Board: Hasso Plattner
Registergericht/Commercial Register Mannheim No HRB
350269
Diese E-Mail kann Betriebs- oder Geschäftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtümlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielfältigung oder Weitergabe der E-Mail ausdrücklich untersagt.
Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank.
This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]