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

 


Help: OASIS Mailing Lists Help | MarkMail Help

bpel4people-editors message

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


Subject: Re: [bpel4people-editors] BP-16: Comments on B4P


Hi Ivana,

Thanks for the review, i will update B4P tomorrow and send a note once I'm done.

Best Regards,
  Ralf

On Dec 17, 2008, at 4:22 PM, Trickovic, Ivana wrote:

Hi all,
Please find below my comments on the B4P specifiction and the proposed changes.
Kind regards,
Ivana


Line 226:
"However, in a situation where those elements or other text within this document contradict the separate B4P/HT, WSDL or schema files, it is those files that have precedence and not this document."

change to
"However, in a situation where those elements or other text within this document contradict the separate BPEL4People, WS-HumanTask, WSDL or schema files, it is those files that have precedence and not this document."

Line 377:
"Compliant BPEL4People Processor implementations MUST ensure that at runtime at least one person is associated with this role."

change to
"A BPEL4People Definition MAY define assignment for this generic human role. Compliant BPEL4People Processor MUST ensure that at runtime at least one person is associated with this role."

Line 383:
"Compliant BPEL4People Processor implementations MUST ensure that at runtime at least one person is associated with this role"

change to
"A BPEL4People Definition MAY define assignment for this generic human role. Compliant BPEL4People Processor MUST ensure that at runtime at least one person is associated with this role."

Line 388:
: "Compliant BPEL4People Processor implementations MUST ensure that at runtime at least one person is associated with this role"

change to
"A BPEL4People Definition MAY define assignment for this generic human role. Compliant BPEL4People Processor MUST ensure that at runtime at least one person is associated with this role."

Line 457:
"BPEL4People Definition <assign> activity (see [WS-BPEL 2.0] section 8.4 for more details) MAY be used for manipulating values of logical people group "

change to
"BPEL4People Definition MAY use the <assign> activity (see [WS-BPEL 2.0] section 8.4 for more details) to manipulate values of logical people group"

Line 732:
"there exists be a 1:1 relationship "
change to
"there exists a 1:1 relationship"

Line 841:
"variables of the BPEL4People Definition"
I believe we do not have to refer to BPEL4People Definition here. Remove "of the BPEL4People Definition"

Line 845:
"used to refer to a notification enclosed in the BPEL4People process"
change to
"used to refer to a notification enclosed in the BPEL4People Definition"

Line 915:
"of the human task to the WS-HT implementation hosting the human task. "
change to
"of the human task to the WS-HumanTask Processor hosting the human task. "

Line 935:
"If the human task experiences a non-recoverable error, the WS-HumanTask compliant implementation will signal that to the BPEL4People compliant implementation and an b4p:nonRecoverableError fault is raised in the parent process. "

change to

"If the human task experiences a non-recoverable error, the WS-HumanTask Processor will signal that to the BPEL4People Processor and an b4p:nonRecoverableError fault is raised in the parent process. "








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]