ebBP 5/23/2005: Comment re: Editorial Corrections (Abela wd-2-0-1-05)

[Monica J Martin <Monica.Martin@Sun.COM>]

Editorial corrections received after vote by Jesmond Abela. Two other 
requests were made and are being addressed separately (implementation 
guide and schema locations - latter being worked with OASIS, 
wd-2-0-1-06). Comments welcome and appreciated. Thanks.

-----------------------------------
Section 3.4
Change from:
Business Two or more business partners participate in the Business 
Collaboration through roles. The roles always exchange messages in the 
context of Business Transactions.

Change to:
Two or more business partners participate in the Business Collaboration 
through roles. The roles always exchange messages in the context of 
Business Transactions.

In Appendix B:Sample XML Business Signals (typos)

Receipt Acknowledgement
Change from

<?xml version="1.0" encoding="UTF-8"?>
<bpssignal:ReceiptAcknowledgment 
xmlns:bpssignal="http://www.ebxml.org/BusinessProcess/BPSS_SIGNALS"; 
xmlns:ds="http://www.w3.org/2000/09/xmldsig#"; 
xmlns:xsd="http://www.w3.org/2001/XMLSchema-instance"; 
xmlns:xlink="http://www.w3.org/1999/xlink";....

Change to:
<?xml version="1.0" encoding="UTF-8"?>
<bpssignal:ReceiptAcknowledgement 
xmlns:bpssignal="http://www.ebxml.org/BusinessProcess/BPSS_SIGNALS"; 
xmlns:ds="http://www.w3.org/2000/09/xmldsig#"; 
xmlns:xsd="http://www.w3.org/2001/XMLSchema-instance"; 
xmlns:xlink="http://www.w3.org/1999/xlink";

Acceptance Acknowledgement
Change from:

<?xml version="1.0" encoding="UTF-8"?>
<bpssignal:AcceptanceAcknowledgment 
xmlns:bpssignal="http://www.ebxml.org/BusinessProcess/BPSS_SIGNALS";...
</bpssignal:AcceptanceAcknowledgment>

Change to:

<?xml version="1.0" encoding="UTF-8"?>
<bpssignal:AcceptanceAcknowledgement 
xmlns:bpssignal="http://www.ebxml.org/BusinessProcess/BPSS_SIGNALS";...
</bpssignal:AcceptanceAcknowledgement>


Section 3.4.9.3.2
Change from:
For instance, a Purchase Order could not be considered in the “sent” 
state, unless the other party had sent the corresponding Acceptance 
Acknowledgment.

Change to:
For instance, a Purchase Order could not be considered in the “sent” 
state, unless the other party had sent the corresponding Acceptance 
Acknowledgement.

Signal schema
Change from:
<xsd:complexType name="SignalIdentificationInformation">
<xsd:annotation>
<xsd:documentation>
<xsd:documentation>This defines the content structure for identiying 
various parameters pertaining to the business
signal. "OriginalMessageIdentifier" captures the value of the transport 
message identifier for original message to which this business signal
is being sent. If business message has an identifier, that can be 
captured by the "OriginalDocumentIdentifier" attribute.
"OriginalMessageDateTime" is the time when the original message was 
sent. "ThisMessageDateTime" is the time when this signal
message is being sent. The following optional elements are there to 
provide access to information that can be used by
processing logic outside the business process engine. One example of 
this could be a monitoring application which can use
this information to provide status of a collaboration. "FromPartyInfo" 
describes the party id that is sending the signal
message. "ToPartyInfo" describes the party id that is being sent the 
signal message. The roles described below are based
on the implicit relationship between the partner sending the signal 
message and the partner who sent the original message
to which this particular signal is being sent. The role relationship 
between partner sending the business message and the
partner receiving it is captured in the BPSS document. "FromRole" 
captures the role being played by the party that is
sending the signal message. "ToRole" captures the role played by the 
party that is being sent the signal message.
"ProcessSpecificationInfo" type descibes the BPSS information which 
defines the runtime collaborations for which this
signal is being sent "CollaborationIdentifier" is the unique identifer 
that associates the signal with a particular
collaboration. This could come from the business message itself or in 
case of ebXML MSH, could be the messaging level
header "ConversationId" "BusinessActivityIdentifier" identifies the 
business requesting or responding activity to which
this signal is being sent. This would identify the "BusinessAction" from 
the BPSS document and could be implemented using
the "name" attribute on either the RequestingBusinessActivity or the 
RespondingBusinessActivity.</xsd:documentation>
</xsd:annotation>

Change to:
<xsd:complexType name="SignalIdentificationInformation">
<xsd:annotation>
<xsd:documentation>This defines the content structure for identiying 
various parameters pertaining to the business
signal. "OriginalMessageIdentifier" captures the value of the transport 
message identifier for original message to which this business signal
is being sent. If business message has an identifier, that can be 
captured by the "OriginalDocumentIdentifier" attribute.
"OriginalMessageDateTime" is the time when the original message was 
sent. "ThisMessageDateTime" is the time when this signal
message is being sent. The following optional elements are there to 
provide access to information that can be used by
processing logic outside the business process engine. One example of 
this could be a monitoring application which can use
this information to provide status of a collaboration. "FromPartyInfo" 
describes the party id that is sending the signal
message. "ToPartyInfo" describes the party id that is being sent the 
signal message. The roles described below are based
on the implicit relationship between the partner sending the signal 
message and the partner who sent the original message
to which this particular signal is being sent. The role relationship 
between partner sending the business message and the
partner receiving it is captured in the BPSS document. "FromRole" 
captures the role being played by the party that is
sending the signal message. "ToRole" captures the role played by the 
party that is being sent the signal message.
"ProcessSpecificationInfo" type descibes the BPSS information which 
defines the runtime collaborations for which this
signal is being sent "CollaborationIdentifier" is the unique identifer 
that associates the signal with a particular
collaboration. This could come from the business message itself or in 
case of ebXML MSH, could be the messaging level
header "ConversationId" "BusinessActivityIdentifier" identifies the 
business requesting or responding activity to which
this signal is being sent. This would identify the "BusinessAction" from 
the BPSS document and could be implemented using
the "name" attribute on either the RequestingBusinessActivity or the 
RespondingBusinessActivity.</xsd:documentation>
</xsd:annotation>